ORABPEL START-UP ERROR!!!!!!!! - Connection Pool Deployment failure

I have installed BPEL Process Manager with Weblogic 8.1SP4.
I am using Oracle Database 9.2.0.5.0 for Oracle BPEL Process
Manager installation.
Also i have made following changes for JDBC thin driver accordingly.
<JDBCConnectionPool CapacityIncrement="2"
DriverName="oracle.jdbc.OracleDriver"
MaxCapacity="15" LoginDelaySeconds="1"
Name="BPELServerPool"
ShrinkPeriodMinutes="15"
ShrinkingEnabled="true" SupportsLocalTransaction="true"
Targets="orabpelServer"
URL="jdbc:oracle:thin:orabpel/orabpel_password@hostname:port:database_servoce_
name"/>
I m getting following error while starting the server :-
Connection Pool "BPELServerPool" deployment failed with the following error: 0:Could not create pool connection. The DBMS driver exception was: invalid arguments in call.
Also I m getting following error during startup
ORABPEL-04076
Cannot lookup jdbc datasource.
The process domain was unable to lookup the TX datasource "BPELServerDataSourceWorkflow".
Please check that the machine hosting the datasource is physically connected to the network. Additionally check that the connection pool properties as defined in the application server startup properties are valid.
at com.collaxa.cube.engine.data.ConnectionFactory$ConnectionFactoryImpl.init(ConnectionFactory.java:268)
at com.collaxa.cube.engine.data.ConnectionFactory.update(ConnectionFactory.java:54)
at com.collaxa.cube.engine.data.ConnectionFactory.init(ConnectionFactory.java:42)
at com.collaxa.cube.admin.data.ServerConnectionFactory.init(ServerConnectionFactory.java:34)
at com.collaxa.cube.admin.adaptors.ServerAdaptorManager.init(ServerAdaptorManager.java:66)
at com.collaxa.cube.admin.ServerManager.__init(ServerManager.java:211)
at com.collaxa.cube.admin.ServerManager.init(ServerManager.java:99)
at com.collaxa.cube.ejb.impl.ServerBean.init(ServerBean.java:200)
at com.collaxa.cube.ejb.impl.ServerBean_g9inc6_EOImpl.init(ServerBean_g9inc6_EOImpl.java:856)
at com.collaxa.cube.admin.CXLoaderServlet.init(CXLoaderServlet.java:62)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1028)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:904)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:883)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:822)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3333)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3278)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3259)
at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5949)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:862)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2127)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2168)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2115)
at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:3082)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1751)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:359)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
<Error> <HTTP> <BEA-101216> <Servlet: "cxloader" failed to preload on startup in Web application: "startup".
javax.servlet.ServletException:
ORABPEL START-UP ERROR!!!!!!!!
Can Anyone kindly suggest what is the problem ?

Similar Messages

Unable to start the Universal Connection Pool error

Hi,
I am trying to deploy two instances of one and the same web application on Tomcat 6. I have application test.war, I have copied and renamed it to test2.war and moved both wars in Tomcat' webapps folder. One of those (which Tomcat decides to start first) correctly gets connection from PoolDataSourceFactory.getPoolDataSource() and works fine, but the second throws this exception while trying to get database connection.
Please help,
Thanks
java.sql.SQLException: Unable to start the Universal Connection Pool: java.sql.SQLException: Unable to start the Universal Connection Pool: oracle.ucp.UniversalConnectionPoolException: MBean exception occurred while registering or unregistering the MBean
at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:541)
at oracle.ucp.jdbc.PoolDataSourceImpl.throwSQLException(PoolDataSourceImpl.java:587)
at oracle.ucp.jdbc.PoolDataSourceImpl.startPool(PoolDataSourceImpl.java:276)
at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:646)
at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:613)
at oracle.ucp.jdbc.PoolDataSourceImpl.getConnection(PoolDataSourceImpl.java:607)
at com.avalonsql.core.db.connection.ConnectionWrapper.<init>(ConnectionWrapper.java:26)
... 31 more
Caused by: java.sql.SQLException: Unable to start the Universal Connection Pool: oracle.ucp.UniversalConnectionPoolException: MBean exception occurred while registering or unregistering the MBean
at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:541)
at oracle.ucp.jdbc.PoolDataSourceImpl.throwSQLException(PoolDataSourceImpl.java:587)
at oracle.ucp.jdbc.PoolDataSourceImpl.startPool(PoolDataSourceImpl.java:247)
... 35 more
Caused by: oracle.ucp.UniversalConnectionPoolException: MBean exception occurred while registering or unregistering the MBean
at oracle.ucp.util.UCPErrorHandler.newUniversalConnectionPoolException(UCPErrorHandler.java:421)
at oracle.ucp.util.UCPErrorHandler.newUniversalConnectionPoolException(UCPErrorHandler.java:389)
at oracle.ucp.admin.UniversalConnectionPoolManagerMBeanImpl.getUniversalConnectionPoolManagerMBean(UniversalConnectionPoolManagerMBeanImpl.java:149)
at oracle.ucp.jdbc.PoolDataSourceImpl.startPool(PoolDataSourceImpl.java:242)
... 35 more
Caused by: java.security.PrivilegedActionException: javax.management.InstanceAlreadyExistsException: oracle.ucp.admin:name=UniversalConnectionPoolManagerMBean
at java.security.AccessController.doPrivileged(Native Method)
at oracle.ucp.admin.UniversalConnectionPoolManagerMBeanImpl.getUniversalConnectionPoolManagerMBean(UniversalConnectionPoolManagerMBeanImpl.java:136)
... 36 more
Caused by: javax.management.InstanceAlreadyExistsException: oracle.ucp.admin:name=UniversalConnectionPoolManagerMBean
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
at oracle.ucp.admin.UniversalConnectionPoolManagerMBeanImpl$2.run(UniversalConnectionPoolManagerMBeanImpl.java:142)
... 38 more

I was getting the following exception.. However after setting the property ConnectionFactoryClassName, it went off..
Caused by: java.sql.SQLException: Invalid Universal Connection Pool configuration: java.sql.SQLException: Unable to create factory class instance with provided factory class name: java.lang.ClassNotFoundException:
 at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:541)
 at oracle.ucp.jdbc.PoolDataSourceImpl.throwSQLException(PoolDataSourceImpl.java:587)
 at oracle.ucp.jdbc.PoolDataSourceImpl.createUniversalConnectionPool(PoolDataSourceImpl.java:523)
 at oracle.ucp.admin.UniversalConnectionPoolManagerBase.createConnectionPool(UniversalConnectionPoolManagerBase.java:554)
 ... 92 more
Caused by: java.sql.SQLException: Unable to create factory class instance with provided factory class name: java.lang.ClassNotFoundException:
 at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:541)
 at oracle.ucp.jdbc.PoolDataSourceImpl.throwSQLException(PoolDataSourceImpl.java:587)
 at oracle.ucp.jdbc.PoolDataSourceImpl.initConnectionFactory(PoolDataSourceImpl.java:2457)
 at oracle.ucp.jdbc.PoolDataSourceImpl.createUniversalConnectionPool(PoolDataSourceImpl.java:386)
 ... 93 more
Caused by: java.lang.ClassNotFoundException:
 at java.lang.Class.forNameImpl(Native Method)
 at java.lang.Class.forName(Class.java:169)
 at oracle.ucp.jdbc.PoolDataSourceImpl.initConnectionFactory(PoolDataSourceImpl.java:2444)
 ... 94 more
Edited by: user7953709 on Aug 26, 2011 1:08 AM

Weblogic server not starting due to connection pool error.

