Thought posting netconf traceoptions might help solving this issue, allthough everything seems to be alright.
Nov 30 10:35:43 [18521] Incoming: <rpc><close-session/></rpc>]]>]]>
Nov 30 10:35:43 [18521] Outgoing: <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos="http://xml.juniper.net/junos/12.3R8/junos">
Nov 30 10:35:43 [18521] Outgoing: <ok/>
Nov 30 10:35:43 [18521] Outgoing: </rpc-reply>
Nov 30 10:35:43 [18521] Outgoing: ]]>]]>
Nov 30 10:35:43 [18521] Outgoing: <!-- session end at 2015-11-30 10:35:43 UTC -->
Nov 30 10:35:51 Started tracing session: 18526
Nov 30 10:35:51 [18526] Incoming: <hello>
<capabilities>
<capability>urn:ietf:params:xml:ns:netconf:base:1.0</capability>
<capability>urn:ietf:params:xml:ns:netconf:base:1.0#candidate</capability>
<capability>urn:ietf:params:xml:ns:netconf:base:1.0#confirmed-commit</capability>
<capability>urn:ietf:params:xml:ns:netconf:base:1.0#validate</capability>
<capability>urn:ietf:params:xml:ns:netconf:base:1.0#url?protocol=http,ftp,file</capability>
</capabilities>
</hello>
]]>]]>
Nov 30 10:35:51 [18526] Incoming:
<rpc><edit-config><target><candidate/></target><default-operation>merge</default-operation><config><configuration><system><services><ftp></ftp></services></system></configuration></config></edit-config></rpc>]]>]]>
Nov 30 10:35:51 [18526] Outgoing: <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos="http://xml.juniper.net/junos/12.3R8/junos">
Nov 30 10:35:51 [18526] Outgoing: <ok/>
Nov 30 10:35:51 [18526] Outgoing: </rpc-reply>
Nov 30 10:35:51 [18526] Outgoing: ]]>]]>
Nov 30 10:35:51 [18526] Incoming: <rpc><close-session/></rpc>]]>]]>
Nov 30 10:35:51 [18526] Outgoing: <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos="http://xml.juniper.net/junos/12.3R8/junos">
Nov 30 10:35:51 [18526] Outgoing: <ok/>
Nov 30 10:35:51 [18526] Outgoing: </rpc-reply>
Nov 30 10:35:51 [18526] Outgoing: ]]>]]>
Nov 30 10:35:51 [18526] Outgoing: <!-- session end at 2015-11-30 10:35:51 UTC -->