"ritesh163" wrote : 
  | But the main thing is that for the same project, jboss-4.0.4.GA doesn't 
display any error message while jboss-4.2.2.GA does. 
  | 

In your two servers, check the value of "Debug" attribute for the 
CachedConnectionManager in %JBOSS_HOME%/server/< 
serverName>/deploy/jbossjca-service.xml file. I guess for JBoss-4.0.4GA its set 
to false where as it is true in your JBoss-4.2.2GA.

  | <!-- 
  |      | The CachedConnectionManager is used partly to relay started 
UserTransactions to 
  |      | open connections so they may be enrolled in the new tx.
  |    -->
  |   <mbean 
code="org.jboss.resource.connectionmanager.CachedConnectionManager" 
  |          name="jboss.jca:service=CachedConnectionManager">
  |     <depends 
optional-attribute-name="TransactionManagerServiceName">jboss:service=TransactionManager</depends>
  | 
  |     <!-- Enable connection close debug monitoring -->
  |     <attribute name="Debug">true</attribute>
  | 
  |   </mbean>


"ritesh163" wrote : 
  | Will I have to create other function for closing this connection
  | 

Any connection that is opened needs to be closed, after its use. If you leave 
the connection open forever, then it will lead to a connection leak. The 
message that JBoss logs is an indication that you are not closing the 
connection.



View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4120728#4120728

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4120728
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to