SUN IDM 7.1 - Weblogic 8.1 SP6 Connection Pooling error

Hi,
We have a POC environment and IDM is being moved onto the weblogic server.
I need to have the IDM use the weblogic connection pooling, however i am getting the following issue:
Oracle is 10g and wl oracle drivver is oracle.jdbc.driver.OracleDriver
/lh setRepo -v -tOracle -iweblogic.jndi.WLInitialContextFactory -fCIIDMDS -ut3://localhost:29003/" -U"weblogic" -P"password"
Defaulting administrator to 'configurator'.
Defaulting credentials to 'configurator'.
DB Server @ jdbc:hsqldb:hsql://127.0.0.1:53111/idm
Checking 'OracleDataStore:CIIDMDS'...
==> java.sql.SQLException: Internal error: Invalid NLS Conversion ratio
com.waveset.util.IOException:
==> java.sql.SQLException: Internal error: Invalid NLS Conversion ratio
at com.waveset.repository.RelationalDataStore.checkDatabaseMetaData(RelationalDataStore.java:4155)
at com.waveset.repository.RelationalDataStore.init(RelationalDataStore.java:3788)
at com.waveset.install.RepoMan.check(RepoMan.java:1194)
at com.waveset.install.RepoMan.setRepo(RepoMan.java:1082)
at com.waveset.install.RepoMan.main(RepoMan.java:1314)
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 com.waveset.util.CommandProcess.invokeMain(CommandProcess.java:212)
at com.waveset.util.CommandProcess.launch(CommandProcess.java:162)
at com.waveset.util.CommandProcess.run(CommandProcess.java:300)
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 com.waveset.util.Command.main(Command.java:117)
Caused by: java.sql.SQLException: Internal error: Invalid NLS Conversion ratio
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:164)
at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_T4CConnection_814_WLStub.getMetaData(Unknown Source)
at weblogic.jdbc.rmi.SerialConnection.getMetaData(SerialConnection.java:312)
at com.waveset.util.PooledConnection.getMetaData(PooledConnection.java:213)
at com.waveset.repository.RelationalDataStore.checkDatabaseMetaData(RelationalDataStore.java:3940)
... 16 more
Caused by: java.sql.SQLException: Internal error: Invalid NLS Conversion ratio
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:227)
at oracle.jdbc.driver.PhysicalConnection.getMaxCharSize(PhysicalConnection.java:4485)
at weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection.getMaxCharSize(Unknown Source)
at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_T4CConnection.getMaxCharSize(Unknown Source)
at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_T4CConnection_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
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:415)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Wrapped exception:
java.sql.SQLException: Internal error: Invalid NLS Conversion ratio
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:164)
at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_T4CConnection_814_WLStub.getMetaData(Unknown Source)
at weblogic.jdbc.rmi.SerialConnection.getMetaData(SerialConnection.java:312)
at com.waveset.util.PooledConnection.getMetaData(PooledConnection.java:213)
at com.waveset.repository.RelationalDataStore.checkDatabaseMetaData(RelationalDataStore.java:3940)
at com.waveset.repository.RelationalDataStore.init(RelationalDataStore.java:3788)
at com.waveset.install.RepoMan.check(RepoMan.java:1194)
at com.waveset.install.RepoMan.setRepo(RepoMan.java:1082)
at com.waveset.install.RepoMan.main(RepoMan.java:1314)
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 com.waveset.util.CommandProcess.invokeMain(CommandProcess.java:212)
at com.waveset.util.CommandProcess.launch(CommandProcess.java:162)
at com.waveset.util.CommandProcess.run(CommandProcess.java:300)
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 com.waveset.util.Command.main(Command.java:117)
Caused by: java.sql.SQLException: Internal error: Invalid NLS Conversion ratio
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:227)
at oracle.jdbc.driver.PhysicalConnection.getMaxCharSize(PhysicalConnection.java:4485)
at weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection.getMaxCharSize(Unknown Source)
at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_T4CConnection.getMaxCharSize(Unknown Source)
at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_T4CConnection_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
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:415)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

Hi,
Are you getting any other Exception when performing basic operations other than ones you had mentioned like search,delete,report etc..?
What was your JDK version earlier and now?
Have you re-build the custom java classes if any?
Have you re-build the custom objects like Forms,WF,TDs etc..?
Regards,
Ferose

Similar Messages

resources connection pool error in weblogic ????!!!!!

