[jbossws-users] [JBossWS] - Re: Problems with Jboss and Sun's 1.6 JDK

[pedro_sf18]

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

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002150#4002150

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002150