Configure a BEA Jolt connection pool
The Jolt for Weblogic property in the property file is as follow :
eblogic.system.startupClass.demojoltpoolStart=\
bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
weblogic.system.startupArgs.demojoltpoolStart=\
poolname=demojoltpool,\
appaddrlist=//10.0.0.7:8001,\
failoverlist=//10.0.0.7:8005,\
minpoolsize=1,\
maxpoolsize=3
weblogic.system.shutdownClass.demojoltpoolStop=\
bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
weblogic.system.shutdownArgs.demojoltpoolStop=\
poolname=demojoltpool
I couldn't get it connected, a message said 'Unable to connect to primary server at //10.0.0.7:8001'.
When is the reason?
Hi there!
You have to start Tuxedo JOLT servers at the same address of parameters
"appaddrlist", and if you have security implemetation you have to add those
parameters.
You should use Jolt 1.2 in tuxedo Application
Best Regards
Mauricio
"Chaang" <[email protected]> wrote in message
news:[email protected]..
The Jolt for Weblogic property in the property file is as follow :
eblogic.system.startupClass.demojoltpoolStart=\
bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
weblogic.system.startupArgs.demojoltpoolStart=\
poolname=demojoltpool,\
appaddrlist=//10.0.0.7:8001,\
failoverlist=//10.0.0.7:8005,\
minpoolsize=1,\
maxpoolsize=3
weblogic.system.shutdownClass.demojoltpoolStop=\
bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
weblogic.system.shutdownArgs.demojoltpoolStop=\
poolname=demojoltpool
I couldn't get it connected, a message said 'Unable to connect to primaryserver at file://10.0.0.7:8001'.
>
When is the reason?
Similar Messages
-
Jolt client vs. jolt connection pooling
We are porting our app to weblogic. We are current users of jolt but since we weren't
using weblogic
we are currently using jolt client out of the app server. We are examining the merits
of converting to use
the jolt connection pool.
I have been told that jolt client is multi-threaded so the question is: if we convert
to jolt connection pooling
will we see a performance improvement, and if so, why? Or is the advantage purely
from an administrative
standpoint, and if so, what are the advantages there?Connections are resources that the application uses and a fewer connections can be used by multiple threads if the threads are not always busy with the database activity only, and are doing other work too. This sharing (pooling) can be implemented by the application or the application can leverage the connection pooling features offered by OCI/OCCI (recommended).
Be aware of connections vs sessions and sharing them (refer to :
OCI Programming Advanced Topics
OCCIConnectionPool is to pool connections and OCCIStatelessConnectionPool is to pool sessions. Please see the differences in the above link and apply as appropriate. -
BEA-001156 - connection pool reset failed on WLS 8.1.6
Hi,
I run WLS 8.1.6 on Linux and JRockit 1.4.2_12. I got the following error when I tried to reset a connection pool manually from the console. This does not happen all the time, so it is hard to reproduce. There is no change to database login credential. Any suggestions are appreciated. Thanks in advance.
BEA-141132
Dynamic invocation while executing action reset on etg:Locat
ion=nyclrwp_14654_2,Name=testPool,ServerRuntime=mycluster,
Type=JDBCConnectionPoolRuntime MBean instance
failed. The method reset with signature [] was invoked with
parameters as [].
weblogic.common.ResourceException: Refresh operation was partially successful, (1)
out of (1) resources could not be refreshed.
at weblogic.common.resourcepool.ResourcePoolImpl.refresh(ResourcePoolImpl.java:669)
at weblogic.jdbc.common.internal.ConnectionPool.reset(ConnectionPool.java:789)
at weblogic.jdbc.common.internal.ConnectionPoolRuntimeMBeanImpl.reset(ConnectionPoolRuntimeMBeanImpl.java:420)
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:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
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(RemoteMBeanServerImpl.java:990)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:491)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:434)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:429)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
BEA-001156
Stack trace associated with message 001129 follows:
java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings chained to
this exception for the reason(s).
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:506)
at com.sybase.jdbc2.tds.Tds.processLoginAckToken(Tds.java:3224)
at com.sybase.jdbc2.tds.Tds.doLogin(Tds.java:483)
at com.sybase.jdbc2.tds.Tds.login(Tds.java:405)
at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:218)
at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:195)
at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:174)
at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:126)
at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:251)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:330)
at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:1694)
at weblogic.common.resourcepool.ResourcePoolImpl.refreshAvlResources(ResourcePoolImpl.java:1982)
at weblogic.common.resourcepool.ResourcePoolImpl.refresh(ResourcePoolImpl.java:664)
at weblogic.jdbc.common.internal.ConnectionPool.reset(ConnectionPool.java:789)
at weblogic.jdbc.common.internal.ConnectionPoolRuntimeMBeanImpl.reset(ConnectionPoolRuntimeMBeanImpl.java:420)
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:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
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(RemoteMBeanServerImpl.java:990)
BEA-001129
Received exception while creating connection for pool "cpl1C
onnectionPool": JZ00L: Login failed. Examine the SQLWarnings
chained to this exception for the reason(s).
BEA-001128 Connection for pool "testPool" closed.
BEA-001099 Connection pool "testPool" reset by "system"lei wang wrote:
Hi,
I run WLS 8.1.6 on Linux and JRockit 1.4.2_12. I got the following error when I tried to reset a connection pool manually from the console. This does not happen all the time, so it is hard to reproduce. There is no change to database login credential. Any suggestions are appreciated. Thanks in advance.
Please tell me why you are resetting the pool. The reason may have something
to do with the failure messages below. The root cause of these messages is
that the pool is trying to make a new JDBC connection to Sybase, in exactly
the same way it does all the time, but for whatever reason, the DBMS is
refusing the connection request. The pool should be OK anyway, ongoing,
as long as/when the DBMS is back up and accepting connection requests.
Joe
>
BEA-141132
Dynamic invocation while executing action reset on etg:Locat
ion=nyclrwp_14654_2,Name=testPool,ServerRuntime=mycluster,
Type=JDBCConnectionPoolRuntime MBean instance
failed. The method reset with signature [] was invoked with
parameters as [].
weblogic.common.ResourceException: Refresh operation was partially successful, (1)
out of (1) resources could not be refreshed.
at weblogic.common.resourcepool.ResourcePoolImpl.refresh(ResourcePoolImpl.java:669)
at weblogic.jdbc.common.internal.ConnectionPool.reset(ConnectionPool.java:789)
at weblogic.jdbc.common.internal.ConnectionPoolRuntimeMBeanImpl.reset(ConnectionPoolRuntimeMBeanImpl.java:420)
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:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
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(RemoteMBeanServerImpl.java:990)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:491)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:434)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:429)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
BEA-001156
Stack trace associated with message 001129 follows:
java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings chained to
this exception for the reason(s).
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:506)
at com.sybase.jdbc2.tds.Tds.processLoginAckToken(Tds.java:3224)
at com.sybase.jdbc2.tds.Tds.doLogin(Tds.java:483)
at com.sybase.jdbc2.tds.Tds.login(Tds.java:405)
at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:218)
at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:195)
at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:174)
at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:126)
at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:251)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:330)
at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:1694)
at weblogic.common.resourcepool.ResourcePoolImpl.refreshAvlResources(ResourcePoolImpl.java:1982)
at weblogic.common.resourcepool.ResourcePoolImpl.refresh(ResourcePoolImpl.java:664)
at weblogic.jdbc.common.internal.ConnectionPool.reset(ConnectionPool.java:789)
at weblogic.jdbc.common.internal.ConnectionPoolRuntimeMBeanImpl.reset(ConnectionPoolRuntimeMBeanImpl.java:420)
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:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
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(RemoteMBeanServerImpl.java:990)
BEA-001129
Received exception while creating connection for pool "cpl1C
onnectionPool": JZ00L: Login failed. Examine the SQLWarnings
chained to this exception for the reason(s).
BEA-001128 Connection for pool "testPool" closed.
BEA-001099 Connection pool "testPool" reset by "system" -
What about session memory when using BEA Weblogic connection pooling?
Hi,
consider a web application, allowing database connections via a BEA Weblogic 8.1 application server. The app-server is pooling the oracle connections. The oracle database is running in dedicated server mode.
How are the database requests from the web app served by the connection pool from BEA?
1) Does one oracle session serve more than one request simultanously?
2) Does BEA serialize the requests, which means, that a session from the pool is always serving only one request at a time?
If (1) is true, than what about the session memory of Oracle sessions? I understand, that things like package global variables are beeing stored in this session private memory. If (1) is true, the PL/SQL programmer has the same situation, as with programming an Oracle databas in "shared server" mode, that is, he should not use package global variables etc.
Thankful for any ideas...
Message was edited by:
XenofonXenofon Grigoriadis wrote:
Hi,
consider a web application, using BEA between client and an Oracle Database (v9i). BEA is pooling the oracle connections. The oracle database is running in dedicated server mode.
How are the database requests from the web app beeing served by the connection pool from BEA?
1) Does one oracle session serve more than one request simultanously?no.
2) Or does BEA serialize the requests, which means, that a session from the pool is always serving only one request at a time?
Reading "Configuring and Using WebLogic JDBC" from weblogic8.1 documentation, I read:
"... Your application "borrows" a connection from the pool, uses it, then returns it to the pool by closing it...."
What do you mean by returning the connection by closing it? Tbe server will either return the connection to the pool or close it...When application code does typical jdbc code, it obtains
a connection via a WebLogic DataSource, which reserves an
unused pooled connection and passes it (transparently wrapped)
to the application. The application uses it, and then closes
it. WebLogic intercepts the close() call via the wrapper, and
puts the DBMS connection back into the WebLogic pool.
The reason, why I as an Oracle programmer ask this is, because every session (=connection)
in Oracle has its own dedicate, private memory for things like global PL/SQL variables.
Now I want to figure out, if you have to careful in programming your databases, when
one Oracle session (=connection) is serving many weblogic requests.It is serving many requests, but always serially. Do note however, that we
also transparently cache/pool prepared and callable statements with the
connection so repeat uses of the connection will be able to get already-made
statements when they call prepareStatement() and prepareCall(). These
long-lived statements will each require a DBMS-side cursor.
>
Thankful for any ideas or practical experience...
Message was edited by:
mk637Joe -
Tomcat connection pooling configuration
I have configured the datasource with connection pool as per
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html
All the required jar fles are in $CATALINA_HOME/common/lib.
When I run my app,I am getting the following error even though commons-pool.jar file is there which contains GenericObjectPool.class file
java.lang.NoSuchMethodError: org.apache.commons.pool.impl.GenericObjectPool: method <init>()V not found
at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:652)
at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:403)
Did anyone run into similar issue?
ThanksI am running into this same issue at the moment.
If you found the solution, it would be much appreciated if you could give me some insight into this problem.
Thanks. -
Configure Database Connection to Weblogic 8.1 Connection Pool
Hi,
I've got an ADF BC web application which is working find for an embedded JDBC Oracle Database connection. It's Jdeveloper 10.1.2 deployed to Weblogic 8.1.
Now I'm trying to change the Database connection so it can point to a weblogic connection pool through its JNDI name. The goal is to make .ear file transportable through different weblogic domains and databases, without recompile application.
I've been trying to configure an "OracleConnectionPoolDataSource" selecting "third party driver" in Database connection wizard, but Jdeveloper throws error: Java Cast Exception, and don't let continue. What else have to do?
thanks.I did that, but WebLogic ignores whatever I configure in Services->JDB->Connection Pools and Data Sources. Even if I remove them the application keeps on running.
Because the server only reads the connection defined from JDeveloper, which is configured in the connections.xml file placed inside the deployed .ear file.
I need to change this behaviour, and configure connections.xml pointing to Weblogic Datasource.
Thanks for your attention. -
How to use more than one connection pool to 2 different databases ??? (Weblogic 5.1)
Hello,
In my application, I must use two different databases to retrieve
informations...
My application use EJB so I created two pool of connection named pool1 and
pool2...
But when I yet used the pool1 to connect to first database and I try to use
the pool2 (to connect to the second database), an SQLException occurs :
"java.sql.SQLException: Connection has already been created in this tx
context for pool named <first pool's name>. Illegal attempt to create
connection from another pool: <second pool's name>"
I have found the answer in www.bea.com
http://e-docs.bea.com/wls/docs61/faq/JTA.html#738373
Anybody can help me and give me the more easy,quickly and the more efficient
way to use two database with two different connection pool..
Thanks..
DephiHi
You need to configure TxDataSource with XA connection pool.
More information can be found here:
http://e-docs.bea.com/wls/docs61/jta/thirdpartytx.html
Regards,
Slava Imeshev
[email protected]
"Philippe Da Cunha" <pdacunha@@webraska.com> wrote in message
news:3bfcd6ee$[email protected]..
Hello,
In my application, I must use two different databases to retrieve
informations...
My application use EJB so I created two pool of connection named pool1 and
pool2...
But when I yet used the pool1 to connect to first database and I try touse
the pool2 (to connect to the second database), an SQLException occurs :
"java.sql.SQLException: Connection has already been created in this tx
context for pool named <first pool's name>. Illegal attempt to create
connection from another pool: <second pool's name>"
I have found the answer in www.bea.com
http://e-docs.bea.com/wls/docs61/faq/JTA.html#738373
Anybody can help me and give me the more easy,quickly and the moreefficient
way to use two database with two different connection pool..
Thanks..
Dephi -
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.Parekhketan 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 -
Different connection pool for a report
Hi experts,
For one my reports using 'CLOBS' like explained (http://oraclebizint.wordpress.com/2007/11/12/oracle-bi-ee-101332-working-with-clob-fields/) I need to disable parallel processing because it's not supported.
NO_PARALLEL and NO_INDEX_PARALLEL hints at the query level couldn't disable the parallelism.the optimizer still use it.
I thought about having a new connection pool that contains 'before query' and 'after query' statements that will disable the parallelism.This will take me a lot of time to rebuild the whole Presentation and Business layers to point to a new physical tables.
Any one has an idea about how I can use another connection pool for a specific report?
RegardsI have the problem. My issue is that I need to have a webservice use the 2 database connection pools I have created. Originally the pools were Non-XA. When I change them to XA I cannot get the JMS JDBC Store to work.
java.lang.Exception: WebLogic Pool Driver doesn't support XA driver, Please change your config to use a Non-XA driver
However, part of what you wrote below I don't understand. You said you configured a brand new JMS JDBC Store and was able to use an XA Connection Pool? I tried to delete my existing one and create it anew, but was not able to use an XA pool.
Is there any solution around this? I need to have an XA Pool for a webservice but non-XA for my JMS Store.
"After much digging I found documentation that you cannot configure an XA JDBC Connection Pool for use with a JMS JDBC Store: http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#1128929
The only thing is that if I configure a brand new JMS JDBC Store and make it use the XA JDBC Connection Pool (instead of just selecting the new MySQLXAConnPool from the list that includes the non XA pool) it works without an error." -
Pointbase Server, Connection Pool Issue
Hi All,
I have set up a cluster containing two nodes - one local and other
remote machine.
I have extended my domain to include the Integration and Workshop
extensions, as my application needs them. I have also configured the
Node Manager to start the remote server and also setup the workshop
database on my machine.
I have set the classpath in the Node Manager to contain the jars -
E:\bea_sp5\weblogic81\server\lib\weblogic.jar;E:\bea_sp5\weblogic81\common\eval\pointbase\lib\pbserver44.jar;
E:\bea_sp5\weblogic81\common\eval\pointbase\lib\pbtools44.jar;
E:\bea_sp5\weblogic81\server\lib\wli.jar;E:\bea_sp5\weblogic81\server\lib\knex.jar;
<Jun 15, 2006 2:52:59 PM GMT+05:30> <Info>
<[email protected]:5557> <Starting Server
VSDClusterDomain2::MngdServer2 ...>
<Jun 15, 2006 2:53:00 PM GMT+05:30> <Info>
<[email protected]:5557> <Server VSDClusterDomain2::MngdServer2
started, process id = 2,364>
<Jun 15, 2006 2:53:02 PM GMT+05:30> <Info> <WebLogicServer>
<BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM
Version 1.4.2_08-b03 from Sun Microsystems Inc.>
<Jun 15, 2006 2:53:02 PM GMT+05:30> <Info> <Management> <BEA-141140>
<The managed server is going to contact the admin server at
http://15.76.223.63:7001 to check if there exists a running admin
server at this URL.>
<Jun 15, 2006 2:53:04 PM GMT+05:30> <Info> <Configuration Management>
<BEA-150017> <This server is being started as a dependent managed
server.>
<Jun 15, 2006 2:53:04 PM GMT+05:30> <Info> <Management> <BEA-141107>
<Version: WebLogic Server 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358
WebLogic XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358
WebLogic Integration 8.1 SP5 Wed Sep 21 21:56:54 PDT 2005 643163>
<Jun 15, 2006 2:53:04 PM GMT+05:30> <Info> <Configuration Management>
<BEA-150015> <Connecting to the administration server
http://15.76.223.63:7001 to retrieve the initial configuration.>
<Jun 15, 2006 2:53:13 PM GMT+05:30> <Notice> <Log Management>
<BEA-170019> <The server log file
E:\bea_sp5\weblogic81\common\nodemanager\MngdServer2\MngdServer2.log is
opened. All server side log events will be written to this file.>
<Jun 15, 2006 2:53:16 PM GMT+05:30> <Notice> <Security> <BEA-090082>
<Security initializing using security realm myrealm.>
<Jun 15, 2006 2:53:16 PM GMT+05:30> <Notice> <Security> <BEA-090170>
<Loading the private key stored under the alias DemoIdentity from the
jks keystore file E:\bea_sp5\weblogic81\server\lib\DemoIdentity.jks.>
<Jun 15, 2006 2:53:16 PM GMT+05:30> <Notice> <Security> <BEA-090171>
<Loading the identity certificate stored under the alias DemoIdentity
from the jks keystore file
E:\bea_sp5\weblogic81\server\lib\DemoIdentity.jks.>
<Jun 15, 2006 2:53:16 PM GMT+05:30> <Notice> <Security> <BEA-090169>
<Loading trusted certificates from the jks keystore file
E:\bea_sp5\weblogic81\server\lib\DemoTrust.jks.>
<Jun 15, 2006 2:53:16 PM GMT+05:30> <Notice> <Security> <BEA-090169>
<Loading trusted certificates from the jks keystore file
E:\bea_sp5\jdk142_08\jre\lib\security\cacerts.>
<Jun 15, 2006 2:53:17 PM GMT+05:30> <Notice> <WebLogicServer>
<BEA-000328> <Starting WebLogic Managed Server "MngdServer2" for domain
"VSDClusterDomain2">
<Jun 15, 2006 2:53:21 PM GMT+05:30> <Warning> <HTTP> <BEA-101296>
<Unable to load the default compiler class "com.sun.tools.javac.Main".
Using the default javac compiler to compile JSPs.>
<Jun 15, 2006 2:53:22 PM GMT+05:30> <Notice> <Cluster> <BEA-000138>
<Listening for announcements from cluster Cluster1 on 237.0.0.1:7001.>
<Jun 15, 2006 2:53:22 PM GMT+05:30> <Notice> <Cluster> <BEA-000133>
<Waiting to synchronize with other running members of Cluster1.>
<Jun 15, 2006 2:53:53 PM GMT+05:30> <Error> <JDBC> <BEA-001150>
<Connection Pool "cgJMSPool-nonXA" deployment failed with the following
error: No registered driver accepts URL:
jdbc:pointbase:server://15.76.223.63:9093/workshop.>
<Jun 15, 2006 2:53:54 PM GMT+05:30> <Error> <JDBC> <BEA-001150>
<Connection Pool "bpmArchPool" deployment failed with the following
error: No registered driver accepts URL:
jdbc:pointbase:server://15.76.223.63:9093/workshop.>
<Jun 15, 2006 2:53:54 PM GMT+05:30> <Error> <JDBC> <BEA-001150>
<Connection Pool "cgPool" deployment failed with the following error:
No registered driver accepts URL:
jdbc:pointbase:server://15.76.223.63:9093/workshop.>
<Jun 15, 2006 2:53:54 PM GMT+05:30> <Error> <JDBC> <BEA-001151> <Data
Source "cgDataSource-nonXA" deployment failed with the following error:
DataSource(cgDataSource-nonXA;weblogic.jdbc.jts.ebusinessPool) can't be
created with non-existent Pool (connection or multi)
(cgJMSPool-nonXA).>
<Jun 15, 2006 2:53:54 PM GMT+05:30> <Error> <JDBC> <BEA-001151> <Data
Source "cgDataSource" deployment failed with the following error:
DataSource(cgDataSource;cgSampleDataSource) can't be created with
non-existent Pool (connection or multi) (cgPool).>
<Jun 15, 2006 2:53:54 PM GMT+05:30> <Error> <JDBC> <BEA-001151> <Data
Source "bpmArchDataSource" deployment failed with the following error:
DataSource(bpmArchDataSource) can't be created with non-existent Pool
(connection or multi) (bpmArchPool).>
<Jun 15, 2006 2:54:07 PM GMT+05:30> <Alert> <JMS> <BEA-040052>
<JMSServer "cgJMSServer_auto_2" store failed to open
java.io.IOException: JMS JDBC store, connection pool =
<cgJMSPool-nonXA>, prefix = <VSD_2>: connection pool does not exist.
java.io.IOException: JMS JDBC store, connection pool =
<cgJMSPool-nonXA>, prefix = <VSD_2>: connection pool 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)
at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
at weblogic.jms.backend.BackEnd.migratableActivate(BackEnd.java:2939)
at
weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
at
weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
at
weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:2226)
at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
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:324)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.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(RemoteMBeanServerImpl.java:990)
at
weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
at
weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
at
weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7731)
at
weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1321)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:339)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java: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 15, 2006 2:54:07 PM GMT+05:30> <Error> <JMS> <BEA-040368> <The
following exception has occurred:
weblogic.jms.common.JMSException: JMS can not open store
cgJMSStore_auto_2
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.backend.BackEnd.migratableActivate(BackEnd.java:2939)
at
weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
at
weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
at
weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:2226)
at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
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:324)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.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(RemoteMBeanServerImpl.java:990)
at
weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
at
weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
at
weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7731)
at
weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1321)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:339)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java: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 =
<cgJMSPool-nonXA>, prefix = <VSD_2>: connection pool 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)
... 33 more
weblogic.jms.common.JMSException: JMS can not open store
cgJMSStore_auto_2
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.backend.BackEnd.migratableActivate(BackEnd.java:2939)
at
weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
at
weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
at
weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:2226)
at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
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:324)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.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(RemoteMBeanServerImpl.java:990)
at
weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
at
weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
at
weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7731)
at
weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1321)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:339)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java: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 =
<cgJMSPool-nonXA>, prefix = <VSD_2>: connection pool 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)
... 33 more
--------------- nested within: ------------------
weblogic.cluster.migration.MigrationException: Failed to activate
JMSServer cgJMSServer_auto_2 - with nested exception:
[weblogic.jms.common.JMSException: JMS can not open store
cgJMSStore_auto_2]
at weblogic.jms.backend.BackEnd.migratableActivate(BackEnd.java:2946)
at
weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
at
weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
at
weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:2226)
at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
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:324)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.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(RemoteMBeanServerImpl.java:990)
at
weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
at
weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
at
weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7731)
at
weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1321)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:339)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java: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)
Why do you think this error is occuring? Any other setting needs to be
done to overcome this problem ?
Thanks in advance,
SandeepPlease verify following
1) have you defined jndi name for database correctly ??
2) Have you added sqljdbc jar file in soa suite server?
3) How much time it takes when you execute same query in JDev ?
4) If you think configuration is issue, please verify the Jdev conn details @ http://soasphere.blogspot.com/2008/11/connecting-sql-server-from-jdeveloper.html and soa suite server side required settings @ Deploy error because of sql server database adapter -
In the case of a crash, if my weblogic server starts up before my tuxedo/jolt server does, is there a way to configure weblogic to retry to connect and create the jolt connections pool?
ODBC is the Microsoft database connection. O stands for Open, and it isn't. You want JDBC, Java DataBase Connectivity.
Now, do you see the search button and text rectangle next to it? (Upper-right corner whenever you're in these forums.) Type "JDBC" into the box, and click search and you'll have more answers than you could wish for.
Good luck! -
[原创] 有关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！ -
How to monitor connection pools using wlsd
Hi
i need to monitor connectionpools , i dont know that much about wlsd, how can we configure wlsd to monitor connection pools.
Cheers
RaghuU can use a Simple Java Code for that: http://jaysensharma.wordpress.com/2010/02/19/jdbcconnectionpool-parameters-using-jmx/
In the above program you need to just change the following 4-lines:
int port = 7001; // AdminServer Port
String hostname = “localhost”; // AdminSewrver HostName
h.put(Context.SECURITY_PRINCIPAL, “weblogic”); // AdminUserName
h.put(Context.SECURITY_CREDENTIALS, “weblogic”); // Admin Paassword...
====================================
Using WLST if you want to do it then you need to edit the following Script a Bit : http://jaysensharma.wordpress.com/2010/03/23/testing-datasource-status-using-wlst/ -
Hi All ,
i am developing a struts based web-application with JBoss 4.0.5 as Application Server and Oracle 10g Express edition .
I am configuring my application for connection pooling .
I have tried following methods :
1. Oracle Connection Pooling following thius link http://www.lc.leidenuniv.nl/awcourse/oracle/java.920/a96654/connpoca.htm
2. Configuring Jboss's Internal Container Level Connection pooling simply creating the datasources
3. JDBC level Connection Pooling
but unluckily did not succeed in any of these method .
The application works OK with Second method but When it is being hit with 200 request/second The pool gets exhaulsted .
i am unable to decide which approach i should be using as my application can receive large no. of requests around 1000/sec ?
Please help me out ,
Tell some useful link if possible ..
Regards JasdeepThe pool can't do magic. If your database operations take ten seconds each, you get 1000 requests a second, and you have a pool size of 200, the pool will effectively empty instantly.
You need to get some measurements of how long the typical transactions last and figure out an appropriate pool size for that. If it's more than the database can handle then you're going to have to upgrade.
It's that simple. -
hi,
<b>How to create connection pooling in WAS for SAP R/3 System.</b>
I have written session bean for Creating SalesOrder in SAP Using JCO.
my application will create 100 connection objects if 100 Client Calls for my SessionBean .so that i need to avoid creation of connection objects for <i><b>every time</b></i>.
pls tell me how configure WAS for JCO connection pooling .and How to get those connection objects. and how to use that connction object in my application.
regards
GuruHi
See this help
http://help.sap.com/saphelp_nw2004s/helpdata/en/83/85343e8c7f6329e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/6a/82343ecc7f892ee10000000a114084/frameset.htm
Kind Regards
Mukesh
Maybe you are looking for
-
Thanks to all who responded to my question about memory utilization. There were some good suggestions that I will follow up on. I am very grateful for the help. As a general rule, I would agree that memory utilzation problems tend to be developer-ind
-
Net value and tax is not apperaring properly
dear all, Scenario : Direct Sale to customer (MTS) from Factory In this specific pricing procedure we take PR00 value as assessable value .On this we add BED and ECESS excise duty and arrive at Sub Total . ( PR00BEDECESS) We mean this value as Net Va
-
Can I delete downloaded purchased tv programmes from my ipad4
Hi I have tv programmes purchased from itunes on my ipad which I want to delete. Can I do this?
-
Flex application to display in the center
I have an application where I use viewStack with a login box and the main app. Code is as below. <Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute"> <mx:Script> private function handleAuthentic
-
Hi, I want to redirect some url on a specific server of mywebfarm. The loadbalancing work but the specific rules I create based on http url not. (The loadbalancing dont keep the same server during the same user session by the way) Here is my config :