I have pl/sql webservice that call from C#.net .
After call webservice in .net the jdbc connection of weblogic do not close
AND in Webloic have resources connection pool error .
then .net can not call this web service ..
Edited by: Esmaiel Soroor on May 31, 2013 8:34 PM

This is the wrong forum for this question.
CM.

Weblogic server not starting due to connection pool error.

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

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

Weblogic 6.1 sp2 Connection Pool will not connect to oci901 driver

ok, I am trying to get weblogic to connect to the connection pool in solaris. I created
the pool in the console with the following:
URL = jdbc:weblogic:oracle
Driver Class Name = weblogic.jdbc.oci.Driver
Properties = user=sa password=*****
I also set the LD_LIBRARY PATH as directed.
LD_LIBRARY_PATH=/usr/local/wlserver6.1/lib/solaris/oci901_8:ORACLE/lib
Oracle is on a seperate box then the box that Weblogic is installed on so I think
the problem is in my LD_LIBRARY_PATH. Here is the error I am getting. Any help
would be appreciated.
Starting Loading jDriver/Oracle .....
<Jun 7, 2002 9:04:25 AM CDT> <Error> <JDBC> <Cannot startup connection pool "FargoPool"
weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: System.loadLibrary(weblogicoci37) threw java.lang.UnsatisfiedLinkError:
/usr/local/wlserver6.1/lib/solaris/oci901_8/libweblogicoci37.so: ld.so.1: /home/bea/jdk131/jre/bin/../bin/sparc/native_threads/java:
fatal: libclntsh.so.9.0: open failed: No such file or directory
at weblogic.jdbc.oci.Driver.loadLibraryIfNeeded(Driver.java:226)
at weblogic.jdbc.oci.Driver.connect(Driver.java:76)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:193)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy8.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy17.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:209)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy8.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy17.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

"Tim" <[email protected]> wrote:
>
I have the following setup.
For QA, 1 IIS Server (using plug-in from 6.1 SP2) forwarding all request
to a
cluster on the backend. (2 Physical Servers, 4 JVM's). I do have a firewall
in
between the IIS Server & the backend servers.
According to the docs, the IIS plug-in is supposed to establish a connection
pool
to the backend. I do not see this behavior.
I see a connection created/close per request.
So , I have 2 questions:
1. Does the IIS Plug-in use connection Pooling, Do you have to enable
it ?
2. How do I control the pool size ?
Thanks in advance,
TimDoes anyone from BEA monitor this newsgroup ?
I have also opened up a case (1 week old) with tech support and still do not have
an answer. This is very frustrating considering the cost of owning this environment.
Tim

Weblogic Eclipselink Sequence Table Connection Pool Sequence Separate transaction while JTA on main transaction

Hi,
And thanks in advance for your support.
In weblogic 12, managing to get the eclipse link connection sequencing mechanism when one uses Tables for sequencing entity ids seems to be complicated.
QUICK REFERENCE:
http://www.eclipse.org/eclipselink/api/2.5/org/eclipse/persistence/config/PersistenceUnitProperties.html
The concept:
While having EJB, MDBs etc... run on a JEE container, be it glassfish or weblogic, it should be possible to have the main thread transaction be managed as part of JTA global transactions by the contianer.
Namely, pumping messages to JMS queues, persisting entities etc.
Meanwhile, it should be also possible to as the transaction is on going write and update entity ids from sequencing tables.
For this very purpose, eclipse link provides persistence.xml properties, such as the now deprecated eclipselink.jdbc.sequence-connection-pool" value="true", to fullfill this very purpose.
This option greatly avoids dead longs, by allowing eclipse link to fetch a non JTA managed connection, pseudo "two phase locking read table update table" go to the datbase and fetch a new sequence.
The same mechnism under JTA is a disaster. A transaction that creates ten different entities, might do ten reads and updates on this table, while mean while a competing transaction might be trying to do the same. It is guaranteed dead lock with minimal stress on the environment.
Under glassfish, for example, tagging a persistence.xml with :
<persistence-unit name="MY_PU" transaction-type="JTA">
        <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
        <jta-data-source>jdbc/DERBY_DS</jta-data-source>
        <non-jta-data-source>jdbc/DERBY_DS</non-jta-data-source>
        <properties>
            <property name="eclipselink.jdbc.sequence-connection-pool" value="true" />
        </properties>
</peristence-unit>
does miracles, when entities are using TABLE sequencing.
Under weblogic, say you are using the Derby embedded XA driver with two phase commit, deploying the applicaiton immediately leads to:
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.3.v20120629-r11760): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Cannot call commit when using distributed transactions
Error Code: 0
at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:324)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicCommitTransaction(DatabaseAccessor.java:426)
at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.commitTransaction(DatasourceAccessor.java:389)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.commitTransaction(DatabaseAccessor.java:409)
at org.eclipse.persistence.internal.sequencing.SequencingManager$Preallocation_Transaction_Accessor_State.getNextValue(SequencingManager.java:579)
at org.eclipse.persistence.internal.sequencing.SequencingManager.getNextValue(SequencingManager.java:1067)
at org.eclipse.persistence.internal.sequencing.ClientSessionSequencing.getNextValue(ClientSessionSequencing.java:70)
at org.eclipse.persi
While weblogic is right that their might be a distributed transaction ongoing, it is mistaken in the fact tha tthe connection requested by eclipse link for generating the ID should be part of the global transaciton.
Eclipse link provides other ways to attempt to configure the sequencing mechanism, by sating for example a non-jta transaction.
I have attempted also using these properties both withe original data DERBY_DS that uses the XA driver, and later with a new data source i created on purpose to try to work around the sequencing contengy.
For example:

            
This new DERBY_SEQUENCING_NON_JTA is explicitly configured to use a NON_XA driver with global transactions flag set to disabled.
Regardless, the only thing I get out of this is that the application is deployed and super fast, up to the point where i stress it with a system test that introduces some degreee of concurrency, and then I see the dead locks on the sequencing table.
Meaning that the ongoing transactions are holding tight to their locks on the sequencing table.
Is this a known issue?
Is there something I am missing in the configuration?
It really should not be this diffcult to get eclipse link to run its sequence reads and updates on a separate transaction of the main JTA transaction, but so far looks impossible.
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.3.v20120629-r11760): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested
Error Code: 30000
Call: UPDATE ID_GEN SET SEQ_VALUE = SEQ_VALUE + ? WHERE SEQ_NAME = ?
bind => [2 parameters bound]
Query: DataModifyQuery(name="MyEntity_Gen" sql="UPDATE ID_GEN SET SEQ_VALUE = SEQ_VALUE + ? WHERE SEQ_NAME = ?")
Many thanks for your help.