Hi all,
We have some issues with the network due to that, weblog server not able to create the connection pool or make physical connection with the database in the allocated time, we need to increase the timeout so that weblogic can wait and create a connection and then start the apps. How to achieve this?
Currently the server crashes and forcing to shutdown the error listed below
<Oct 10, 2012 5:08:47 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "oltpDS": IO Error: Socket read timed out>
<Oct 10, 2012 5:09:48 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "oltpDS": IO Error: Socket read timed out>
<Oct 10, 2012 5:10:49 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "oltpDS": IO Error: Socket read timed out>
<Oct 10, 2012 5:10:50 PM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'oltpDS' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
 at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:302)
 at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
 Truncated. see log file for complete stacktrace
Caused By: weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: Socket read timed out
 at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:276)
 at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1249)
 at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1166)
 at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:249)
 at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1155)
 Truncated. see log file for complete stacktrace
javax.naming.NameNotFoundException: Unable to resolve 'oltpDS'. Resolved ''; remaining name 'oltpDS'
 at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
 at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
 at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
 at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
 at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
 at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
 at javax.naming.InitialContext.lookup(InitialContext.java:392)
 at com.healthedge.j2ee.PooledConnectionHelper.addDataSource(PooledConnectionHelper.java:202)
 at com.healthedge.j2ee.PooledConnectionHelper.getSTConnection(PooledConnectionHelper.java:281)
 at com.healthedge.j2ee.PooledConnectionHelper.getConnectionIgnoreTxn(PooledConnectionHelper.java:268)
 at com.healthedge.j2ee.PooledConnectionHelper.getConnection(PooledConnectionHelper.java:251)
 at com.healthedge.query.execution.Query.prepareStatement(Query.java:504)
 at com.healthedge.query.execution.Query.setValue(Query.java:716)
 at com.healthedge.config.util.ReferenceResolutionHelper.setConstraintValues(ReferenceResolutionHelper.java:277)
 at com.healthedge.config.util.ReferenceResolver.getTypeReference(ReferenceResolver.java:232)
 at com.healthedge.config.util.ReferenceResolver.resolveTypeReference(ReferenceResolver.java:221)
 at com.healthedge.config.util.ReferenceResolver.resolveTypeReference(ReferenceResolver.java:211)
 at com.healthedge.config.util.ReferenceResolver.resolveTypeReference(ReferenceResolver.java:187)
 at com.healthedge.config.util.ReferenceResolver.resolveTypeReference(ReferenceResolver.java:156)
 at com.healthedge.config.eval.HicIdentifier.getReference(HicIdentifier.java:58)
 at com.healthedge.startup.StartupService.startup(StartupService.java:56)
 at com.healthedge.startup.wl.WLStartupService.main(WLStartupService.java:13)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeMain(ClassDeploymentManager.java:362)
 at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:272)
 at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
 at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:214)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:207)
 at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployments(ClassDeploymentManager.java:186)
 at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsAfterAppAdminState(ClassDeploymentManager.java:162)
 at weblogic.management.deploy.classdeployment.StartupClassPrelistenService.start(StartupClassPrelistenService.java:13)
 at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
NESTED TRACES DONE
>
<Oct 10, 2012 5:11:18 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Oct 10, 2012 5:11:18 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Oct 10, 2012 5:11:18 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

Hi,
It looks like your DB is down for now and that is reason why the server cannot initialize your App while startup.
Check which Data source you are using and make initial capacity as zero and try to restart the server again.
Note: you need to do this changes from JMS module under %Domain_Home% / config / jdbc/
Regards,
Kal

Error: : connection pool does not exist

