Weblogic Pool Driver doesn't support XA driver - Weblogic

This is a discussion on Weblogic Pool Driver doesn't support XA driver - Weblogic ; I am trying to set up a JDBC Strore for a JMS Server. The JDBC Store uses the Oracle XA driver (oracle.jdbc.xa.client.OracleXADataSource). However whaen the JMS server starts it gives me the following exception: Weblogic Pool Driver doesn't support XA ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: Weblogic Pool Driver doesn't support XA driver

  1. Weblogic Pool Driver doesn't support XA driver


    I am trying to set up a JDBC Strore for a JMS Server. The JDBC Store uses the Oracle
    XA driver (oracle.jdbc.xa.client.OracleXADataSource). However whaen the JMS server
    starts it gives me the following exception: Weblogic Pool Driver doesn't support
    XA driver. Any idea what I am doing wrong? I am using WL 8.1 SP2. THe full error
    trace is shown below:

    store failed to open java.io.IOException: JMS JDBC store, connection pool = ,
    prefix = : cannot determine DBMS type
    Driver doesn't support XA driver, Please change your config to use a Non-XA driver
    < at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThro wResourceException(JDBCUtil.java:160)
    < at weblogic.jdbc.pool.Driver.connect(Driver.java:156)
    < at weblogic.jms.store.JDBCIOStream.checkDbmsType(JDBC IOStream.java:1490)
    < at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream. java:420)
    < 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:15 1)
    < at weblogic.jms.backend.BackEnd.openStores(BackEnd.ja va:1171)
    < at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1 290)
    < at weblogic.jms.JMSService.addJMSServer(JMSService.ja va:2241)
    < at weblogic.jms.JMSService.addDeployment(JMSService.j ava:2012)
    < at weblogic.management.mbeans.custom.DeploymentTarget .addDeployment(DeploymentTarget.java:330)
    < at weblogic.management.mbeans.custom.DeploymentTarget .addDeployments(DeploymentTarget.java:590)
    < at weblogic.management.mbeans.custom.DeploymentTarget .updateServerDeployments(DeploymentTarget.java:568 )
    < at weblogic.management.mbeans.custom.DeploymentTarget .updateDeployments(DeploymentTarget.java:240)
    < at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    < at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    < at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    < at java.lang.reflect.Method.invoke(Method.java:324)
    < at weblogic.management.internal.DynamicMBeanImpl.invo keLocally(DynamicMBeanImpl.java:711)
    < at weblogic.management.internal.DynamicMBeanImpl.invo ke(DynamicMBeanImpl.java:690)
    < at weblogic.management.internal.ConfigurationMBeanImp l.invoke(ConfigurationMBeanImpl.java:476)
    < at com.sun.management.jmx.MBeanServerImpl.invoke(MBea nServerImpl.java:1557)
    < at com.sun.management.jmx.MBeanServerImpl.invoke(MBea nServerImpl.java:1525)
    < at weblogic.management.internal.RemoteMBeanServerImpl .private_invoke(RemoteMBeanServerImpl.java:947)
    < at weblogic.management.internal.RemoteMBeanServerImpl .invoke(RemoteMBeanServerImpl.java:908)
    < at weblogic.management.internal.MBeanProxy.invoke(MBe anProxy.java:946)
    < at weblogic.management.internal.MBeanProxy.invokeForC achingStub(MBeanProxy.java:481)
    < at weblogic.management.configuration.ServerMBean_Stub .updateDeployments(ServerMBean_Stub.java:7271)
    < at weblogic.management.deploy.slave.SlaveDeployer.upd ateServerDeployments(SlaveDeployer.java:1210)
    < at weblogic.management.deploy.slave.SlaveDeployer.res ume(SlaveDeployer.java:362)
    < at weblogic.management.deploy.DeploymentManagerServer LifeCycleImpl.resume(DeploymentManagerServerLifeCy cleImpl.java:229)
    < at weblogic.t3.srvr.SubsystemManager.resume(Subsystem Manager.java:131)
    < at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
    < at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
    < at weblogic.Server.main(Server.java:32)


  2. Re: Weblogic Pool Driver doesn't support XA driver

    Just use a non-XA driver and non-XA pool for JMS JDBC stores.
    WL JMS' XA capability does not come from its JDBC driver.

    Naresh Bhatia wrote:

    > I am trying to set up a JDBC Strore for a JMS Server. The JDBC Store uses the Oracle
    > XA driver (oracle.jdbc.xa.client.OracleXADataSource). However whaen the JMS server
    > starts it gives me the following exception: Weblogic Pool Driver doesn't support
    > XA driver. Any idea what I am doing wrong? I am using WL 8.1 SP2. THe full error
    > trace is shown below:
    >
    > > store failed to open java.io.IOException: JMS JDBC store, connection pool = ,
    > prefix = : cannot determine DBMS type
    > > Driver doesn't support XA driver, Please change your config to use a Non-XA driver
    > < at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThro wResourceException(JDBCUtil.java:160)
    > < at weblogic.jdbc.pool.Driver.connect(Driver.java:156)
    > < at weblogic.jms.store.JDBCIOStream.checkDbmsType(JDBC IOStream.java:1490)
    > < at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream. java:420)
    > < 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:15 1)
    > < at weblogic.jms.backend.BackEnd.openStores(BackEnd.ja va:1171)
    > < at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1 290)
    > < at weblogic.jms.JMSService.addJMSServer(JMSService.ja va:2241)
    > < at weblogic.jms.JMSService.addDeployment(JMSService.j ava:2012)
    > < at weblogic.management.mbeans.custom.DeploymentTarget .addDeployment(DeploymentTarget.java:330)
    > < at weblogic.management.mbeans.custom.DeploymentTarget .addDeployments(DeploymentTarget.java:590)
    > < at weblogic.management.mbeans.custom.DeploymentTarget .updateServerDeployments(DeploymentTarget.java:568 )
    > < at weblogic.management.mbeans.custom.DeploymentTarget .updateDeployments(DeploymentTarget.java:240)
    > < at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    > < at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    > < at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    > < at java.lang.reflect.Method.invoke(Method.java:324)
    > < at weblogic.management.internal.DynamicMBeanImpl.invo keLocally(DynamicMBeanImpl.java:711)
    > < at weblogic.management.internal.DynamicMBeanImpl.invo ke(DynamicMBeanImpl.java:690)
    > < at weblogic.management.internal.ConfigurationMBeanImp l.invoke(ConfigurationMBeanImpl.java:476)
    > < at com.sun.management.jmx.MBeanServerImpl.invoke(MBea nServerImpl.java:1557)
    > < at com.sun.management.jmx.MBeanServerImpl.invoke(MBea nServerImpl.java:1525)
    > < at weblogic.management.internal.RemoteMBeanServerImpl .private_invoke(RemoteMBeanServerImpl.java:947)
    > < at weblogic.management.internal.RemoteMBeanServerImpl .invoke(RemoteMBeanServerImpl.java:908)
    > < at weblogic.management.internal.MBeanProxy.invoke(MBe anProxy.java:946)
    > < at weblogic.management.internal.MBeanProxy.invokeForC achingStub(MBeanProxy.java:481)
    > < at weblogic.management.configuration.ServerMBean_Stub .updateDeployments(ServerMBean_Stub.java:7271)
    > < at weblogic.management.deploy.slave.SlaveDeployer.upd ateServerDeployments(SlaveDeployer.java:1210)
    > < at weblogic.management.deploy.slave.SlaveDeployer.res ume(SlaveDeployer.java:362)
    > < at weblogic.management.deploy.DeploymentManagerServer LifeCycleImpl.resume(DeploymentManagerServerLifeCy cleImpl.java:229)
    > < at weblogic.t3.srvr.SubsystemManager.resume(Subsystem Manager.java:131)
    > < at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
    > < at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
    > < at weblogic.Server.main(Server.java:32)
    >



  3. Re: Weblogic Pool Driver doesn't support XA driver


    So I assume that the XA capability is enabled by checking the "XA Connection Factory
    Enabled" checkbox for the JMS connection factory.

    Thanks.
    Naresh

    Tom Barnes wrote:
    >Just use a non-XA driver and non-XA pool for JMS JDBC stores.
    >WL JMS' XA capability does not come from its JDBC driver.
    >
    >Naresh Bhatia wrote:
    >
    >> I am trying to set up a JDBC Strore for a JMS Server. The JDBC Store

    >uses the Oracle
    >> XA driver (oracle.jdbc.xa.client.OracleXADataSource). However whaen

    >the JMS server
    >> starts it gives me the following exception: Weblogic Pool Driver doesn't

    >support
    >> XA driver. Any idea what I am doing wrong? I am using WL 8.1 SP2. THe

    >full error
    >> trace is shown below:
    >>
    >>
    >"jmsTestJmsServer1"
    >> store failed to open java.io.IOException: JMS JDBC store, connection

    >pool = ,
    >> prefix = : cannot determine DBMS type
    >>
    >Weblogic Pool
    >> Driver doesn't support XA driver, Please change your config to use

    >a Non-XA driver
    >> < at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThro wResourceException(JDBCUtil.java:160)
    >> < at weblogic.jdbc.pool.Driver.connect(Driver.java:156)
    >> < at weblogic.jms.store.JDBCIOStream.checkDbmsType(JDBC IOStream.java:1490)
    >> < at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream. java:420)
    >> < 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:15 1)
    >> < at weblogic.jms.backend.BackEnd.openStores(BackEnd.ja va:1171)
    >> < at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1 290)
    >> < at weblogic.jms.JMSService.addJMSServer(JMSService.ja va:2241)
    >> < at weblogic.jms.JMSService.addDeployment(JMSService.j ava:2012)
    >> < at weblogic.management.mbeans.custom.DeploymentTarget .addDeployment(DeploymentTarget.java:330)
    >> < at weblogic.management.mbeans.custom.DeploymentTarget .addDeployments(DeploymentTarget.java:590)
    >> < at weblogic.management.mbeans.custom.DeploymentTarget .updateServerDeployments(DeploymentTarget.java:568 )
    >> < at weblogic.management.mbeans.custom.DeploymentTarget .updateDeployments(DeploymentTarget.java:240)
    >> < at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    >> < at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    >> < at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    >> < at java.lang.reflect.Method.invoke(Method.java:324)
    >> < at weblogic.management.internal.DynamicMBeanImpl.invo keLocally(DynamicMBeanImpl.java:711)
    >> < at weblogic.management.internal.DynamicMBeanImpl.invo ke(DynamicMBeanImpl.java:690)
    >> < at weblogic.management.internal.ConfigurationMBeanImp l.invoke(ConfigurationMBeanImpl.java:476)
    >> < at com.sun.management.jmx.MBeanServerImpl.invoke(MBea nServerImpl.java:1557)
    >> < at com.sun.management.jmx.MBeanServerImpl.invoke(MBea nServerImpl.java:1525)
    >> < at weblogic.management.internal.RemoteMBeanServerImpl .private_invoke(RemoteMBeanServerImpl.java:947)
    >> < at weblogic.management.internal.RemoteMBeanServerImpl .invoke(RemoteMBeanServerImpl.java:908)
    >> < at weblogic.management.internal.MBeanProxy.invoke(MBe anProxy.java:946)
    >> < at weblogic.management.internal.MBeanProxy.invokeForC achingStub(MBeanProxy.java:481)
    >> < at weblogic.management.configuration.ServerMBean_Stub .updateDeployments(ServerMBean_Stub.java:7271)
    >> < at weblogic.management.deploy.slave.SlaveDeployer.upd ateServerDeployments(SlaveDeployer.java:1210)
    >> < at weblogic.management.deploy.slave.SlaveDeployer.res ume(SlaveDeployer.java:362)
    >> < at weblogic.management.deploy.DeploymentManagerServer LifeCycleImpl.resume(DeploymentManagerServerLifeCy cleImpl.java:229)
    >> < at weblogic.t3.srvr.SubsystemManager.resume(Subsystem Manager.java:131)
    >> < at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
    >> < at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
    >> < at weblogic.Server.main(Server.java:32)
    >>

    >



  4. Re: Weblogic Pool Driver doesn't support XA driver

    Actually, all you normally need to check is "user transactions enabled".
    The XA versions of the javax.jms interfaces (which are generated
    via XA connection factories) are not required - except
    that I think that MDBs make a check for this.

    Naresh Bhatia wrote:
    > So I assume that the XA capability is enabled by checking the "XA Connection Factory
    > Enabled" checkbox for the JMS connection factory.
    >
    > Thanks.
    > Naresh
    >
    > Tom Barnes wrote:
    >
    >>Just use a non-XA driver and non-XA pool for JMS JDBC stores.
    >>WL JMS' XA capability does not come from its JDBC driver.
    >>
    >>Naresh Bhatia wrote:
    >>
    >>
    >>>I am trying to set up a JDBC Strore for a JMS Server. The JDBC Store

    >>
    >>uses the Oracle
    >>
    >>>XA driver (oracle.jdbc.xa.client.OracleXADataSource). However whaen

    >>
    >>the JMS server
    >>
    >>>starts it gives me the following exception: Weblogic Pool Driver doesn't

    >>
    >>support
    >>
    >>>XA driver. Any idea what I am doing wrong? I am using WL 8.1 SP2. THe

    >>
    >>full error
    >>
    >>>trace is shown below:
    >>>
    >>>
    >>
    >>"jmsTestJmsServer1"
    >>
    >>>store failed to open java.io.IOException: JMS JDBC store, connection

    >>
    >>pool = ,
    >>
    >>>prefix = : cannot determine DBMS type
    >>>
    >>
    >>Weblogic Pool
    >>
    >>>Driver doesn't support XA driver, Please change your config to use

    >>
    >>a Non-XA driver
    >>
    >>>< at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThro wResourceException(JDBCUtil.java:160)
    >>>< at weblogic.jdbc.pool.Driver.connect(Driver.java:156)
    >>>< at weblogic.jms.store.JDBCIOStream.checkDbmsType(JDBC IOStream.java:1490)
    >>>< at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream. java:420)
    >>>< 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:15 1)
    >>>< at weblogic.jms.backend.BackEnd.openStores(BackEnd.ja va:1171)
    >>>< at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1 290)
    >>>< at weblogic.jms.JMSService.addJMSServer(JMSService.ja va:2241)
    >>>< at weblogic.jms.JMSService.addDeployment(JMSService.j ava:2012)
    >>>< at weblogic.management.mbeans.custom.DeploymentTarget .addDeployment(DeploymentTarget.java:330)
    >>>< at weblogic.management.mbeans.custom.DeploymentTarget .addDeployments(DeploymentTarget.java:590)
    >>>< at weblogic.management.mbeans.custom.DeploymentTarget .updateServerDeployments(DeploymentTarget.java:568 )
    >>>< at weblogic.management.mbeans.custom.DeploymentTarget .updateDeployments(DeploymentTarget.java:240)
    >>>< at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    >>>< at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    >>>< at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    >>>< at java.lang.reflect.Method.invoke(Method.java:324)
    >>>< at weblogic.management.internal.DynamicMBeanImpl.invo keLocally(DynamicMBeanImpl.java:711)
    >>>< at weblogic.management.internal.DynamicMBeanImpl.invo ke(DynamicMBeanImpl.java:690)
    >>>< at weblogic.management.internal.ConfigurationMBeanImp l.invoke(ConfigurationMBeanImpl.java:476)
    >>>< at com.sun.management.jmx.MBeanServerImpl.invoke(MBea nServerImpl.java:1557)
    >>>< at com.sun.management.jmx.MBeanServerImpl.invoke(MBea nServerImpl.java:1525)
    >>>< at weblogic.management.internal.RemoteMBeanServerImpl .private_invoke(RemoteMBeanServerImpl.java:947)
    >>>< at weblogic.management.internal.RemoteMBeanServerImpl .invoke(RemoteMBeanServerImpl.java:908)
    >>>< at weblogic.management.internal.MBeanProxy.invoke(MBe anProxy.java:946)
    >>>< at weblogic.management.internal.MBeanProxy.invokeForC achingStub(MBeanProxy.java:481)
    >>>< at weblogic.management.configuration.ServerMBean_Stub .updateDeployments(ServerMBean_Stub.java:7271)
    >>>< at weblogic.management.deploy.slave.SlaveDeployer.upd ateServerDeployments(SlaveDeployer.java:1210)
    >>>< at weblogic.management.deploy.slave.SlaveDeployer.res ume(SlaveDeployer.java:362)
    >>>< at weblogic.management.deploy.DeploymentManagerServer LifeCycleImpl.resume(DeploymentManagerServerLifeCy cleImpl.java:229)
    >>>< at weblogic.t3.srvr.SubsystemManager.resume(Subsystem Manager.java:131)
    >>>< at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
    >>>< at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
    >>>< at weblogic.Server.main(Server.java:32)
    >>>

    >>

    >



  5. Re: Weblogic Pool Driver doesn't support XA driver


    It appears that WebLogic 8.1 does not have the "user transactions enabled" flag
    for a connection factory. I see references to this flag in earlier versions of
    WebLogic. The closest thing in WL 8.1 seems to be the "XA Connection Factory Enabled"
    flag.

    Tom Barnes wrote:
    >Actually, all you normally need to check is "user transactions enabled".
    >The XA versions of the javax.jms interfaces (which are generated
    >via XA connection factories) are not required - except
    >that I think that MDBs make a check for this.
    >
    >Naresh Bhatia wrote:
    >> So I assume that the XA capability is enabled by checking the "XA Connection

    >Factory
    >> Enabled" checkbox for the JMS connection factory.
    >>
    >> Thanks.
    >> Naresh
    >>
    >> Tom Barnes wrote:
    >>
    >>>Just use a non-XA driver and non-XA pool for JMS JDBC stores.
    >>>WL JMS' XA capability does not come from its JDBC driver.
    >>>
    >>>Naresh Bhatia wrote:
    >>>
    >>>
    >>>>I am trying to set up a JDBC Strore for a JMS Server. The JDBC Store
    >>>
    >>>uses the Oracle
    >>>
    >>>>XA driver (oracle.jdbc.xa.client.OracleXADataSource). However whaen
    >>>
    >>>the JMS server
    >>>
    >>>>starts it gives me the following exception: Weblogic Pool Driver doesn't
    >>>
    >>>support
    >>>
    >>>>XA driver. Any idea what I am doing wrong? I am using WL 8.1 SP2.

    >THe
    >>>
    >>>full error
    >>>
    >>>>trace is shown below:
    >>>>
    >>>> >>>
    >>>"jmsTestJmsServer1"
    >>>
    >>>>store failed to open java.io.IOException: JMS JDBC store, connection
    >>>
    >>>pool = ,
    >>>
    >>>>prefix = : cannot determine DBMS type
    >>>> >>>
    >>>Weblogic Pool
    >>>
    >>>>Driver doesn't support XA driver, Please change your config to use
    >>>
    >>>a Non-XA driver
    >>>
    >>>>< at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThro wResourceException(JDBCUtil.java:160)
    >>>>< at weblogic.jdbc.pool.Driver.connect(Driver.java:156)
    >>>>< at weblogic.jms.store.JDBCIOStream.checkDbmsType(JDBC IOStream.java:1490)
    >>>>< at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream. java:420)
    >>>>< 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:15 1)
    >>>>< at weblogic.jms.backend.BackEnd.openStores(BackEnd.ja va:1171)
    >>>>< at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1 290)
    >>>>< at weblogic.jms.JMSService.addJMSServer(JMSService.ja va:2241)
    >>>>< at weblogic.jms.JMSService.addDeployment(JMSService.j ava:2012)
    >>>>< at weblogic.management.mbeans.custom.DeploymentTarget .addDeployment(DeploymentTarget.java:330)
    >>>>< at weblogic.management.mbeans.custom.DeploymentTarget .addDeployments(DeploymentTarget.java:590)
    >>>>< at weblogic.management.mbeans.custom.DeploymentTarget .updateServerDeployments(DeploymentTarget.java:568 )
    >>>>< at weblogic.management.mbeans.custom.DeploymentTarget .updateDeployments(DeploymentTarget.java:240)
    >>>>< at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    >>>>< at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    >>>>< at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    >>>>< at java.lang.reflect.Method.invoke(Method.java:324)
    >>>>< at weblogic.management.internal.DynamicMBeanImpl.invo keLocally(DynamicMBeanImpl.java:711)
    >>>>< at weblogic.management.internal.DynamicMBeanImpl.invo ke(DynamicMBeanImpl.java:690)
    >>>>< at weblogic.management.internal.ConfigurationMBeanImp l.invoke(ConfigurationMBeanImpl.java:476)
    >>>>< at com.sun.management.jmx.MBeanServerImpl.invoke(MBea nServerImpl.java:1557)
    >>>>< at com.sun.management.jmx.MBeanServerImpl.invoke(MBea nServerImpl.java:1525)
    >>>>< at weblogic.management.internal.RemoteMBeanServerImpl .private_invoke(RemoteMBeanServerImpl.java:947)
    >>>>< at weblogic.management.internal.RemoteMBeanServerImpl .invoke(RemoteMBeanServerImpl.java:908)
    >>>>< at weblogic.management.internal.MBeanProxy.invoke(MBe anProxy.java:946)
    >>>>< at weblogic.management.internal.MBeanProxy.invokeForC achingStub(MBeanProxy.java:481)
    >>>>< at weblogic.management.configuration.ServerMBean_Stub .updateDeployments(ServerMBean_Stub.java:7271)
    >>>>< at weblogic.management.deploy.slave.SlaveDeployer.upd ateServerDeployments(SlaveDeployer.java:1210)
    >>>>< at weblogic.management.deploy.slave.SlaveDeployer.res ume(SlaveDeployer.java:362)
    >>>>< at weblogic.management.deploy.DeploymentManagerServer LifeCycleImpl.resume(DeploymentManagerServerLifeCy cleImpl.java:229)
    >>>>< at weblogic.t3.srvr.SubsystemManager.resume(Subsystem Manager.java:131)
    >>>>< at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
    >>>>< at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
    >>>>< at weblogic.Server.main(Server.java:32)
    >>>>
    >>>

    >>

    >