You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Ben Reif (JIRA)" <ji...@apache.org> on 2008/12/11 17:47:44 UTC
[jira] Created: (AXIS2-4173) NullPointerException from
ServiceClient.fireAndForget()
NullPointerException from ServiceClient.fireAndForget()
-------------------------------------------------------
Key: AXIS2-4173
URL: https://issues.apache.org/jira/browse/AXIS2-4173
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: client-api
Affects Versions: 1.4, 1.4.1, 1.5
Environment: Windows
Reporter: Ben Reif
When you call ServiceClient.fireAndForget(QName, OMElement), it creates an OutInAxisOperationClient but the AxisCallback is never set. The call eventually goes into OutInAxisOperationClient.executeImpl(false) and then calls NonBlockingInvocationWorker.run().
You get a NullPointerException on line 454 or 462 because there is no Null check before it calls
axisCallback.onError(fault);
or
axisCallback.onMessage(response);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AXIS2-4173) NullPointerException from
ServiceClient.fireAndForget()
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe resolved AXIS2-4173.
--------------------------------------
Resolution: Fixed
> NullPointerException from ServiceClient.fireAndForget()
> -------------------------------------------------------
>
> Key: AXIS2-4173
> URL: https://issues.apache.org/jira/browse/AXIS2-4173
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: client-api
> Affects Versions: 1.4.1, 1.4
> Environment: Windows
> Reporter: Ben Reif
> Original Estimate: 0.17h
> Remaining Estimate: 0.17h
>
> When you call ServiceClient.fireAndForget(QName, OMElement), it creates an OutInAxisOperationClient but the AxisCallback is never set. The call eventually goes into OutInAxisOperationClient.executeImpl(false) and then calls NonBlockingInvocationWorker.run().
> You get a NullPointerException on line 454 or 462 because there is no Null check before it calls
> axisCallback.onError(fault);
> or
> axisCallback.onMessage(response);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2-4173) NullPointerException from
ServiceClient.fireAndForget()
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor updated AXIS2-4173:
-------------------------------
Affects Version/s: (was: 1.5)
> NullPointerException from ServiceClient.fireAndForget()
> -------------------------------------------------------
>
> Key: AXIS2-4173
> URL: https://issues.apache.org/jira/browse/AXIS2-4173
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: client-api
> Affects Versions: 1.4.1, 1.4
> Environment: Windows
> Reporter: Ben Reif
> Original Estimate: 0.17h
> Remaining Estimate: 0.17h
>
> When you call ServiceClient.fireAndForget(QName, OMElement), it creates an OutInAxisOperationClient but the AxisCallback is never set. The call eventually goes into OutInAxisOperationClient.executeImpl(false) and then calls NonBlockingInvocationWorker.run().
> You get a NullPointerException on line 454 or 462 because there is no Null check before it calls
> axisCallback.onError(fault);
> or
> axisCallback.onMessage(response);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-4173) NullPointerException from
ServiceClient.fireAndForget()
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655705#action_12655705 ]
Jarek Gawor commented on AXIS2-4173:
------------------------------------
This issue is already fixed in trunk.
> NullPointerException from ServiceClient.fireAndForget()
> -------------------------------------------------------
>
> Key: AXIS2-4173
> URL: https://issues.apache.org/jira/browse/AXIS2-4173
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: client-api
> Affects Versions: 1.4.1, 1.4
> Environment: Windows
> Reporter: Ben Reif
> Original Estimate: 0.17h
> Remaining Estimate: 0.17h
>
> When you call ServiceClient.fireAndForget(QName, OMElement), it creates an OutInAxisOperationClient but the AxisCallback is never set. The call eventually goes into OutInAxisOperationClient.executeImpl(false) and then calls NonBlockingInvocationWorker.run().
> You get a NullPointerException on line 454 or 462 because there is no Null check before it calls
> axisCallback.onError(fault);
> or
> axisCallback.onMessage(response);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.