asked on

JDBC connection error

I have a portal server instance running. It is running fine but it is throwing the following exception from time to time.

java.io.IOException: JMS JDBC store, connection pool = <cgJMSPool-nonXA>, prefix
= <weblogic>: ping failed, database not responding
java.io.IOException: JMS JDBC store, connection pool = <cgJMSPool-nonXA>, prefix
= <weblogic>: SQL exception
java.sql.SQLException: Connection failure. sendMethodRequestNoFlush(...).
at com.pointbase.dbexcp.dbexcpException.getSQLException()Ljava/sql/SQLEx
ception;(Unknown Source)
at com.pointbase.net.netJDBCPrimitives.sendMethodRequestPrivate(Lcom/poi
ntbase/net/netJDBCConnection;Ljava/io/DataOutputStream;BILjava/lang/String;[Ljav
a/lang/Object;)V(Unknown Source)
at com.pointbase.net.netJDBCPrimitives.sendMethodRequestByID(Lcom/pointb
ase/net/netJDBCConnection;Ljava/io/DataOutputStream;I[Ljava/lang/Object;)V(Unkno
wn Source)
at com.pointbase.net.netJDBCConnection.setAutoCommit(Z)V(Unknown Source)

at weblogic.jdbc.wrapper.PoolConnection.setAutoCommit(Z)V(PoolConnection
.java:141)
at weblogic.jms.store.JDBCIOStream.opendb()V(JDBCIOStream.java:2205)
at weblogic.jms.store.JDBCIOStream.ping()V(JDBCIOStream.java:1286)
at weblogic.jms.store.StoreRequest.doTheIO(Lweblogic/jms/store/StoreIOSt
ream;Z)Z(StoreRequest.java:355)
at weblogic.jms.store.JMSStore.execute(Lweblogic/kernel/ExecuteThread;)V
(JMSStore.java:493)
at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest

ECollin

hi,

cross-post...

your domain uses a jms server with a jdbc persistence store. Unfortunatly the configured connection pool cannot reach the database.
Watch the configuration of the connection pool (cgJMSPool-nonXA)

Emmanuel

Ajar

You can choose a file store for JMS to avoid this problem

Ajar

The HARMLESS error is occuring while the server is testing the 'IDLE' connections for validity. You can disable this check by going to

[your domain]> JDBC Connection Pools> cgJMSPool-nonXA > connections>advanced

set the Test Frequency: parameter to a high value

Becky

cgJMSPool-nonXA is a connectin pool that Weblgoic automatically creates when you configure a new "Weblogic Enabled" domain instead of a "Regular" domain (it's one of the options in the domain configuration wizard)

Anyone that uses Weblogic Portal must run it in a "Weblogic Enabled" domain and not a standard domain because there are couple of back-end things that get ore-cofigured by weblogic for Portal and Weblogic Workshop applications.

** If you're not using conversational state (asynchronous) Web Services you won't encounter any problems and can ignore those errors. **

If you want to make the messages go away, re-create your domain and instead select a Weblogic Enabled domain type as opposed to the standard domain, then of course don't delete any of the internal connection pools, JMS queues, JMS servers, or the running instance of Pointbase that Weblogic configures and starts up. (Pointbase has a very small footprint)

Wtritepo

ASKER

Thanks for your suggestions. I will try these.

Wtritepo

ASKER

Can you please close the above question. I got it resolved.

thanks for your help

Becky

How did you resolve it?

Becky

cgJMSPool-nonXA is a standard connection pool name created by a Weblogic Workshop domain, so did creating a new Weblogic Workshop Enabled domain work, or did you hand-create them?

Wtritepo

ASKER

I have two instances of servers running in two different domains on two different ports but the same pointbase port . I changed one of them to run in a different pointbase port and I see that it is not thowing this exception anymore.

thanks,
Anu

ASKER CERTIFIED SOLUTION

Computer101

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial