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 "Carsten Lohmann (JIRA)" <ji...@apache.org> on 2008/08/20 14:36:47 UTC
[jira] Issue Comment Edited: (AXIS2-3276) Null pointer exception
while doing wsdl get using useOriginalWsdl option. Reason : underlying
definitiion is not threadsafe
[ https://issues.apache.org/jira/browse/AXIS2-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623978#action_12623978 ]
carstensis edited comment on AXIS2-3276 at 8/20/08 5:35 AM:
-----------------------------------------------------------------
As a further note:
We experienced this problem with Axis2 (*) running under JBoss.
After the exception shown above, we got the following exception:
java.lang.StackOverflowError
at java.util.Hashtable.get(Hashtable.java:336)
at com.ibm.wsdl.util.ObjectRegistry.lookup(ObjectRegistry.java:43)
at com.ibm.wsdl.util.ObjectRegistry.lookup(ObjectRegistry.java:46)
at com.ibm.wsdl.util.ObjectRegistry.lookup(ObjectRegistry.java:46)
at com.ibm.wsdl.util.ObjectRegistry.lookup(ObjectRegistry.java:46)
...
It occured everytime the WSDL was accessed through the ListingAgent.
It seems like the javax.wsdl.Definition instance is permanently corrupted by these thread issues.
-
* We use Axis2 1.1.1, but from looking at the code, I guess this problem still exists in the current version
was (Author: carstensis):
As a further note:
We experienced this problem with Axis2 (*) running under JBoss.
After the exception shown above, we got the following exception:
java.lang.StackOverflowError
at java.util.Hashtable.get(Hashtable.java:336)
at com.ibm.wsdl.util.ObjectRegistry.lookup(ObjectRegistry.java:43)
at com.ibm.wsdl.util.ObjectRegistry.lookup(ObjectRegistry.java:46)
at com.ibm.wsdl.util.ObjectRegistry.lookup(ObjectRegistry.java:46)
at com.ibm.wsdl.util.ObjectRegistry.lookup(ObjectRegistry.java:46)
...
It occured everytime the WSDL was accessed through the ListingAgent.
It seems like the javax.wsdl.Definition is permanently corrupted by these thread issues.
-
* We use Axis2 1.1.1, but from looking at the code, I guess this problem still exists in the current version
> Null pointer exception while doing wsdl get using useOriginalWsdl option. Reason : underlying definitiion is not threadsafe
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-3276
> URL: https://issues.apache.org/jira/browse/AXIS2-3276
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: wsdl
> Affects Versions: 1.2
> Environment: HP UX
> Reporter: Haneef Ali
> Assignee: Deepal Jayasinghe
> Priority: Critical
>
> I'm seeing Nullpointer exception during wsdl fetch. My webservice is created using "useOriginalWSDL=true" option.
> This happens only during concurrent access. It can be easily reproduced by creating a JMeter test for http get with 5 thread. BTW I'm using Axis 1.2
> From google search the reason for this seems to be
> " This is because the WSDL handling system reuses javax.wsdl.Definition objects across threads, which are not thread safe, because they internally use DOM elements."
> References
>
> http://jira.jboss.com/jira/browse/JBWS-419;jsessionid=AA4270C1E4896751CF
> 2440D7C6696706
> http://www.mail-archive.com/j-dev@xerces.apache.org/msg01292.html
> java.lang.NullPointerException
> at org.apache.xerces.dom.ParentNode.nodeListItem(Unknown Source)
> at org.apache.xerces.dom.ParentNode.item(Unknown Source)
> at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
> at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
> at com.ibm.wsdl.util.xml.DOM2Writer.serializeAsXML(Unknown
> Source)
> at
> com.ibm.wsdl.extensions.schema.SchemaSerializer.marshall(Unknown Source)
> at
> com.ibm.wsdl.xml.WSDLWriterImpl.printExtensibilityElements(Unknown
> Source)
> at com.ibm.wsdl.xml.WSDLWriterImpl.printTypes(Unknown Source)
> at com.ibm.wsdl.xml.WSDLWriterImpl.printDefinition(Unknown
> Source)
> at com.ibm.wsdl.xml.WSDLWriterImpl.writeWSDL(Unknown Source)
> at com.ibm.wsdl.xml.WSDLWriterImpl.writeWSDL(Unknown Source)
> at
> org.apache.axis2.description.AxisService.printWSDL(AxisService.java:848)
> at
> org.apache.axis2.transport.http.ListingAgent.processListService(ListingA
> gent.java:221)
> at
> org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:225)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
> at
> weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(St
> ubSecurityHelper.java:223)
> at
> weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityH
> elper.java:125)
> at
> weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:2
> 83)
> at
> weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:1
> 75)
> at
> weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r
> un(WebAppServletContext.java:3245)
> at
> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
> bject.java:321)
> at
> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
> )
> at
> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
> letContext.java:2003)
> at
> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
> ext.java:1909)
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org