[
https://jira.jboss.org/jira/browse/TEIID-721?page=com.atlassian.jira.plug...
]
Ramesh Reddy resolved TEIID-721.
--------------------------------
Resolution: Done
As all the classes where the Thread context class loader is used, we can safely replace
with current class loader as all the resources that are being looked up will surely
available in the same class loader as the loaded class.
JDBC Connection thru SQuirreL to Teiid Server instance not working
-------------------------------------------------------------------
Key: TEIID-721
URL:
https://jira.jboss.org/jira/browse/TEIID-721
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 6.1.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.2.0
Caused by: java.lang.ClassNotFoundException:
com.metamatrix.common.comm.platform.socket.client.AdminApiServerDiscovery
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at com.metamatrix.core.util.ReflectionHelper.loadClass(ReflectionHelper.java:251)
at com.metamatrix.core.util.ReflectionHelper.create(ReflectionHelper.java:292)
--
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