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"
Similar Messages
-
Startup problems with XA connection pools on Oracle and WLS 6.1
I am having starup problems trying to set up a WLS 6.1 connection pool using
XA. When I try to start the server, I get the following exception:
<Nov 19, 2001 3:06:28 PM EST> <Error> <JDBC> <Cannot startup connection pool
"dbdev1XAPool" weblogic.common.ResourceException: java.sql.SQLException:
open failed for XAResource 'dbdev1' with error XAER_RMERR : A resource
manager error has occured in the transaction branch. Check Oracle XA trace
file(s) (if any) for database errors. The Oracle XA trace file(s) are
located at the directory where yo
u start the Weblogic Server, and have names like
xa_<pool_name><MMDDYYYY>.trc.
at weblogic.jdbc.oci.xa.XAConnection.<init>(XAConnection.java:58)
at
weblogic.jdbc.oci.xa.XADataSource.getXAConnection(XADataSource.java:600)
at
weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnec
tionEnvFactory.java:194)
at
weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnec
tionEnvFactory.java:54)
at
weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
ava:698)
at
weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
at
weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:620
at
weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:329)
The contents of the Oracle trace file:
ORACLE XA: Version 8.1.7.0.0. RM name = 'Oracle_XA'.
150627.1312:344.344.330727191:
xaoopen:
xa_info=Oracle_XA+Acc=P/cmauser/admin+SesTm=100+DB=dbdev1+Threads=true+LogDi
r=.+DbgFl=0x15,rmid=330727191,flags=0x0
150627.1312:344.344.330727191:
ORA-12560: TNS:protocol adapter error
150627.1312:344.344.330727191:
xaolgn_help: XAER_RMERR; OCIServerAttach failed. ORA-12560.
150627.1312:344.344.330727191:
xaoopen: return -3
I am running WLS 6.1 and Oracle 8.1.7 on windows (separate machines). The
connection pool settings are:
<JDBCConnectionPool CapacityIncrement="0"
DriverName="weblogic.jdbc.oci.xa.XADataSource" InitialCapacity="40"
MaxCapacity="40" Name="dbdev1XAPool"
Properties="user=cmauser;password=admin;dataSourceName=dbdev1"
RefreshMinutes="15" ShrinkingEnabled="false" SupportsLocalTransaction="true"
Targets="cmatest" TestTableName="hppcontentsource" />
I have not had any problems connecting to the same database through regular
JDBC connection pools or through the utils.dbping utility.
What am I doing wrong?This is a dup message. Add "DebugConfigInfo OFF" in httpd.conf.
Jong
[email protected] (Olaf Foellinger) wrote:
>
Hi,
we're trying to setup apache on linux so that it's forwarding all jsp
requests to Bea WLS 6.0 on Solaris. We've installed the mod_wl.so
modules according to the documentation. When apache starts it shows the
following warning:
[Tue Jan 9 13:22:55 2001] [warn] Loaded DSO
/usr/lib/apache/1.3/mod_wl.so uses plain Apache 1.3 +API, this module
might crash under EAPI! (please recompile it with -DEAPI)
and in fact, when we try to load a jsp page we get
[Tue Jan 9 13:29:14 2001] [notice] child pid 5780 exit signal
Segmentation fault (11)
Does anyone have a working solution ? Can bea provide us with a plugin
compiled with EAPI ?
Greetings Olaf -
Dynamic Connection Pool Creation Failing in a cluster
Hi,
I am trying to create a connection pool in a clustered environment. This connection
pool is created lazily behind a Stateless Session Bean. We first attempt to determine
whether, the connection pool exists using JdbcServices.poolExists(someName), and
create it if it does not exist. A failure occurs on creation because it looks
like the connection pool might have been created by a bean on a different weblogic
VM instance. Is there any way to dynamically create a connection pool and make
it visible to the whole cluster? Thanks in advance for any help. Michael Dolbear
Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Checking existence of connection pool
Content
ConnectionPool requested by user guest>
<Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Creating connection pool ContentConnectionPoo
l requested by user guest>
weblogic.common.ResourceException: weblogic.management.MBeanCreationException:
Start server side stack trace:
javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=JD
BCConnectionPool
at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:
2352)
at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:874)
at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanSer
verImpl.java:181)
at weblogic.management.internal.Helper.createMBean(Helper.java:376)
at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
ServerImpl.java:278)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
635)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
621)
at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
Impl.java:397)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.MBeanCreationException: - with nested exception:
[javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=J
DBCConnectionPool]
at weblogic.management.internal.Helper.createMBean(Helper.java:383)
at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
ServerImpl.java:278)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
635)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
621)
at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
Impl.java:397)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=J
DBCConnectionPool
Start server side stack trace:
javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=JD
BCConnectionPool
at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:
2352)
at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:874)
at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanSer
verImpl.java:181)
at weblogic.management.internal.Helper.createMBean(Helper.java:376)
at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
ServerImpl.java:278)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
635)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
621)
at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
Impl.java:397)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at weblogic.jdbc.common.internal.ConnectionPool.dynaStartup(ConnectionPool.java:47
2)
at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:727
at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:709
at com.thc.ids.inf.framework.opf.rdbms.datastore.ConnectionPoolCreator.createConne
ctionPool(ConnectionPoolCreator.java:82)
at com.thc.ids.inf.framework.opf.datastore.DataStoreRepository.createConnectionPoo
lIfNonExistent(DataStoreRepository.java:211)
at com.thc.ids.inf.util.persistence.content.ConnectionPoolInitializer.createConnec
tionPoolIfNeeded(ConnectionPoolInitializer.java:48)
at com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.create
ConnectionPoolIfNeeded(Unknown Source)
at com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.getIma
ge(Unknown Source)
at com.thc.ids.inf.services.business.crs.ContentRetrievalService.getImage(Unknown
Source)
at java.lang.reflect.Method.invoke(Native Method)
at com.thc.ids.inf.util.reflection.MethodDescription.invokeMethod(MethodDescriptio
n.java:181)
at com.thc.ids.inf.util.reflection.MethodInvocation.invoke(MethodInvocation.java:7
9)
at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean.invoke(ServiceBean.java:
186)
at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl.invoke(Ser
viceBean_bjedmi_EOImpl.java:37)
at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl_WLSkel.inv
oke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
<Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Checking existence of connection
pool Content
ConnectionPool requested by user guest>
<Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Creating connection pool ContentConnectionPoo
l requested by user guest>
weblogic.common.ResourceException: weblogic.management.MBeanCreationException:
Start server side stack trace:
javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=JD
BCConnectionPool
at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:
2352)
at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:874)
at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanSer
verImpl.java:181)
at weblogic.management.internal.Helper.createMBean(Helper.java:376)
at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
ServerImpl.java:278)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
635)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
621)
at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
Impl.java:397)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.MBeanCreationException: - with nested exception:
[javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=J
DBCConnectionPool]
at weblogic.management.internal.Helper.createMBean(Helper.java:383)
at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
ServerImpl.java:278)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
635)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
621)
at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
Impl.java:397)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=J
DBCConnectionPool
Start server side stack trace:
javax.management.InstanceAlreadyExistsException: domain:Name=ContentConnectionPool,Type=JD
BCConnectionPool
at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:
2352)
at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:874)
at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanSer
verImpl.java:181)
at weblogic.management.internal.Helper.createMBean(Helper.java:376)
at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBean
ServerImpl.java:278)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
635)
at weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.java:
621)
at weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBeanHome
Impl.java:397)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at weblogic.jdbc.common.internal.ConnectionPool.dynaStartup(ConnectionPool.java:47
2)
at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:727
at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:709
at com.thc.ids.inf.framework.opf.rdbms.datastore.ConnectionPoolCreator.createConne
ctionPool(ConnectionPoolCreator.java:82)
at com.thc.ids.inf.framework.opf.datastore.DataStoreRepository.createConnectionPoo
lIfNonExistent(DataStoreRepository.java:211)
at com.thc.ids.inf.util.persistence.content.ConnectionPoolInitializer.createConnec
tionPoolIfNeeded(ConnectionPoolInitializer.java:48)
at com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.create
ConnectionPoolIfNeeded(Unknown Source)
at com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.getIma
ge(Unknown Source)
at com.thc.ids.inf.services.business.crs.ContentRetrievalService.getImage(Unknown
Source)
at java.lang.reflect.Method.invoke(Native Method)
at com.thc.ids.inf.util.reflection.MethodDescription.invokeMethod(MethodDescriptio
n.java:181)
at com.thc.ids.inf.util.reflection.MethodInvocation.invoke(MethodInvocation.java:7
9)
at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean.invoke(ServiceBean.java:
186)
at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl.invoke(Ser
viceBean_bjedmi_EOImpl.java:37)
at com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl_WLSkel.inv
oke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)The only way to do it is using MBeans. You could search this newsgroup
for "JDBCConnectionPoolMBean" to get an idea of how it could be done.
Slava
P.S. http://search.bea.com/weblogic/gonews
"Mark Mortensen" <[email protected]> wrote in message
news:[email protected]...
>
Slava,
I am working with Mike on this issue and wanted to add some moreclarifications.
We have a two server cluster where one of the EJB's on one of the Managedservers
creates the connection pool. The problem comes in when a request comes tothe
second server in the cluster. The connection pool is created by the firstserver
but it is only assigned to the first server in the targets section on theconsole.
It isn't assigned to the cluster. Is there a way to programmaticallyassign the
pool to the cluster instead of just the server that created the pool?
-Mark
"Michael Dolear" <[email protected]> wrote:
Hi Slava,
Here is what I am doing. The code is spread across a couple of classes.
I am using
what was described in BEA's doc on dynamic connection pool creation.
I didn't
see anything about MBean apis required:
* Dynamically create a connection pool using
aConnectionPoolProperties.
Please
see ConnectionPoolCreator
* for the required properties that must be sent in.
* @param aConnectionPoolProperties
public synchronized void createConnectionPoolIfNonExistent(Properties
aConnectionPoolProperties)
throwsPersistenceFrameworkInitializationException
ConnectionPoolCreator tempPoolCreator;
Pool tempPool;
tempPoolCreator = new ConnectionPoolCreator();
tempPool =tempPoolCreator.getConnectionPool(aConnectionPoolProperties);
if (tempPool == null)
tempPoolCreator.createConnectionPool(aConnectionPoolProperties);
>>
* Create Connection pool given the properties that I have beenconfigured
with
* @return Pool
public Pool createConnectionPool(Properties aConnectionProperties)
throwsPersistenceFrameworkInitializationException
JdbcServices tempServices;
try
tempServices = this.lookupJdbcServices();
tempServices.createPool(aConnectionProperties);
returntempServices.getPool(aConnectionProperties.getProperty(CONNECTION_POOL_NAME)
catch (Exception e)
PersistenceFrameworkUtils.logException(e);
throw newPersistenceFrameworkInitializationException(e.getMessage());
* Answer a connectionPool or null.
* @return Pool
public Pool getConnectionPool(Properties aConnectionProperties)
throwsPersistenceFrameworkInitializationException
JdbcServices tempServices;
try
tempServices = this.lookupJdbcServices();
if (tempServices.poolExists(
aConnectionProperties.getProperty(CONNECTION_POOL_NAME)))
return tempServices.getPool(
aConnectionProperties.getProperty(CONNECTION_POOL_NAME));
else
return null;
catch (Exception e)
PersistenceFrameworkUtils.logException(e);
throw
newPersistenceFrameworkInitializationException(e.getMessage());
"Slava Imeshev" <[email protected]> wrote:
Hi Michael,
Could you show us the code? Without looking at the code
I can only say that JdbcServices.poolExists(someName)
returns true only in case the pool is up and running.
If the connection pool MBean was created but not assigned
a target, subsequent tries to create it would fail.
Regards,
Slava Imeshev
"Michael Dolbear" <[email protected]> wrote in message
news:[email protected]...
Hi,
I am trying to create a connection pool in a clustered environment.This
connection
pool is created lazily behind a Stateless Session Bean. We first
attempt
to determine
whether, the connection pool exists usingJdbcServices.poolExists(someName), and
create it if it does not exist. A failure occurs on creation becauseit
looks
like the connection pool might have been created by a bean on a
different
weblogic
VM instance. Is there any way to dynamically create a connection pooland
make
it visible to the whole cluster? Thanks in advance for any help.
Michael
Dolbear
Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Checking existence ofconnection pool
Content
ConnectionPool requested by user guest>
<Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Creating connection poolContentConnectionPoo
l requested by user guest>
weblogic.common.ResourceException:weblogic.management.MBeanCreationException:
Start server side stack trace:
javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=JD
BCConnectionPool
at
com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:1
34
at
com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.
ja
va:
2352)
at
com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:
87
4)
at
weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBe
an
Ser
verImpl.java:181)
atweblogic.management.internal.Helper.createMBean(Helper.java:376)
atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at
weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
MB
ean
ServerImpl.java:278)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
635)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
621)
at
weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
nH
ome
Impl.java:397)
atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.MBeanCreationException: - with nested exception:
[javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=J
DBCConnectionPool]
atweblogic.management.internal.Helper.createMBean(Helper.java:383)
atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at
weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
MB
ean
ServerImpl.java:278)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
635)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
621)
at
weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
nH
ome
Impl.java:397)
atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=J
DBCConnectionPool
Start server side stack trace:
javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=JD
BCConnectionPool
at
com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:1
34
at
com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.
ja
va:
2352)
at
com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:
87
4)
at
weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBe
an
Ser
verImpl.java:181)
atweblogic.management.internal.Helper.createMBean(Helper.java:376)
atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at
weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
MB
ean
ServerImpl.java:278)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
635)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
621)
at
weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
nH
ome
Impl.java:397)
atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at
weblogic.jdbc.common.internal.ConnectionPool.dynaStartup(ConnectionPool.ja
va
:47
2)
at
weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.jav
a:
727
at
weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.jav
a:
709
at
com.thc.ids.inf.framework.opf.rdbms.datastore.ConnectionPoolCreator.create
Co
nne
ctionPool(ConnectionPoolCreator.java:82)
at
com.thc.ids.inf.framework.opf.datastore.DataStoreRepository.createConnecti
on
Poo
lIfNonExistent(DataStoreRepository.java:211)
at
com.thc.ids.inf.util.persistence.content.ConnectionPoolInitializer.createC
on
nec
tionPoolIfNeeded(ConnectionPoolInitializer.java:48)
at
com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.c
re
ate
ConnectionPoolIfNeeded(Unknown Source)
at
com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.g
et
Ima
ge(Unknown Source)
at
com.thc.ids.inf.services.business.crs.ContentRetrievalService.getImage(Unk
no
wn
Source)
at java.lang.reflect.Method.invoke(Native Method)
at
com.thc.ids.inf.util.reflection.MethodDescription.invokeMethod(MethodDescr
ip
tio
n.java:181)
at
com.thc.ids.inf.util.reflection.MethodInvocation.invoke(MethodInvocation.j
av
a:7
9)
at
com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean.invoke(ServiceBean.
ja
va:
186)
at
com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl.invok
e(
Ser
viceBean_bjedmi_EOImpl.java:37)
at
com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl_WLSke
l.
inv
oke(Unknown Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.ja
va
:93
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
<Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Checking existence ofconnection
pool Content
ConnectionPool requested by user guest>
<Mar 28, 2002 5:35:08 PM MST> <Info> <JDBC> <Creating connection poolContentConnectionPoo
l requested by user guest>
weblogic.common.ResourceException:weblogic.management.MBeanCreationException:
Start server side stack trace:
javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=JD
BCConnectionPool
at
com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:1
34
at
com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.
ja
va:
2352)
at
com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:
87
4)
at
weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBe
an
Ser
verImpl.java:181)
atweblogic.management.internal.Helper.createMBean(Helper.java:376)
atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at
weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
MB
ean
ServerImpl.java:278)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
635)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
621)
at
weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
nH
ome
Impl.java:397)
atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.MBeanCreationException: - with nested exception:
[javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=J
DBCConnectionPool]
atweblogic.management.internal.Helper.createMBean(Helper.java:383)
atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at
weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
MB
ean
ServerImpl.java:278)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
635)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
621)
at
weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
nH
ome
Impl.java:397)
atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
- with nested exception:
[javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=J
DBCConnectionPool
Start server side stack trace:
javax.management.InstanceAlreadyExistsException:domain:Name=ContentConnectionPool,Type=JD
BCConnectionPool
at
com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:1
34
at
com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.
ja
va:
2352)
at
com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:
87
4)
at
weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBe
an
Ser
verImpl.java:181)
atweblogic.management.internal.Helper.createMBean(Helper.java:376)
atweblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
at
weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(Remote
MB
ean
ServerImpl.java:278)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
635)
at
weblogic.management.internal.MBeanHomeImpl.createAdminMBean(MBeanHomeImpl.
ja
va:
621)
at
weblogic.management.internal.AdminMBeanHomeImpl.createAdminMBean(AdminMBea
nH
ome
Impl.java:397)
atweblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
at
weblogic.jdbc.common.internal.ConnectionPool.dynaStartup(ConnectionPool.ja
va
:47
2)
at
weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.jav
a:
727
at
weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.jav
a:
709
at
com.thc.ids.inf.framework.opf.rdbms.datastore.ConnectionPoolCreator.create
Co
nne
ctionPool(ConnectionPoolCreator.java:82)
at
com.thc.ids.inf.framework.opf.datastore.DataStoreRepository.createConnecti
on
Poo
lIfNonExistent(DataStoreRepository.java:211)
at
com.thc.ids.inf.util.persistence.content.ConnectionPoolInitializer.createC
on
nec
tionPoolIfNeeded(ConnectionPoolInitializer.java:48)
at
com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.c
re
ate
ConnectionPoolIfNeeded(Unknown Source)
at
com.thc.ids.inf.services.business.crs.spi.oracle.OracleRetrievalProvider.g
et
Ima
ge(Unknown Source)
at
com.thc.ids.inf.services.business.crs.ContentRetrievalService.getImage(Unk
no
wn
Source)
at java.lang.reflect.Method.invoke(Native Method)
at
com.thc.ids.inf.util.reflection.MethodDescription.invokeMethod(MethodDescr
ip
tio
n.java:181)
at
com.thc.ids.inf.util.reflection.MethodInvocation.invoke(MethodInvocation.j
av
a:7
9)
at
com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean.invoke(ServiceBean.
ja
va:
186)
at
com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl.invok
e(
Ser
viceBean_bjedmi_EOImpl.java:37)
at
com.thc.ids.inf.framework.service.J2EE.ejb.ServiceBean_bjedmi_EOImpl_WLSke
l.
inv
oke(Unknown Source)
atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.ja
va
:93
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java
:2
2)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120) -
Cannot startup connection pool no suitable driver /WLS 6.1 SP4
hi all,
i got a problem in creating a ConnectionPool with weblogic 6.1 sp4.
my connection pool has following config data:
URL:jdbc:oracle:[email protected]:1521:ESECD7
Driver:oracle.jdbc.driver.OracleDriver
props
username=aaaa
password=bbbb
in my startWebLogic.cmd i have following classpath:
set PATH=.\bin;%PATH%;c:\bea\wlserver6.1\config\mydomain;c:\bea\wlserver6.1\bin\oci817_8;c:\oracle\ora92\bin;%PATH%
set CLASSPATH=C:\oracle\ora92\jdbc\lib\classes111.zip;C:\oracle\ora92\jdbc\lib\classes12.zip;.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;c:\bea\jolt.jar;c:\bea\joltwls.jar;c:\bea\joltjse.jar
but i keep on gettign the exception Cannot startup connection pool.. no suitable
driver
to me it looks like everything is in classpath...
any ideas?
regards
marcoMarco wrote:
hi all,
i got a problem in creating a ConnectionPool with weblogic 6.1 sp4.
my connection pool has following config data:
URL:jdbc:oracle:[email protected]:1521:ESECD7
Driver:oracle.jdbc.driver.OracleDriver
props
username=aaaa
password=bbbb
in my startWebLogic.cmd i have following classpath:
set PATH=.\bin;%PATH%;c:\bea\wlserver6.1\config\mydomain;c:\bea\wlserver6.1\bin\oci817_8;c:\oracle\ora92\bin;%PATH%
set CLASSPATH=C:\oracle\ora92\jdbc\lib\classes111.zip;C:\oracle\ora92\jdbc\lib\classes12.zip;.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;c:\bea\jolt.jar;c:\bea\joltwls.jar;c:\bea\joltjse.jar
but i keep on gettign the exception Cannot startup connection pool.. no suitable
driver
to me it looks like everything is in classpath...
any ideas?
regards
marcoHi. Read the weblogi startServer script, and the startWLS script it calls. These
scripts build up a string which is added to the java commandline that starts
the server, with an argument -classpath ....... Unless the driver shows up there,
the server doesn't see it.
However, we already include a version of the oracle thin driver. It may not be
the best (it's old), so you will want to make sure you version gets in to the classpath
argument ahead of our stuff, but the old driver would have been invoked...
Therefore, I suspect your URL is not exactly correct. Please verify that this exact URL
works in a simple standalone JDBC program using the driver you want, without any
weblogic code in the picture.
thanks,
Joe -
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 -
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? -
DBCP Connection pooling apparently failing!
I am trying out the following code per directions from DBCP site, but the output indicates that after I call con.close(), the con.isClosed() return true. Does that mean that DBCP is not working the way I am setting it up or what? Please help!
try
Class.forName("oracle.jdbc.OracleDriver");
StackObjectPool pool=new StackObjectPool(2);
DriverManagerConnectionFactory confactory=new DriverManagerConnectionFactory(url,null);
PoolableConnectionFactory poolconfactory=new PoolableConnectionFactory(confactory,pool,new StackKeyedObjectPoolFactory(2),null,false,true);
PoolingDataSource source=new PoolingDataSource(pool);
Connection con=source.getConnection();
PreparedStatement stat=con.prepareStatement("select * from employee");
stat.executeQuery();
System.out.println(con.isClosed());
stat.close();
con.close();
System.out.println(con.isClosed());
catch (Exception ex)
ex.printStackTrace();
}Does that mean that DBCP is not working the way I am
setting it up or what? Please help!It's probably working the way it should. The DBCP is probably wrapping the OracleConnection in its own wrapper. When you close the wrapper, it just changes its internal state to say it is closed but doesn't actually close the OracleConnection it has a reference to internally.
Try seeing what class con really is:
System.out.println(con.getClass().getName());Whatever class that is, it probably has a method to get the real connection so that you can make OracleConnection specific calls. If it does, type cast it to the implementor's Connection Class and get the real internal connection from con before you close it and then check its class name. After you close the con check the isClosed method on the internal OracleConnection. -
WLS 10.0 JDBC connection pool shrink not working
We seem to be having a problem with jdbc connection pools not shrinking. In the connection pool properties in the WLS console we have:
Initial Capacity 4
Maximum Capacity 15
Shrink Frequency 900
However when I look at the underlying xml config file (see below) the last two values above are not present in the config!
Any ideas what is going on here?
thankyou,
Chris
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns
:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLo
cation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
<name>mdmrDataSource</name>
<jdbc-driver-params>
<url>jdbc:oracle:thin:@(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = xxxrac01-vip.nzlxxx01.com) (PORT = 1521))
(ADDRESS = (PROTOCOL = TCP) (HOST = xxxrac02-vip.nzlxxx01.com) (PORT = 1521)) (LOAD_BALANCE = yes) (CONNECT_DATA =(SERVE
R = DEDICATED) (SERVICE_NAME = xxxrac.nzlami01.com)))</url>
<driver-name>oracle.jdbc.pool.OracleDataSource</driver-name>
<properties>
<property>
<name>user</name>
<value>xxx_comms</value>
</property>
<property>
<name>fastConnectionFailoverEnabled</name>
<value>true</value>
</property>
<property>
<name>implicitCachingEnabled</name>
<value>true</value>
</property>
<property>
<name>connectionCachingEnabled</name>
<value>true</value>
</property>
<property>
<name>ONSConfiguration</name>
<value>nodes=xxxrac1:6251,xxxrac2:6251</value>
</property>
</properties>
<password-encrypted>xxx</password-encrypted>
</jdbc-driver-params>
<jdbc-connection-pool-params>
<initial-capacity>4</initial-capacity>
<test-connections-on-reserve>true</test-connections-on-reserve>
<test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
</jdbc-connection-pool-params>
<jdbc-data-source-params>
<jndi-name>jdbc/XXXX</jndi-name>
<global-transactions-protocol>None</global-transactions-protocol>
</jdbc-data-source-params>
</jdbc-data-source>You are right that the XML seems to lask those other settings... Did you
sae those settings from the console?
This is what's in one of mine....
<jdbc-connection-pool-params>
<initial-capacity>0</initial-capacity>
<max-capacity>300</max-capacity>
<shrink-frequency-seconds>900</shrink-frequency-seconds> -
Using Connection Pooling in a WLS 5.1.x - Cluster
Hi,
We have problems using connection pooling in a WLS 5.1.x - Cluster. Is it
possible to use CP in such a cluster at all ? The problem is, connections
will be opened and never been closed. How can I configure a cluster for CP?
I have a WLS-Cluster with 2 instances and my webApp uses connection pooling.
By the way I get a connection on Instance 1, Instance 2 gets a connection
also, but never releases it.
In my opinion, the reference to the connection in the partner-instance will
be lost.
How do I have to configure my cluster to work well with that stuff ?
Thank a lot,
Markus.
Clustering with connection pools works fine in WLS 5.1. If connections are
not being release, you have bugs in your code.
When a connection is retrieved from a pool on one instance, a corresponding
connection is NOT retrieved on another instance.
Mike
"M. Hammer" <[email protected]> wrote in message
news:[email protected]..
> Hi,
>
> We have problems using connection pooling in a WLS 5.1.x - Cluster. Is it
> possible to use CP in such a cluster at all ? The problem is, connections
> will be opened and never been closed. How can I configure a cluster for
CP?
>
> I have a WLS-Cluster with 2 instances and my webApp uses connection
pooling.
> By the way I get a connection on Instance 1, Instance 2 gets a connection
> also, but never releases it.
> In my opinion, the reference to the connection in the partner-instance
will
> be lost.
> How do I have to configure my cluster to work well with that stuff ?
>
> Thank a lot,
>
> Markus.
>
>
>
-
Automatic Reset of Connection Pools
Is there a way to have connection pools reset when the database they are pointing to restarts?
We are currently using these two options :
Test Reserved Connections
When this feature is set to true, WebLogic Server tests a connection before giving it to the client
Test Frequency
The number of seconds (between 0 and a positive 32-bit integer) between when WebLogic Server tests unused database connections
Nik
Message was edited by krisnik at Oct 27, 2004 8:42 AM -
[原创] 有关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！ -
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 -
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 -
Error While Creating Informix Connection Pool
Hi,
I am trying to port an application from Weblogic 6.1 to Weblogic 8.1. The Application accesses Informix database. I used the following driver, url and properties while connecting to this database using Weblogic 6.1
url:->jdbc:weblogic:informix4:snss_live
Driver ClassName :-> weblogic.jdbc.informix.InformixDriver
Properties :->
port=22000
user=snssadmn
password=snssadmn
server=10.115.26.40
The above used to work fine with weblogic 6.1
With Weblogic 8.1, I am using the following properties
url :-> jdbc:bea:informix://10.115.26.40:22000;informixServer=10.115.26.40;databaseName=snss_live
Driver ClassName :-> weblogic.jdbc.informix.InformixDriver
Properties :->
informixServer=10.115.26.40
user=snssadmn
portNumber=22000
databaseName=snss_live
serverName=10.115.26.40
However using these properties I am getting the following error while deploying the Connection Pool to the Managed Server
<Dec 29, 2004 12:26:53 PM EST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "Btv_Vms_Pool": [BEA][Informix JDBC Driver][Informix]INFORMIXSERVER does not match either DBSERVERNAME or DBSERVERALIASES.>
<Dec 29, 2004 12:26:54 PM EST> <Error> <JDBC> <BEA-001150> <Connection Pool "Btv_Vms_Pool" deployment failed with the following error: 0:Could not create pool connection. The DBMS driver exception was: [BEA][Informix JDBC Driver][Informix]INFORMIXSERVER does not match either DBSERVERNAME or DBSERVERALIASES..>
Any idea as to why this is happening
Regards
Nitin NairHi. I suspect that the databaseName property is causing the problem in
8.1. Remove it and see if that works. Also, try running:
java utils.dbping, and giving it the properties it asks for, for your
Informix connection. Once it succeeds in making a connection, it will
print out the URL and properties it used. Then define the pool with
those (and only those) properties and URL.
Joe
Nitin Nair wrote:
Hi,
I am trying to port an application from Weblogic 6.1 to Weblogic 8.1. The Application accesses Informix database. I used the following driver, url and properties while connecting to this database using Weblogic 6.1
url:->jdbc:weblogic:informix4:snss_live
Driver ClassName :-> weblogic.jdbc.informix.InformixDriver
Properties :->
port=22000
user=snssadmn
password=snssadmn
server=10.115.26.40
The above used to work fine with weblogic 6.1
With Weblogic 8.1, I am using the following properties
url :-> jdbc:bea:informix://10.115.26.40:22000;informixServer=10.115.26.40;databaseName=snss_live
Driver ClassName :-> weblogic.jdbc.informix.InformixDriver
Properties :->
informixServer=10.115.26.40
user=snssadmn
portNumber=22000
databaseName=snss_live
serverName=10.115.26.40
However using these properties I am getting the following error while deploying the Connection Pool to the Managed Server
<Dec 29, 2004 12:26:53 PM EST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "Btv_Vms_Pool": [BEA][Informix JDBC Driver][Informix]INFORMIXSERVER does not match either DBSERVERNAME or DBSERVERALIASES.>
<Dec 29, 2004 12:26:54 PM EST> <Error> <JDBC> <BEA-001150> <Connection Pool "Btv_Vms_Pool" deployment failed with the following error: 0:Could not create pool connection. The DBMS driver exception was: [BEA][Informix JDBC Driver][Informix]INFORMIXSERVER does not match either DBSERVERNAME or DBSERVERALIASES..>
Any idea as to why this is happening
Regards
Nitin Nair -
Installation of CM fails(par files deployed but connection to database fail
Hi,
I have just installed CM EP6 SP2 on an old sandbox system (which has been upgrade from SP0 I believe), and I have some problems. The installation went fine untill I got the error message "CJS-00276 The upgrade failed. The installation report file cf_installation.report does not exist. Check the log files under the server directory and, if necessary, contact your local support center." But I, at least now, find the file but this is probably from my installation of CM SP2 Patch4 and CM SP2 Patch4 hf8 (I was hoping the installation of them would clear the problem).
I believe the problem is that there are missing some files under the SAPPRT share (
server\SAPPRT\EPS1\global\config\cm), this because it was giving some error messages earlier about it. I was running the portal under localsystem user, which hasn't got the possiblity to have access to share's. (I would get an exception about access denied from the file system when starting it up, but after changing the user I don't).
Under
server\SAPPRT\EPS1\global\config\cm the portal has created the following folders:
Backups
config
etc
reports
<b>Are there any one missing ?</b>
(to resolve the problem I tried create the following folders, but still the same problem:
system/updateQueue/events
system/command
system/deployment/archives
system/deployment/upgrades
utilities/connection_pools/db_type/default)
The property files in \usr\sap\EPS1\j2ee\j2ee_01\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\system\cm
look correct, and also the file under portalapps/com.sap.portal.km.application (or something).
When I went into KM configuration in the portal, I noticed there were no JDBC connection pools, and I therefore created two as described in http://help.sap.com/saphelp_ep60sp2/helpdata/en/eb/d10ef2b6a311d5993900508b6b8b11/content.htm
But that is something which the installer should have done for me. (and still the connection pools won't start)
The main error message I get at startup is the following:
Jun 28, 2005 4:45:17 PM com.sapportals.config.queue.UpdateQueueService [System_Thread_12] Warning": There was a problem initializing the queue service for config manager : configuration plugin for queue service not found (/system/updateQueue/events)
java.lang.RuntimeException: Failed to init. connection pool configuration: Failed to init. connection pool configuration: missing configurable /cm/utilities/connection_pools/db_type/default
at com.sapportals.wcm.util.jdbc.connectionpool.JDBCConnectionPoolManager.initConfig(JDBCConnectionPoolManager.java:566)
at com.sapportals.wcm.util.jdbc.connectionpool.JDBCConnectionPoolManager.getInstance(JDBCConnectionPoolManager.java:99)
at com.sap.workflow.util.config.WorkflowProperties.initProperties(WorkflowProperties.java:188)
at com.sap.workflow.util.config.WorkflowProperties.<init>(WorkflowProperties.java:48)
at com.sap.workflow.util.config.WorkflowProperties.getInstance(WorkflowProperties.java:56)
at com.sap.workflow.es.portal.WFPortalService.init(WFPortalService.java:74)
at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1470)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1426)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1383)
at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:371)
at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:765)
at com.inqmy.services.servlets_jsp.server.WebApplicationStarter.run(WebApplicationStarter.java:57)
at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
at java.security.AccessController.doPrivileged(Native Method)
at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
java.lang.NullPointerException
at javax.naming.NameImpl.<init>(NameImpl.java:250)
at javax.naming.CompositeName.<init>(CompositeName.java:223)
at com.inqmy.services.jndi.implclient.OffsetClientContext.parse(OffsetClientContext.java:129)
at com.inqmy.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:200)
at javax.naming.InitialContext.lookup(InitialContext.java:345)
at com.sap.workflow.util.ejbfactory.EJBFactory.getUserTransaction(EJBFactory.java:282)
at com.sap.workflow.es.portal.WFPortalService.init(WFPortalService.java:83)
at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1470)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1426)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1383)
at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:371)
at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:765)
at com.inqmy.services.servlets_jsp.server.WebApplicationStarter.run(WebApplicationStarter.java:57)
at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
at java.security.AccessController.doPrivileged(Native Method)
at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
And if I go to content administration->KM content I get the following stack trace:
java.lang.RuntimeException: Failed to init. connection pool configuration: Failed to init. connection pool configuration: missing configurable /cm/utilities/connection_pools/db_type/default
at com.sapportals.wcm.util.jdbc.connectionpool.JDBCConnectionPoolManager.initConfig(JDBCConnectionPoolManager.java:566)
at com.sapportals.wcm.util.jdbc.connectionpool.JDBCConnectionPoolManager.getInstance(JDBCConnectionPoolManager.java:99)
at com.sapportals.wcm.repository.runtime.CmSystemInfo.createDBConnection(CmSystemInfo.java:221)
at com.sapportals.wcm.repository.runtime.CmSystemInfo.checkDB(CmSystemInfo.java:138)
at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:226)
at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:161)
at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:81)
at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:260)
at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:736)
at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:909)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1470)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1426)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1383)
at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:371)
at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
at com.sapportals.portal.prt.dispatcher.PortalInitializer.(PortalInitializer.java:129)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:765)
at com.inqmy.services.servlets_jsp.server.WebApplicationStarter.run(WebApplicationStarter.java:57)
at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
at java.security.AccessController.doPrivileged(Native Method)
at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
com.sapportals.wcm.repository.ResourceException: CM Startup failed: CM startup failed: Failed to init. connection pool configuration: Failed to init. connection pool configuration: missing configurable /cm/utilities/connection_pools/db_type/default
at com.sapportals.wcm.repository.ResourceException.fillInStackTrace(ResourceException.java:401)
at java.lang.Throwable.(Throwable.java:85)
at java.lang.Exception.(Exception.java:33)
at com.sapportals.wcm.WcmException.(WcmException.java:78)
at com.sapportals.wcm.WcmException.(WcmException.java:74)
at com.sapportals.wcm.util.content.ContentException.(ContentException.java:42)
at com.sapportals.wcm.repository.ResourceException.(ResourceException.java:251)
at com.sapportals.wcm.repository.runtime.CmAdapter.makeStartupResourceException(CmAdapter.java:397)
at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:84)
at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:260)
at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:736)
at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:909)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1470)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1426)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1383)
at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:371)
at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:55)
at com.sapportals.portal.prt.dispatcher.PortalInitializer.(PortalInitializer.java:129)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3284)
at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2542)
at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:765)
at com.inqmy.services.servlets_jsp.server.WebApplicationStarter.run(WebApplicationStarter.java:57)
at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
at java.security.AccessController.doPrivileged(Native Method)
at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
javax.servlet.ServletException: CM Startup failed: CM startup failed: Failed to init. connection pool configuration: Failed to init. connection pool configuration: missing configurable /cm/utilities/connection_pools/db_type/default
at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:111)
at com.sapportals.portal.prt.core.broker.ServletComponentItem$ServletWrapperComponent.doContent(ServletComponentItem.java:110)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:300)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:190)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:209)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:576)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:300)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:190)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:669)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:209)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:532)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:832)
at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:665)
at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:312)
at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1245)
at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
at java.security.AccessController.doPrivileged(Native Method)
at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
I appreciate any help !
PS sorry for the unstructured post, but I am hungry and want to go home now.The files under the SAPPRT share had somehow failed (some where there, but a lot of the important ones where missing).
I found out that these files were in .configarchive files in the par files to be deployed, and manually unpacked them using these two commands
$ for file in `ls -1 .par` ; do unzip $file ".configarchive" -d extracted >> logfile.txt ; done
$ for file in `ls -1 *.configarchive` ; do unzip -o $file -d extracted >> logfile.txt ; done
Afterwards I had to make some tiny customization (search for %[a-zA-Z]% , especially for the connection pools.
Then a restart, and most of it seems to work (the system will not live much longer so that is acceptable)
Maybe you are looking for
-
How do I reset the e-printer's web embedded server network password?
I have an HP Photosmart 7520 e-all in one. I use Windows 7. I could tried to set a password in the EWS network tab. I could not change the user name so it remains "admin". I set the passwork and it seemed ok. But when I tried to log on again, it wou
-
Interactive PDF: Rollover button state no longer working properly ???
Okay, what's going on with the Interactive PDFs lately? Now all my rollover buttons no longer work properly. If I have a button that's simply a black arrow, and in the rollover state it's red. No matter if I'm checking it out in the latest Acrobat R
-
Does IPC require an SAP CRM system ?
Hello, we need to install the SAP Internet Pricing and Configurator (IPC). Does this IPC require a CRM landscape ? As we have ERP usage type... Many thanks!
-
hi guys i would like to know more about this method.I want my applet to obtain information about its information and display it somewhere. Does the above method help and if so how to implement it? thanks in advance ilango
-
Combo Box missing in the output
Dear All, I cannot find the reason why combo box is not coming in the output. All the other components are coming. Please help me since i am a beginner in java. Please. import java.awt.event.*; import java.awt.*; import javax.swing.*; class update