9 Replies Latest reply on Oct 29, 2013 2:22 PM by bourasom

JBoss 5.0.1.GA, JBossWS 3.0.5, JDK 1.6 - java.lang.Unsupport

afluegge Jul 10, 2009 6:00 AM

Hello!

I'm trying to call a simple web service with following configuration: 5.0.1.GA, JBossWS 3.0.5, JDK 1.6.0_14. Details below.

Callin the service gets the following exception:

11:33:16,163 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
 at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:445)
 at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:82)
 at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:215)
 at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:193)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:455)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
 at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
 at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
 at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
 at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
 at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
 at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
 at java.lang.Thread.run(Thread.java:619)

I suppose that the SOAPMessage class comes from the JDK 1.6 which is incompatible with the one from JBossWS (in jbossws-native-saaj.jar). The jar file is located in the <JBOSS_HOME>/lib/endorsed dir. All suggestions to solve this problem are to copy the jar files to the endorsed dir, but they are already there!

Can anybody help me?

Thanks,
Andreas

This is the source:

package test;

import javax.ejb.Stateless;
import javax.jws.WebMethod;
import javax.jws.WebService;

import org.apache.commons.logging.Log;
import org.jboss.seam.annotations.Logger;

@Stateless
@WebService(name = "testService", serviceName = "testService")
public class TestService implements TestServiceRemote {

 @Logger
 private Log log;

 @WebMethod
 public String testService(String name) {
 String txt = "testService:" + name;

 log.info("testService:" + name);

 return txt;
 }
}

package test;

import javax.ejb.Remote;
import javax.jws.WebMethod;

@Remote
public interface TestServiceRemote {
 @WebMethod
 public String testService(String name);
}

Deployment is no problem, calling the http:.../TestService?wsdl URL gets the following:

<definitions name='testService' targetNamespace='http://test/' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://test/' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
 <types>
 <xs:schema targetNamespace='http://test/' version='1.0' xmlns:tns='http://test/' xmlns:xs='http://www.w3.org/2001/XMLSchema'>
 <xs:element name='testService' type='tns:testService'/>
 <xs:element name='testServiceResponse' type='tns:testServiceResponse'/>
 <xs:complexType name='testService'>
 <xs:sequence>
 <xs:element minOccurs='0' name='arg0' type='xs:string'/>
 </xs:sequence>

 </xs:complexType>
 <xs:complexType name='testServiceResponse'>
 <xs:sequence>
 <xs:element minOccurs='0' name='return' type='xs:string'/>
 </xs:sequence>
 </xs:complexType>
 </xs:schema>
 </types>
 <message name='testService_testServiceResponse'>

 <part element='tns:testServiceResponse' name='testServiceResponse'></part>
 </message>
 <message name='testService_testService'>
 <part element='tns:testService' name='testService'></part>
 </message>
 <portType name='testService'>
 <operation name='testService' parameterOrder='testService'>
 <input message='tns:testService_testService'></input>
 <output message='tns:testService_testServiceResponse'></output>

 </operation>
 </portType>
 <binding name='testServiceBinding' type='tns:testService'>
 <soap:binding style='document' transport='http://schemas.xmlsoap.org/soap/http'/>
 <operation name='testService'>
 <soap:operation soapAction=''/>
 <input>
 <soap:body use='literal'/>
 </input>

 <output>
 <soap:body use='literal'/>
 </output>
 </operation>
 </binding>
 <service name='testService'>
 <port binding='tns:testServiceBinding' name='testServicePort'>
 <soap:address location='http://127.0.0.1:8080/spaceserver-spaceserver/TestService'/>
 </port>

 </service>
</definitions>

1. Re: JBoss 5.0.1.GA, JBossWS 3.0.5, JDK 1.6 - java.lang.Unsup

peterj Jul 10, 2009 11:51 AM (in response to afluegge)

Did you download the JDK6 variant of JBoss AS 5.0.1.GA? It already has the necessary jar files in the endorsed directory to avoid this issue:

lib/endorsed/activation.jar
lib/endorsed/jaxb-api.jar
lib/endorsed/jbossws-native-jaxrpc.jar
lib/endorsed/jbossws-native-jaxws-ext.jar
lib/endorsed/jbossws-native-jaxws.jar
lib/endorsed/jbossws-native-saaj.jar
lib/endorsed/resolver.jar
lib/endorsed/serializer.jar
lib/endorsed/stax-api.jar
lib/endorsed/xalan.jar
lib/endorsed/xercesImpl.jar

