[JCA/JBoss] - [JBossManagedConnectionPool] Destroying connection
by MarcReis
I have been using AS 4.0.4.GA for a while and never seen the following warning.
I updated the JBossCache lately from 1.4.0GA to 1.4.0.SP1, that is the only thing that I can thing of at the moment that could be related.
I am not sure if this is the cause or if this is the correct place to ask (JCA, JBossCache, or TX?). At first shoot, I didn't realy find any usefull info in the forum or doc's, so please feel free to point me to the correct starting point.
I also posted this at the transactions thread, but havent received any feedback.
| [JBossManagedConnectionPool] Destroying connection that could not be successfully matched: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@16998b9[state=NORMAL mc=org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@92e1b2 handles=0 lastUse=1158079794828 permit=false trackByTx=false tcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePo
| ol@1fa4f8d context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@7cb926 xaResource=org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource@11fa7e2 txSync=null]
|
Sincerly
Marc
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971852#3971852
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971852
19 years, 7 months
[Persistence, JBoss/CMP, Hibernate, Database] - Scaling JBoss Persistence
by tvanbuskirk
Hello,
I have a single database schema that will be replicated many times for different "users" (more like corporate entities) on the system. When a client (user) makes a request, I'd like for an EJB 3.0 session bean to determine which database instance to connect to based upon the name of the client (user).
As for my database, I have multiple database schemas defined in MySQL that can be accessed via
hostname:3306/duplicateSchema1,
hostname:3306/duplicateSchema2,
...etc.
Does anyone know the best way to encorporate all of these schemas and dynamically determine which database instance to connect to based upon the client?
One thought I had was to create a DataSource (*-ds.xml) file for each schema. However, I'm concerned about how this would scale if I have between 50 and 2000 duplicate schemas. (50 to 2000 *-ds.xml files seems to be the wrong way to do this .. but maybe it's right)
Does anyone have any ideas?
I really appreciate your help on this. Thanks in advance!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971846#3971846
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971846
19 years, 7 months