There are at least 3 problems here: 1. You appear to be using config appropriate for jboss 3 in jboss 2.4. The corresponding attribute in 2.4.x is "Properties".
2. AFAIK non-string properties are not handled [well] at the moment, so the "4" is apt to run into problems when you use the correct attribute name. 3. Currently jboss has a limitation that you MUST get a connection within a method call to your ejb and AFTER the transaction starts and you MUST close it before the transaction ends and before the method returns. I think perhaps you not doing one of these is causing the lack of cleanup calls on your managed connections. I'm currently working on a reimplementation of the ConnectionManager for jboss 3 that will remove this limitation. Then I'll fix (2), also for jboss 3. david jencks On 2002.03.10 05:01:52 -0500 Polman wrote: > Hi all, > > I have recently implemented a resource adapter for an XML database > product, and deployed it to JBoss appserver (2.4.4). The thign I cannot > seem to get to work is the ManagedConnectionFactoryProperties in > the jcml code. I use the following: > > <attribute name="ManagedConnectionFactoryProperties"> > UserName=Administrator > Password=secret > DatabaseName=MyDatabase > PropertiesURL=d:/xhive/bin/xhive.properties.default > LogLevel=4 > </attribute> > > Are these supposed to overrule their <config-property> > counterparts in ra.xml? Then this does not happen (the > values in ra.xml are always chosen. > > The second problem is ManagedConnection cleanup. In section > 5.8.3 of the connection spec it says that: > > "The application server can also initiate cleanup of a ManagedConnection > instance when the > container terminates the application component instance that has the > corresponding connec-tion > handle. The application server should call ManagedConnection.cleanup to > initiate the > connection cleanup. After the cleanup, the application server puts the > ManagedConnection in-stance > into the pool to serve future allocation requests." > > This suggests that cleanup is called after I call remove on a bean that > has a connection handle to my XML database through the resource > adapter. However, when I log events on ManagedConnection, cleanup is > never invoked. Also, whenever I remove a bean with still open connection > handles, the next time I create such a bean, a new physical connection > is always opened. > > The first question was posted one one of the forums before, > but no reactions were posted. > > Thanks in advance, > > --Mark Polman-- > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