Are you calling the cmp bean code and your new Sql code under a same transactional context?
The following setting
"rollbackLocalTxUponConnClose=true"
will make the connectionpool to call the rollback method on the connection object before keeping it back in the pool. In your sql code if you are calling connection.close() , then your entire transaction will be rolled back.
CMP bean requires a transactional connection while communicating with the database.
What is the sequence of code execution?
I think you must be calling sql code first and then cmp bean code later.
You may avoid this problem in this way. This is my guess based on my understanding on your code execution.
1. set rollbackLocalTxUponConnClose=false
Execute the sql code and cmp code in a single transaction (in a single session bean method with cmt or bmt transaction ). Specify tx.rollback if it is bmt. or call tx.setRollbackOnly() if it is a cmt. In this way you will have control to roll back the transactions.
Hope this helps you.
bmt-> bean managed transaction
cmt-> container managed transaction.
Regards,
Seshi.

WebLogic 6.1 losing connection pools and deployments on restart

Hi,
Has anyone else seen a problem where it appears that processing of
config.xml is incomplete, without any error message? For example, a
connection pool that is deployed fine through the console, shows as
undeployed (available) when the server is restarted, regardless of how the
server is shut down.
Most recently, this happened with a connection pool and tx data source I've
been using for weeks, when I added a RDBMSRealm going to the same database.
The EJB deployment that needs the tx data source fails on startup, but if I
redeploy the connection pool and tx data source through the console and then
deploy the EJBs everything works. Until I restart the server, when the
problem recurs.
If I go back to my backed up config.xml, without the RDBMSRealm, everything
works fine at startup.
I see no error message in any log file: it's as though config.xml entries
are being ignored.
I attach my config.xml file. The multiple targets are the result of
redeploying through the console: editing them out does't fix the problem.
Regards,
Rod Johnson
[config.xml]

hi.
Please post this question in weblogic.developer.interest.jdbc.
Thanks,
Michael
Rod Johnson wrote:
Hi,
Has anyone else seen a problem where it appears that processing of
config.xml is incomplete, without any error message? For example, a
connection pool that is deployed fine through the console, shows as
undeployed (available) when the server is restarted, regardless of how the
server is shut down.
Most recently, this happened with a connection pool and tx data source I've
been using for weeks, when I added a RDBMSRealm going to the same database.
The EJB deployment that needs the tx data source fails on startup, but if I
redeploy the connection pool and tx data source through the console and then
deploy the EJBs everything works. Until I restart the server, when the
problem recurs.
If I go back to my backed up config.xml, without the RDBMSRealm, everything
works fine at startup.
I see no error message in any log file: it's as though config.xml entries
are being ignored.
I attach my config.xml file. The multiple targets are the result of
redeploying through the console: editing them out does't fix the problem.
Regards,
Rod Johnson
<?xml version="1.0" encoding="UTF-8"?>

<Domain Name="rj">
<Log FileName="config/rj/logs/wl-domain.log" Name="rj"/>
<Application Deployed="true" Name="ticket-app" Path=".\config\rj\applications\ticket-app">
<EJBComponent Name="ticket-ejb/ticket-ejb"
Targets="rj,rj,rj,rj,rj,rj" URI="ticket-ejb/ticket-ejb.jar"/>
<WebAppComponent Name="ticket-war" Targets="rj,rj" URI="ticket-war"/>
</Application>
<Security GuestDisabled="false" Name="rj"
PasswordPolicy="wl_default_password_policy" Realm="wl_default_realm"/>
<CustomRealm
ConfigurationData="server.host=ldapserver.example.com;membership.scope.depth=1;microsoft.membership.scope=sub;membership.filter=(|(&(memberobject=%M)(objectclass=memberof))(&(groupobject=%M)(objectclass=groupmemberof)));group.dn=ou=Groups, o=ExampleMembershipDir;group.filter=(&(cn=%g)(objectclass=mgroup));server.principal=cn=Administrator, ou=Members, o=ExampleMembershipDir;user.dn=ou=Members, o=ExampleMembershipDir;user.filter=(&(cn=%u)(objectclass=member))"
Name="defaultLDAPRealmForMicrosoftSiteServer"
Notes="This is provided as an example. Before enabling this Realm, you must edit the configuration parameters as appropriate for your environment."
Password="{3DES}aTzgEUdjzAqaEDs0MC2lBQ==" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<JDBCTxDataSource JNDIName="ticket-ds" Name="ticket-ds"
PoolName="ticket-pool" Targets="rj,rj,rj,rj"/>
<Application Deployed="true" Name="DefaultWebApp" Path=".\config\rj\applications">
<WebAppComponent Name="DefaultWebApp" Targets="rj" URI="DefaultWebApp"/>
</Application>
<PasswordPolicy Name="wl_default_password_policy"/>
<JTA Name="rj"/>
<Application Deployed="true" Name="certificate" Path=".\config\rj\applications">
<WebAppComponent Name="certificate" Targets="rj" URI="certificate.war"/>
</Application>
<Realm CachingRealm="ticketCaching Realm"
FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
<CachingRealm BasicRealm="ticketRDBMS Realm" Name="ticketCaching Realm"/>
<JDBCConnectionPool DriverName="COM.cloudscape.core.RmiJdbcDriver"
InitialCapacity="3" MaxCapacity="15" Name="ticket-pool"
Properties="user=portal;password=portal" Targets="rj,rj,rj,rj" URL="jdbc:cloudscape:rmi:d:\\book\\db\\csdb"/>
<DomainLogFilter Name="MyDomain Log Filter" SeverityLevel="64" SubsystemNames="JTA,EJB"/>
<Server DomainLogFilter="MyDomain Log Filter" ListenPort="7001"
Name="rj" NativeIOEnabled="true" StdoutDebugEnabled="true"
StdoutSeverityLevel="64" TransactionLogFilePrefix="config/rj/logs/">
<ExecuteQueue Name="default" ThreadCount="15"/>
<KernelDebug Name="rj"/>
<Log FileName="config/rj/logs/weblogic.log" Name="rj"/>
<ServerStart Name="rj"/>
<ServerDebug Name="rj"/>
<WebServer DefaultWebApp="DefaultWebApp"
LogFileName="./config/rj/logs/access.log"
LoggingEnabled="true" Name="rj"/>
<SSL Enabled="true" ListenPort="7002" Name="rj"
ServerCertificateChainFileName="config/rj/ca.pem"
ServerCertificateFileName="config/rj/democert.pem" ServerKeyFileName="config/rj/demokey.pem"/>
</Server>
<SNMPAgent Name="rj"/>
<ApplicationManager Name="rj"/>
<CustomRealm
ConfigurationData="user.filter=(&(uid=%u)(objectclass=person));user.dn=ou=people, dc=example, dc=com;server.principal=cn=Manager, dc=example, dc=com;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=ldapserver.example.com;group.dn=ou=groups, dc=example, c=com"
Name="defaultLDAPRealmForOpenLDAPDirectoryServices"
Notes="This is provided as an example. Before enabling this Realm, you must edit the configuration parameters as appropriate for your environment."
Password="{3DES}aTzgEUdjzAqaEDs0MC2lBQ==" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<CustomRealm
ConfigurationData="user.filter=(&(uid=%u)(objectclass=person));user.dn=ou=people, o=beasys.com;server.principal=uid=admin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=ldapserver.example.com;group.dn=ou=groups, o=beasys.com"
Name="defaultLDAPRealmForNetscapeDirectoryServer"
Notes="This is provided as an example. Before enabling this Realm, you must edit the configuration parameters as appropriate for your environment."
Password="{3DES}aTzgEUdjzAqaEDs0MC2lBQ==" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<FileRealm Name="wl_default_file_realm"/>
<CustomRealm
ConfigurationData="user.filter=(&(cn=%u)(objectclass=person));user.dn=ou=people, o=example.com;server.principal=cn=admin, o=example.com;membership.filter=(&(member=%M)(objectclass=groupofuniquenames));group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=ldapserver.example.com;server.ssl=true;group.dn=ou=groups, o=example.com"
Name="defaultLDAPRealmForNovellDirectoryServices"
Notes="This is provided as an example. Before enabling this Realm, you must edit the configuration parameters as appropriate for your environment."
Password="{3DES}aTzgEUdjzAqaEDs0MC2lBQ==" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<RDBMSRealm DatabaseDriver="COM.cloudscape.core.RmiJdbcDriver"
DatabaseURL="jdbc:cloudscape:rmi:d:\\book\\db\\csdb"
DatabaseUserName="portal" Name="ticketRDBMS Realm" SchemaProperties="getGroupMembers=SELECT GM_GROUP, GM_MEMBER from groupmembers WHERE GM_GROUP = ?;deleteGroup2=DELETE FROM aclentries WHERE A_PRINCIPAL = ?;deleteGroup1=DELETE FROM groupmembers WHERE GM_GROUP = ?;addGroupMember=INSERT INTO groupmembers VALUES ( ? , ? );getUser=SELECT EMAIL, PASSWORD FROM LOGINS WHERE EMAIL = ?;getPermission=SELECT DISTINCT A_PERMISSION FROM aclentries WHERE A_PERMISSION = ?;deleteUser3=DELETE FROM aclentries WHERE A_PRINCIPAL = ?;getGroupNewStatement=true;deleteUser2=DELETE FROM groupmembers WHERE GM_MEMBER = ?;deleteUser1=DELETE FROM LOGINS WHERE EMAIL = ?;getAcls=SELECT A_NAME, A_PRINCIPAL, A_PERMISSION FROM aclentries ORDER BY A_NAME, A_PRINCIPAL;getUsers=SELECT EMAIL, PASSWORD FROM LOGINS;getGroups=SELECT GM_GROUP, GM_MEMBER FROM groupmembers;getPermissions=SELECT DISTINCT A_PERMISSION FROM aclentries;getAclEntries=SELECT A_NAME, A_PRINCIPAL, A_PERMISSION FROM aclentries WHERE A_NAME = ?
ORDER BY A_PRINCIPAL;newUser=INSERT INTO LOGINS VALUES ( ? , ? );removeGroupMember=DELETE FROM groupmembers WHERE GM_GROUP = ? AND GM_MEMBER = ?"/>
</Domain>--
Developer Relations Engineer
BEA Support

Connection pool error with oracle 11g and weblogic 10

Hi,
my code is:
public Connection getConnection() {
          properties = new Properties();
          properties.put(Context.INITIAL_CONTEXT_FACTORY,
                    "weblogic.jndi.T3InitialContextFactory");
          //properties.put(Context.SECURITY_PRINCIPAL, "weblogic");
          //properties.put(Context.SECURITY_CREDENTIALS, "weblogic");
          properties.put(Context.PROVIDER_URL, "t3://172.23.61.214:7001/");
          try {
               initialContext = new InitialContext(properties);
               datasource = (DataSource) initialContext.lookup("sample_jndi");
               try {
                    connection = datasource.getConnection();
               } catch (SQLException e) {
                    e.printStackTrace();
          } catch (NamingException e) {
               e.printStackTrace();
          return connection;
it is giving Exception at line " connection = datasource.getConnection(); "
Exception is:
javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
     java.io.EOFException]
     at weblogic.jrmp.Context.lookup(Context.java:189)
     at weblogic.jrmp.Context.lookup(Context.java:195)
     at javax.naming.InitialContext.lookup(Unknown Source)
     at com.code.sample.connectionDB.JDBCConnectionPool.getConnection(JDBCConnectionPool.java:35)
     at com.code.sample.connectionDB.JDBCConnectionPool.main(JDBCConnectionPool.java:52)
Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
     java.io.EOFException
     at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
     at sun.rmi.server.UnicastRef.newCall(Unknown Source)
     at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
     at weblogic.jrmp.Context.lookup(Context.java:185)
     ... 4 more
Caused by: java.io.EOFException
     at java.io.DataInputStream.readByte(Unknown Source)
     ... 9 more
Please Advice.... Thanks

I removed the "/" and tried..
But the exception is same:
javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
     java.io.EOFException]
     at weblogic.jrmp.Context.lookup(Context.java:189)
     at weblogic.jrmp.Context.lookup(Context.java:195)
     at javax.naming.InitialContext.lookup(Unknown Source)
     at com.code.sample.connectionDB.JDBCConnectionPool.getConnection(JDBCConnectionPool.java:35)
     at com.code.sample.connectionDB.JDBCConnectionPool.main(JDBCConnectionPool.java:52)
Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
     java.io.EOFException
     at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
     at sun.rmi.server.UnicastRef.newCall(Unknown Source)
     at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
     at weblogic.jrmp.Context.lookup(Context.java:185)
     ... 4 more
Caused by: java.io.EOFException
     at java.io.DataInputStream.readByte(Unknown Source)
     ... 9 more

WebLogic 11g data source connection pooling failed with IO error:socket read timed out.

Hi all,
We encountered IO Error: Socket read timed out( <Received exception while creating connection for pool "DS_1": IO Error: Socket read timed out> ) during the creation of data sources in WebLogic 11g. Manual data source testing seems to indicate intermittent connection and the server seems to take a long time to start up with multiple IO errors. We increased the timeout at the database side but it does not seems to help. The database is 11g (11.2.0.3). The database services and listener are up which does not indicate that the database instance is down.

This particular error means your database is down and socket is timedout. Or the query takes so long that the reader timedout -- unlikely.
Also, the general weblogic socket write errors, which you might see sometimes means that the client got disconnected before the server wrote results back. This is harmless

Problem with Weblogic 9.1 JDBC connection pooling

Hi,
We are currently in the middle of a migration from JBoss & WAS to BEA Weblogic. Both in JBoss and Websphere there are no problems with the connection but in Weblogic we (quickly) run out of connections.
Our project uses Hibernate 3.1.3, Spring 1.2.7 and EJB 2.1. Using CMT and Spring to connect to our Oracle database. We tried different using the different drivers Weblogic offers, XA and non-AX, but in all cases we create connections quickly but they are almost never closed... until we run out of connections and get a Exception.
Any ideas what this could be? Are there known errors?

Roy van Rijn wrote:
Hi,
We are currently in the middle of a migration from JBoss & WAS to BEA Weblogic. Both in JBoss and Websphere there are no problems with the connection but in Weblogic we (quickly) run out of connections.
Our project uses Hibernate 3.1.3, Spring 1.2.7 and EJB 2.1. Using CMT and Spring to connect to our Oracle database. We tried different using the different drivers Weblogic offers, XA and non-AX, but in all cases we create connections quickly but they are almost never closed... until we run out of connections and get a Exception.
Any ideas what this could be? Are there known errors?Hi. Please try setting the pool's idle-connection-timeout to 10 seconds or something
reasonable, and we'll forcibly retract any leaked connections. So you don't write any
JDBC code yourself, right?
Joe

SUN TEAM URGENT: auto creation of data source, connection pool, ...etc

to the sun team,
i have been using NB+VWP to deploy an application created in JSCU2 to a Sun App Server 9.
for some reason, whenever am viewing a DB connection in the servers window and drag-drop a table on the page, the system is automatically creating a new data source, a new conneciton pool, and new jdbc resource. also, it is removing the necessary references in web.xml and sun-web.xml.
is there any way to get around this? otherwise, i am forced to modify the jdbc settings in the server as well as the config file each i drag-drop a DB table/view.
thanks so much
- Peter

Unfortunately, this is a bug and should be fixed in the next release.
I'll look for the issue id.
In the meantime, this workaround may help:
http://wiki.netbeans.org/wiki/view/VWPUserFAQsavewebxml
John Baker
http://blogs.sun.com/dashboy

Error when calling powershell from Sun IDM

Hello Experts,
In our environment we have a powershell script which takes command-line arguments as input and creates mailbox. To create a mailbox for newly on-boarded user we just need to call this script and pass the args. When i run the script from Gateway server (by physically logging into the server) it works as expected but when i call the same script from Sun IDM (using resource actions) I'm getting the following error,
The type initializer for 'InstanceContext' threw an exception
any idea to fix or troubleshoot this?
We are using Sun IDM 6.0 SP1 and exchange 2007.

Which version of the Gateway?
Are you calling the script with afterAction scriptcalls?
Adapter or connector?
I do know that the powershellcalls are supposed to have two restrictions which are truly hampering...
1.0 (which means not remote calls?) and 32 bits.
If you have any insights, please share :D
I will start coding agains this next week I think, so I guess I will see all problems then :D

Unable to create connection pool on weblogic startup

Hi, I have a problem currently with the connection pool of weblogic 8.1 not being able to be created on a scheduled restart daily.
The weblogic server is restarted daily at 6am. However, the oracle database is shut down for maintenance daily till 7am before it is up again. It is not possible to shift either timings of restarting weblogic and oracle.
Is there any script or option settings in weblogic to reconnect the connection pool after 7am daily without restarting the weblogic instance?
Please help. Thanks.

Kwee Tin Toh wrote:
Hi, I have a problem currently with the connection pool of weblogic 8.1 not being able to be created on a scheduled restart daily.
The weblogic server is restarted daily at 6am. However, the oracle database is shut down for maintenance daily till 7am before it is up again. It is not possible to shift either timings of restarting weblogic and oracle.
Is there any script or option settings in weblogic to reconnect the connection pool after 7am daily without restarting the weblogic instance?
Please help. Thanks.You can use the weblogic.Admin command line program to create, destroy, disable, or enable pools
in a running server. However, the easiest thing to do is to define your pool to have an initial
capacity of zero, so it is allowed to be created at startup, without needing to make any connections.
Then it will self-populate as needed when application load starts, if/when the DBMS is available.
Joe

Multiple Connection Pools in Weblogic

Hello.
We have a requirement whereby a user logging on to an existing web application has the option to then use another application that uses a different database.
So.. I configured Weblogic with a second Connection Pool and a second Data Source, which references the new Connection Pool.
In order acces the new Connection Pool, I tried this:
      Context ctx = null;
      Hashtable ht = new Hashtable();
      ht.put(Context.INITIAL_CONTEXT_FACTORY,
          "weblogic.jndi.WLInitialContextFactory");
      ht.put(Context.PROVIDER_URL, "ourProviderUrl");
      ctx = new InitialContext(ht);
      ds = (javax.sql.DataSource) ctx.lookup("newDataSourceName");but it didn't work. The Data Source couldn't be resolved (I don't have the stack trace of the exception at the moment.)
How can I access the different connection pools?
Am I going about this the wrong way?
Help much appreciated!!

Here's the stack trace:
java.rmi.UnexpectedException: Unexpected exception in indecs.bip.services.UserManagerEJB.getNumSesionesActivas():
java.lang.Exception: javax.transaction.TransactionRolledbackException: Error in ejbCreate:: javax.ejb.CreateException: SessionManager.create error: javax.naming.NameNotFoundException: Unable to resolv
e 'TxBIPDataSource' Resolved: '' Unresolved:'TxBIPDataSource' ; remaining name 'TxBIPDataSource'
        at indecs.bip.services.SessionManagerEJB.ejbCreate(SessionManagerEJB.java:235)
        at indecs.bip.services.SessionManagerEJB_qjvfpz_Impl.ejbCreate(SessionManagerEJB_qjvfpz_Impl.java:112)
        at java.lang.reflect.Method.invoke(Native Method)
        at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:148)
        at weblogic.ejb20.pool.StatelessSessionPool.getBean(StatelessSessionPool.java:98)
        at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:154)
        at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:126)
        at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:61)
        at indecs.bip.services.SessionManagerEJB_qjvfpz_EOImpl.getSesion(SessionManagerEJB_qjvfpz_EOImpl.java:29)
        at indecs.bip.services.UserManagerEJB.getNumSesionesActivas(UserManagerEJB.java:79)
        at indecs.bip.services.UserManagerEJB_ymjd1a_EOImpl.getNumSesionesActivas(UserManagerEJB_ymjd1a_EOImpl.java:1254)
        at indecs.bip.services.UserManagerEJB_ymjd1a_EOImpl_WLSkel.invoke(Unknown Source)
        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:359)
        at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:114)
        at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
        at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:762)
        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
        at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)"TxBIPDataSource" is the name of the original Data Source.

