[Persistence, JBoss/CMP, Hibernate, Database] - thin driver ojdbc14.jar, Java 6 (1.6) and -Xss
by mclu
Hi out there!
We are using Jboss 4.x with Oracle 9 and 10.
Because in the Java 5 there are some Bugs/Issues with Threads we are forced to upgrade to Java 6. We are using plain J2EE with EJB 2.0 and mostly 1.1
With Java 6 and MSSQL all works but not with Oracle. We we found the Error...
It has to Do with the VM Parameter -Xss (Setting Stack Size)
At JBoss we are using the Thin Driver and the newest ojdbc14.jar
Configutation DS:
<local-tx-datasource>
<jndi-name>AeosDS</jndi-name>
<connection-url>jdbc:oracle:thin:@NVC0534:1521:test</connection-url>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<min-pool-size>0</min-pool-size>
<max-pool-size>50</max-pool-size>
<security-domain>MyDatabaseRealm</security-domain>
<type-mapping>Oracle9i</type-mapping>
</local-tx-datasource>
When we now start the Server without the -Xss setting all is OK.
When I start up the Server with -Xss64k I get a NoClassDefFoundError ???
Stacktrace:
09:14:16,765 INFO [DbManager] Trying to get connection from datasource with name= java:/AeosDS
09:14:16,906 WARN [JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
java.lang.NoClassDefFoundError: oracle/jdbc/driver/OracleCallableStatement
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:568)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFacto
ry.java:151)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnect
ionPool.java:508)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:207
)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:
534)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:396)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:299)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:448)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionMan
ager2.java:838)
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:102)
at com.nedap.aeos.ejbutil.DbManager.getConnectionOnce(DbManager.java:174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
...
Why the Driver change his behaviour dependend on the Xss setting?
Is there a Bug on Jboss side?
I Also posted this in the Oracle Tech Channel.
With an older Version like the classes12.jar it works!!
Greets
Markus Lutum
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002151#4002151
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002151
19 years, 3 months
[JBossWS] - Re: Problems with Jboss and Sun's 1.6 JDK
by 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@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
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
19 years, 3 months