Facing Issue while accessing list of entities with Teiid 8.7 final, JBoss EAP 6.1.0 Alpha and EclipseLink2.5.2

[rajni.kumari14]

Hi ,

We are using JBoss EAP 6.1.0 Alpha and EclipseLink2.5.2 in our project and recently migrated from Teiid 8.4 final to the Teiid 8.7 final,  we are facing problem  while trying to access list of entities after deploying a vdb.

We created  a dynamic VDB (for mysql datasource) deployed the same on Jboss EAP 6.1.0 Alpha (Which has Teiid 8.7 final exacted on it),  vdb gets 'active' but when  we try to access the list of entities exception is thrown from eclipselink side -

SEVERE [org.eclipse.persistence.session.vfs:/C:/Users/rdxsz0008/Desktop/jboss-eap-6.1/bin/content/dsdataserver.war/WEB-INF/classes/_teiid

DynamicUnit_transactionType=RESOURCE_LOCAL_url=jdbc:teiid:SampleMYSQL;version=1;PassthroughAuthentication=true;fetchSize=2048;ApplicationName=MySQL|No

rthwindMSQLModel;VirtualDatabaseName=SampleMYSQL;useCallingThread=true.ejb] (http-/0.0.0.0:8080-1)       __EclipseLinkSessionId__: 1667083228: java.la

1. ng.IllegalAccessError: tried to access class org.teiid.jdbc.SocketProfile from class org.teiid.jdbc.TeiidDriver

        at org.teiid.jdbc.TeiidDriver.<init>(TeiidDriver.java:72) [teiid-admin-8.7.0.Final.jar:8.7.0.Final]

        at org.teiid.jdbc.TeiidDriver.<clinit>(TeiidDriver.java:60) [teiid-admin-8.7.0.Final.jar:8.7.0.Final]

        at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_33]

        at java.lang.Class.forName(Unknown Source) [rt.jar:1.6.0_33]

        at org.eclipse.persistence.internal.security.PrivilegedAccessHelper.getClassForName(PrivilegedAccessHelper.java:124) [eclipselink.jar:2.5.2.v2

0140319-9ad6abd]

        at org.eclipse.persistence.sessions.DefaultConnector.loadDriverClass(DefaultConnector.java:253) [eclipselink.jar:2.5.2.v20140319-9ad6abd]

        at org.eclipse.persistence.sessions.DefaultConnector.connect(DefaultConnector.java:85) [eclipselink.jar:2.5.2.v20140319-9ad6abd]

        at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162) [eclipselink.jar:2.5.2.v20140319-9ad6abd]

        at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connectInternal(DatasourceAccessor.java:346) [eclipselink.jar:2.5.2.v201

40319-9ad6abd]

at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.connectInternal(DatabaseAccessor.java:307) [eclipselink.jar:2.5.2.v2014031

9-9ad6abd]

        at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connect(DatasourceAccessor.java:434) [eclipselink.jar:2.5.2.v20140319-9a

d6abd]

        at org.eclipse.persistence.sessions.server.ConnectionPool.buildConnection(ConnectionPool.java:217) [eclipselink.jar:2.5.2.v20140319-9ad6abd]

        at org.eclipse.persistence.sessions.server.ConnectionPool.startUp(ConnectionPool.java:505) [eclipselink.jar:2.5.2.v20140319-9ad6abd]

        at org.eclipse.persistence.sessions.server.ServerSession.connect(ServerSession.java:488) [eclipselink.jar:2.5.2.v20140319-9ad6abd]

        at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.login(DatabaseSessionImpl.java:755) [eclipselink.jar:2.5.2.v20140319-9ad6abd]

        at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:241) [eclipselink.jar:2.5.2.v2014

0319-9ad6abd]

        at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:685) [eclipselink.jar:2.5.2.v20140319-9ad6ab

d]

        at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.getAbstractSession(EntityManagerFactoryDelegate.java:204) [eclipselink.ja

r:2.5.2.v20140319-9ad6abd]

        at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.createEntityManagerImpl(EntityManagerFactoryDelegate.java:304) [eclipseli

1. nk.jar:2.5.2.v20140319-9ad6abd]

        at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:336) [eclipselink.jar:2

.5.2.v20140319-9ad6abd]

        at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:302) [eclipselink.jar:2.5.2

.v20140319-9ad6abd]

Which we think could be from the Teiid side, please advice how we can proceed on solving the same.

Thanks

Rajni

[rajni.kumari14]

Hi,

We further look into above mentioned issue and found that Eclispelink uses DynamicClassLoader to load 'org.teiid.jdbc.TeiidDriver' class which internally uses  'org.teiid.jdbc.SocketProfiler' class which it couldn't load.

In case of Teiid 8.4 these two classes were packaged under the Teiid-Client jar while in Teiid 8.7 these classes are part of three module jars Teiid-Admin, Teiid-Engine and Teiid-Client. Looks like packaging of the jars is changed from 8.4 to 8.7 and this could be the reason that DynamicClassLoader is unable to figure out which one to load.

Is there any reason to why 'org.teiid.jdbc.TeiidDriver' class is packaged under Teiid-Admin, Teiid-Engine and Teiid-Client jars?

Thanks,

Rajni

[shawkins]

> Is there any reason to why 'org.teiid.jdbc.TeiidDriver' class is packaged under Teiid-Admin, Teiid-Engine and Teiid-Client jars?

No, between the changes to made to create bundles and the other build updates the kitting is not correct.

[shawkins]

Yes, this is an regression with the bundle build logic.  It will be resolved with [TEIID-3029] Duplicate classes with bundle builds - JBoss Issue Tracker