-
1. Re: Connection in Use Keeps going Up Jboss 4.0.4.GA Jboss 4.
kazam Oct 17, 2006 3:31 PM (in response to kazam)Forgot to mention that I have my jboss-jca configured as follows
<!-- | 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>
I am getting these messages on startup however, they are not impacting my application. In some of these messages I see
jboss.jca:service=DataSourceBinding,name=DefaultDS
However, my oracle-ds.xml has datasource as jdbc/oracle, but I think I don't need the mentioned services.
Can these be related to the malfunction of jca?--- MBeans waiting for other MBeans --- ObjectName: jboss.ws:service=DeployerInterceptorEJB3 State: CONFIGURED I Depend On: jboss.ejb3:service=EJB3Deployer ObjectName: jboss.mq:service=InvocationLayer,type=HTTP State: CONFIGURED I Depend On: jboss.mq:service=Invoker jboss.web:service=WebServer ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo State: CONFIGURED I Depend On: jboss:service=TransactionManager jboss.jca:service=DataSourceBinding,name=DefaultDS ObjectName: jboss.mq:service=StateManager State: CONFIGURED I Depend On: jboss.jca:service=DataSourceBinding,name=DefaultDS Depends On Me: jboss.mq:service=DestinationManager ObjectName: jboss.mq:service=DestinationManager State: CONFIGURED I Depend On: jboss.mq:service=MessageCache jboss.mq:service=PersistenceManager jboss.mq:service=StateManager jboss.mq:service=ThreadPool jboss:service=Naming Depends On Me: jboss.mq.destination:service=Topic,name=testTopic jboss.mq.destination:service=Topic,name=securedTopic jboss.mq.destination:service=Topic,name=testDurableTopic jboss.mq.destination:service=Queue,name=testQueue jboss.mq.destination:service=Queue,name=A jboss.mq.destination:service=Queue,name=B jboss.mq.destination:service=Queue,name=C jboss.mq.destination:service=Queue,name=D jboss.mq.destination:service=Queue,name=ex jboss.mq:service=SecurityManager jboss.mq.destination:service=Queue,name=DLQ ObjectName: jboss.mq:service=PersistenceManager State: CONFIGURED I Depend On: jboss.jca:service=DataSourceBinding,name=DefaultDS Depends On Me: jboss.mq:service=DestinationManager ObjectName: jboss.mq.destination:service=Topic,name=testTopic State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager jboss.mq:service=SecurityManager ObjectName: jboss.mq.destination:service=Topic,name=securedTopic State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager jboss.mq:service=SecurityManager ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager jboss.mq:service=SecurityManager ObjectName: jboss.mq.destination:service=Queue,name=testQueue State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager jboss.mq:service=SecurityManager ObjectName: jboss.mq.destination:service=Queue,name=A State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager ObjectName: jboss.mq.destination:service=Queue,name=B State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager ObjectName: jboss.mq.destination:service=Queue,name=C State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager ObjectName: jboss.mq.destination:service=Queue,name=D State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager ObjectName: jboss.mq.destination:service=Queue,name=ex State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager ObjectName: jboss.mq:service=Invoker State: CONFIGURED I Depend On: jboss.mq:service=TracingInterceptor jboss:service=Naming Depends On Me: jboss.mq:service=InvocationLayer,type=HTTP jboss.mq:service=InvocationLayer,type=JVM jboss.mq:service=InvocationLayer,type=UIL2 ObjectName: jboss.mq:service=TracingInterceptor State: CONFIGURED I Depend On: jboss.mq:service=SecurityManager Depends On Me: jboss.mq:service=Invoker ObjectName: jboss.mq:service=SecurityManager State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager Depends On Me: jboss.mq.destination:service=Topic,name=testTopic jboss.mq.destination:service=Topic,name=securedTopic jboss.mq.destination:service=Topic,name=testDurableTopic jboss.mq.destination:service=Queue,name=testQueue jboss.mq:service=TracingInterceptor jboss.mq.destination:service=Queue,name=DLQ ObjectName: jboss.mq.destination:service=Queue,name=DLQ State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager jboss.mq:service=SecurityManager ObjectName: jboss.mq:service=InvocationLayer,type=JVM State: CONFIGURED I Depend On: jboss.mq:service=Invoker ObjectName: jboss.mq:service=InvocationLayer,type=UIL2 State: CONFIGURED I Depend On: jboss.mq:service=Invoker --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS State: NOTYETINSTALLED Depends On Me: jboss:service=KeyGeneratorFactory,type=HiLo jboss.mq:service=StateManager jboss.mq:service=PersistenceManager ObjectName: jboss.ejb3:service=EJB3Deployer State: NOTYETINSTALLED Depends On Me: jboss.ws:service=DeployerInterceptorEJB3
Thanks, kazam. -
2. Re: Connection in Use Keeps going Up Jboss 4.0.4.GA Jboss 4.
kazam Oct 17, 2006 3:39 PM (in response to kazam)More Information
------------------------
Looking at the forum, I think I am missing this piece of information.
This is how I am retrieving my connectionsprotected Connection retrieveConnection() { DataSource oradbConnection; try { //Get DataSource from JNDI repository in JBoss 4.0.2 Context jndiContext= new InitialContext(); oradbConnection=(DataSource)jndiContext.lookup("java:jdbc/oracle"); return oradbConnection.getConnection(); } catch(NamingException e) { throw new RuntimeException("NamingException: Failed to retrieve initial naming Context through JNDI : "+ e.getMessage(),e); } catch(SQLException e) { throw new RuntimeException("SQLException: Failed to retrieve DB connection from JNDI connection pool : "+e.getMessage(),e); } }
All connections are being closed in finally block.
Please look at the previous 2 posts for problem description and information.
Thanks, kazam. -
3. Re: Connection in Use Keeps going Up Jboss 4.0.4.GA Jboss 4.
wmprice Oct 17, 2006 11:58 PM (in response to kazam)I have no idea what you are talking about when you say 4.0.4c, there has never been such a release, there is no corresponding tag, and I am not sure what you are talking about.
The deployment issues you are seeing suggest that the Default datasource cannot be deployed and as a result, JMS cannot be deployed either. JMS depends on JDBC for message persistence. This is not a trivial error and generally suggests something is wrong with your JBoss installation. Did you modify the DefaultDS in any way?
My next question would be where does retrieveConnection occur? Servlet, EJB? By default you will not get connection close behavior (or logging) in a Serlvet, it has to be specifically enabled. For EJB's the ConnectionCacheInterceptor performs this task.
Have you enabled TRACE in your log4j.xml configuration?
' I have two hibernate applications running on this jboss which use same database but are running fine and aren't using JNDI pooling.
What does this mean? There is no such thing as 'JNDI pooling'. -
4. Re: Connection in Use Keeps going Up Jboss 4.0.4.GA Jboss 4.
kazam Oct 18, 2006 2:29 AM (in response to kazam)Thanks very much,
4.0.4c was a jboss version I got when I installed jbpm, it was part of the starters kit, I was not aware that it was not a release or tag.
However, it is the same behaviour on the JBOSS 4.0.4 GA.
RetrieveConnection() is being used in servlets, so I will turn it on for servlets and also turn trace onb in log4j.xml.
Also, you are correct it is not JNDI Pooling, I meant the JCA Connection pool.
Thanks very much for the help.
Kazam.