WebLogic 6.0 SP1 - No JdbcServices for connection pools.

"My question is what version of WebLogic will the progromatic connection pool creation be re-introduced? Is it available in SP2 or version

Edit the registry.xml file and change "6.0 Beta" to "6.0"
-Greg
On 12 Mar 2001 10:02:19 -0800, "Raman Trikkur" <[email protected]>
wrote:
>
Hello Kumar,
Here is my registry.xml.
<?xml version="1.0" encoding="UTF-8"?>
<bea-product-information>
<host name="ramantrik2pc">
<product name="WebLogic Server" format="1.0">
<release level="6.0 Beta" Status="installed" InstallDir="D:\bea\wlserver6.0"
InstallTime="Mar 1, 2001 5:18:57 PM" InstallSet="Server">
<component name="Program" />
<component name="Samples" />
</release>
</product>
</host>
</bea-product-information>
Thanks for helping me figure this out. If this doesn't work,
I'll just try installing the whole package (WLS 6.0 with SP1
applied) as Xiang suggested.
Regards,
Raman
Kumar Allamraju <[email protected]> wrote:
could you post your registry.xml ?
Raman Trikkur wrote:
Hi,
I'm trying to get the service pack SP1 ((wls60sp1_upgrade_win.exe)
) installed on my NT box. I have wls 6.0 installed andworking.
After unpacking and choosing my bea home directory (D:\bea),I
get an error that says "Weblogic Server Service Pack1 Installation
failed. You do not seem to have Weblogic server 6.0installed for
BEAHOME D:\bea".
But that is untrue. I DO have it installed in D:\bea,and I have
the environment shell up by running setEnv.cmd and Iinvoked the
service pack installer from within that shell.
Is there anything I'm missing? Has anyone else encounteredthis
problem? Any help with this would be much appreciated.
Regards,
Raman

