Switch to the jboss-local-jdbc.rar that is in the jboss 3.1 cvs, it does not have this problem. The 3.1 hsqldb-service.xml is set up to use this adapter rather than the Minerva one. I will be migrating the new one to 3.0 rc2 as well, give me a little time.
thanks david jencks On 2002.04.25 14:02:15 -0400 [EMAIL PROTECTED] wrote: > I have a session bean with several different methods that look up a > datasource, create a connection, and execute some queries. My client > keeps > getting this exception: > > [java] Exception in thread "main" > java.lang.reflect.UndeclaredThrowableException: > javax.resource.ResourceException: associateConnection not supported > [java] at > sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteC > all.java:245) > [java] at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:220) > [java] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122) > [java] at > org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) > [java] at > org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProx > y.java:128) > [java] at > org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:108) > [java] at > org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:73 > ) > [java] at > org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:76) > [java] at > org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInter > ceptor.java:111) > [java] at > org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76) > [java] at $Proxy1.getTypeEnumIdMap(Unknown Source) > [java] at > com.tacintel.tee.cbs.UnitSIFParser.<init>(UnitSIFParser.java:103) > [java] at > com.tacintel.tee.cbs.UnitSIFParser.main(UnitSIFParser.java:772) > > This is not happening in my bean (I have tried to catch it in there) so, > it > must be getting thrown by one of the interceptors? Does > associateConnection > have anything to do with associating a datasource.getConnection() to a > transaction? Well, I thought that, so I removed the transaction on my > session bean, but I still sometimes get this exception in my client... > > The class that is throwing the exception is (well that is the only place > that throws a ResourceException with the above message): > connector/src/main/org/jboss/resource/adapter/jdbc/BaseManagedConnection.jav > a > > And it somehow made it through all the JBoss try/catches because I don't > see > it anywhere in the log files and because it comes back to my client as an > UndeclaredThrowableException.... > > Any ideas? > > Michael > > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
