Bugs item #664081, was opened at 2003-01-07 15:45 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=664081&group_id=22866
Category: JBossCX Group: v3.2 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Scott M Stark (starksm) Assigned to: David Jencks (d_jencks) Summary: JCA rars packaging causes IllegalAccessError Initial Comment: An java.lang.IllegalAccessError: tried to access method org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnectionFactory.getConnectionProperties (Ljavax/security/auth/Subject;Ljavax/resource/spi/Conne ctionRequestInfo;)Ljava/util/Properties; from class org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnection has been reported and this is an issue with the jca classes being deployed redundantly: lib 634>jar -tf ra-xa-libs.jar | grep BaseWrapper org/jboss/resource/adapter/jdbc/BaseWrapperManagedC onnection.class org/jboss/resource/adapter/jdbc/BaseWrapperManagedC onnectionFactory.class lib 635>jar -tf local-ra-jdbc-libs.jar | grep BaseWrapper org/jboss/resource/adapter/jdbc/BaseWrapperManagedC onnection.class org/jboss/resource/adapter/jdbc/BaseWrapperManagedC onnectionFactory.class Under a usage pattern that happens to load the BaseWrapperManagedConnectionFactory class from the local-ra-jdbc-libs.jar, while the BaseWrapperManagedConnection class is later loaded from the ra-xa-libs.jar, because two different class loaders are involved, the package protected access fails. These classes cannot be deployed redundantly in the same scope in different jars as there is no way for the ULR to ensure that the same class loader handles the classes with package protected access. The jboss-xa.rar and jboss-local-jdbc.rar need to be refactored to fix this. > Here's the exception: > > 16:17:58,415 ERROR [LogInterceptor] Unexpected Error: > java.lang.IllegalAccessError: tried to access method > org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnectionFactory.getConnectionProperties (Ljavax/security/auth/Subject;Ljavax/resource/spi/Conne ctionRequestInfo;)Ljava/util/Properties; > from class org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnection > at > org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnection.checkIdentity (BaseWrapperManagedConnection.java:295) > at > org.jboss.resource.adapter.jdbc.BaseWrapperManagedC onnection.getConnection (BaseWrapperManagedConnection.java:188) > at > org.jboss.resource.connectionmanager.BaseConnection Manager2.allocateConnection (BaseConnectionManager2.java:596) > at > org.jboss.resource.connectionmanager.BaseConnection Manager2$ConnectionManagerProxy.allocateConnection (BaseConnectionManager2.java:885) > at > org.jboss.resource.adapter.jdbc.WrapperDataSource.get Connection(WrapperDataSource.java:102) ---------------------------------------------------------------------- >Comment By: Scott M Stark (starksm) Date: 2003-01-07 19:48 Message: Logged In: YES user_id=175228 Ok, thanks. I don't care about 4.0 at this point ---------------------------------------------------------------------- Comment By: David Jencks (d_jencks) Date: 2003-01-07 19:28 Message: Logged In: YES user_id=60525 I've fixed this in 3.2. I don't think it is a problem in 3.0.x since there are no shared classes between the adapters (different xa adapter than 3.2 and 4). I haven't fixed it in 4.0 because once jca 1.5 deployment is written both adapters can be packaged together, eliminating the extra jar. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=664081&group_id=22866 ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
