[
https://issues.apache.org/jira/browse/AXIS2-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306534#comment-15306534
]
Rajesh commented on AXIS2-5775:
-------------------------------
During 6th request service cleanup is making the axisconfiguration to null
,seventh is failing with null pointer exception.
Above 6th and 7th requests are just example. Sometimes it can withstand from 10
to 15 requests.
Error:
null ponter- at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:423)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
> upgrading from axis2 1.4 to 1.6.4
> ---------------------------------
>
> Key: AXIS2-5775
> URL: https://issues.apache.org/jira/browse/AXIS2-5775
> Project: Axis2
> Issue Type: Test
> Components: kernel
> Affects Versions: 1.6.4
> Reporter: Rajesh
>
> Hi All,
> This is related to existing JIRA AXIS2-5774.
> We are upgrading from axis2 1.4 to 1.6.4. We upgraded successfully and got
> response from provider with execute() method.
> After 4 to 8 request , the service is throwing below error intemittently.
> Error:
> =======================
> null
> org.apache.axis2.context.AbstractContext.needPropertyDifferences(AbstractContext.java:239)
> org.apache.axis2.context.AbstractContext.setProperty(AbstractContext.java:202)
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:237)
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> java.lang.reflect.Method.invoke(Method.java:613)
> com.tibco.amf.platform.runtime.componentframework.internal.proxies.operation.OperationHandler.invokeMethodWithThreadContext(OperationHandler.java:486)
> com.tibco.amf.platform.runtime.componentframework.internal.proxies.operation.MultiThreadedASyncToSyncOperationHandler$ASyncToSyncInvocationHandler.run(MultiThreadedASyncToSyncOperationHandler.java:203)
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121)
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
> java.lang.Thread.run(Thread.java:779)
> =========================
> So we added few logging to Kernel 1.6.4 and found that after few request
> Cleanup() method in the serviceclient is cleaning the AxisConfiguration,hence
> the following request getting failed with Null error.
> Also we see changes in AxisCOnfiguration in 1.4 and 1.6.4 in Cleanup method().
> Is this the normal behaviour in axis2 1.6.4?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
