[JCA/JBoss] - Re: InUseConnections > MaxPoolSize... is this possible?
by Sancheski
Here you are:
| 2007-09-19 11:12:04,088 DEBUG [org.jboss.deployment.XSLSubDeployer] transformed into doc: <server>
| <mbean code='org.jboss.resource.connectionmanager.NoTxConnectionManager' display-name='ConnectionManager for ConnectionFactory LdapConnector' name='jboss.jca:service=NoTxCM,name=LdapConnector'>
| <depends optional-attribute-name='ManagedConnectionPool'>
| <mbean code='org.jboss.resource.connectionmanager.JBossManagedConnectionPool' display-name='Connection Pool for DataSource LdapConnector' name='jboss.jca:service=ManagedConnectionPool,name=LdapConnector'>
| <depends optional-attribute-name='ManagedConnectionFactoryName'>
| <mbean code='org.jboss.resource.connectionmanager.RARDeployment' display-name='ManagedConnectionFactory for ConnectionFactory LdapConnector' name='jboss.jca:service=ManagedConnectionFactory,name=LdapConnector'>
| <attribute name='ManagedConnectionFactoryProperties'>
| <properties>
| <config-property name='ldapContextFactory' type='java.lang.String'>com.sun.jndi.ldap.LdapCtxFactory</config-property>
| <config-property name='providerUrl' type='java.lang.String'>ldap://13.24.21.78:389/</config-property>
| <config-property name='securityAuthentication' type='java.lang.String'>SIMPLE</config-property>
| <config-property name='securityPrincipal' type='java.lang.String'>uid=admin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot</config-property>
| <config-property name='securityCredentials' type='java.lang.String'>admin</config-property>
| </properties>
| </attribute>
| <attribute name='RARName'>10sss.ear#ldap-connector.rar</attribute>
| <attribute name='ConnectionDefinition'>foo.bar.connector.CapabilityConnectionFactory</attribute>
| <depends optional-attribute-name='OldRarDeployment'>jboss.jca:service=RARDeployment,name='10sss.ear#ldap-connector.rar'</depends>
| </mbean>
| </depends>
| <attribute name='PoolJndiName'>LdapConnector</attribute>
| <attribute name='MinSize'>1</attribute>
| <attribute name='MaxSize'>3</attribute>
| <attribute name='BlockingTimeoutMillis'>3000</attribute>
| <attribute name='IdleTimeoutMinutes'>0</attribute>
| <attribute name='BackGroundValidation'>true</attribute>
| <attribute name='BackGroundValidationMinutes'>1</attribute>
| <attribute name='PreFill'>False</attribute>
| <attribute name='UseFastFail'>False</attribute>
| <attribute name='Criteria'>ByNothing</attribute>
| </mbean>
| </depends>
| <attribute name='JndiName'>LdapConnector</attribute>
| <depends optional-attribute-name='CachedConnectionManager'>jboss.jca:service=CachedConnectionManager</depends>
| </mbean>
| <mbean code='org.jboss.resource.connectionmanager.ConnectionFactoryBindingService' display-name='Binding for ConnectionFactory LdapConnector' name='jboss.jca:service=ConnectionFactoryBinding,name=LdapConnector'>
| <attribute name='JndiName'>LdapConnector</attribute>
| <attribute name='UseJavaContext'>true</attribute>
| <depends optional-attribute-name='ConnectionManager'>jboss.jca:service=NoTxCM,name=LdapConnector</depends>
| </mbean>
| </server>
| 2007-09-19 11:12:04,088 DEBUG [org.jboss.deployment.SARDeployer] Using existing deployment.document
Thanks a lot
David
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085932#4085932
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085932
18 years, 10 months
[JBoss Seam] - Stored procedure call causes connection close
by nickarls
Yep, Hibernate specific but some of you might have come across this in a seam context (no pun intended):
I execute a stored procedure by getting a connection from the (Hibernate) JPA delegate but when the original method exits, my friendly CachedConnectionManager closes the connection. Which isn't very nice in a long running conversation with SMPC.
Is there a better way to execute stored procedures or is there a way to leave the connection open?
| 12:00:34,082 INFO [CachedConnectionManager] Closing a connection for you. Please close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@170e652
| java.lang.Throwable: STACKTRACE
| at org.jboss.resource.connectionmanager.CachedConnectionManager.registerConnection(CachedConnectionManager.java:290)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:417)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
| at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
| at org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider.getConnection(InjectedDataSourceConnectionProvider.java:47)
| at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423)
| at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
| at org.hibernate.jdbc.BorrowedConnectionProxy.invoke(BorrowedConnectionProxy.java:50)
| at $Proxy136.prepareCall(Unknown Source)
| at concept.misc.Repository.getNextOrderNumber(Repository.java:370)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085927#4085927
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085927
18 years, 10 months