[
https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889775#action_12889775
]
gerhard presser commented on AXIS2-4755:
----------------------------------------
I think the name does matter!
for example, multiple hashmaps for caching various contextes/axisservicegroups
etc. use the service(group)-name as key, so if there are multiple services with
the same name, IMO, this can't work at all.
in my case i have a shared axis-configuration and multiple parallel invocations
of the same service (but not the same serviceclient-instance)
while(true) {
new Thread(new Runnable() {
ServiceClient client = new ServiceClient(ConfigurationContext, Definition,
QName, String);
try {
client.sendReceive(QName, OMElement);
} finally {
client.cleanup();
}
}).start();
}
having the same servicename causes following NPE:
java.lang.NullPointerException
at
org.apache.axis2.context.ServiceGroupContext.getServiceContext(ServiceGroupContext.java:141)
at
org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:184)
at org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:220)
at com.groiss.test.LoadTester$1.run(LoadTester.java:46)
at java.lang.Thread.run(Unknown Source)
> dynamic serviceclient: axisservice-names are not unique
> -------------------------------------------------------
>
> Key: AXIS2-4755
> URL: https://issues.apache.org/jira/browse/AXIS2-4755
> Project: Axis2
> Issue Type: Bug
> Components: client-api, deployment
> Affects Versions: 1.5.1
> Reporter: gerhard presser
>
> in case of concurrent invocations, this may cause problems, because one
> client cleans up the other-clients context etc.
> both, anonservices and stub-services generate a unique service name; dynamic
> service-clients should do so too.
--
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]