I am getting a Connection pool does not exitst Error on starting Web
Logic. When i Checked on http://localhost:8002/console ->
jdbc-connectionpools
Productionpool(name of the connection pool), I checked the testing tab
it shows it is unavailable while it shows Deployed=true on the
Configuraton tab.
It is failing on my system while its working on other systems. I am
using weblogicSP4_814
Can u pls provide me some solution for this error.
<Jun 16, 2006 4:33:11 PM IST> <Warning> <JDBC> <BEA-001129> <Received
exception while creating connection for pool "noti
fJMSJDBCConnPool": access denied (java.util.PropertyPermission
oracle.net.wallet_location read)>
<Jun 16, 2006 4:33:12 PM IST> <Warning> <JDBC> <BEA-001129> <Received
exception while creating connection for pool "noti
fJMSJDBCConnPool": access denied (java.util.PropertyPermission
oracle.net.wallet_location read)>
<Jun 16, 2006 4:33:13 PM IST> <Error> <JDBC> <BEA-001150> <Connection
Pool "notifJMSJDBCConnPool" deployment failed with
the following error: 0:Could not create pool connection. The DBMS
driver exception was: access denied (java.util.Proper
tyPermission oracle.net.wallet_location read).>
<Jun 16, 2006 4:33:13 PM IST> <Warning> <JDBC> <BEA-001129> <Received
exception while creating connection for pool "prod
uctionPool": access denied (java.util.PropertyPermission
oracle.net.wallet_location read)>
<Jun 16, 2006 4:33:14 PM IST> <Warning> <JDBC> <BEA-001129> <Received
exception while creating connection for pool "prod
uctionPool": access denied (java.util.PropertyPermission
oracle.net.wallet_location read)>
<Jun 16, 2006 4:33:15 PM IST> <Error> <JDBC> <BEA-001150> <Connection
Pool "productionPool" deployment failed with the f
ollowing error: 0:Could not create pool connection. The DBMS driver
exception was: access denied (java.util.PropertyPerm
ission oracle.net.wallet_location read).>
<Jun 16, 2006 4:33:15 PM IST> <Error> <JDBC> <BEA-001151> <Data Source
"notifJMSJDBCConnPool" deployment failed with the
following error: DataSource(weblogic.jdbc.jts.notifJMSJDBCConnPool)
can't be created with non-existent Pool (connection
or multi) (notifJMSJDBCConnPool).>
<Jun 16, 2006 4:33:15 PM IST> <Error> <JDBC> <BEA-001151> <Data Source
"productionPool" deployment failed with the follo
wing error: DataSource(weblogic.jdbc.jts.productionPool) can't be
created with non-existent Pool (connection or multi) (
productionPool).>
<Jun 16, 2006 4:33:15 PM IST> <Alert> <JMS> <BEA-040052> <JMSServer
"NotificationJMSServer" store failed to open java.io
.IOException: JMS JDBC store, connection pool = <notifJMSJDBCConnPool>,
prefix = <notif>: connection pool does not exist
java.io.IOException: JMS JDBC store, connection pool =
<notifJMSJDBCConnPool>, prefix = <notif>: connection pool does no
t exist
at
weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:488)
at
weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
at weblogic.jms.backend.BEStore.open(BEStore.java:262)
at weblogic.jms.backend.BEStore.start(BEStore.java:151)
at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentÂTarget.java:337)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymenÂtTarget.java:597)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(ÂDeploymentTarget.java:575)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeployÂmentTarget.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3Â9)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpÂl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpÂl.java:755)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:Â734)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeÂanImpl.java:516)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at
weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeÂanServerImpl.java:990)
at
weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerÂImpl.java:948)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
at
weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.javÂa:475)
at
weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerÂMBean_Stub.java:7731)
at
weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlavÂeDeployer.java:1321)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:33Â9)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeplÂoymentManagerServerLifeCycleImpl.j
ava:229)
at
weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
<Jun 16, 2006 4:33:15 PM IST> <Error> <JMS> <BEA-040123> <Failed to
start JMS Server "NotificationJMSServer" due to webl
ogic.jms.common.JMSException: JMS can not open store notifJMSJDBCStore.
weblogic.jms.common.JMSException: JMS can not open store
notifJMSJDBCStore
at weblogic.jms.backend.BEStore.start(BEStore.java:163)
at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentÂTarget.java:337)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymenÂtTarget.java:597)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(ÂDeploymentTarget.java:575)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeployÂmentTarget.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3Â9)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpÂl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpÂl.java:755)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:Â734)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeÂanImpl.java:516)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at
weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeÂanServerImpl.java:990)
at
weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerÂImpl.java:948)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
at
weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.javÂa:475)
at
weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerÂMBean_Stub.java:7731)
at
weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlavÂeDeployer.java:1321)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:33Â9)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeplÂoymentManagerServerLifeCycleImpl.j
ava:229)
at
weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
Caused by: java.io.IOException: JMS JDBC store, connection pool =
<notifJMSJDBCConnPool>, prefix = <notif>: connection p
ool does not exist
at
weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:488)
at
weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
at weblogic.jms.backend.BEStore.open(BEStore.java:262)
at weblogic.jms.backend.BEStore.start(BEStore.java:151)
... 29 more
<Jun 16, 2006 4:33:32 PM IST> <Warning> <HTTP> <BEA-101248>
<[D:\Build\autodeploys\i2\weblogic_home\config\vendavo\.\app
lications\.wlnotdelete\wlap12518\vendavo.war]: Deployment descriptor
"web.xml" is malformed. Check against the DTD: org.
xml.sax.SAXParseException: The content of element type "web-app" must
match "(icon?,display-name?,description?,distribut
able?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapÂping*,session-config?,mime-mapping*,welcome-f
ile-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-consÂtraint*,login-config?,security-role*,env-entr
y*,ejb-ref*,ejb-local-ref*)". (line 252, column 11).>
java.lang.ExceptionInInitializerError
at com.vendavo.cl.ClassHelper.<clinit>(ClassHelper.java:28)
at
com.vendavo.cl.io.ResourceHelper.addLoader(ResourceHelper.java:121)
at
com.vendavo.cl.io.ResourceHelper.<init>(ResourceHelper.java:39)
at
com.vendavo.cl.io.ResourceHelper.<clinit>(ResourceHelper.java:29)
at
com.vendavo.platform.action.StartupAction.init(StartupAction.java:75)
at
com.vendavo.platform.action.StartupAction.contextInitialized(StartupAction.Âjava:311)
at
weblogic.servlet.internal.WebAppServletContext$FireContextListenerAction.ruÂn(WebAppServletContext.java:7044)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubjeÂct.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at
weblogic.servlet.internal.WebAppServletContext.notifyCreated(WebAppServletCÂontext.java:1753)
at
weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServlÂetContext.java:3352)
at
weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:727)
at
weblogic.servlet.internal.WebService.preloadResources(WebService.java:486)
at
weblogic.servlet.internal.ServletInitService.resume(ServletInitService.javaÂ:30)
at
weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
Caused by: java.security.AccessControlException: access denied
(java.util.PropertyPermission * read,write)
at
java.security.AccessControlContext.checkPermission(AccessControlContext.javÂa:269)
at
java.security.AccessController.checkPermission(AccessController.java:401)
at
java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
at
java.lang.SecurityManager.checkPropertiesAccess(SecurityManager.java:1243)
at java.lang.System.getProperties(System.java:501)
at
com.vendavo.cl.property.AppProperties.loadSystemProperties(AppProperties.jaÂva:411)
at
com.vendavo.cl.property.AppProperties.loadBasics(AppProperties.java:326)
at
com.vendavo.cl.property.AppProperties.getInstance(AppProperties.java:160)
at com.vendavo.cl.log.VLog.loadAppProperties(VLog.java:134)
at com.vendavo.cl.log.VLog.createDefaultSetup(VLog.java:94)
at com.vendavo.cl.log.VLog.<clinit>(VLog.java:66)
... 18 more
<Jun 16, 2006 4:33:34 PM IST> <Warning> <HTTP> <BEA-101162> <User
defined listener com.vendavo.platform.action.StartupAc
tion failed: java.lang.NoClassDefFoundError.>
<Jun 16, 2006 4:33:34 PM IST> <Warning> <HTTP> <BEA-101162> <User
defined listener com.vendavo.platform.action.StartupAc
tion failed: java.lang.NoClassDefFoundError.>
<Jun 16, 2006 4:33:34 PM IST> <Error> <HTTP> <BEA-101216> <Servlet:
"AdminServlet" failed to preload on startup in Web a
pplication: "soap".
Thanks in Advance,
Ketan.B.Parekh

