RMMessageProcessorIdentifier throws NullPointerException when processing an
empty SOAP envelope
-----------------------------------------------------------------------------------------------
Key: SAND-11
URL: https://issues.apache.org/jira/browse/SAND-11
Project: Sandesha
Issue Type: Bug
Environment: Windows XP
Axis 1.4
Sandesha 1.0
Reporter: Akitoshi Yoshida
Assigned To: Davanum Srinivas
This problem occurs, when the response message to the TerminateSequence is not
HTTP202 but
HTTP200 with an empty SOAP envelope. In this case, RMMessageProcessorIdentifier
tries to find the Sequence object and reading its value, because the sequence
object is null, resulting in a NullPointerException.
It would be better to check the existance of this object to avoid a NPE.
The following change prevents a NPE to be thrown.
org.apache.sandesha.server.RMMessageProcessorIdentifier#getMessageProcessor
53c53
< rmHeaders.getSequence().getMessageNumber() != null) {
---
> (rmHeaders.getSequence() != null &&
> rmHeaders.getSequence().getMessageNumber() != null)) {
58c58
< rmHeaders.getSequence().getMessageNumber() != null) {
---
> (rmHeaders.getSequence() != null &&
> rmHeaders.getSequence().getMessageNumber() != null)) {
--
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]
