[JBoss JIRA] Created: (JBWS-2681) Concurrency issues where multiple threads create Port using Service Simultaneously
by Darran Lofthouse (JIRA)
Concurrency issues where multiple threads create Port using Service Simultaneously
----------------------------------------------------------------------------------
Key: JBWS-2681
URL: https://jira.jboss.org/jira/browse/JBWS-2681
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.2
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.2.0
Where multiple threads attempt to create a port or call an endpoint from a newly created Service one of a number of errors is reported.
java.lang.NullPointerException
at org.jboss.ws.extensions.xop.jaxws.ReflectiveAttachmentRefScanner.isJDKType(ReflectiveAttachmentRefScanner.java:262)
at org.jboss.ws.extensions.xop.jaxws.ReflectiveAttachmentRefScanner.scanBean(ReflectiveAttachmentRefScanner.java:78)
at org.jboss.ws.metadata.umdm.ParameterMetaData.initializeAttachmentParameter(ParameterMetaData.java:500)
at org.jboss.ws.metadata.umdm.ParameterMetaData.eagerInitialize(ParameterMetaData.java:485)
at org.jboss.ws.metadata.umdm.OperationMetaData.eagerInitialize(OperationMetaData.java:465)
at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:526)
at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:510)
at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:500)
at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:308)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:262)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:193)
at javax.xml.ws.Service.getPort(Service.java:116)
java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449)
at java.util.AbstractList$Itr.next(AbstractList.java:420)
at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:524)
at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:510)
at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:500)
at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:308)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:262)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:193)
at javax.xml.ws.Service.getPort(Service.java:116)
java.lang.IllegalStateException: Cannot synchronize to any of these methods:
at org.jboss.ws.metadata.umdm.OperationMetaData.eagerInitialize(OperationMetaData.java:492)
at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:526)
at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:510)
at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:500)
at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:308)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:262)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:193)
at javax.xml.ws.Service.getPort(Service.java:116)
java.lang.IllegalStateException: Cannot synchronize to any of these methods:
public abstract org.jboss.support.ws.phonebook.TelephoneNumber org.jboss.support.ws.phonebook.PhoneBook.lookup(org.jboss.support.ws.phonebook.Person)
OperationMetaData:
qname={http://www.jboss.org/support/phonebook}lookup
javaName=lookup
style=document/literal/WRAPPED
oneWay=false
soapAction=
at org.jboss.ws.metadata.umdm.OperationMetaData.eagerInitialize(OperationMetaData.java:492)
at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:526)
at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:510)
at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:500)
at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:308)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:262)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:193)
at javax.xml.ws.Service.getPort(Service.java:116)
javax.xml.ws.WebServiceException: java.lang.IllegalStateException: Cannot find property: javax.xml.ws.handler.message.outbound
at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:307)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:245)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
at $Proxy15.lookup(Unknown Source)
at org.jboss.support.ws.phonebook.ThreadedCallingClient$Caller.run(ThreadedCallingClient.java:51)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalStateException: Cannot find property: javax.xml.ws.handler.message.outbound
at org.jboss.ws.core.jaxws.handler.MessageContextJAXWS.processPivot(MessageContextJAXWS.java:110)
at org.jboss.ws.core.jaxws.client.ClientImpl.processPivot(ClientImpl.java:266)
at org.jboss.ws.core.CommonClient.processPivotInternal(CommonClient.java:467)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:395)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:233)
javax.xml.ws.soap.SOAPFaultException: Request struct cannot be null
at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:75)
at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109)
at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:553)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:371)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:233)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
at $Proxy15.lookup(Unknown Source)
javax.xml.ws.soap.SOAPFaultException: java.lang.NullPointerException
at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:75)
at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109)
at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:553)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:371)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:233)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
at $Proxy15.lookup(Unknown Source)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
- 1
- 1
[JBoss JIRA] Created: (JBWS-2699) BackwardCompatibleURLPatternDeploymentAspect is mangling URLs
by Alessio Soldano (JIRA)
BackwardCompatibleURLPatternDeploymentAspect is mangling URLs
-------------------------------------------------------------
Key: JBWS-2699
URL: https://jira.jboss.org/jira/browse/JBWS-2699
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-cxf, jbossws-metro, jbossws-native
Reporter: Alessio Soldano
Assignee: Richard Opalka
Fix For: jbossws-native-3.2.0, jbossws-cxf-3.2.0, jbossws-metro-3.2.0
Kevin says:
> StringTokenizer st = new StringTokenizer(urlPattern, "/");
> if (st.countTokens() > 1 && urlPattern.startsWith(contextRoot + "/"))
> {
> urlPattern = urlPattern.substring(contextRoot.length());
> }
Yes, this is the part which does the damage.
The contextRoot, in the case I am investigating, is the same as the first part of the urlPattern. This means that the generated WSDL contains the wrong endpoint location, as does the JBossWS console, yet the webservice is still deployed at the right location.
So the webservice is actually deployed at /a/a/b but WSDL and WS console report it at /a/b.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
- 1
- 0
[JBoss JIRA] Created: (JBWS-2698) Calling setPrefix(newPrefix) on any SOAPElement the prefix is not used for marshalling.
by Darran Lofthouse (JIRA)
Calling setPrefix(newPrefix) on any SOAPElement the prefix is not used for marshalling.
---------------------------------------------------------------------------------------
Key: JBWS-2698
URL: https://jira.jboss.org/jira/browse/JBWS-2698
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.2
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.2.0
Calling setPrefix(newPrefix) on any SOAPElement the prefix is not used for marshalling.
This is because the SOAPElementImpl caches the name and does not regenerate the name, when setPrefix is called the cached name should be cleared so it can be re-generated using the new prefix.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
- 1
- 0