SOAPMonitor stops when it receives information about a response that it never
saw a request for.
------------------------------------------------------------------------------------------------
Key: AXIS-2701
URL: https://issues.apache.org/jira/browse/AXIS-2701
Project: Axis
Issue Type: Bug
Affects Versions: 1.4
Environment: 1.5 JVM on firefox on windows, 1.4 AXIS on tomcat on
solaris, but this will happen anywhere.
Reporter: Bill Kuker
Priority: Trivial
There is a minor bug in SOAPMonitor applet. If you start it after a
request has come in, but before the response gets sent back, the
SOAPMonitorHandler sends the response to the applet, which can't find a
request and disconnects, saying "The server communication has been
terminated."
The following function throws a NullPointerException trying to get the
id value. For clarity I've just included the fix in context. The stderr
output is clearly not necessary.
/**
* Find the data for a given id
*/
public SOAPMonitorData findData(Long id) {
SOAPMonitorData soap = null;
for (int row=data.size(); (row > 0) && (soap == null);
row--) {
soap = (SOAPMonitorData) data.elementAt(row-1);
//NEW CODE
if ( soap == null || soap.getId() == null ){
System.err.println("Never saw a request to match
this response.");
return null;
}
//END NEW CODE
if (soap.getId().longValue() != id.longValue()) {
soap = null;
}
}
return soap;
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