ketan parekh wrote:
I am getting a Connection pool does not exitst Error on starting Web
Logic. When i Checked on http://localhost:8002/console ->
jdbc-connectionpools
Productionpool(name of the connection pool), I checked the testing tab
it shows it is unavailable while it shows Deployed=true on the
Configuraton tab.
It is failing on my system while its working on other systems. I am
using weblogicSP4_814
Can u pls provide me some solution for this error. Hi. Would you run the utils.dbping utility, and then
give it the arguments to connect to the same DBMS with
the same user as your pool? Show me the exception you
get if it fails:
C:\bea81sp5\weblogic81>java utils.dbping
Usage: java utils.dbping DB2B [-d dynamicSections] USER PASS HOST:PORT/DBNAME
or java utils.dbping JCONN2 USER PASS HOST:PORT/DBNAME
or java utils.dbping JCONNECT USER PASS HOST:PORT/DBNAME
or java utils.dbping INFORMIXB USER PASS HOST:PORT/DBNAME/INFORMIXSERVER
or java utils.dbping MSSQLSERVER4 USER PASS HOST:PORT/DBNAME
or java utils.dbping MSSQLSERVER4 USER PASS [DBNAME@]HOST[:PORT]
or java utils.dbping MSSQLSERVERB USER PASS HOST:PORT/DBNAME
or java utils.dbping ORACLE USER PASS DBNAME
or java utils.dbping ORACLEB USER PASS HOST:PORT/DBNAME
or java utils.dbping ORACLE_THIN USER PASS HOST:PORT:DBNAME
or java utils.dbping POINTBASE USER PASS HOST[:PORT]/DBNAME
or java utils.dbping SYBASEB USER PASS HOST:PORT/DBNAME
>
>
<Jun 16, 2006 4:33:11 PM IST> <Warning> <JDBC> <BEA-001129> <Received
exception while creating connection for pool "noti
fJMSJDBCConnPool": access denied (java.util.PropertyPermission
oracle.net.wallet_location read)>
<Jun 16, 2006 4:33:12 PM IST> <Warning> <JDBC> <BEA-001129> <Received
exception while creating connection for pool "noti
fJMSJDBCConnPool": access denied (java.util.PropertyPermission
oracle.net.wallet_location read)>
<Jun 16, 2006 4:33:13 PM IST> <Error> <JDBC> <BEA-001150> <Connection
Pool "notifJMSJDBCConnPool" deployment failed with
the following error: 0:Could not create pool connection. The DBMS
driver exception was: access denied (java.util.Proper
tyPermission oracle.net.wallet_location read).>
<Jun 16, 2006 4:33:13 PM IST> <Warning> <JDBC> <BEA-001129> <Received
exception while creating connection for pool "prod
uctionPool": access denied (java.util.PropertyPermission
oracle.net.wallet_location read)>
<Jun 16, 2006 4:33:14 PM IST> <Warning> <JDBC> <BEA-001129> <Received
exception while creating connection for pool "prod
uctionPool": access denied (java.util.PropertyPermission
oracle.net.wallet_location read)>
<Jun 16, 2006 4:33:15 PM IST> <Error> <JDBC> <BEA-001150> <Connection
Pool "productionPool" deployment failed with the f
ollowing error: 0:Could not create pool connection. The DBMS driver
exception was: access denied (java.util.PropertyPerm
ission oracle.net.wallet_location read).>
<Jun 16, 2006 4:33:15 PM IST> <Error> <JDBC> <BEA-001151> <Data Source
"notifJMSJDBCConnPool" deployment failed with the
following error: DataSource(weblogic.jdbc.jts.notifJMSJDBCConnPool)
can't be created with non-existent Pool (connection
or multi) (notifJMSJDBCConnPool).>
<Jun 16, 2006 4:33:15 PM IST> <Error> <JDBC> <BEA-001151> <Data Source
"productionPool" deployment failed with the follo
wing error: DataSource(weblogic.jdbc.jts.productionPool) can't be
created with non-existent Pool (connection or multi) (
productionPool).>
<Jun 16, 2006 4:33:15 PM IST> <Alert> <JMS> <BEA-040052> <JMSServer
"NotificationJMSServer" store failed to open java.io
.IOException: JMS JDBC store, connection pool = <notifJMSJDBCConnPool>,
prefix = <notif>: connection pool does not exist
java.io.IOException: JMS JDBC store, connection pool =
<notifJMSJDBCConnPool>, prefix = <notif>: connection pool does no
t exist
at
weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:488)
at
weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
at weblogic.jms.backend.BEStore.open(BEStore.java:262)
at weblogic.jms.backend.BEStore.start(BEStore.java:151)
at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deployment??Target.java:337)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deploymen??tTarget.java:597)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(??DeploymentTarget.java:575)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploy??mentTarget.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3??9)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp??l.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImp??l.java:755)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:??734)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBe??anImpl.java:516)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at
weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBe??anServerImpl.java:990)
at
weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServer??Impl.java:948)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
at
weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.jav??a:475)
at
weblogic.management.configuration.ServerMBean_Stub.updateDeployments(Server??MBean_Stub.java:7731)
at
weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(Slav??eDeployer.java:1321)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:33??9)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl??oymentManagerServerLifeCycleImpl.j
ava:229)
at
weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
<Jun 16, 2006 4:33:15 PM IST> <Error> <JMS> <BEA-040123> <Failed to
start JMS Server "NotificationJMSServer" due to webl
ogic.jms.common.JMSException: JMS can not open store notifJMSJDBCStore.
weblogic.jms.common.JMSException: JMS can not open store
notifJMSJDBCStore
at weblogic.jms.backend.BEStore.start(BEStore.java:163)
at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deployment??Target.java:337)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deploymen??tTarget.java:597)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(??DeploymentTarget.java:575)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploy??mentTarget.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3??9)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp??l.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImp??l.java:755)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:??734)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBe??anImpl.java:516)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at
weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBe??anServerImpl.java:990)
at
weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServer??Impl.java:948)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
at
weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.jav??a:475)
at
weblogic.management.configuration.ServerMBean_Stub.updateDeployments(Server??MBean_Stub.java:7731)
at
weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(Slav??eDeployer.java:1321)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:33??9)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl??oymentManagerServerLifeCycleImpl.j
ava:229)
at
weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
Caused by: java.io.IOException: JMS JDBC store, connection pool =
<notifJMSJDBCConnPool>, prefix = <notif>: connection p
ool does not exist
at
weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:488)
at
weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
at weblogic.jms.backend.BEStore.open(BEStore.java:262)
at weblogic.jms.backend.BEStore.start(BEStore.java:151)
... 29 more
<Jun 16, 2006 4:33:32 PM IST> <Warning> <HTTP> <BEA-101248>
<[D:\Build\autodeploys\i2\weblogic_home\config\vendavo\.\app
lications\.wlnotdelete\wlap12518\vendavo.war]: Deployment descriptor
"web.xml" is malformed. Check against the DTD: org.
xml.sax.SAXParseException: The content of element type "web-app" must
match "(icon?,display-name?,description?,distribut
able?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-map??ping*,session-config?,mime-mapping*,welcome-f
ile-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-cons??traint*,login-config?,security-role*,env-entr
y*,ejb-ref*,ejb-local-ref*)". (line 252, column 11).>
java.lang.ExceptionInInitializerError
at com.vendavo.cl.ClassHelper.<clinit>(ClassHelper.java:28)
at
com.vendavo.cl.io.ResourceHelper.addLoader(ResourceHelper.java:121)
at
com.vendavo.cl.io.ResourceHelper.<init>(ResourceHelper.java:39)
at
com.vendavo.cl.io.ResourceHelper.<clinit>(ResourceHelper.java:29)
at
com.vendavo.platform.action.StartupAction.init(StartupAction.java:75)
at
com.vendavo.platform.action.StartupAction.contextInitialized(StartupAction.??java:311)
at
weblogic.servlet.internal.WebAppServletContext$FireContextListenerAction.ru??n(WebAppServletContext.java:7044)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubje??ct.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at
weblogic.servlet.internal.WebAppServletContext.notifyCreated(WebAppServletC??ontext.java:1753)
at
weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServl??etContext.java:3352)
at
weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:727)
at
weblogic.servlet.internal.WebService.preloadResources(WebService.java:486)
at
weblogic.servlet.internal.ServletInitService.resume(ServletInitService.java??:30)
at
weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
Caused by: java.security.AccessControlException: access denied
(java.util.PropertyPermission * read,write)
at
java.security.AccessControlContext.checkPermission(AccessControlContext.jav??a:269)
at
java.security.AccessController.checkPermission(AccessController.java:401)
at
java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
at
java.lang.SecurityManager.checkPropertiesAccess(SecurityManager.java:1243)
at java.lang.System.getProperties(System.java:501)
at
com.vendavo.cl.property.AppProperties.loadSystemProperties(AppProperties.ja??va:411)
at
com.vendavo.cl.property.AppProperties.loadBasics(AppProperties.java:326)
at
com.vendavo.cl.property.AppProperties.getInstance(AppProperties.java:160)
at com.vendavo.cl.log.VLog.loadAppProperties(VLog.java:134)
at com.vendavo.cl.log.VLog.createDefaultSetup(VLog.java:94)
at com.vendavo.cl.log.VLog.<clinit>(VLog.java:66)
... 18 more
<Jun 16, 2006 4:33:34 PM IST> <Warning> <HTTP> <BEA-101162> <User
defined listener com.vendavo.platform.action.StartupAc
tion failed: java.lang.NoClassDefFoundError.>
<Jun 16, 2006 4:33:34 PM IST> <Warning> <HTTP> <BEA-101162> <User
defined listener com.vendavo.platform.action.StartupAc
tion failed: java.lang.NoClassDefFoundError.>
<Jun 16, 2006 4:33:34 PM IST> <Error> <HTTP> <BEA-101216> <Servlet:
"AdminServlet" failed to preload on startup in Web a
pplication: "soap".
Thanks in Advance,
Ketan.B.Parekh

Connection pool / db failure

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
will

Hi 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

Error Connecting or Deploying from JDEV to BPEL Server

