setLastRpcReply method fails to parse data

Open
#68 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java
Domain
backend, networking

Research direction

Start by locating the setLastRpcReply method and reproduce the failure using an rpc-reply containing multiple XML data elements across multiple sessions. Check how the default NETCONF session handles this response; done means the reply parses successfully without the reported Invalid RPC reply exception.

Written by the indexing model from the issue text.

Description

I have a question asking how to perform rpc over multiple sessions when connecting to netconf via juniper netconf client 2.1.1.7.

At present, there is a problem that multiple RPCS fail to parse data through the default netconf session. It is found that an rpc-reply contains multiple xml data. The setLastRpcReply method fails to parse data. Such as this (net.juniper.netconf.Net confException: Invalid < RPC reply - > message from server: < RPC - reply XMLNS = "urn: ietf: params: XML: ns: netconf: base: 1.0..." )

Dominant language
Java
Stars
90
Forks
64
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Juniper/netconf-java

All issues in Juniper/netconf-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.