jboss-embedded-all-beta3.jar in seam's maven repo is JDK6 specific ------------------------------------------------------------------ Key: JBSEAM-3263 URL: https://jira.jboss.org/jira/browse/JBSEAM-3263 Project: Seam Issue Type: Bug Components: Build, Test Harness Affects Versions: 2.1.0.A1, 2.0.3.CR1 Reporter: Jay Balunas Priority: Blocker Fix For: 2.0.3.CR2, 2.1.0.BETA1 The jboss-embedded-all-beta3.jar located in the "org/jboss/seam/embedded/jboss-embedded-all/beta3" repository directory is specific to JDK6. Earlier versions were specific to JDK5, but would execute with JDK6. This change appears to have been made on august 8th and is likely related to JBoss 4.2.3 dependency alignment. First noticed because most hudson builds were skipping a large # of their tests. Builds that do not clear out their repo were not showing this issue because they were still using the older version, and of coarse the JDK6 builds were fine. This issue can be reproduced locally by either cleaning your repo, or pointing it to a new location then executing "ant testall" using JDK5. This may be complicated or related to the jboss 4.2.3 jar upgrade because jboss 4.2.3 is distributed with separate binaries for JDK 5 and JDK 6. This is because at compile time of some of the components JDK version specific code is included, or excluded. From what I can see there is not JDK specific entries in the JBoss 4.2.3 maven repository locations (might be a separate issue for the AS team). Hopefully we can revert to a JDK5 specific version of the embedded jar, although it will need to be tested with JDK6, and the 4.2.3 jars. The exception below is an example of what was seen. As you can see the resource adapter has the JDK6 dependent package and calls an a JDK 6 specific class. [testng] Caused by: org.jboss.resource.JBossResourceException: Unchecked throwable in ManagedConnection.getConnection() cl=org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@921a90[state=NORMAL mc=org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@dc5733 handles=0 lastUse=1218664283785 permit=true trackByTx=true mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$PoolBySubject@1e0f790 context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@9d1714 xaResource=org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource@11fc6b2 txSync=TxSync9884354{tx=TransactionImple < ac, BasicAction: a1012c7:eacd:48a35756:6 status: ActionStatus.RUNNING > wasTrackByTx=true enlisted=true}]; - nested throwable: (java.lang.reflect.UndeclaredThrowableException) [testng] at org.jboss.resource.JBossResourceException.rethrowAsResourceException(JBossResourceException.java:61) [testng] at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:408) [testng] at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:838) [testng] at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88) [testng] ... 105 more [testng] Caused by: java.lang.reflect.UndeclaredThrowableException [testng] at org.jboss.resource.JBossResourceException.process(JBossResourceException.java:204) [testng] at org.jboss.resource.JBossResourceException.<init>(JBossResourceException.java:111) [testng] ... 109 more [testng] Caused by: java.lang.NoClassDefFoundError: java/sql/SQLClientInfoException [testng] at org.jboss.resource.adapter.jdbc.jdk6.WrappedConnectionFactoryJDK6.createWrappedConnection(WrappedConnectionFactoryJDK6.java:44) [testng] at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.getConnection(BaseWrapperManagedConnection.java:244) [testng] at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:403) [testng] ... 107 more [testng] [testng] =============================================== [testng] Lacewiki - All [testng] Total tests run: 123, Failures: 0, Skips: 123 [testng] Configuration Failures: 1, Skips: 457 [testng] =============================================== -- 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