Hi,
I am using BPEL PM 10.1.2 installed on a UNIX box.
I am unable to connect from JDEV to the BPEL server installed in a UNIX server. I get the following error when trying to test the connection
org.apache.soap.SOAPException:Unsupported response content type "text/plain", must be: "text/xml". Response was:
<html><head><title>Error instantiating web-application</title></head><bodyError instantiating web-application
No application named 'hw_services' found in the server 
java.lang.InstantiationException: No application named 'hw_services' found in the server at com.evermind.server.http.HttpServer.getHttpApplication(HttpServer.java:705) at com.evermind.server.http.HttpSite.getApplication(HttpSite.java:426) at com.evermind.server.http.AJPRequestHandler.initAJP(AJPRequestHandler.java:694) at com.evermind.server.http.AJPRequestHandler.initRequest(AJPRequestHandler.java:430) at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:188) at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:127) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186) at java.lang.Thread.run(Thread.java:534) 
</body></html>
This has been working fine until recently.
I am still able to test processes from the BPEL console.
Please let me know if anyone has come across this error earlier.

Hi,
change the named connection in JDeveloper to not use localhost reference but the data server host reference. The data sources are created from the available named connections.Alternatively you can switch off the automatic datasource creation in Jdeveloper and create them manually
Frank

[原创] 有关Weblogic Connection Pool 连接恢复的问题

这是一个古老的问题，一直困扰我，这里既然碰到了，就看看能不能解决。
环境描述：
WEBLOGIC版本是8.1 SP2，数据库是SQL SERVER 2000，分别部署在两个服务器上。
第一步：
问题描述：
数据库服务器重新启动，导致WEBLOGIC 的CONNECTION POOL中的连接中断，EJB无法获得连接，导致应用出错。
解决方法：
进入WEBLOGIC ADMIN CONSOLE,
Services->JDBC->Connection Pools->Config->Connections，点开Advanced Options.
打开 Test Reserved Connections ，Test Created Connections，Test Released Connections这三个选项。
将Test Table Name属性设置为:sysproperties(SQL Server系统表，即使自己的应用不存在，这个表也存在，而且默认的内部没有数据)
根据如下解释：
Connections that fail the test are closed and reopened to re-establish a valid physical database connection.
(You must specify a Test Table Name below.)
每次调用首先进行测试连接，如果测试失败连接将重新建立。
测试结果：
WEBLOGIC启动后，关闭数据库SQL SERVER，应用服务器前端调用此时失败。
重新启动SQL SERVER后，WEBLOGIC端略做等待，前端应用恢复正常。
第二步：
问题描述：
进一步测试，如果WEBLOGIC先启动，启动完成后再启动数据库。
在WEBLOGIC CONSOLE得到如下输出：
<2006-3-22 上午11时50分08秒 GMT+08:00> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for p
ool "MyJDBC Connection Pool": [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.>
<2006-3-22 上午11时50分10秒 GMT+08:00> <Error> <JDBC> <BEA-001150> <Connection Pool "MyJDBC Connection Pool" deployment
failed with the following error: 0:Could not create pool connection. The DBMS driver exception was: [Microsoft][SQLServe
r 2000 Driver for JDBC]Error establishing socket..>
<2006-3-22 上午11时50分10秒 GMT+08:00> <Error> <JDBC> <BEA-001151> <Data Source "MyJDBC Data Source" deployment failed w
ith the following error: DataSource(jdbc/OMSEIITxDS) can't be created with non-existent Pool (connection or multi) (MyJD
BC Connection Pool).>
Unable to deploy EJB: XXXXXXX from XXXXXXX.jar:
[EJB:011028]The DataSource with the JNDI name: jdbc/XXXXXX could not be located. Please ensure that the DataSource h
as been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
1、在默认初始化打开的连接一一失败以后，连接池发现可用的连接为0，郁闷的宣布自己部署失败。
2、接着数据源发现没有可用的连接池，自己也宣布部署失败。
3、下面所有的EJB发现不了数据源的JNDI名，部署也全部失败。
应用启动完成后，大部分EJB的状态为INACTIVE。前端应用无法使用，此时启动数据库，前端应用无法使用。
手动重新部署 EJB失败,错误还是找不到JNDI，前端应用无法使用。
手动重新部署连接池，数据源后，部署EJB 依然失败。前端应用无法使用。
解决方法：
进入WEBLOGIC ADMIN CONSOLE,
Services->JDBC->Connection Pools->Config->Connections，点开Advanced Options.
将
Connection Creation Retry Frequency 参数设置为 60。
ConnectionCreationRetryFrequencySeconds含义：
当创建数据库连接时,如果数据库不可用(如数据库没启动),隔多长时间试着重新创建该连接,
WLS8.1会每隔ConnectionCreationRetryFrequencySeconds秒重试一次.直到JDBC POOL创建成功
参考：http://dev2dev.bea.com.cn/techdoc/20030469.html，‘JDBC Connect Pool’部分。
英文解释可以直接控制台上看到，或者edocs查。
测试结果：
将数据库关闭，WEBLOGIC重新启动。
在WEBLOGIC CONSOLE得到如下输出：
打开Connection Creation Retry Frequency 参数后，连接池在第一轮尝试失败以后，就成功部署了，数据源也成功部署。
EJB部署会失败，但是提示也与先前的不同：
Unable to deploy EJB: XXXXXXX from XXXXXXX.jar:
weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool MyJDBC Connection Pool to
allocate to applications, please increase the size of the pool and retry..
每隔一段时间会看到，CONNECTION POOL不断的重新进行连接：
<2006-3-22 下午12时17分56秒 GMT+08:00> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for p
ool "MyJDBC Connection Pool": [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.>
在WEBLOGIC启动完成后，所有EJB为INACTIVE状态。
启动数据库服务器，稍后，手动重新部署所有的EJB，EJB可以部署成功，前端应用可以正常使用。
此时，此问题已经基本解决，仍需要手动部署EJB。
第三步：
问题描述：
解决方法：
有关部署次序的问题，首先查阅WEBLOGIC文档，http://edocs.bea.com/wls/docs81/faq/deploy.html#744900，得到
WebLogic Server deploys server-level resources (first JDBC and then JMS) before deploying applications.
Applications are deployed in this order: connectors, then EJBs, then Web Applications.
If the application is an EAR, the individual components are loaded in the order in which they are declared
in the application.xml deployment descriptor.
WEBLOGIC先部署服务器端资源，JDBC -> JMS....，然后部署我们的应用，EJB->WEB APPLICATION。
实际从WEBLOGIC启动日志来看，即使打开了Connection Creation Retry Frequency，如果当时数据库不是可用的，CONNECTION POOL
会不断的调度CONNECTION进行重新连接。但是此时，EJB的部署也同时在进行。个人猜测这应该是两个不同的线程（组）分别调度的任务。
现在考虑的是能不能用StartupClass截住EJB的部署过程，粗略的说是如果DATASOURCE没有连接好，或者没有可用的连接池，
就不往下进行EJB部署的过程。
参考：http://edocs.bea.com/wls/docs81/config_xml/EJBComponent.html#DeploymentOrder
DeploymentOrder：
A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable
items of the same type. For example, the server prioritizes and deploys all EJBs before it prioritizes and
deploys startup classes.Items with the lowest Deployment Order value are deployed first.
There is no guarantee on the order of deployments with equal Deployment Order values.
There is no guarantee of ordering across clusters. Default: 1000 Minimum: 0 Maximum: 2N31-1
在部署同一类应用时，按照 DEPLOYMENT LOADER的数值决定，数值越小越先。（EJB的参数在ADMIN CONSOLE界面上叫做LOAD ORDER)
而且上面看来服务器是先部署EJB，再部署STARTUP CLASS，遗憾了。
好在STARTUP CLASS上有两个选项，
Run Before Application Deployments
Run Before Application Activations
这两个选项分别可以设置StartupClass分别在系统资源部署之前，以及在系统资源部署和用户应用部署之间启动。
选上Run Before Application Activations。
现在可以了，我写了一个STARTUP CLASS，思路见下：
主代码：
private void testConnection(){
while (!isTimeout() && !getConnection()){
try{
Thread.sleep(testInterval*1000);
}catch(Exception ignor){}
log("DBConnectHolder job finished with following status:");
log("Timeout:"+isTimeout +",Connection OK:"+isConnected);
测试结果：
只要配置的等待时间足够长，应用服务器先行启动的情况下，等待数据库启动后才进行EJB等等的部署。
（主要考虑如果数据库连接不OK，EJB启动了也没有太大用，还得手工重新部署。）算是比较完满的解决了问题。
另外一个思路是是否可行？通过MBean, 在CONNECTION 建立起来以后通知一把，进行EJB的重新部署。
没来得及研究，请有经验的同学帮我补充完善。
结论：
其实也没什么结论，只是把自己遇到问题，解决问题的思路写了一下。短时间内阅读的文献有限，可能采用了一些苯方法
，或者走了弯路，也请大家拍砖。
在WL8版本上，数据库连接进行恢复和重新连接的时候，上面提出的几个参数应该是比较重要的，我再次强调一下。
Services->JDBC->Connection Pools->Config->Connections，点开Advanced Options.
Test Reserved Connections
Test Created Connections
Test Released Connections
Test Table Name
Connection Creation Retry Frequency

在第一个情景中应该只需要打开Test Reserved Connections 就可以了。
Test Created Connections表示创建连接后放到pool之前进行测试看连接是否可用
Test Released Connections表示释放连接回到pool之前进行测试看连接是否可用
I think so！

Connection Pooling in Tomcat with SQL Server

Hey Guys,
I have been banging my head against this all day :( so i now turn to you for some help :) I have a web app that uses a database now i want to start using this connection pooling that is supposed to be greatly more efficient than creating a new statement each time i need something from the database.
I have read many articles about this already today and feel that a lot of the contradict each other and one thing that i saw was that there seems to be different way of doing this.
One solution i have tried to implement but have so far failed is as follows:
In Web app:
Update Web.xml to include:
<resource-ref>
 <description>
 Resource reference to a factory for java.sql.Connection
 instances that may be used for talking to a particular
 database that is configured in the server.xml file.
 </description>
 <res-ref-name>
 jdbc/BBL
 </res-ref-name>
 <res-type>
 javax.sql.DataSource
 </res-type>
 <res-auth>
 Container
 </res-auth>
 </resource-ref>Update Context.xml to include:
<Context path="/TEST_CON_POOLING">
<Resource name="jdbc/BBL"
auth="Container"
type="javax.sql.DataSource"
username="sa"
password="sa"
driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"
url="jdbc:microsoft:sqlserver://10.20.1.91:1433;DatabaseName=BBL"
maxActive="8"
maxIdle="4" />
</Context>And then my jsp to test this:
<%@taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
--%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <title>JSP Page</title>
 </head>
 <body>
 <%@ page import="java.sql.ResultSet, java.sql.*,java.sql.SQLException,javax.naming.Context,javax.naming.InitialContext,
 javax.naming.NamingException,javax.sql.DataSource" %>
 <%
 Context initCtx = new InitialContext();
 Context envCtx = (Context) initCtx.lookup("java:comp/env");
 DataSource ds = (DataSource)
 envCtx.lookup("jdbc/BBL");
 Connection conn = ds.getConnection();
 //... use this connection to access the database ...
 Statement stmt = conn.createStatement();
 ResultSet rs = stmt.executeQuery("select id from users");
 while(rs.next()){
 out.write(rs.getString("ID"));
 conn.close();
 %>
 </body>
</html>When i actually deply this i get the following nasty tomcat error:
root cause
org.apache.tomcat.dbcp.dbcp.SQLNestedException:
Cannot create JDBC driver of class 'com.microsoft.sqlserver.jdbc.SQLServerDriver' for connect URL 'jdbc:microsoft:sqlserver://10.20.1.91:1433;DatabaseName=BBL'
 org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1150)
 org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
 org.apache.jsp.index_jsp._jspService(index_jsp.java:71)
 org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
 org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
root cause
java.sql.SQLException: No suitable driver
 java.sql.DriverManager.getDriver(DriverManager.java:243)
 org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1143)
 org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
 org.apache.jsp.index_jsp._jspService(index_jsp.java:71)
 org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
 org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:803)As far as i know all the necessary sql server jar files are in my classpath, and any way i have them all sitting in the CATALINA_HOME/common/lib directory.