A search of "setProperty must be overridden" should yield several posts discussing this. (It it should, if search was not broke - at this time only your post shows up.)
Actions
2. Re: JBoss 5.0.1.GA, JBossWS 3.0.5, JDK 1.6 - java.lang.Unsup

afluegge Jul 13, 2009 4:18 AM (in response to afluegge)

Yes, I'm already using the JDK6 version of JBoss. And in fact, there are no search results concerning this issue. :-(
Actions
3. Re: JBoss 5.0.1.GA, JBossWS 3.0.5, JDK 1.6 - java.lang.Unsup

peterj Jul 13, 2009 11:02 AM (in response to afluegge)

Perhaps a stray jaxws library is being picked up. Try adding -verbose:class to the JAVA_OPTS in the run script. This option causes the JVM to print the location of each class loaded. Look for where the SOAPMessage class gets loaded. By the way, this option generate a lot of output - you better redirect both stdout and stderr to a file.
Actions
4. Re: JBoss 5.0.1.GA, JBossWS 3.0.5, JDK 1.6 - java.lang.Unsup

afluegge Jul 13, 2009 12:35 PM (in response to afluegge)

Thanks for your answer!

I could solve this issue, although it is a strange behaviour. Testing the web service on another system running Windows XP works fine (I'm using Vista!, didn't mind it matters).

The solution under Vista is to copy all JARs from <JBOSS_HOME>/lib endorsed to <JAVA_HOME>/jre/lib/endorsed (I had to create this directory).

I don't know if the OS is the real reason, but now it works!

Thank you very much!
Actions
5. Re: JBoss 5.0.1.GA, JBossWS 3.0.5, JDK 1.6 - java.lang.Unsup

peterj Jul 13, 2009 1:39 PM (in response to afluegge)

I'm using Vista and don't have this problem. Copying the JARs to the JRE's endorsed directory might fix this issue but it could cause you grief with other Java apps. I still think you have some stray jar files that were being picked up by your JVM (you don't have CLASSPATH set, do you?), but -verbose:class will help you locate them.
Actions
6. Re: JBoss 5.0.1.GA, JBossWS 3.0.5, JDK 1.6 - java.lang.Unsup

asoldano Jul 15, 2009 12:20 PM (in response to afluegge)

Thanks Peter for spreading the right directions on this topic.
Actions
7. Re: JBoss 5.0.1.GA, JBossWS 3.0.5, JDK 1.6 - java.lang.Unsup

donboscosamson Aug 8, 2012 12:03 PM (in response to asoldano)

No need to copy to JDK lib. Just make sure you have the following JAR files in your <JBOSS_HOME>/lib/endorsed

jbossws-native-jaxrpc.jar
jbossws-native-jaxws-ext.jar
jbossws-native-jaxws.jar
jbossws-native-saaj.jar
Actions
8. Re: JBoss 5.0.1.GA, JBossWS 3.0.5, JDK 1.6 - java.lang.Unsupport

bourasom Oct 29, 2013 11:28 AM (in response to afluegge)

In my case the SOAPMessage is loaded from the rt.jar

[Loaded javax.xml.soap.SOAPMessage from /usr/share/jdk1.6.0_31/jre/lib/rt.jar]

Is there a way to avoid this?
Actions
9. Re: JBoss 5.0.1.GA, JBossWS 3.0.5, JDK 1.6 - java.lang.Unsupport

bourasom Oct 29, 2013 2:22 PM (in response to afluegge)

Finally, in order to execute my client, I had to set the following jvm opt

-Djava.endorsed.dirs=/path/to/endorsed/jars

In the endorsed dirs contains the jars of jboss endorsed lib:
activation.jar
jaxb-api.jar
jbossws-native-jaxrpc.jar
jbossws-native-jaxws.jar
jbossws-native-jaxws-ext.jar
jbossws-native-saaj.jar
resolver.jar
serializer.jar
stax-api.jar
xalan.jar
xercesImpl.jar
Of course, not all jars are needed.
Finally, there is no more issue with the SOAPMessage
Actions

Go to original post