I've traced the problem to DriverManager. In my case, I'm using mySQL, and DriverManager has the Driver class loaded, but it skips it because it tries to load the class from the callers ClassLoader, and class doesn't match the class that was already loaded, so, it skips it.
So, either the caller's ClassLoader can't find the class or it finds the class, loads it, but because the class is '!=' to the class that DriverManager already has (i.e. it was loaded from a different codebase) it skips it. Looking for ClassLoading wizards to intervene and fix this. This problem exits not only in 3.0.5, but in jboss-head as well. So, changes from 3.0.4 to 3.0.5 and recent jboss-head changes are causing this problem. Thanks, Michael > -----Original Message----- > From: Meyer-Willner, Bernhard [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 17, 2003 10:22 AM > To: '[EMAIL PROTECTED]' > Cc: '[EMAIL PROTECTED]' > Subject: AW: [JBoss-user] Oracle / DataSource Deployment Problem with > 3.0. 5 > > > I took out the <loader-repository> tag out of jboss-app.xml > and it deployed > fine. What's wrong there? Did the change of the classloading > procedure in > JBoss 3.0.5 (as compared to 3.0.4) introduce an error, so that > loader-repository doesn't do what it's supposed to any longer? > > Bernhard > > > -----Ursprüngliche Nachricht----- > Von: Meyer-Willner, Bernhard [mailto:[EMAIL PROTECTED]] > Gesendet: Freitag, 17. Januar 2003 16:02 > An: '[EMAIL PROTECTED]' > Betreff: Re: [JBoss-user] Oracle / DataSource Deployment Problem with > 3.0. 5 > > > Yes, I'm using > <loader-repository>com.ourcompany.ourproject:loader=ourapp.ear > </loader-repos > itory> > > (the EAR directory is ourapp.ear) > > So you are saying if we take the loader-repository out then > it would deploy > fine? > > Bernhard > > -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Gesendet: Freitag, 17. Januar 2003 15:14 > An: [EMAIL PROTECTED] > Betreff: RE: [JBoss-user] Oracle / DataSource Deployment Problem with > 3.0. 5 > > > Do you have <loader-repository> in your jboss-app.xml file > for you EAR? I > am getting this same error with jboss-head (1/16/03, > 9:30am-ish EST) using a > mySQL datasource that was fine in jboss-head from 11/26/02. > Everything > deploys fine when I use the default loader-repository. > > > -----Original Message----- > > From: Meyer-Willner, Bernhard [mailto:[EMAIL PROTECTED]] > > Sent: Friday, January 17, 2003 4:36 AM > > To: JBoss-User (E-Mail) > > Subject: [JBoss-user] Oracle / DataSource Deployment Problem > > with 3.0.5 > > > > > > Hi, > > > > we just tried switching our JBoss 3.0.4 to 3.0.5. Although > > the class loading > > procedure seems to have changed a bit, we managed to pretty > > much deploy our > > app in 3.0.5 successfully (we're using an exploded EAR for > > development use). > > We do, however, have problems with deploying our oracle > > datasource. Seems > > like it doesn't work the same way as before. > > > > We have an ejb-jar in our deployment containing CMP entity > > beans that use > > this datasource. > > The Oracle DS is deployed as an exploded SAR inside of our > > exploded EAR. The > > dir is called oracle-service.sar. We're using the same driver > > jar for Oracle > > 8i as we did before (doesn't matter if it's put in the SAR > > directory or > > directly into the deploy directory). Inside the > > oracle-service.sar dir, we > > have a meta-inf dir that contains the jboss-service.xml for > > deploying our > > Oracle datasource (see jboss-service.xml below). Remember, > > this all worked > > perfectly well with 3.0.4. Following is my jboss-service.xml > > for Oracle, > > thereafter the stacktrace I'm getting when my CMP beans jar > > is deployed. > > Strange enough, after gazillions lines of stacktraces and > > JBoss saying the > > the deployment of all of those entity beans failed, I can all > > see them in > > the JMX console. What's up with that message, saying that the > > wrong driver > > class is specified. How can that be? And why is the driver "not yet > > registered"? > > > > Grateful for any ideas. > > > > Thanks, > > Bernhard > > > > Appendix: > > > > jboss-service.xml > > ----------------- > > > > <?xml version="1.0" encoding="UTF-8"?> > > <!-- > > > ===================================================================== > > --> > > <!-- > > --> > > <!-- JBoss Server Configuration > > --> > > <!-- > > --> > > <!-- > > > ===================================================================== > > --> > > <server> > > > > <classpath codebase="." archives="oraclejdbc.jar"/> > > <!-- > > ============================================================== > > ====== --> > > <!-- ConnectionManager setup for Oracle dbs > > --> > > <!-- Build jmx-api (build/build.sh all) and view for config > > documentation --> > > <!-- Thanks to Steven Coy > > --> > > <!-- > > ============================================================== > > ====== --> > > <mbean > > code="org.jboss.resource.connectionmanager.LocalTxConnectionManager" > > name="jboss.jca:service=LocalTxCM,name=OracleDS"> > > <!-- Include a login module configuration named > > OracleDbRealm. > > Update your login-conf.xml, here is an example for a > > ConfiguredIdentityLoginModule: > > > > <application-policy name = "OracleDbRealm"> > > <authentication> > > <login-module code = > > "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = > > "required"> > > <module-option name = > > "principal">yourprincipal</module-option> > > <module-option name = > > "userName">yourusername</module-option> > > <module-option name = > > "password">yourpassword</module-option> > > <module-option name = > > "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,nam > > e=OracleDS</mo > > dule-option> > > </login-module> > > </authentication> > > </application-policy> > > > > NOTE: the application-policy name attribute must match > > SecurityDomainJndiName, and the > > module-option name = "managedConnectionFactoryName" > > must match the object name of the ConnectionManager you > > are configuring > > here. > > --> > > <!--uncomment out this line if you are using the > > OracleDbRealm above > > <attribute > name="SecurityDomainJndiName">OracleDbRealm</attribute> > > --> > > <depends > > optional-attribute-name="ManagedConnectionFactoryName"> > > <!--embedded mbean--> > > <mbean > > code="org.jboss.resource.connectionmanager.RARDeployment" > > name="jboss.jca:service=LocalTxDS,name=OracleDS"> > > <attribute > > name="JndiName">OracleDS</attribute> > > <attribute > > name="ManagedConnectionFactoryProperties"> > > <properties> > > <config-property > > name="ConnectionURL" > > type="java.lang.String">jdbc:oracle:thin:@hamsrvnvg01:1521:isi > > sdbv</config-p > > roperty> > > <config-property > > name="DriverClass" > > type="java.lang.String">oracle.jdbc.driver.OracleDriver</confi > > g-property> > > <!--set these > > only if you > > want only default logins, not through JAAS --> > > <config-property > > name="UserName" type="java.lang.String">user</config-property> > > <config-property > > name="Password" type="java.lang.String">pass</config-property> > > </properties> > > </attribute> > > <!--Below here are advanced > > properties --> > > <!--hack--> > > <depends > > optional-attribute-name="OldRarDeployment">jboss.jca:service=R > > ARDeployment,n > > ame=JBoss LocalTransaction JDBC Wrapper</depends> > > </mbean> > > </depends> > > <depends > > optional-attribute-name="ManagedConnectionPool"> > > <!--embedded mbean--> > > <mbean > > > code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool" > > name="jboss.jca:service=LocalTxPool,name=OracleDS"> > > <attribute name="MinSize">0</attribute> > > <attribute name="MaxSize">50</attribute> > > <attribute > > name="BlockingTimeoutMillis">5000</attribute> > > <attribute > > name="IdleTimeoutMinutes">15</attribute> > > <!--criteria indicates if Subject (from > > security domain) or app supplied > > parameters (such as from getConnection(user, pw)) > > are used to > > distinguish > > connections in the pool. Choices are > > ByContainerAndApplication (use both), > > ByContainer (use Subject), > > ByApplication (use app supplied params only), > > ByNothing (all connections are equivalent, > > usually if adapter > > supports > > reauthentication)--> > > <attribute > > name="Criteria">ByContainer</attribute> > > </mbean> > > </depends> > > <depends > > optional-attribute-name="CachedConnectionManager">jboss.jca:se > rvice=CachedCo > > nnectionManager</depends> > > <depends > > optional-attribute-name="JaasSecurityManagerService">jboss.sec > urity:service= > > JaasSecurityManager</depends> > > <attribute > > name="TransactionManager">java:/TransactionManager</attribute> > > <!--make the rar deploy! hack till better deployment--> > > <depends>jboss.jca:service=RARDeployer</depends> > > </mbean> > > </server> > > > > jboss-service.xml > > ----------------- > > end > > > > > > Stacktrace on deployment of CMP entity bean jar > > ----------------------------------------------- > > > > 2003-01-17 10:18:22,346 DEBUG > > [org.jboss.resource.connectionmanager.IdleRemover] > > internalRegisterPool: > > about to notify thread: old next: 1042795552346, new next: > > 1042795552346 > > 2003-01-17 10:18:22,346 DEBUG > > [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionF > > actory] Using > > properties: {user=user, password=pass} > > 2003-01-17 10:18:22,346 DEBUG > > > [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] > > Checking driver for URL: jdbc:oracle:thin:@hamsrvnvg01:1521:isisdbv > > 2003-01-17 10:18:22,366 DEBUG > > [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionF > > actory] Driver > > not yet registered for url: > jdbc:oracle:thin:@hamsrvnvg01:1521:isisdbv > > 2003-01-17 10:18:22,376 DEBUG > > [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionF > > actory] Driver > > not yet registered for url: > jdbc:oracle:thin:@hamsrvnvg01:1521:isisdbv > > 2003-01-17 10:18:22,386 DEBUG > > [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionF > > actory] Driver > > not yet registered for url: > jdbc:oracle:thin:@hamsrvnvg01:1521:isisdbv > > 2003-01-17 10:18:22,386 DEBUG [org.jboss.util.NestedThrowable] > > org.jboss.util.NestedThrowable.parentTraceEnabled=true > > 2003-01-17 10:18:22,386 DEBUG [org.jboss.util.NestedThrowable] > > org.jboss.util.NestedThrowable.nestedTraceEnabled=false > > 2003-01-17 10:18:22,386 DEBUG [org.jboss.util.NestedThrowable] > > org.jboss.util.NestedThrowable.detectDuplicateNesting=true > > 2003-01-17 10:18:22,436 WARN > > [org.jboss.system.ServiceController] Problem > > starting service jboss.j2ee:jndiName=ejb/GeschSparte,service=EJB > > org.jboss.deployment.DeploymentException: Error while fixing > > table name; - > > nested throwable: (org.jboss.util.NestedSQLException: > Apparently wrong > > driver class specified for URL: class: > > oracle.jdbc.driver.OracleDriver, url: > > jdbc:oracle:thin:@hamsrvnvg01:1521:isisdbv; - nested throwable: > > (javax.resource.ResourceException: Apparently wrong driver > > class specified > > for URL: class: oracle.jdbc.driver.OracleDriver, url: > > jdbc:oracle:thin:@hamsrvnvg01:1521:isisdbv)) > > at > > org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:67) > > at > > org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.<init>( > > JDBCEntityBrid > > ge.java:103) > > at > > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManag > > er(JDBCStoreMa > > nager.java:397) > > at > > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStor > > eManager.java: > > 339) > > at > > org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersisten > > ceManager.java > > :198) > > at org.jboss.ejb.EntityContainer.start(EntityContainer.java:376) > > at org.jboss.ejb.Container.invoke(Container.java:756) > > at > > org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1058) > > at > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) > > at > > org.jboss.system.ServiceController$ServiceProxy.invoke(Service > > Controller.jav > > a:1003) > > at $Proxy4.start(Unknown Source) > > at > > org.jboss.system.ServiceController.start(ServiceController.java:413) > > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > > odAccessorImpl > > .java:25) > > at java.lang.reflect.Method.invoke(Method.java:324) > > at > > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec > > tedMBeanDispat > > cher.java:284) > > at > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) > > at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) > > at $Proxy14.start(Unknown Source) > > at org.jboss.ejb.EjbModule.startService(EjbModule.java:430) > > at > > org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport > > .java:165) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess > > orImpl.java:39 > > ) > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > > odAccessorImpl > > .java:25) > > at java.lang.reflect.Method.invoke(Method.java:324) > > at > > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec > > tedMBeanDispat > > cher.java:284) > > at > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) > > at > > org.jboss.system.ServiceController$ServiceProxy.invoke(Service > > Controller.jav > > a:1003) > > at $Proxy4.start(Unknown Source) > > at > > org.jboss.system.ServiceController.start(ServiceController.java:413) > > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > > odAccessorImpl > > .java:25) > > at java.lang.reflect.Method.invoke(Method.java:324) > > at > > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec > > tedMBeanDispat > > cher.java:284) > > at > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) > > at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) > > at $Proxy8.start(Unknown Source) > > at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:395) > > at > > org.jboss.deployment.MainDeployer.start(MainDeployer.java:814) > > at > > org.jboss.deployment.MainDeployer.start(MainDeployer.java:806) > > at > > org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627) > > at > > org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591) > > at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source) > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > > odAccessorImpl > > .java:25) > > at java.lang.reflect.Method.invoke(Method.java:324) > > at > > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec > > tedMBeanDispat > > cher.java:284) > > at > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) > > at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) > > at $Proxy3.deploy(Unknown Source) > > at > > org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDe > > ploymentScanne > > r.java:435) > > at > > org.jboss.deployment.scanner.URLDeploymentScanner.scanDirector > > y(URLDeploymen > > tScanner.java:656) > > at > > org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDepl > > oymentScanner. > > java:507) > > at > > org.jboss.deployment.scanner.AbstractDeploymentScanner.startSe > > rvice(Abstract > > DeploymentScanner.java:261) > > at > > org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport > > .java:165) > > at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > > odAccessorImpl > > .java:25) > > at java.lang.reflect.Method.invoke(Method.java:324) > > at > > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec > > tedMBeanDispat > > cher.java:284) > > at > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) > > at > > org.jboss.system.ServiceController$ServiceProxy.invoke(Service > > Controller.jav > > a:1003) > > at $Proxy0.start(Unknown Source) > > at > > org.jboss.system.ServiceController.start(ServiceController.java:413) > > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > > odAccessorImpl > > .java:25) > > at java.lang.reflect.Method.invoke(Method.java:324) > > at > > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec > > tedMBeanDispat > > cher.java:284) > > at > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) > > at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) > > at $Proxy2.start(Unknown Source) > > at org.jboss.deployment.SARDeployer.start(SARDeployer.java:229) > > at > > org.jboss.deployment.MainDeployer.start(MainDeployer.java:814) > > at > > org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:627) > > at > > org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591) > > at > > org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess > > orImpl.java:39 > > ) > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > > odAccessorImpl > > .java:25) > > at java.lang.reflect.Method.invoke(Method.java:324) > > at > > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec > > tedMBeanDispat > > cher.java:284) > > at > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) > > at > > org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:325) > > at org.jboss.system.server.ServerImpl.start(ServerImpl.java:222) > > at org.jboss.Main.boot(Main.java:148) > > at org.jboss.Main$1.run(Main.java:381) > > at java.lang.Thread.run(Thread.java:536) > > Caused by: org.jboss.util.NestedSQLException: Apparently > > wrong driver class > > specified for URL: class: oracle.jdbc.driver.OracleDriver, url: > > jdbc:oracle:thin:@hamsrvnvg01:1521:isisdbv; - nested throwable: > > (javax.resource.ResourceException: Apparently wrong driver > > class specified > > for URL: class: oracle.jdbc.driver.OracleDriver, url: > > jdbc:oracle:thin:@hamsrvnvg01:1521:isisdbv) > > at > > org.jboss.resource.adapter.jdbc.local.LocalDataSource.getConne > > ction(LocalDat > > aSource.java:106) > > at > > org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:38) > > ... 84 more > > Caused by: javax.resource.ResourceException: Apparently wrong > > driver class > > specified for URL: class: oracle.jdbc.driver.OracleDriver, url: > > jdbc:oracle:thin:@hamsrvnvg01:1521:isisdbv > > at > > org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFa > > ctory.checkDri > > ver(LocalManagedConnectionFactory.java:453) > > at > > org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFa > > ctory.createMa > > nagedConnection(LocalManagedConnectionFactory.java:130) > > at > > org.jboss.resource.connectionmanager.InternalManagedConnection > > Pool.createCon > > nection(InternalManagedConnectionPool.java:259) > > at > > org.jboss.resource.connectionmanager.InternalManagedConnection > > Pool.getConnec > > tion(InternalManagedConnectionPool.java:106) > > at > > org.jboss.resource.connectionmanager.JBossManagedConnectionPoo > > l$BasePool.get > > Connection(JBossManagedConnectionPool.java:323) > > at > > org.jboss.resource.connectionmanager.BaseConnectionManager2.ge > > tManagedConnec > > tion(BaseConnectionManager2.java:467) > > at > > org.jboss.resource.connectionmanager.LocalTxConnectionManager. > > getManagedConn > > ection(LocalTxConnectionManager.java:221) > > at > > org.jboss.resource.connectionmanager.BaseConnectionManager2.al > > locateConnecti > > on(BaseConnectionManager2.java:532) > > at > > org.jboss.resource.connectionmanager.BaseConnectionManager2$Co > > nnectionManage > > rProxy.allocateConnection(BaseConnectionManager2.java:822) > > at > > org.jboss.resource.adapter.jdbc.local.LocalDataSource.getConne > > ction(LocalDat > > aSource.java:102) > > ... 85 more > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: Thawte.com > Understand how to protect your customers personal information by > implementing > SSL on your Apache Web Server. Click here to get our FREE > Thawte Apache > Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > This e-mail and any attachment is for authorised use by the intended > recipient(s) only. It may contain proprietary material, confidential > information and/or be subject to legal privilege. It should > not be copied, > disclosed to, retained or used by, any other party. If you are not an > intended recipient then please promptly delete this e-mail and any > attachment and all copies and inform the sender. Thank you. > > > ------------------------------------------------------- > This SF.NET email is sponsored by: Thawte.com - A 128-bit > supercerts will > allow you to extend the highest allowed 128 bit encryption to > all your > clients even if they use browsers that are limited to 40 bit > encryption. > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > This e-mail and any attachment is for authorised use by the > intended recipient(s) only. It may contain proprietary > material, confidential information and/or be subject to legal > privilege. It should not be copied, disclosed to, retained > or used by, any other party. If you are not an intended > recipient then please promptly delete this e-mail and any > attachment and all copies and inform the sender. Thank you. > ------------------------------------------------------- This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will allow you to extend the highest allowed 128 bit encryption to all your clients even if they use browsers that are limited to 40 bit encryption. Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