Question:
Am i going about this correctly? Some tutorials i have read say that i should be updateing the server.xml file but whenever i go near that tomcat will not even start.
Help greatly appreciated.
If there is anything i have not posted let me know and i will get it up.
Rob

Updating the server.xml file used to be necessary. It is no longer required, and actually not recommended any more.
The best approach I feel is as you have done here, putting the definition into a context.xml file specifically for this application.
In fact it all looks pretty good to me.
JDBC driver jar in [TOMCAT]/common/lib - check
Configuration in context.xml rather than server.xml - check
Using JNDI - check.
Have you got the connection url right?
Is it jdbc:microsoft:sqlserver or just jdbc:sqlserver ? I have seen both on various sites around the internet.
What version of SQL Server are you using? Check its documentation on the JDBC driver as to what class to use, and what the connection string should be.
Try it in a plain java class - can you get a connection just using plain JDBC code?
What values do you use for that?
Hope this helps,
evnafets

How to use connection pooling in JDev 10.1.2

In all the ADF apps I have created, I have always used the defined connection in JDev and deployed the password. I'm now being told I need to stop doing that and start using oc4j connection pool with datasource definition so the passwords won't have to be deployed.
I pretty much need step by step instructions on how to do this becasue I've never done it. Any help would be greatly appreciated. Thanks.

Hi,
How about these tutorials?
http://www.oracle.com/technology/tech/java/newsletter/articles/oc4j_data_sources/oc4j_ds.htm
http://www.oracle.com/technology/products/jdev/tips/duff/mysql_and_oc4j3.html

XA error when starting WLS6.1(SP2) with XA connection pools

I am running WLS6.1 on HPUX11 with an Oracle Database 8.1.7. I am using the XA jDriver/Oracle
for my connection pools but when I start the server I get the following error:-
<Apr 25, 2002 6:10:21 PM BST> <Error> <JDBC> <neptune.xenicom.net> <myserver> <main>
<system> <> <001060> <Cannot startup connection pool "test" weblogic.common.ResourceException:
java.s
ql.SQLException: open failed for XAResource 'test' 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 you 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:601)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:200)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:57)
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.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
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.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy29.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2761)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:370)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
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.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy38.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:209)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:57)
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.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
I can create a normal (non-X/A) connection pools without any problems however the
X/A one will just not work at all. I spotted on a goggle newsgroup that someone else
had this exact same problem but running on WINNT but there was no resolution. The
following is the trace from the XA trace file:-
ORACLE XA: Version 8.1.7.0.0. RM name = 'Oracle_XA'.
181020.21758.1.-662733300:
xaoopen: xa_info=Oracle_XA+Acc=P/imsi/imsi+SesTm=100+DB=test+Threads=true+LogDir
=.+DbgFl=0x15,rmid=-662733300,flags=0x0
181020.21758.1.-662733300:
ORA-12547: TNS:lost contact
181020.21758.1.-662733300:
xaolgn_help: XAER_RMERR; OCIServerAttach failed. ORA-12547.
181020.21758.1.-662733300:
xaoopen: return -3
I have the whole application up and running fine on a WIN2000 platform with its own
database on the local machine. Also I can point my WIN2000 application to use the
database on the HPUX11 machine no problem.
This leads me to think this is a TNS related problem as I cant think of anything
else !.
Any help greatly appreciated...!
Martin

