13 Replies Latest reply on Apr 17, 2009 5:16 AM by Vladimir Bezugliy

    Problems with Jboss and Sun's 1.6 JDK

    pedro salgado Newbie

      Hello!

      I'm using Jboss 4.0.4GA to deploy a SessionBean-based webservice.

      When I use 1.5 JDK to run JBoss there's no problem and the webservice and it's clients run smoothly, the problem arises when Jboss is started with Sun's 1.6 (6.0) JDK, then this exception is thrown every time a client tries to consume the service:

      14:24:07,046 ERROR [SOAPFaultExceptionHelper] SOAP request exception
      java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
      at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:424)
      at org.jboss.ws.soap.SOAPMessageImpl.(SOAPMessageImpl.java:65)
      at org.jboss.ws.soap.MessageFactoryImpl.createMessageInternal(MessageFactoryImpl.java:209)
      at org.jboss.ws.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:142)
      at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:190)
      at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:355)
      at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:115)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
      at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:76)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
      at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
      at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
      at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
      at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
      at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
      at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
      at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
      at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
      at java.lang.Thread.run(Thread.java:619)

      Seems to me that Jboss has some kind of incompatibility with sun's 1.6 implementation.

      Is this any known error?

      thanks!

        • 1. Re: Problems with Jboss and Sun's 1.6 JDK
          Thomas Diesler Master

          Thats, because the jaxrpc API is part of the JDK. Make sure javax.xml.soap.SOAPMessage is pulled from jboss-jaxrpc.jar

          You can use system properties. The endorsed mechanism should work as well.

          • 2. Re: Problems with Jboss and Sun's 1.6 JDK
            David Win Newbie

            Thomas,

            with regards to changing out the jax-rpc.jar to use JBoss' implementation, would you say its safe to use 1.6 to run the latest JBoss 4.x AS and JBossWS (JAXWS)?

            • 3. Re: Problems with Jboss and Sun's 1.6 JDK
              pedro salgado Newbie

              Hello!

              Thanks for your fast answer, but i'm already using the endorsed mechanism and I'm notifying the virtual machine where jboss' endorsed jars are:

              java -Djava.endorsed.dirs=C:\...\jboss-4.0.5.GA\lib\endorsed -Djavax.xml.rpc.ServiceFactory=org.jboss.ws.jaxrpc.ServiceFactoryImpl -cp build;lib\jboss-saaj.jar;lib\jboss-backport-concurrent.jar;lib\jboss-xml-binding.jar;lib\jbossretro-rt.jar;lib\activation.jar;lib\concurrent.jar;lib\wsdl4j.jar;lib\jboss-jaxrpc.jar;lib\jbossws14-client.jar;lib\jboss-common-client.jar;...

              • 4. Re: Problems with Jboss and Sun's 1.6 JDK
                Thomas Diesler Master

                I have not tried jdk1.6 with jbossws. I know however that there are several issues with running jbossas with jdk1.6

                Make sure jboss-jaxrpc.jar actually is in lib/endorsed

                • 5. Re: Problems with Jboss and Sun's 1.6 JDK
                  pedro salgado Newbie

                  OK, I wasn't including jboss' jax-rpc implementation as a jdk-endorsed jar (I thought Jboss' implementation should be compatible with Sun's included one).

                  But unfortunately when I include jboss-jaxrpc.jar in the endorsed lib claims that org.jboss.logging.Logger is not found and when that class is included in classpath to fullfill the requirement a long list of messages are thrown (this only means that I'm loosing log, not funtionality), but the problem (the exception at webservice invocation) remains unsolved:

                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@1f934ad, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@1d05c81, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@26d4f1, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@82701e, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@8fce95, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@143c8b3, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@6e70c7, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@a6aeed, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@126804e, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@64f6cd, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@47393f, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@1ff7a1e, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@763f5d, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@186768e, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@d19bc8, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@1e8a1f6, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@1e152c5, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@1319c, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@6025e7, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@15b0afd, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@2e7820, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@14c1103, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@f11404, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@1592174, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@a352a5, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@704baa, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@77a7f9, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@c7b00c, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@5329c5, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@1db699b, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@10f11b8, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@18f6235, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@1c282a1, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@10e3293, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@11a64ed, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@1c9a690, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@13ad085, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@4fce71, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@698403, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@15a0305, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@7c4c51, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@765a16, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@148bd3, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@12bb7e0, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@12d15a9, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@1238bd2, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@a761fe, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@4f80d6, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@193722c, cause: org/apache/log4j/LogManager
                  Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@12cc95d, cause: org/apache/log4j/LogManager


                  Seems that JBoss is having serious issues with JDK 1.6, so going back to JDK 1.5 where all runs OK.

                  I would offer my assistance to debug this issues if asked. I can provide several use cases that reproduce this kind of problems (all related to jbossws).

                  Greets,
                  Pedro

                  • 6. Re: Problems with Jboss and Sun's 1.6 JDK
                    akira inoue Newbie

                    Can you share how to implement web service client stub as an EJB, generated by sun jwsdp (wscompile) in jboss?

                    My EJB is calling web service to 3rd party provider. The client stub is generated through Sun's jwsdp. However I encountered the following exception:
                    java.lang.ClassCastException: org.jboss.ws.soap.SOAPMessageImpl
                    at com.sun.xml.rpc.client.StubBase._postSendingHook(StubBase.java:231)
                    at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:324)

                    I added the following jar from jwsdp to the lib dir:
                    FastInfoset.jar
                    jaxrpc-impl.jar
                    jaxrpc-spi.jar
                    jsr173_api.jar
                    saaj-impl.jar

                    I am running jboss-4.0.5.GA.

                    How can I resolve the problem? Can the stub generated by jwsdp be used in JBoss or any application other the Sun?

                    • 7. Re: Problems with Jboss and Sun's 1.6 JDK
                      Stephan Fudeus Newbie

                       

                      "thomas.diesler@jboss.com" wrote:
                      Thats, because the jaxrpc API is part of the JDK. Make sure javax.xml.soap.SOAPMessage is pulled from jboss-jaxrpc.jar



                      Actually javax.xml.soap.SOAPMessage is provided in jboss-saaj.jar.

                      Nevertheless - issues remain the same with putting jboss-saaj to endorsed, since saaj references org.jboss.logging ...

                      • 8. Re: Problems with Jboss and Sun's 1.6 JDK
                        Mark Berner Newbie

                        Nothing helps :(

                        After adding jboss-jaxrpc.jar or/and jboss-saaj.jar into endorsed dir it fails on class not found org.jboss.logger.Logger

                        Revision of JBoss source file shows that javax.xml.soap classes refer to JBoss proprietary classes that unacceptable.

                        I've found a vandal workaround removing javax/xml/soap package from rt.jar.

                        I believe that JBoss team will solve this problem.

                        • 9. Re: Problems with Jboss and Sun's 1.6 JDK
                          dibin d Newbie

                          I got the same problem with jboss.4.0.4.GA and jdk 1.5.

                          I got around the problem by deleting saaj-api.jar and saaj-imp.jar from JBOSS_HOME/lib directory and putting jboss-saaj.jar in JBOSS_HOME/lib directory.


                          • 12. Re: Problems with Jboss and Sun's 1.6 JDK
                            Maxi Ng Newbie

                            web service using JAX-WS 2.0 run on JBoss AS 4.2.1
                            This method works!
                            thank you.

                            • 13. Re: Problems with Jboss and Sun's 1.6 JDK
                              Vladimir Bezugliy Novice

                              I had the same problem with jboss-5.0.1.GA and jdk1.5.0_11.
                              And I just copied jboss-saaj.jar from jbossws-native-2.0.2.GA(http://www.jboss.org/jbossws/downloads/) package and now all is ok.