Connection pool in Solaris 8
I am getting this error after a few transactions.
Error : No available resource. Wait-time expired.
I am using Sun One App Server 7 on Solaris 8.
I am not getting this error on a Windows 2000 Professional machine.
Any ideas why this happens?
Thanks.
Sri.
When are you creating and closing the connection? What is the size of connection pool? You can increase the pool size by clicking on the JDBC resource on admin console. Then click on connection pool.
Then click on the <connection pool name>. You can set the steady pool size and the max pool size. Please make sure that you are creating and closing connection at right time. You can look at the server log for more details.
Thanks,
-Parsu.
Similar Messages
-
Can't create connection pools on Solaris
Any ideas why this is happening?
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: System.loadLibrary(weblogicoci37) threw java.lang.Unsatis
fiedLinkError: /prod/appl/weblogic/6.1.1.0/lib/solaris/oci817_8/libweblogicoci37
.so: ld.so.1: /prod/appl/java/jdk1.3.1/bin/../bin/sparc/native_threads/java: fat
al: libclntsh.so.8.0: open failed: No such file or directory
at weblogic.jdbc.oci.Driver.loadLibraryIfNeeded(Driver.java:226)
at weblogic.jdbc.oci.Driver.connect(Driver.java:76)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:192)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:134)It worked like a charm. Thank you very much.
Deepak Vohra <[email protected]> wrote:
Include /wlserver6.1/lib/solaris/libweblogicoci37.so & ORACLE_HOME/ora81/lib
in solaris environmental variable LD_LIBRARY_PATH.
shane yan wrote:
Any ideas why this is happening?
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: System.loadLibrary(weblogicoci37) threw java.lang.Unsatis
fiedLinkError: /prod/appl/weblogic/6.1.1.0/lib/solaris/oci817_8/libweblogicoci37
so: ld.so.1: /prod/appl/java/jdk1.3.1/bin/../bin/sparc/native_threads/java:fat
al: libclntsh.so.8.0: open failed: No such file or directory
at weblogic.jdbc.oci.Driver.loadLibraryIfNeeded(Driver.java:226)
at weblogic.jdbc.oci.Driver.connect(Driver.java:76)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:192)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:134) -
Weblogic 6.1 sp2 Connection Pool will not connect to oci901 driver
ok, I am trying to get weblogic to connect to the connection pool in solaris. I created
the pool in the console with the following:
URL = jdbc:weblogic:oracle
Driver Class Name = weblogic.jdbc.oci.Driver
Properties = user=sa password=*****
I also set the LD_LIBRARY PATH as directed.
LD_LIBRARY_PATH=/usr/local/wlserver6.1/lib/solaris/oci901_8:ORACLE/lib
Oracle is on a seperate box then the box that Weblogic is installed on so I think
the problem is in my LD_LIBRARY_PATH. Here is the error I am getting. Any help
would be appreciated.
Starting Loading jDriver/Oracle .....
<Jun 7, 2002 9:04:25 AM CDT> <Error> <JDBC> <Cannot startup connection pool "FargoPool"
weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: System.loadLibrary(weblogicoci37) threw java.lang.UnsatisfiedLinkError:
/usr/local/wlserver6.1/lib/solaris/oci901_8/libweblogicoci37.so: ld.so.1: /home/bea/jdk131/jre/bin/../bin/sparc/native_threads/java:
fatal: libclntsh.so.9.0: open failed: No such file or directory
at weblogic.jdbc.oci.Driver.loadLibraryIfNeeded(Driver.java:226)
at weblogic.jdbc.oci.Driver.connect(Driver.java:76)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:193)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy8.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy17.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:209)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy8.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy17.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)"Tim" <[email protected]> wrote:
>
I have the following setup.
For QA, 1 IIS Server (using plug-in from 6.1 SP2) forwarding all request
to a
cluster on the backend. (2 Physical Servers, 4 JVM's). I do have a firewall
in
between the IIS Server & the backend servers.
According to the docs, the IIS plug-in is supposed to establish a connection
pool
to the backend. I do not see this behavior.
I see a connection created/close per request.
So , I have 2 questions:
1. Does the IIS Plug-in use connection Pooling, Do you have to enable
it ?
2. How do I control the pool size ?
Thanks in advance,
TimDoes anyone from BEA monitor this newsgroup ?
I have also opened up a case (1 week old) with tech support and still do not have
an answer. This is very frustrating considering the cost of owning this environment.
Tim -
WLS 10.3.0.0 Solaris SPARC and DBMS Oracle 10gR2 connection pooling issue
Hi all,
we are currently testing Weblogic Server 10.3.0.0 in order to migrate our production system from WLS 8.1 to it.
While testing the new setup, we encountered some strange behaviour of the connection pooling within WLS.
We configured a XA-Connection pool to our DB (Oracle 10gR2) by using
a) the Oracle XA-thin-driver delivered within WLS 10.3.0.0
and alternatively
b) the Oracle 11.2.0.2 OCI-driver of the Oracle 11g database client.
We´ve got the same issue with both variants. We defined an initial capacity of 5 connections and a maximum capacity of 30 connections.
Our application is running flawlessly using the connection pool, but the amount of active sessions between the application server and the database server is increasing rapidly and the maximum capacity is exceeded. We are seeing up to multiple hundreds of sessions from the application server to our database server. Obviously the connections aren´t cleaned up.
We are using the following settings for the JDBC-Connection:
initial capacity = 5
max. capacity = 30
Capacity increment = 1
Statement cache type = LRU
Statement cache size = 10
Test connections on reserve = true
Test frequency = 120
Test table name = "sql select 1 from dual"
seconds to trust an idle pool connection = 10
shrink frequency = 0
connecttion creation retry frequency = 120
login delay = 0
incative connection timeout = 10
max. waiting for connection = 2147483647
connection reserve timeout= = -1
Ignare in-use connections = true
pinned-to-thread = false
remoce infected connections enabled = true
Does anyone have an idea how to track/solve this issue?
Kind regards
MarcHi Joe,
we´ve tested with the thin driver using an initial capacity of 5 and a maximum capacity of 15. During our tests (in a very short time period) the maximum capacity has not been exceeded. But we saw some exceptions in the managed server logfile which made us curious.
When these exceptions are occuring, a new connection to the database server is established. We are seeing for a short time a total count of 6 connections which is immediately decreasing to the initial capacity of 5. We will do some further testing over the next hours and monitor the connection usage.
The connection we are dealing with is the one called "ZDB2".
This is an excerpt of the logfile:
####<18.10.2010 19:45 Uhr MESZ> <Debug> <JDBCConn> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-02F7EA174F1D84653A69> <> <1287423940610> <BEA-000000> <java.lang.Exception: Pinned: autoCommit=true,enabled=true,isXA=true,isJTS=false,vendorID=0,connUsed=true,doInit=false,'null',destroyed=false,poolname=ZDB2,appname=null,moduleName=null,connectTime=177,dirtyIsolationLevel=false,initialIsolationLevel=2,infected=true,lastSuccessfulConnectionUse=1287423940605,secondsToTrustAnIdlePoolConnection=10,currentUser=java.lang.Exception
at weblogic.jdbc.common.internal.ConnectionEnv.setup(ConnectionEnv.java:308)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:314)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:427)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:316)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:93)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:61)
at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1473)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1272)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:425)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:382)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:338)
at org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)
at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423)
at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:139)
at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1547)
at org.hibernate.loader.Loader.doQuery(Loader.java:673)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236)
at org.hibernate.loader.Loader.doList(Loader.java:2220)
at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104)
at org.hibernate.loader.Loader.list(Loader.java:2099)
at org.hibernate.hql.classic.QueryTranslatorImpl.list(QueryTranslatorImpl.java:912)
at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121)
at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:811)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderPersistenceGenerated.findByPrimaryKey(OrderPersistenceGenerated.java:45)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImplStandard.findOrderByPrimaryKey(OrderManagementServiceImplStandard.java:1356)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKeyTx(OrderManagementServiceTransactionHandler.java:830)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.findOrderByPrimaryKey(OrderManagementServiceSessionBean.java:1276)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_ELOImpl.findOrderByPrimaryKey(OrderManagementEJB_yb2dzq_ELOImpl.java:19812)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceApplicationProxy.findOrderByPrimaryKey(OrderManagementServiceApplicationProxy.java:1289)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKey(OrderManagementServiceTransactionHandler.java:823)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImplStandard.findOrderByPrimaryKey(OrderManagementServiceImplStandard.java:1341)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKeyTx(OrderManagementServiceTransactionHandler.java:816)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.findOrderByPrimaryKey(OrderManagementServiceSessionBean.java:1255)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_ELOImpl.findOrderByPrimaryKey(OrderManagementEJB_yb2dzq_ELOImpl.java:7332)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceApplicationProxy.findOrderByPrimaryKey(OrderManagementServiceApplicationProxy.java:1266)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKey(OrderManagementServiceTransactionHandler.java:809)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.publishOrder(OrderManagementServiceImpl.java:1636)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.savePublishedOrder(OrderManagementServiceImpl.java:1606)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.savePublishedOrderTx(OrderManagementServiceTransactionHandler.java:3467)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.savePublishedOrder(OrderManagementServiceSessionBean.java:5272)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl.savePublishedOrder(OrderManagementEJB_yb2dzq_EOImpl.java:3263)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke2(Unknown Source)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke1(Unknown Source)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
,currentThread=Thread[[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads],lastUser=null,currentError=null,currentErrorTimestamp=null,JDBC4Runtime=true,supportStatementPoolable=true,needRestoreClientInfo=false,defaultClientInfo={} is set to be refreshed
at weblogic.jdbc.common.internal.ConnectionEnv.setRefreshNeeded(ConnectionEnv.java:518)
at weblogic.jdbc.wrapper.Connection.getVendorConnection(Connection.java:292)
at de.dpcom.persistence.hibernate.BinaryBlobType.nullSafeSet(BinaryBlobType.java:109)
at org.hibernate.type.CustomType.nullSafeSet(CustomType.java:146)
at org.hibernate.persister.entity.AbstractEntityPersister.dehydrate(AbstractEntityPersister.java:1997)
at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2371)
at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2307)
at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2607)
at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:92)
at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:140)
at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)
at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
at APPNAME-ROOT-PATH.components.customermanagement.biz.CertificatePersistenceGenerated.updateCertificate(CertificatePersistenceGenerated.java:116)
at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceImplStandard.updateCertificate(CustomerManagementServiceImplStandard.java:1282)
at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceTransactionHandler.updateCertificateTx(CustomerManagementServiceTransactionHandler.java:711)
at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceSessionBean.updateCertificate(CustomerManagementServiceSessionBean.java:1104)
at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementEJB_ap2i9a_ELOImpl.updateCertificate(CustomerManagementEJB_ap2i9a_ELOImpl.java:19199)
at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceApplicationProxy.updateCertificate(CustomerManagementServiceApplicationProxy.java:1101)
at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceImpl.publishCertificate(ProductionResultProcessingServiceImpl.java:1131)
at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceTransactionHandler.publishCertificateTx(ProductionResultProcessingServiceTransactionHandler.java:298)
at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceSessionBean.publishCertificate(ProductionResultProcessingServiceSessionBean.java:517)
at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceSessionBean_yaua6q_ELOImpl.publishCertificate(ProductionResultProcessingServiceSessionBean_yaua6q_ELOImpl.java:1804)
at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceApplicationProxy.publishCertificate(ProductionResultProcessingServiceApplicationProxy.java:471)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.publishCertificate(OrderManagementServiceImpl.java:1825)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.publishOrder(OrderManagementServiceImpl.java:1664)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.savePublishedOrder(OrderManagementServiceImpl.java:1606)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.savePublishedOrderTx(OrderManagementServiceTransactionHandler.java:3467)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.savePublishedOrder(OrderManagementServiceSessionBean.java:5272)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl.savePublishedOrder(OrderManagementEJB_yb2dzq_EOImpl.java:3263)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke2(Unknown Source)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke1(Unknown Source)
at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
####<18.10.2010 19:45 Uhr MESZ> <Info> <JDBC> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1287423940797> <BEA-001072> <Connection for XA pool "ZDB2" created.>
####<18.10.2010 19:45 Uhr MESZ> <Info> <JDBC> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1287423940808> <BEA-001132> <Initialized statement cache of size "10" for connection in pool "ZDB2".>
####<18.10.2010 19:45 Uhr MESZ> <Info> <Common> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1287423940808> <BEA-000628> <Created "1" resources for pool "ZDB2", out of which "1" are available and "0" are unavailable.>
Any suggestions?
Kind regards
Marc -
WLS6.0 sp2 / Win2k
Oracle 8.1.7 / Solaris 8
problem is if DB fails, the connection pool fails, and will not restart. If I run a java weblogic.Admin EXISTS_POOL command, it says the pool doesnt exist.
If i run a RESET_POOL, using the system user password, it comes back with:
Exception in thread "main" javax.naming.AuthenticationException. Root exception is java.lang.Securi
tyException: Authentication for user guest denied in realm weblogic
<<no stack trace available>>
I have test on reserved set (and dual as the table).
Anyone shed any light on what could be going wrong, because right now, every time the DB fails, we have to restart the **&$"&^ server.... (and that takes around 20mins for all the apps to init)
tks
willHi Will,
When you bring up the server, if the database is down, your connection pools
will not come up if you have an initial capacity greater than 0. This is a
known issue and the workaround for this is to set the initial capacity to
zero so the pool comes up even when the database is down, then make sure you
set the capacity increment to the value that you like your initial capacity
to be and have the TestConnectionOnReserve to true.
hth
sree
"Will" <[email protected]> wrote in message
news:3d13111f$[email protected]..
WLS6.0 sp2 / Win2k
Oracle 8.1.7 / Solaris 8
problem is if DB fails, the connection pool fails, and will not restart.If I run a java weblogic.Admin EXISTS_POOL command, it says the pool doesnt
exist.
If i run a RESET_POOL, using the system user password, it comes back with:
Exception in thread "main" javax.naming.AuthenticationException. Rootexception is java.lang.Securi
tyException: Authentication for user guest denied in realm weblogic
<<no stack trace available>>
I have test on reserved set (and dual as the table).
Anyone shed any light on what could be going wrong, because right now,every time the DB fails, we have to restart the **&$"&^ server.... (and that
takes around 20mins for all the apps to init)
>
tks
will -
Hi, guys
I use instant client 11.2.0.3.0 OCCI to create a connection pool, when create a connection from pool, it supposed using the existing connection, but the code created anohter new connection to database, any ideas? appreciate your help.
client side is running on Windows 7 32 bit, Database server is 10.2.05 on Solaris 10, development tool is MS VS 2010
here is the code:
Environment *env;
Connection *conn;
Statement *stmt;
string sqlStmt;
env = Environment::createEnvironment (Environment::THREADED_MUTEXED);
const string poolUserName = "scott";
const string poolPassword = "1234";
const string connectString = "192.168.0.70/orcl";
const string username = "scott";
const string passWord = "1234";
unsigned int maxConn =5;
unsigned int minConn = 2;
unsigned int incrConn = 1;
ConnectionPool *connPool = env->createConnectionPool(poolUserName, poolPassword, connectString, minConn, maxConn, incrConn);
try{
if (connPool)
cout << "SUCCESS - createConnectionPool" << endl;
else
cout << "FAILURE - createConnectionPool" << endl;
conn = connPool->createConnection (username, passWord); _// after this code, connection increase to 3 from 2._*
if (conn)
cout << "SUCCESS - createConnection" << endl;
else
cout << "FAILURE - createConnection" << endl;
}catch(SQLException ex)
cout<<"Exception thrown for createConnectionPool"<<endl;
cout<<"Error number: "<< ex.getErrorCode() << endl;
cout<<ex.getMessage() << endl;
......Hi Nicolas,
Have you tried to turn on testOnReserve setting of the coneection pool?
Regards,
"Nicolas Devos" <[email protected]> wrote in message
news:3c5fa916$[email protected]..
>
Hi,
I am using weblogic 6.1 and oracle 8.1.6, and experiences
problems with connections pools and database crash.
When the database server crashes during an EJB transactions,
the connection used by that transaction seems to be lost and
is never rebuilt when the database server restarts, therefore
the number of connections within the pool shrinks thoroughly
if I have several connections used while the database crashes
or is shutdown for maintenance.
If this db crash takes time to recover, all connections
are destroyed and the pool become unusable.
As soon as all connections have been 'destroyed' I have
the following exception:
'connection pool - none available' when trying to get
a connection.
When I restart the database server, the pool does not rebuilt
itself.
(I am using a test table to test the presence of the database
with a frequency set to 60s)
I did the same operation without EJB transactions and the pool
could rebuilt itself after the database has been restarted.
I had that problem with weblogic 6.0 already and in the
release notes of 6.0_sp2, 2 issues are fixed concerning
the pool fail-over: 044223 and 041793.
I would like to know if these issues are fixed in 6.1 as well,
and if they are related to my problem (Their description is
quite short).
Thank you
Nicolas -
Connection Pooling and JSP Custom Tag Library - is code (inside) the best way/correc?
Hi, can anyone advise as to whether my tag library code (based
on Apache Jakarta Project) will actually achieve connection
pooling functionality across my entire JSP based application? I
am slightly concerned that my OracleConnectionCacheImpl object
may exist multiple times, hence rendering my conection pooling
attempt useless.
package com.solved.tag.dbtags.connection;
import java.io.IOException;
import java.sql.Connection;
import java.sql.SQLException;
import javax.servlet.jsp.tagext.TagSupport;
import javax.servlet.jsp.JspTagException;
import javax.sql.DataSource;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import oracle.jdbc.pool.OracleConnectionCacheImpl;
* <p>JSP tag connection, used to get a
* java.sql.Connection object.</p>
* <p>JSP Tag Lib Descriptor
* <pre>
* <name>connection</name>
<tagclass>com.solved.tag.dbtags.connection.ConnectionTag</t
agclass>
* <bodycontent>JSP</bodycontent>
<teiclass>com.solved.tag.dbtags.connection.ConnectionTEI</t
eiclass>
* <info>Opens a connection based on a jndiName.</info>
* <attribute>
* <name>id</name>
* <required>true</required>
* <rtexprvalue>false</rtexprvalue>
* </attribute>
* </pre>
* @author Matt Shannon
public class ConnectionTag extends TagSupport {
static private OracleConnectionCacheImpl cache = null;
public int doStartTag() throws JspTagException {
try {
Connection conn = null;
if (cache == null) {
try {
InitialContext ic = new InitialContext();
DataSource ds = (DataSource) ic.lookup
("jdbc/pool/OracleCache");
cache = (OracleConnectionCacheImpl)ds;
catch (NamingException ne) {
throw new JspTagException(ne.toString());
conn = cache.getConnection();
pageContext.setAttribute(getId(),conn);
catch (SQLException e) {
throw new JspTagException(e.toString());
return EVAL_BODY_INCLUDE;
package com.solved.tag.dbtags.connection;
import java.sql.Connection;
import java.sql.SQLException;
import javax.servlet.jsp.tagext.TagSupport;
* <p>JSP tag closeconnection, used to close the
* specified java.sql.Connection.<p>
* <p>JSP Tag Lib Descriptor
* <pre>
* <name>closeConnection</name>
<tagclass>com.solved.tag.dbtags.connection.CloseConnectionTag&
lt;/tagclass>
* <bodycontent>empty</bodycontent>
* <info>Close the specified connection. The "conn"
attribute is the name of a
* connection object in the page context.</info>
* <attribute>
* <name>conn</name>
* <required>true</required>
* <rtexprvalue>false</rtexprvalue>
* </attribute>
* </pre>
* @author Matt Shannon
* @see ConnectionTag
public class CloseConnectionTag extends TagSupport {
private String _connId = null;
* The "conn" attribute is the name of a
* page context object containing a
* java.sql.Connection.
* @param connectionId
* attribute name of the java.sql.Connection to
close.
* @see ConnectionTag
public void setConn(String connectionId) {
_connId = connectionId;
public int doStartTag() {
try {
Connection conn = (Connection)pageContext.getAttribute
(_connId);
conn.close();
} catch (SQLException e) {
// failing to close a connection is not fatal
e.printStackTrace();
return EVAL_BODY_INCLUDE;
public void release() {
_connId = null;
package com.solved.tag.dbtags.connection;
import javax.servlet.jsp.tagext.TagData;
import javax.servlet.jsp.tagext.TagExtraInfo;
import javax.servlet.jsp.tagext.VariableInfo;
* TagExtraInfo for the connection tag. This
* TagExtraInfo specifies that the ConnectionTag
* assigns a java.sql.Connection object to the
* "id" attribute at the end tag.
* @author Matt Shannon
* @see ConnectionTag
public class ConnectionTEI extends TagExtraInfo {
public final VariableInfo[] getVariableInfo(TagData data)
return new VariableInfo[]
new VariableInfo(
data.getAttributeString("id"),
"java.sql.Connection",
true,
VariableInfo.AT_END
data-sources.xml:
<?xml version="1.0"?>
<!DOCTYPE data-sources PUBLIC "Orion data-
sources" "http://xmlns.oracle.com/ias/dtds/data-sources.dtd">
<data-sources>
<data-source
class="oracle.jdbc.pool.OracleConnectionCacheImpl"
name="jdbc/pool/OracleCache"
location="jdbc/pool/OracleCache"
url="jdbc:oracle:thin:@oracle1:1521:pdev"
>
<property name="maxLimit" value="15" />
<property name="cacheScheme" value="2" />
<property name="user" value="console" />
<property name="password" value="console" />
<description>
This DataSource is using an Oracle-native DataSource Class so as
to allow Oracle Specific extensions.
A getConnection() call on this DataSource will return
oracle.jdbc.driver.OracleConnection.
The connection returned is a logical connection.
The caching scheme in place is Fixed Wait. Refer below to
possible values.
Dynamic 1
Fixed Wait 2
Fixed Return Null 3
</description>
</data-source>
</data-sources>
many thanks,
Matt.Hi. Show me your pool definition.
Joe
Ramamurthy wrote:
I am using the jsp custom tag library from BEA called sqltags.tld which came with Weblogic 5.1. Currently I am using Weblogic6.1 sp2 on Solaris.
I have created a Connection Pool for Sybase database using the driver com.sybase.jdbc.SybDriver.
When I created jsp page to connect to the connection pool using sqltags custom tag library, I am getting the error
"javax.servlet.jsp.JspException: Failed to write body content
at weblogic.taglib.sql.ConnectionTag.doAfterBody(ConnectionTag.java:43)
at jsp_servlet.__hubwcdata._jspService(__sampletest.java:1014)"
After this message, whenever I try to access the same jsp page I am getting the message
"javax.servlet.jsp.JspException: Failed to load JDBC driver: weblogic.jdbc.pool.D
river
at weblogic.taglib.sql.ConnectionTag.doStartTag(ConnectionTag.java:34)
at jsp_servlet.__hubwcdata._jspService(__sampletest.java:205)".
Can you please help me the reason why this problem is happening and how to fix this ?
This problem doexn't happen consistently. This occurs once in a while.
I tried to increase Login delay Seconds parameter in the Connection Pool to 15 sec. It didn't help me much.
Thanks for your help !!!
Ram -
How To: Monitor usage of a connection pool
So I have a bunch of EJBs using a DB connection pool hosted under iAS
6sp2 on Solaris. How do I monitor pool usage? I would like to see
available pooled connections and in use connections - that would refresh
periodically.
The iAST tool has the monitor thing, which I turned on and added some
plots (active connection, and something else)...but those plots flat
lined and never showed any activity nor usefull information.
Can you hook up SNMP to an iAS? What about JMX? What are other
suggestions?
Thanks in advance,
Fred Welland
[email protected]
Intelix Inc.You can enable debug ( level = 1 ) at the pool level. This would throw some additonal information into kjs log. Unfortunately there is no time stamp with these lines. But you will get an ides of how your pool is performing during the test.
-
Help in creating the connection pool for Oracle 8i using Jdriver
Hi
Iam pretty new to Weblogic and would be greatfull if some one can help me
out in finding the parameters to be specified in Weblogic console for creating
a Connection pool for Oracle 8i database running on solaris. I have installed
necessary client libraries in weblogic machine.
The details for my database are as follows
database name : mydb
database server : 173.24.24.1
database port : 1521
username : myuser
I would appreciate if you can provide me the following details to be entered in
weblogic console for creating the connection pool
URL
DRIVER CLASS NAME
PROPERTIES
ACL NAME
PASSWORD
Thanks,
S HariHari
Jdbc Connection Pool Configuration
URL= jdbc:weblogic:oracle
DRIVER CLASS NAME=weblogic.jdbc.oci.Driver
PROPERTIES
user=myuser
password=<password in mydb>
server=mydb
After configuring Connection Pool Select Targets tab. Select Server from Available
to Chosen.
Deepak
Hari wrote:
Hi
Iam pretty new to Weblogic and would be greatfull if some one can help me
out in finding the parameters to be specified in Weblogic console for creating
a Connection pool for Oracle 8i database running on solaris. I have installed
necessary client libraries in weblogic machine.
The details for my database are as follows
database name : mydb
database server : 173.24.24.1
database port : 1521
username : myuser
I would appreciate if you can provide me the following details to be entered in
weblogic console for creating the connection pool
URL
DRIVER CLASS NAME
PROPERTIES
ACL NAME
PASSWORD
Thanks,
S Hari -
ORA-22881: dangling REF during getConnection() on stateless connection pool
Hello,
I have some trouble with "ORA-22881: dangling REF" error against getConnection() on a stateless connection pool.
Following the relevant part of the code:
return = gstatelessConnectionPool->getConnection( "scott[austin]",
"tiger",
"tag1");
Is anybody get rid of such problems.
I'm running Oracle 10.2.0.4.0 on Solaris.
Thanks,
YaakovThere is nothing much available on Metalink either for this error during an upgrade. I would advise you to get your accounting in order and raise the SR with Oracle support.
-
5.1.0 sp11 Connection pool refresh issue, revisited....again...!!!
"Hello,
From reading of these newsgroups I've seen many different manifestations
of what seems to be the same root cause with connection pools and
connections which are refreshed/replaced when found broken. In our
case weblogic server hangs.
Kit: 2xWeblogic 5.1.0 sp11 (not clusterd), Solaris 8,
java 1.3.1_01, 1xoracle 8.1.6, latest JDBC 2.0 drivers from oracle. Each weblogic instance and oracle have their own machines.
We do indeed have a firewall employed to run our subnets, and hence
our weblogic servers and oracle databses are in different DMZ's, but are
allowed to communicate to each other via rules set up on the firewall and
inspection of the logs show no such connections being dropped.
As far as the db is concerned, lookups (no writes) never take more than a few
hundred milliseconds and are then closed and given back to the connection pool
immediately from within the 'finally' block of code, hence hard to see when,if ever, the db is
is closing them due to excessive idle time.
weblogic.jdbc.connectionPool.RecipeDBPool=\
url=jdbc:oracle:thin:@foo:1521:BAA,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=30,\
maxCapacity=50,\
capacityIncrement=1,\Alkesh wrote:
Hi Joe,
The fix you suggested has been implemented and has been running fine
now for the past 3 days. I'm delighted with the result,Great. Glad to help.
but am concerned as to why this problem wasnt highlighted during our
load-testing phases...It's a possibility that your load-testing didn't present the same sort
of load that your actual runtime does.
Thanks for your time on this.Well sure. We want you successful.
Joe
Alkesh
At 01:52 PM 2/22/2002 +0000, you wrote:
Hi Joe,
Thanks for your reply
Please find attached a copy of the jvm thread dump we got from thelast time
that weblogic blocked upon trying to refresh a broken connection.
We have turned off JIT with the environment settingJAVA_COMPILER=NONE.
FYI hotspot is enabled with '-hotspot', these settings can be foundin the
attached 'startWeblogic.sh'.Hi. I found a serious problem by reading the thread dump:
"ExecuteThread-11" daemon prio=5 tid=0x179d40 nid=0x19 waiting for
monitor entry
[0xeee80000..0xeee819e0]
at java.sql.DriverManager.getConnection(DriverManager.java:144)
- waiting to lock <f8e77ad0> (a java.lang.Class)
at com.akqa.sainsburys.jv_recipe.ejb.session.RecipeBean.getConnection(Re
cipeBean.java:759)
It is important to never call DriverManager methods in a multithreaded
application
such as Weblogic, because these JVM methods are alloverly synchronized
at
the class level. One such method, DriverManager.println(), is called
continuously
by all JDBC drivers as well as the SQLException constructor. If one
server thread
makes a long-lasting or hanging call to DriverManager.getConnection(),
it can halt
all JDBC in the whole JVM including work on other open driver
connections.
Please show me the code for RecipeBean.java, and I will send you an
altered version
that should solve this problem. In fact, I can infer from the thread
dump what is needed.
Change the one method getConnection() to this:
// Make once and re-use a driver instance directly, avoiding
DriverManager
Driver d = (Driver)class.forName("weblogic.jdbc.jts.Driver").newInstance();
public Connection getConnection()
return d.connect("jdbc:weblogic:jts:yourPoolNameHere", null );
Also, change your pool definition. I assume you have
testConnsOnReserve set to true.
(You should). Also, you should change your refresh minutes to
something huge, like
9999999. The refresh is interfering with your online performance and
is unnecessary
if you have testConnsOnReserve set. I recommend:
weblogic.jdbc.connectionPool.RecipeDBPool=\
url=jdbc:oracle:thin:@foo:1521:BAA,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=50,\ <------ note that this should be the
same as max, so all cons are made at startup
maxCapacity=50,\
testTable=dual,\
testConnsOnReserve=true,\
refreshTestMinutes=9999999,\
etc.
Joe
I've also attached some firewall logs around the time of weblogicblocking
(12.09). I could only get screen dumps for you, this may or maynot be
useful.
For the firewall logs use the following legend :-
195.110.64.205 - DNS
172.16.160.195 - host webserver 1 (i.e. what our licenses are boundto)
172.16.160.196 - host webserver 2
172.16.160.220 - website 1
172.16.160.230 - website 2
Thanks
Alkesh
-----Original Message-----
From: Joe [mailto:[email protected]]
Sent: 20 February 2002 22:09
To: [email protected]
Subject: Re: 5.1.0 sp11 Connection pool refresh issue,
revisited....again...!!!
At 02:47 PM 2/20/2002 +0000, you wrote:
Hi Joe,
Please find attached a copy of our thread dumps for the most recentoccasion
that weblogic server has stopped.
Apologies for any misunderstandings with my previous post, it appears to
have been cropped. Full posting below (yes we do have testConnOnReserve and
testTable properties set).
Thanks for your time.sure, but first let's get you running OK. These dumps seem to be
very cryptic, as if you're running a highly optimized JVM that
loses almost all of the Java class references I'd normally see.
Can you run again with a more basic JVM? I am beginning to suspect
the JIT JVM...
Joe
Alkesh
Joseph Weinstein wrote:
Hello,
From reading of these newsgroups I've seen many
different manifestations of what seems to be the sameroot cause with connection pools and connections
which are refreshed/replaced when found broken. In our
case weblogic server hangs.
Kit: Weblogic 5.1.0 sp11 (not clusterd),
Solaris 8, java 1.3.1_01, oracle 8.1.6,
latest JDBC 2.0 drivers from oracle.
We do indeed have a firewall employed to run our subnets,
and hence our weblogic servers and oracle databses are
in different DMZ's, but are allowed to communicate to each
other via rules set up on the firewall and inspection of
the logs show no such connections being dropped.
As far as the db is concerned, lookups (no writes) never
take more than a few hundred milliseconds and are then
closed and given back to the connection pool immediately
from within the 'finally' block of code, hence hard to
see when,if ever, the db is is closing them due to excessive idle time.
weblogic.jdbc.connectionPool.RecipeDBPool=\
url=jdbc:oracle:thin:@foo:1521:BAA,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=30,\
maxCapacity=50,\
capacityIncrement=1,\
allowShrinking=false,\
testTable=dual,\
testConnsOnReserve=true,\
shrinkPeriodMins=1,\
refreshTestMinutes=10,\ // has been 1 and 5 but 10 'more' stable.
Fequently however, connections are found to be broken
(either by periodical refresh - refreshTestMinutes or
testing connection before granting it to the
application - testConnsOnReserve=true), this has been
confirmed by viewing JDBC.log .
When this is so, weblogic attempts to replace these
broken connections with new ones and then proceeds
to grant it to the application. Once in a while however
(and by no means 'x' refreshes later), weblogic will not
come back.
One of 2 errors occur in our deployment which cuase weblogic
to refresh a connection.
<JDBC Pool RecipeDBPool> java.sql.SQLException: No more data to read fromsocket
and
<JDBC Pool RecipeDBPool> java.sql.SQLException: Io exception: Broken pipe
I believe these settings to all be correct, JDBC drivers
in the correct point BEFORE weblogic.aux in classpath, yet
still have the issue of broken connections.
Any ideas ? I've been reading a lot into this probelm
on various postings now, and i'm completely stumped.
Thanks for your time.
Alkesh -
Hello All,
Environment details: OBIEE - 10.1.3.4.1 on 10gAS , Solaris 10. Single Node
We are implementing OBIEE in our organization and every quarter we add more number of data sources, dashboards and users. Recently we have started observing slowness while logging in. After crosschecking we have observed that not having separate connection pools for session variables might be one of the issue.
Before defining any new connection pools, we would like to take a proper step to design our connection pools. But we are unable to locate proper resources for monitoring the connection pool usage at a give point of time. Ideally we would to automate a job which will collect statistics of all available connection pools, users at a decent level of detail. This can help us in identifying the pattern of usage and further help us in defining an optimal connection pool strategy.
Could someone please guide me to a proper resource ? Can UDML help me here ? Any tips?
Thanks a lot for your help.
~Ravi.MAs far as I know there isn't any way of checking the connection pool usage from the OBIEE layer. But your DBA should able to queries to monitor the OBIEE connection usage from the database side. As for your question about designing connections pools the documentation is very extensive on this subject, have you reviewed the relevant section in the server Administration Guide?
After crosschecking we have observed that not having separate connection pools for session variables might be one of the issue.This is specifically mentioned in the documentation, you should separate connections for your Init Blocks. Also you should try to consolidate Init Blocks to reduce the database call overhead. In addition to this I can mention that most login problems relate to Init Blocks taking long to run rather than connection pool issues. Make sure your Init Blocks return data quickly. Also if you have a lot of session init blocks you may want to set some depencies between them. Suppose you have 10 session init blocks. If two users login at the same time OBIEE will try to run all those queries at the same time, should the max connections be set that high (20). By setting some execution depencies in your Init Blocks you can control the execution to reduce the parallelism and make them to run a bit more serial reducing the connection pool usage. -
JDBC Connection Pool to DB2 database - Problem
When trying to create a new JDBC Connection Pool in WebLogic using BEA Type 4 driver
for DB2, I get the following error:
[BEA][DB2 JDBC Driver]A commitment command has been received on a protected conversation.
The commit and rollback commands are not allowed on protected conversations.
DB2 v8.1 Enterprise Edition on Sun Solaris v8
WebLogic 8.1 SP2 on Windows 2000/XP
Please help!Sorry forgot to add the exception, this is the exception,
java.sql.SQLException: RSR0029: Missing Password for Application Authorization
Any idea as when we get this exception? -
Startup problems with XA connection pools on Oracle and WLS 6.1
I am having starup problems trying to set up a WLS 6.1 connection pool using
XA. When I try to start the server, I get the following exception:
<Nov 19, 2001 3:06:28 PM EST> <Error> <JDBC> <Cannot startup connection pool
"dbdev1XAPool" weblogic.common.ResourceException: java.sql.SQLException:
open failed for XAResource 'dbdev1' with error XAER_RMERR : A resource
manager error has occured in the transaction branch. Check Oracle XA trace
file(s) (if any) for database errors. The Oracle XA trace file(s) are
located at the directory where yo
u start the Weblogic Server, and have names like
xa_<pool_name><MMDDYYYY>.trc.
at weblogic.jdbc.oci.xa.XAConnection.<init>(XAConnection.java:58)
at
weblogic.jdbc.oci.xa.XADataSource.getXAConnection(XADataSource.java:600)
at
weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnec
tionEnvFactory.java:194)
at
weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnec
tionEnvFactory.java:54)
at
weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
ava:698)
at
weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
at
weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:620
at
weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:329)
The contents of the Oracle trace file:
ORACLE XA: Version 8.1.7.0.0. RM name = 'Oracle_XA'.
150627.1312:344.344.330727191:
xaoopen:
xa_info=Oracle_XA+Acc=P/cmauser/admin+SesTm=100+DB=dbdev1+Threads=true+LogDi
r=.+DbgFl=0x15,rmid=330727191,flags=0x0
150627.1312:344.344.330727191:
ORA-12560: TNS:protocol adapter error
150627.1312:344.344.330727191:
xaolgn_help: XAER_RMERR; OCIServerAttach failed. ORA-12560.
150627.1312:344.344.330727191:
xaoopen: return -3
I am running WLS 6.1 and Oracle 8.1.7 on windows (separate machines). The
connection pool settings are:
<JDBCConnectionPool CapacityIncrement="0"
DriverName="weblogic.jdbc.oci.xa.XADataSource" InitialCapacity="40"
MaxCapacity="40" Name="dbdev1XAPool"
Properties="user=cmauser;password=admin;dataSourceName=dbdev1"
RefreshMinutes="15" ShrinkingEnabled="false" SupportsLocalTransaction="true"
Targets="cmatest" TestTableName="hppcontentsource" />
I have not had any problems connecting to the same database through regular
JDBC connection pools or through the utils.dbping utility.
What am I doing wrong?This is a dup message. Add "DebugConfigInfo OFF" in httpd.conf.
Jong
[email protected] (Olaf Foellinger) wrote:
>
Hi,
we're trying to setup apache on linux so that it's forwarding all jsp
requests to Bea WLS 6.0 on Solaris. We've installed the mod_wl.so
modules according to the documentation. When apache starts it shows the
following warning:
[Tue Jan 9 13:22:55 2001] [warn] Loaded DSO
/usr/lib/apache/1.3/mod_wl.so uses plain Apache 1.3 +API, this module
might crash under EAPI! (please recompile it with -DEAPI)
and in fact, when we try to load a jsp page we get
[Tue Jan 9 13:29:14 2001] [notice] child pid 5780 exit signal
Segmentation fault (11)
Does anyone have a working solution ? Can bea provide us with a plugin
compiled with EAPI ?
Greetings Olaf -
Principals for connection pools
We are using a dbms realm for our application on a Bea WeblogicServer
5.1 on Solaris
7.
It seems that it is not possible to use a group as principal for
a connection pool in the
weblogic.properties file. This results in a SecurityException when
a user which is a
member of the corresponding group tries to get a connection from
the connection pool.
Does anybody have similar problems or even better a solution or
explanation for this
problem?
Dieter Arnold
GFT Technologies AG
Curiestr. 5
D-70563 Stuttgart-Vaihingen
Tel:+49-711-62042-100, Fax: +49-711-62042-101,
mailto:[email protected]
http://www.gft.comprobably not your problem, but groupnames and usernames should
be unique in weblogic, so if you happen to have a user with the
same name as the group you are trying to use, it would confuse
the server.
but, like I said, probably not your problem.
-Don
"Ken Hu" <[email protected]> wrote:
Dieter,
I got the same problem as yours when I am working with
WLS 5.1:
I have a connection pool set up in the weblogic.properties
file and a Oracle
RDBMSRealm. And there is an acl entry in the database
indicating that a
certain group has 'reserve' right to the connection pool.
Then when one user which in fact belongs to that group
try to use the
connection pool, he will get SecurityException saying
that he doesn't has a
reserve right. But when I change group name of the acl
entry to that user,
he is able to use the connection pool. All seems that
I can't use a group as
principal in the Connection Pool acl settings.
But when I used WLS6.0, the problem disappeared. Does
anybody have any idea?
Thanks,
Ken
Tom Mitchell <[email protected]> wrote in message news:[email protected]..
Dieter,
I am not sure I understand what you are trying to do.a group is a
collection of users and does not have a password. Canyou explain what
you are trying to accomplish?
Thanks.
Dieter Arnold wrote:
It seems that it is not possible to use a group as
principal for
a connection pool in the
weblogic.properties file. This results in a SecurityExceptionwhen
a user which is a--
Tom Mitchell
[email protected]
Very Current Stoneham, MA Weather
http://www.tom.org
Maybe you are looking for
-
I just don't want my brother or anybody else to have access to my iCloud or my money in my AppleID.
-
Access to view blocking sessions in sql server 2008
Hi, One of my client wrote a stored procedure. we scheduled this SP in a job. while job is running, it is blocking other sessions. It is happening frequently. So, client is asking me to grant permission to view blocking session( want to execute sp_wh
-
Modification of program LRRSVF20
Hi Experts, I am applying doc "How to....Report Data in Alternate Units of Measure" in BW3.5 Can you mention OSS Note to modify program LRRSVF20 for unit conversion? Useful answer will be rewarded with suitable points. Thanks in advance! Sapna
-
HEEELP: Recreate procedure for Essbase.sec file in 11.1.2.0
Hi, What is the procedure to re-create Essbase.sec file in Essbase 11.1.2.0 environment.... In older versions it was used to delete Essbase.sec, start Essbase server and it was recreated an empty essbase.sec file.. But in 11.1.2.0 with Shared service
-
Email for users / processor in outlook
Hi Friends, We have configured support help desk for solution Mgr. I want to understand what is the std. method of getting mail to users / message processor when ever messge is created / answer to given. I think in this we get mails in SAP Inbox. Can