Hi Martin,
Using oracles Advanced Security Options can cause this, comment security
related lines out of your "sqlnet.ora" they generally have the words,
ENCRYPTION or CRYPTO in them.
Also try to set ORACLE_SID environment variable, like in the server startup
script.
ORACLE_SID=<SID_NAME>
export ORACLE_SID
Try it and see if it works. This is purely an Oracle issue not WebLogic
related. Try to contact Oracle support if you cannot resolve the issue with
above steps. You may have to reinstall the Client.
hth
sree
"Martin Porter" <[email protected]> wrote in message
news:[email protected]...
>
I am running WLS6.1 on HPUX11 with an Oracle Database 8.1.7. I am usingthe XA jDriver/Oracle
for my connection pools but when I start the server I get the followingerror:-
>
<Apr 25, 2002 6:10:21 PM BST> <Error> <JDBC> <neptune.xenicom.net><myserver> <main>
<system> <> <001060> <Cannot startup connection pool "test"weblogic.common.ResourceException:
java.s
ql.SQLException: open failed for XAResource 'test' with error XAER_RMERR :A resource
manager error has occured in the transaction branch. Check Oracle XA tracefile(s)
(if any) for database
errors. The Oracle XA trace file(s) are located at the directory whereyou start
the Weblogic Server, and have names like xa_<pool_name><MMDDYYYY>.trc.
at weblogic.jdbc.oci.xa.XAConnection.<init>(XAConnection.java:58)
atweblogic.jdbc.oci.xa.XADataSource.getXAConnection(XADataSource.java:601)
atweblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnec
tionEnvFactory.java:200)
atweblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnec
tionEnvFactory.java:57)
atweblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
ava:698)
atweblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623
atweblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:329)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:279)
atweblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:233)
atweblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy29.updateDeployments(Unknown Source)
atweblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2761)
atweblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:370)
atweblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.java:160)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy38.start(Unknown Source)
atweblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
atweblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
atweblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnec
tionEnvFactory.java:209)
atweblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnec
tionEnvFactory.java:57)
atweblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
ava:698)
atweblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623
atweblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:329)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:279)
atweblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:233)
atweblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:193)
>
I can create a normal (non-X/A) connection pools without any problemshowever the
X/A one will just not work at all. I spotted on a goggle newsgroup thatsomeone else
had this exact same problem but running on WINNT but there was noresolution. The
following is the trace from the XA trace file:-
ORACLE XA: Version 8.1.7.0.0. RM name = 'Oracle_XA'.
181020.21758.1.-662733300:
xaoopen:xa_info=Oracle_XA+Acc=P/imsi/imsi+SesTm=100+DB=test+Threads=true+LogDir
=.+DbgFl=0x15,rmid=-662733300,flags=0x0
181020.21758.1.-662733300:
ORA-12547: TNS:lost contact
181020.21758.1.-662733300:
xaolgn_help: XAER_RMERR; OCIServerAttach failed. ORA-12547.
181020.21758.1.-662733300:
xaoopen: return -3
I have the whole application up and running fine on a WIN2000 platformwith its own
database on the local machine. Also I can point my WIN2000 application touse the
database on the HPUX11 machine no problem.
This leads me to think this is a TNS related problem as I cant think ofanything
else !.
Any help greatly appreciated...!
Martin

Trying to connect my iPad Air 1 to my iPhone 5S set as a hotspot via WiFi method. iPad sees the iPhone as wifi hotspot, but an error appears 'Remote Hotspot Failure .. Unable to start personal hotspot'. How do I fix this issue??

Trying to connect my iPad Air 1 to my iPhone 5S set as a hotspot via WiFi method. iPad sees the iPhone as wifi hotspot, but an error appears 'Remote Hotspot Failure .. Unable to start personal hotspot'. How do I fix this issue??

iOS: Troubleshooting Personal Hotspot - Apple Support

Error occurred in deployment step 'Recycle IIS Application Pool': Cannot connect to the SharePoint site

How to fix:
Error occurred in deployment step 'Recycle IIS Application Pool': Cannot connect to the SharePoint site: Make sure that this is a valid URL and the SharePoint site is running on the local computer. If you moved this project to a new computer or if
the URL of the SharePoint site has changed since you created the project, update the Site URL property of the project.

Hi
This is an issue with the permissions. Check this link
http://www.spdoctor.net/Pages/message.aspx?name=Error-occurred-in-deployment-step-Recycle-IIS-Application-Pool
http://stackoverflow.com/questions/7417046/vs2010-error-in-recycling-iis-application-pool-not-found
Thanks
Girish

JDBC connection pool failures when used by JMS stores

 We are using WebLogic 6.1 sp2. We defined a separate connection pool for use by
 a JMS Store.
 <JDBCConnectionPool Name="sybaseJMSPool"
 Targets="cluster00"
 InitialCapacity="2"
 MaxCapacity="10"
 DriverName="com.sybase.jdbc2.jdbc.SybDriver"
 Properties="[email protected]@;[email protected]@;charset=utf8"
 URL="jdbc:sybase:Tds:@jms.db.host@/@jms.db.name@"/>
 (note that the @xxx@ string are replaced by actual values).
 We are using Sybase Jconnect 5.5 to a Sybase ASE 12.5 database.
 We deployed this configuration on a number of environments (testing, staging,
 ..). The actual hardware and network configuration is different for the different
 system, but the WebLogic domain stays the same regarding this issue.
 On the test system we frequently get the following exceptions:
 <Aug 13, 2002 1:56:04 PM CEST> <Alert> <JMS> <www00-test> <node00>
 <ExecuteThread: '6' for queue: 'JMS.TimerClientPool'> <> <> <040048>
 <JMSServer "JMSServer00", store failure while writing message for topic
 OrderChangeTopic, java.io.IOException: JMS JDBC store, connection pool =
 <sybaseJMSPool>, prefix = <JMS00>: write failed
 java.sql.SQLException: JZ006: Caught IOException:
 com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
 closed.
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
 (ErrorMessage.java:715)
 at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
 at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
 at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
 at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
 at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
 at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
 (SybStatement.java:1625)
 at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
 (SybPreparedStatement.java:91)
 at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
 (P6LogPreparedStatement.java:179)
 at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
 at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
 at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
 at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 .>
 java.io.IOException: JMS JDBC store, connection pool = <sybaseJMSPool>, prefix
 = <JMS00>: write failed
 java.sql.SQLException: JZ006: Caught IOException:
 com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
 closed.
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
 (ErrorMessage.java:715)
 at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
 at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
 at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
 at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
 at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
 at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
 (SybStatement.java:1625)
 at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
 (SybPreparedStatement.java:91)
 at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
 (P6LogPreparedStatement.java:179)
 at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
 at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
 at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
 at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 at weblogic.jms.store.JDBCIOStream.throwIOException
 (JDBCIOStream.java:1213)
 at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1256)
 at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
 at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 Before that this message appeared:
 <Aug 13, 2002 11:31:16 AM CEST> <Error> <ConnectionManager> <www00-test>
 <node00> <ExecuteThread: '26' for queue: 'default'> <> <> <000000>
 <Closing: 'weblogic.rjvm.t3.T3JVMConnection@795af6' because of: 'Server
 received a message over an uninitialized connection: 'JVMMessage from: 'null'
 to: '-4555218188801970213S:192.168.13.1:[7001,7001,7002,7002,7001,7002,-
 1]:ADIS:node00' cmd: 'CMD_REQUEST', QOS: '101', responseId: '1',
 invokableId: '287', flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev
 offset: '34'''>
 This problem did not occur on another system which was used during a 2 day stress
 testing session.
 It seems that the problem occurs after a period in which no user request where
 made. The user requests trigger EJB's that start sending JMS messages.
 When the problem occurs, the JMS messaging systems seems to lock up as no messages
 are received anymore by the different listeners (MDBs).
 Undeploying and redeploying the JBDC connection pool solves the problem. This
 solution is unacceptable in case of a production system.
 A similarly defined connection pool, which is used by the EJBs to make database
 connection, does not manifest this problem.
 <JDBCConnectionPool Name="sybasePool"
 Targets="cluster00"
 InitialCapacity="10"
 CapacityIncrement="5"
 MaxCapacity="50"
 PreparedStatementCacheSize="150"
 DriverName="com.sybase.jdbc2.jdbc.SybDriver"
 Properties="[email protected]@;[email protected]@;JCONNECT_VERSION=6;charset=utf8"
 URL="jdbc:sybase:Tds:@db.host@/@db.name@"/>
 The JDBC connection pool is used as follows by the JDBC store
 <JMSJDBCStore ConnectionPool="sybaseJMSPool" Name="JDBCStore00" PrefixName="JMS00"/>
 <JMSServer Name="JMSServer00" Store="JDBCStore00" Targets="node00">
 <JMSTopic JNDIName="ADIS.JMSError" JNDINameReplicated="false" Name="ErrorTopic"/>
 <JMSTopic JNDIName="ADIS.Status"
 Name="StatusTopic" RedeliveryDelayOverride="300000"/>
 <JMSTopic JNDIName="ADIS.OrderChange" JNDINameReplicated="false"
 Name="OrderChangeTopic" RedeliveryLimit="3"/>
 </JMSServer>
 Turning on the "Test Reserved Connection" with a appropriate test table does not
 help.
 Some sources on the internet tell us that JZ0C0 errors in the Jconnect driver
 can be related to network problems. Nevertheless the connection pool should be
 able to cope with this.
 Can you provide any solution for this ? Or give us hints what can cause the problem