Getting Error IDM8.1patch11WebLogic Server com/sun/idm/idmx/txn/Transaction

I installed IDM 8.1 Patch 11 on WebLogic server. When I start the server I am getting following error. The Login page never shows up. I will appreciate if you can give me the pointer.
] Root cause of ServletException.
java.lang.NoClassDefFoundError: com/sun/idm/idmx/txn/TransactionManager
     at com.waveset.ui.LoginHelper.csrfGuardTokenEnabled(LoginHelper.java:2471)
     at com.waveset.ui.LoginHelper.handleCSRFGuardToken(LoginHelper.java:2186)
     at jsp_servlet.__login._jspService(__login.java:251)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at com.sun.idm.profiler.instrumentation.RequestTimingFilter.doFilter(RequestTimingFilter.java:76)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Edited by: 842717 on Mar 8, 2011 12:16 PM

You are receiving this error because one of the fields being pulled from IdM, exceeds he column limit defined in the GLOBALUSERS database table.
I received this error before because the PRIMARYEMAIL column in the GLOBALUSERS table was defined as [PRIMARYEMAIL] [nvarchar](50).
I went into Microsoft SQL Server Management Studio and updated the field to [PRIMARYEMAIL] [nvarchar](100), and then the import worked.
Hope this helps,
Larry L. Viars | Senior Consultant
Logic Trends, Identity & Access Management Specialists

SUN IDM 7.1 - Weblogic 8.1 SP6 Connection Pooling error

Similar Messages

Maybe you are looking for