Zhenhao Qi wrote:
thanks! Joe.
The SQL statement itself can no longer be simplified, the long excuation time is due to the database size and complicated Select criteria. I can easily reproduce the problem by using this SQL. I tried "BEA's Oracle driver (Type 4): Version 8.1.7,9.0.1,9.2.0". the question can be dissect into 2 pieces:
1) why the jdbc connection (using oracle.jdbc.OracleDriver) won't return anything if the SQL execution time > 5min, that is probably the Oracle's problem
2) why the occupied connection pool won't release even I set "Statementtimeout=600", this is Weblogic's problem.
ZhenhaoHi. Yes, (1) is oracle's problem. (2) may also be. The JDBC spec has very few
allowances for one thread to interrupt a second thread's JDBC call. If we
transmit your timeout request by calling setQueryTimeout() on the oracle
statement, and if you have a weblogic-controlled transaction we call
Statement.cancel() on any ongoing statement, we end up relying on whether
the Oracle driver implements and responds to those calls.
Are you doing weblogic-controlled transactions? Are you/can you
call Statement.setQueryTimeout() on your statements, or are these
generated JDBC queries?
If you can duplicate the problem using the weblogic.jdbc.oracle.OracleDriver
we have some other debug avenues. This would be good even if you really
want to use the thin driver, because we will do the same JDBC calls to
either driver, and the debug would prove (if) we set up a query timeout
and if we call cancel(). If we do, then we can know that it is the Oracle
driver failing in these regards.
Joe

HELP - DB2 v9 & App Server PE 9.0 - PING Connection Pool Failure - HELP

I've been playing around with Studio Creator and DB2 v9 without any issues.
So I figured I would installed App Server PE 9 and use this as my production server that I would deploy to from studio creator.
However, in my efforts to set up db2/v9 I have been trying to ping a connection pool without any luck. I get the following message:
Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Connection could not be allocated because: [sunm][DB2 JDBC Driver]Resource Limits Reached( ALLOCATE MEMORY FOR NEW SQLSTT FAILED ). Diagnostic Info: FUNCTION ID = 0049 , PROBE POINT = 0400 , TRACE POINT = 0030 , SUBCODE1 = 8B0F0000, SUBCODE2 = 78A68A98, SUBCODE3 = 00000000, ERROR MSG = Parser: Memory allocation error.
My datasource class name is com.sun.sql.jdbcx.db2.DB2DataSource.
And my resource type is javax.sql.datasource
I have copied smbase.jar, smdb2.jar and smutil.jar into c:\sun\appserver\lib
and I have all of the properties (serverName, portNumber, databaseName, user, password) created and set accordingly.
Any help would be greatly appreciated.

Here is how I got the DB2 Express-C and Sun PE 9.0 to work. ( at least base connectivity wise )
1. ) You have to have at least the DB2 Client installed on the system that will be communicating to the DB2 instance.
2.) The following jars will be needed ( depending on the driver type used) . db2java.zip, db2jcc.jar, and db2jcc_license_cu.jar and use them in the App Server ->JVM settings -> Path Settings -> Classpath Suffix
3.) The next setup is dependent on the Type driver you use
I used the Type 4 and this is the resource setup I used.
Connection Pool:
Name: DB2TestPool
Datasource Classname: com.ibm.db2.jcc.DB2SimpleDataSource
Resource Type: javax.sql.ConnectionPoolDataSource
Properties:
user: xxxxxx
password: xxxxxx
databaseName: TEST
serverName: <hostname of machine>
portnumber: 50000
driverType: 4
URL: jdbc:db2://<hostname>:<port>/<database>
JDBC Resource:
JNDI Name: jdbc/TEST
Pool Name: DB2TestPool
With this configuration I was able to ping the database as well as connect to create an entity bean from a table. This should give you a starting point.
I have yet to deploy my application, but should be doing that sometime today to verify that a connection can be made and used from within the application.

Connection pool size limit error

Hi all,
I am trying to execute a BAPI function from MII, execution fails with the following message;
[ERROR] Unable to make RFC call Exception: [Problem retrieving JCO.Function object: Connection pool <ECC_Server>:800:02:EN:ECCUser is exhausted. The current pool size limit (max connections) is 1 connections.]
[WARN] [SAP_JCo_Function_0] Skipping execution of output links due to action failure.
[ERROR] Uncaught exception from SAP_JCo_Function_0, Problem retrieving JCO.Function object: Connection pool <ECC_Server>:800:02:EN:ECCUser is exhausted. The current pool size limit (max connections) is 1 connections.
Config:
1. In 'SAP MII: Connections' of type JCO and have given pool size to 100.
2. In 'SAP MII: Credential Stores' store is created and same is being used in Start Session.
3. In JCO_Function block, we can search for the Function Module and set it.
MII Version:
14.0.2 Build(82)
Am I missing something?
Has any one seen this? please advise.
Thanks,
Message was edited by: Shridhar N

Check if there is another JCo connection configured with the same IP and User. I have found in the past that even though there are two connections configured because they have the same ip and user they are put into one pool with the lowest max pool of the two connections.

ORABPEL START-UP ERROR!!!!!!!! - Connection Pool Deployment failure

Similar Messages

Maybe you are looking for