Weblogic.ejb20.WLDeploymentException

Hi,
I have created a connection pool with the name "MyDataConnectionPool" and selected "myserver" as target in the target tab. Then I have created the Data source with the name "MyDataSource" and selected "myserver" as target.
I mentioned datasource name is "MyDataSource" in the file "weblogic-cmp-rdbms-jar.xml".
I am getting the exception in the server console is
weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: MyDataSource could not be located. Please ensure that the DataSource has been de
ployed successfully and that the JNDI name in your EJB Deployment descriptor is
correct.
at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersisten
ceManager.java:138)
at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.ja
va:211)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java
:181)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:162)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrive
nBeanInfoImpl.java:945)
at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1296)
at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:349)
at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplication
Container.java:1592)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
ner.java:1029)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
ner.java:966)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForA
llApplications(SlaveDeployer.java:619)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:376)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
61)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
at weblogic.Server.main(Server.java:32)
at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1359)
at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:349)
at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplication
Container.java:1592)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
ner.java:1029)
Please help me..
Thanks in advance
regards
Sreehari Bodagala

<data-source-name></data-source-name> tag in
weblogic-cmp-rdbms-jar.xml
specifies the jndi name of the DataSource,
not the DataSource name.
thanks,
Deepak

Similar Messages

  • Java.lang.NoSuchMethodError: weblogic.ejb20.internal.EntityEJBObject_Activa

    We have Weblogic 8.1 SP2. The application has several entity beans. I just upgraded it from SP2 to SP3 and when I try to use these ejb's I am getting the following exception:
    Root cause of ServletException.
    java.lang.NoSuchMethodError: weblogic.ejb20.internal.EntityEJBObject_Activatable.preInvoke(Lweblogic/ejb20/
    internal/MethodDescriptor;Lweblogic/security/service/ContextHandler;)Lweblogic/ejb20/interfaces/InvocationWrapper;
    Note that these ejb's worked fine in SP2.
    Now, just to test, I redeployed some of these ejb's and then these redeployed ejb's worked fine.
    My question is, is it required to redeploy all ejb's to upgrade from SP2 to SP3?
    Thanks.

    redeploying the beans had the upgraded server recompile them which (probably), updated any internal references to methods. I don't quite understand one can run the beans that were compiled on SP2, on an upgraded SP3 server without having deployed (and therefore recompiled) them on the upgraded SP3 server.

  • Error runing Commerce/Campaign Management on extends weblogic.ejb20.internal.StatelessEJBObject

    Hi,
    I just installed WLS6.0 it is running smoothly thanx to Jignesh help , also I
    put in the ejb20.ajr and after that I installed the Campaign Management 1.1 but
    I´m geting this error when I start theh server well this is the first of thousand
    errors:
    /opt/posadas/bea/wlcs3.5/tmp_ejboneworld.cemtec.com7501/events/com/bea/commerce/
    platform/events/internal/EventServiceBeanEOImpl.java:12: Superclass java.lang.Ob
    ject of class com.bea.commerce.platform.events.internal.EventServiceBeanEOImpl
    n
    ot found.
    extends weblogic.ejb20.internal.StatelessEJBObject
    Any one can help me?Thanx in Advanced

    Gerado,
    I guessing you mispelled ejb20.jar - - you need to include this at the front of
    your java.class.path in your WLS 6.0 startup script
    Chuck

  • Java.io.NotSerializableException: weblogic.ejb20.internal.EntityEJBContextImpl

    Hi,
    We are currently in the process of moving from Weblogic 6.1 SP5 and
    Toplink 3.6.3 to Weblogic 8.1 SP2 and Toplink 9.0.4 and during some test
    I have seen a "scaring" stack trace. It seems that, for some reason, a
    thing that "uses to work" failed with a very strange error. I tried to
    reproduce it but without any success. Besides asking if anybody knows
    what could have caused this error I would like to know what the "not
    serializable" object is. Is it the EntityEJBContext?
    <12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
    weblogic.kernel.Default]:Exception:
    javax.transaction.TransactionRolledbackException at getXML
    javax.transaction.TransactionRolledbackException: EJB Exception: :
    java.io.NotSerializableException:
    weblogic.ejb20.internal.EntityEJBContextImpl
    at
    java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
    at
    java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    at
    java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    at
    java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    at
    java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    at
    java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
    at
    weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
    at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
    at
    weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
    at
    weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
    at
    app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
    Source)
    In case it could share some light in the case I will explain a bit what
    does the process intended to do:
    The general idea is that, given some data (managed with Toplink's 9.0.4
    CMP) we take a XML "snapshot" of them (via a custom OBJ2XML class that
    has been working for ages without any problem) and "publish" it via JMS
    in order to perform asyncronous actions with it. I'm sure this is a,
    more than usual, scenario for a lot of folks.
    As it seems looking at the stack at some point during some internal
    object serialization it fails and rollbacks all the process. The object
    being serialized by our side only contains four attributes: a
    java.math.BigDecimal for it's primary key, a java.util.Date for
    timestamp locking and two simple java.lang.String's
    Although I'm pretty sure the problem should not be with the entity bean
    itself but with an internal Weblogic op (is it trying to serialize the
    EntityBeanContext as stated after the java.io.NotSerializableException
    message?
    Any help with this would be greatly appreciated as I have no clue how
    this happened and I'm also unable to reproduce it (I'm also sure if I
    managed to trigger it testing the application alone it will rise many
    more times that could be admited if we move to production).
    I would like to point also that currently until we have some more time
    to fix it we are using "remote" entity bean, I mean even if we are alway
    s calling them within the container they are not deployed with "local"
    interfaces yet (although AFAIK Weblogic should avoid RMI calls on them
    being co-located with the session beans).
    Regards.
    Ignacio.
    P.S. here is the full stack dump
    <12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
    weblogic.kernel.Default]:Exception:
    javax.transaction.TransactionRolledbackException at getXML
    javax.transaction.TransactionRolledbackException: EJB Exception: :
    java.io.NotSerializableException:
    weblogic.ejb20.internal.EntityEJBContextImpl
    at
    java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
    at
    java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    at
    java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    at
    java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    at
    java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    at
    java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
    at
    weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
    at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
    at
    weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
    at
    weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
    at
    app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
    Source)
    at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
    at
    app.data.module.ModuleBean_1v2h9c_EOImpl.EJB2DOM(ModuleBean_1v2h9c_EOImpl.java:3954)
    at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
    at app.data.general.GeneralBean.getXML(GeneralBean.java:1024)
    at app.data.general.GeneralBean.getXML(GeneralBean.java:1002)
    at
    app.data.module.ModuleBean_nw294k_EOImpl.getXML(ModuleBean_nw294k_EOImpl.java:3138)
    at app.biz.common.Publisher.performPublication(Publisher.java:1644)
    at app.biz.common.Publisher.launchPublisher(Publisher.java:1580)
    at app.biz.module.ModuleDAO.update(ModuleDAO.java)
    at
    app.biz.module.ModuleDAO_jcgreo_EOImpl.update(ModuleDAO_jcgreo_EOImpl.java:100)
    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 app.core.util.Proxy.execute(Proxy.java:583)
    at app.core.servlet.BaseServlet.execute(BaseServlet.java:440)
    at
    app.user.servlet.common.BaseServlet.accessSessionBean(BaseServlet.java:279)
    at
    app.user.servlet.common.BaseServlet.buildResponse(BaseServlet.java:132)
    at app.core.servlet.BaseServlet.doGet(BaseServlet.java:116)
    at app.core.servlet.BaseServlet.doPost(BaseServlet.java:154)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6310)
    at
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at
    weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >

    Ignacio,
    6.1 used pass-by-reference by default, so parameters to beans were
    passed by reference.
    It's very likely that you are getting this error because in 8.1 this default
    was turned off. This causes serialization of parameters by default and
    that's why your code that worked started failing - you just did not know
    that you were passing non-serializable objects around.
    To fix this you could either turn on the pass-by-reference explicitly and/or
    find out where your code is passing non-serializable objects. This is a useful
    exercise anyways.
    Hope this helps.
    Regards,
    Slava Imeshev
    "Ignacio G. Dupont" <[email protected]> wrote in message news:41b8c93f@mail...
    Hi,
    We are currently in the process of moving from Weblogic 6.1 SP5 and
    Toplink 3.6.3 to Weblogic 8.1 SP2 and Toplink 9.0.4 and during some test
    I have seen a "scaring" stack trace. It seems that, for some reason, a
    thing that "uses to work" failed with a very strange error. I tried to
    reproduce it but without any success. Besides asking if anybody knows
    what could have caused this error I would like to know what the "not
    serializable" object is. Is it the EntityEJBContext?
    <12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
    weblogic.kernel.Default]:Exception:
    javax.transaction.TransactionRolledbackException at getXML
    javax.transaction.TransactionRolledbackException: EJB Exception: :
    java.io.NotSerializableException:
    weblogic.ejb20.internal.EntityEJBContextImpl
    at
    java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
    at
    java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    at
    java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    at
    java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    at
    java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    at
    java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
    at
    weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
    at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
    at
    weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
    at
    weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
    at
    app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
    Source)
    In case it could share some light in the case I will explain a bit what
    does the process intended to do:
    The general idea is that, given some data (managed with Toplink's 9.0.4
    CMP) we take a XML "snapshot" of them (via a custom OBJ2XML class that
    has been working for ages without any problem) and "publish" it via JMS
    in order to perform asyncronous actions with it. I'm sure this is a,
    more than usual, scenario for a lot of folks.
    As it seems looking at the stack at some point during some internal
    object serialization it fails and rollbacks all the process. The object
    being serialized by our side only contains four attributes: a
    java.math.BigDecimal for it's primary key, a java.util.Date for
    timestamp locking and two simple java.lang.String's
    Although I'm pretty sure the problem should not be with the entity bean
    itself but with an internal Weblogic op (is it trying to serialize the
    EntityBeanContext as stated after the java.io.NotSerializableException
    message?
    Any help with this would be greatly appreciated as I have no clue how
    this happened and I'm also unable to reproduce it (I'm also sure if I
    managed to trigger it testing the application alone it will rise many
    more times that could be admited if we move to production).
    I would like to point also that currently until we have some more time
    to fix it we are using "remote" entity bean, I mean even if we are alway
    s calling them within the container they are not deployed with "local"
    interfaces yet (although AFAIK Weblogic should avoid RMI calls on them
    being co-located with the session beans).
    Regards.
    Ignacio.
    P.S. here is the full stack dump
    <12-09-2004 4:40' GMT> <Error> <app> <000000> <[thread 5
    weblogic.kernel.Default]:Exception:
    javax.transaction.TransactionRolledbackException at getXML
    javax.transaction.TransactionRolledbackException: EJB Exception: :
    java.io.NotSerializableException:
    weblogic.ejb20.internal.EntityEJBContextImpl
    at
    java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
    at
    java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    at
    java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    at
    java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    at
    java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    at
    java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
    at
    weblogic.rmi.internal.CBVOutputStream.writeObject(CBVOutputStream.java:78)
    at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:218)
    at
    weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:158)
    at
    weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
    at
    app.data.production.ProductionBean_3toa0w_EOImpl_811_WLStub.EJB2DOM(Unknown
    Source)
    at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
    at
    app.data.module.ModuleBean_1v2h9c_EOImpl.EJB2DOM(ModuleBean_1v2h9c_EOImpl.java:3954)
    at app.data.general.GeneralBean.EJB2DOM(GeneralBean.java:1180)
    at app.data.general.GeneralBean.getXML(GeneralBean.java:1024)
    at app.data.general.GeneralBean.getXML(GeneralBean.java:1002)
    at
    app.data.module.ModuleBean_nw294k_EOImpl.getXML(ModuleBean_nw294k_EOImpl.java:3138)
    at app.biz.common.Publisher.performPublication(Publisher.java:1644)
    at app.biz.common.Publisher.launchPublisher(Publisher.java:1580)
    at app.biz.module.ModuleDAO.update(ModuleDAO.java)
    at
    app.biz.module.ModuleDAO_jcgreo_EOImpl.update(ModuleDAO_jcgreo_EOImpl.java:100)
    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 app.core.util.Proxy.execute(Proxy.java:583)
    at app.core.servlet.BaseServlet.execute(BaseServlet.java:440)
    at
    app.user.servlet.common.BaseServlet.accessSessionBean(BaseServlet.java:279)
    at
    app.user.servlet.common.BaseServlet.buildResponse(BaseServlet.java:132)
    at app.core.servlet.BaseServlet.doGet(BaseServlet.java:116)
    at app.core.servlet.BaseServlet.doPost(BaseServlet.java:154)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6310)
    at
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at
    weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >

  • Getting this Error Reason=weblogic.ejb20.InternalException: Error writing f

    I am using a weblogic 8.1 sp4 and is getting the following error
    =====
    java.sql.SQLException: Transaction BEA1-00A0C7390CDF3A289F82 not active anymore. tx status = Marked rollback. [Reason=weblogic.ejb20.InternalException: Error writing from flushModified]
    at weblogic.jdbc.jts.Driver.getTransaction(Driver.java:430)
    at weblogic.jdbc.jts.Driver.connect(Driver.java:127)
    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
    =====
    Is this a bug in Weblogic ?
    This happens when the the the container managed entity bean has the following element.
    <cache-strategy>read-write</cache-strategy>
    This does not happend if the following value is set
    <cache-strategy>read-only</cache-strategy>
    Any clues on a resolution to this problem ?
    Thanks in advance.

    I have similar problem with my application. I'm using Weblogic 8.1 sp4 and MS SQL 2000 sp 3 and Hibernate 2.8 to connect to DB. Table causing exception is replicated bidirectional with transactional replication. I get trace of SQL transactions made during user logging process and noticed update querry which is rolled back. There are only select querries before. I wonder if synchronizing triggers used by replication could be the problem. Can it somehow reset the session?
    Stack Trace lools like this below:
    30328 [Thread-5] ERROR pl.computerland.snu.repo.remote.external.RemoteRepoFactoryWrapper - operation():
    pl.computerland.snu.repo.remote.RemoteRepoException: java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: EJB Exception: ; nested exception is:
         javax.ejb.TransactionRolledbackLocalException: Exception during remove.; nested exception is: javax.ejb.EJBException: nested exception is: java.lang.Exception: SQLException on insert: java.sql.SQLException: Transaction BEA1-00042F6B457BAFFD2C3E not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]
    Detail:
    <detail>
    EJB Exception: ; nested exception is:
         javax.ejb.TransactionRolledbackLocalException: Exception during remove.; nested exception is: javax.ejb.EJBException: nested exception is: java.lang.Exception: SQLException on insert: java.sql.SQLException: Transaction BEA1-00042F6B457BAFFD2C3E not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException] </detail>; nested exception is:
         javax.xml.rpc.soap.SOAPFaultException: EJB Exception: ; nested exception is:
         javax.ejb.TransactionRolledbackLocalException: Exception during remove.; nested exception is: javax.ejb.EJBException: nested exception is: java.lang.Exception: SQLException on insert: java.sql.SQLException: Transaction BEA1-00042F6B457BAFFD2C3E not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]
         at pl.computerland.snu.repo.remote.external.RemoteRepoFactory.login(RemoteRepoFactory.java:116)
         at pl.computerland.snu.repo.remote.external.RemoteRepoFactoryWrapper$ExternConnection.operation(RemoteRepoFactoryWrapper.java:301)
         at pl.computerland.snu.rfi.services.TaskService$1.run(TaskService.java:51)
         at java.lang.Thread.run(Unknown Source)
    Caused by: java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: EJB Exception: ; nested exception is:
         javax.ejb.TransactionRolledbackLocalException: Exception during remove.; nested exception is: javax.ejb.EJBException: nested exception is: java.lang.Exception: SQLException on insert: java.sql.SQLException: Transaction BEA1-00042F6B457BAFFD2C3E not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]
    Detail:
    <detail>
    EJB Exception: ; nested exception is:
         javax.ejb.TransactionRolledbackLocalException: Exception during remove.; nested exception is: javax.ejb.EJBException: nested exception is: java.lang.Exception: SQLException on insert: java.sql.SQLException: Transaction BEA1-00042F6B457BAFFD2C3E not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException] </detail>; nested exception is:
         javax.xml.rpc.soap.SOAPFaultException: EJB Exception: ; nested exception is:
         javax.ejb.TransactionRolledbackLocalException: Exception during remove.; nested exception is: javax.ejb.EJBException: nested exception is: java.lang.Exception: SQLException on insert: java.sql.SQLException: Transaction BEA1-00042F6B457BAFFD2C3E not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]
         at pl.computerland.snu.rfi.client.transfer.RepositoryExtSoap_Stub.login(RepositoryExtSoap_Stub.java:241)
         at pl.computerland.snu.rfi.client.transfer.RepositoryExtSoap_Stub.login(RepositoryExtSoap_Stub.java:258)
         at pl.computerland.snu.repo.remote.external.RemoteRepoFactory.login(RemoteRepoFactory.java:114)
         ... 3 more
    Caused by: javax.xml.rpc.soap.SOAPFaultException: EJB Exception: ; nested exception is:
         javax.ejb.TransactionRolledbackLocalException: Exception during remove.; nested exception is: javax.ejb.EJBException: nested exception is: java.lang.Exception: SQLException on insert: java.sql.SQLException: Transaction BEA1-00042F6B457BAFFD2C3E not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]
         at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
         at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
         at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
         at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
         at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:303)
         at pl.computerland.snu.rfi.client.transfer.RepositoryExtSoap_Stub.login(RepositoryExtSoap_Stub.java:236)
         ... 5 more

  • Question about weblogic.ejb20.utils.DDConverter

    Hello.
    I have convert DD using weblogic.ejb20.utils.DDConverter.
    But error happens.
    D:\>java weblogic.ejb20.utils.DDConverter -EJBVer 2.0 -d . forex_tr.jar
    new.jar
    DDConverter starting at 2002-02-21 ¿ÀÈÄ 4:35:26...
    Source file list:
    forex_tr.jar
    new.jar
    Output directory: .
    Converting forex_tr.jar ...
    DDConverter failed due to an unexpected Exception. The stack trace is:
    java.lang.ClassCastException:
    weblogic.management.descriptors.cmp20.WeblogicRDB
    MSBeanMBeanImpl
    at
    weblogic.ejb20.utils.ddconverter.DDConverterBase.convertBeansTo20(DDC
    onverterBase.java:284)
    at
    weblogic.ejb20.utils.ddconverter.DDConverterBase.convertTo20(DDConver
    terBase.java:235)
    at
    weblogic.ejb20.utils.ddconverter.DDConverter_1120.convert(DDConverter
    _1120.java:88)
    at weblogic.ejb20.utils.DDConverter.main(DDConverter.java:155)
    DDConverter was unable to convert all the input beans due to conversion
    errors.
    See "ddconverter.log" for details.
    Bye.
    Hyun Min.

    It's my mistake.
    I not used -c option.
    java weblogic.ejb20.utils.DDConverter -EJBVer 2.0 -d . -c new.jar
    forex_tr.jar
    "Hyun Min" <[email protected]> wrote in message
    news:[email protected]..
    Hello.
    I have convert DD using weblogic.ejb20.utils.DDConverter.
    But error happens.
    D:\>java weblogic.ejb20.utils.DDConverter -EJBVer 2.0 -d . forex_tr.jar
    new.jar
    DDConverter starting at 2002-02-21 ¿ÀÈÄ 4:35:26...
    Source file list:
    forex_tr.jar
    new.jar
    Output directory: .
    Converting forex_tr.jar ...
    DDConverter failed due to an unexpected Exception. The stack trace is:
    java.lang.ClassCastException:
    weblogic.management.descriptors.cmp20.WeblogicRDB
    MSBeanMBeanImpl
    at
    weblogic.ejb20.utils.ddconverter.DDConverterBase.convertBeansTo20(DDC
    onverterBase.java:284)
    at
    weblogic.ejb20.utils.ddconverter.DDConverterBase.convertTo20(DDConver
    terBase.java:235)
    at
    weblogic.ejb20.utils.ddconverter.DDConverter_1120.convert(DDConverter
    _1120.java:88)
    at weblogic.ejb20.utils.DDConverter.main(DDConverter.java:155)
    DDConverter was unable to convert all the input beans due to conversion
    errors.
    See "ddconverter.log" for details.
    Bye.
    Hyun Min.

  • Undocumented weblogic.ejb20.internal.MethodPermissionException?

    Environment: Weblogic 6.0 sp2 w/ ejb20.jar.
    We are experimenting with security and noticed that if a client to an ejb
    (session bean in our case) attempts to make a method call that they do not
    have permission for (due to the descriptor .xml file roles), the exception
    that is thrown on the client is this very proprietary sounding and
    undocumented exception:
    weblogic.ejb20.internal.MethodPermissionException
    Using reflection we can see that this exception class has this lineage:
    weblogic.ejb20.internal.MethodPermissionException
    java.rmi.RemoteException
    java.io.IOException
    java.lang.Exception
    java.lang.Throwable
    java.lang.Object
    Can you provide any more info on this? Ideally I'd like to be able to
    distinguish between the very generic RemoteException, but not code such
    undocumented exception names into my files (i.e. it sounds like the name of
    this "internal" exception could easily change with a service pack or
    something and then we'd be hosed).
    Thanks,
    - John Freeborg

    Lourdes,
    We are encountering the exact same issue and thread dump. Did you ever determine a resolution?
    An example thread dump from our server.
    "ExecuteThread: '38' for queue: 'rplarge1'" daemon prio=10 tid=009e7460 nid=111 lwp_id=1102694 in Object.wait() [0x0e611000..0x0e6104f0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at weblogic.jms.store.StoreRequest.waitForIOComplete(StoreRequest.java:465)
         - locked <5593dbe0> (a weblogic.jms.store.StoreRequest)
         at weblogic.jms.backend.BEXATranEntrySend.finishPrepare(BEXATranEntrySend.java:61)
         at weblogic.jms.backend.BEXAResource.prepare(BEXAResource.java:943)
         at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:1195)
         at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:411)
         at weblogic.transaction.internal.ServerSCInfo$1.execute(ServerSCInfo.java:253)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
         at weblogic.kernel.Kernel.executeIfIdle(Kernel.java:378)
         at weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:244)
         at weblogic.transaction.internal.ServerTransactionImpl.localPrepare(ServerTransactionImpl.java:2301)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2015)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:275)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:244)
         at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:299)
         at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:140)
    We are running wls8.1sp3 on HPUX.
    Thanks

  • Threads Stuck weblogic.ejb20.internal.MDListener@d36ef2

    Hello, we have an application over WebLogic Server 8.1 SP4 and we see this message in logs:
    <Dec 7, 2005 11:15:09 AM CET> <Error> <WebLogicServer> <BEA-000337> <ExecuteThread: '27' for queue: 'weblogic.kernel.Default'
    has been busy for "797" seconds working on the request "weblogic.ejb20.internal.MDListener@d36ef2", which is more than the c
    onfigured time (StuckThreadMaxTime) of "600" seconds.>
    When i have a thread dump the most of threads are :
    "ExecuteThread: '36' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x0074b380 nid=0x3f in Object.wait() [c267f000..
    c267fc28]
    at java.lang.Object.wait(Native Method)
    - waiting on <0xccb4d908> (a weblogic.jms.store.StoreRequest)
    at java.lang.Object.wait(Object.java:429)
    at weblogic.jms.store.StoreRequest.waitForIOComplete(StoreRequest.java:465)
    - locked <0xccb4d908> (a weblogic.jms.store.StoreRequest)
    at weblogic.jms.backend.BEXATranEntrySubscribe.finishPrepare(BEXATranEntrySubscribe.java:95)
    at weblogic.jms.backend.BEXAResource.commit(BEXAResource.java:1087)
    at weblogic.transaction.internal.XAServerResourceInfo.commit(XAServerResourceInfo.java:1291)
    at weblogic.transaction.internal.XAServerResourceInfo.commit(XAServerResourceInfo.java:519)
    at weblogic.transaction.internal.ServerSCInfo.startCommit(ServerSCInfo.java:421)
    at weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransactionImpl.java:1883)
    at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:2515)
    at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:2446)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:280)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:246)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:400)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    Any idea?
    Thanks

    Lourdes,
    We are encountering the exact same issue and thread dump. Did you ever determine a resolution?
    An example thread dump from our server.
    "ExecuteThread: '38' for queue: 'rplarge1'" daemon prio=10 tid=009e7460 nid=111 lwp_id=1102694 in Object.wait() [0x0e611000..0x0e6104f0]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:429)
         at weblogic.jms.store.StoreRequest.waitForIOComplete(StoreRequest.java:465)
         - locked <5593dbe0> (a weblogic.jms.store.StoreRequest)
         at weblogic.jms.backend.BEXATranEntrySend.finishPrepare(BEXATranEntrySend.java:61)
         at weblogic.jms.backend.BEXAResource.prepare(BEXAResource.java:943)
         at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:1195)
         at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:411)
         at weblogic.transaction.internal.ServerSCInfo$1.execute(ServerSCInfo.java:253)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
         at weblogic.kernel.Kernel.executeIfIdle(Kernel.java:378)
         at weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:244)
         at weblogic.transaction.internal.ServerTransactionImpl.localPrepare(ServerTransactionImpl.java:2301)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2015)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:275)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:244)
         at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:299)
         at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:140)
    We are running wls8.1sp3 on HPUX.
    Thanks

  • Weblogic.ejb20.deployer.DeploymentDescriptorException:

    Hi,
    weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml:
    I find this exception when the deploying the weblogic8.1.
    my jar file is correct format that is helloEjb.jar
    this is mypackage name:**com.test.sample** under this contain all class that is
    Hello.class
    HelloHome.class
    HelloBean.class
    My ejb-jar.xml is
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar id="ejb-jar_ID">
         <display-name>HelloEjb</display-name>
         <enterprise-beans>
    <session>
    <ejb-name>HelloEjb</ejb-name>
    <home>com.test.sample.HelloHome</home>
    <remote>com.test.sample.Hello</remote>
    <ejb-class>com.test.sample.HelloBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    </ejb-jar>
    weblogic-ejb-jar.xml is
    <?xml version="1.0"?>
    <!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN"
    "http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd">
    <!-- Sample MessageDriven bean Weblogic deployment descriptor -->
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>HelloEjb</ejb-name>
    <jndi-name>HelloEjb1</jndi-name>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    so can u please solve this issue immediatly
    Thanks,
    rk

    Hi
    open ur jar file in zip, at the end of column ie 'path' it shows the beans path. if it is empty then you have created wrong jar file
    eg: if ur package is like this
    com.mycompany.trade.ejb
    then go to bin directory and make the jar file like
    jar cvf myejb.jar com\mycompany\trade\ejb\*.class
    to add META-INF(ejb-jar.xml and weblogic-ejb-jar.xml)
    jar uvf myejbjar.jar META-INF/*.xml
    and redeploy it
    Regards
    Kasim

  • Weblogic.ejb20.locks.LockTimedOutException ???

    Hi Iam getting a LockTimedOutException while calling a bean method..what could
    be the reason and this is permenent..occuring all the time..
    Below I have given the stack trace..
    what could be the problem??
    Thanks
    Perianayagam.T
    ####<Jun 10, 2003 8:59:28 AM EDT> <Info> <EJB> <dssappsrv01> <myServer> <ExecuteThread:
    '3' for queue: 'default'> <> <> <010051> <EJB Exception during invocation from
    home: com.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_HomeImpl@9c1ee threw exception:
    weblogic.ejb20.locks.LockTimedOutException: The lock request from EJB:EnterpriseUser
    with primary key:<user dn="hnsuid=hsscsr,ou=people,ou=hub0001,hnscompanyid=dway,ou=business,o=hns.com"/>
    timed-out after waiting 60,000 ms. The transaction or thread requesting the lock
    was:Name=[EJB com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hns.iag.framework.UserCredential)],Xid=11814:95f36eb4(3191949),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=60,seconds left=0,activeThread=Thread[ExecuteThread: '3' for queue:
    'default',5,Thread Group for Queue: 'default'],SCInfo[acapulco+myServer]=(state=active),properties=({weblogic.transaction.name=[EJB
    com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hns.iag.framework.UserCredential)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myServer+172.18.2.139:7003+acapulco+,
    Resources={})]).>
    weblogic.ejb20.locks.LockTimedOutException: The lock request from EJB:EnterpriseUser
    with primary key:<user dn="hnsuid=hsscsr,ou=people,ou=hub0001,hnscompanyid=dway,ou=business,o=hns.com"/>
    timed-out after waiting 60,000 ms. The transaction or thread requesting the lock
    was:Name=[EJB com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hns.iag.framework.UserCredential)],Xid=11814:95f36eb4(3191949),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=60,seconds left=0,activeThread=Thread[ExecuteThread: '3' for queue:
    'default',5,Thread Group for Queue: 'default'],SCInfo[acapulco+myServer]=(state=active),properties=({weblogic.transaction.name=[EJB
    com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hns.iag.framework.UserCredential)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myServer+172.18.2.139:7003+acapulco+,
    Resources={})]).
         at weblogic.ejb20.locks.ExclusiveLockManager$LockBucket.lock(ExclusiveLockManager.java:528)
         at weblogic.ejb20.locks.ExclusiveLockManager.lock(ExclusiveLockManager.java:258)
         at weblogic.ejb20.manager.ExclusiveEntityManager.acquireLock(ExclusiveEntityManager.java:164)
         at weblogic.ejb20.manager.ExclusiveEntityManager.getReadyBean(ExclusiveEntityManager.java:219)
         at weblogic.ejb20.manager.ExclusiveEntityManager.preInvoke(ExclusiveEntityManager.java:198)
         at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
         at weblogic.ejb20.internal.EntityEJBObject.preInvoke(EntityEJBObject.java:89)
         at com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean_svris_EOImpl.getRoles(EnterpriseUserBean_svris_EOImpl.java:333)
         at com.hns.iag.acapulco.ejb.elm.ELMBean.getEnterpriseUserRoles(ELMBean.java:1392)
         at com.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_EOImpl.getEnterpriseUserRoles(ELMBean_1h1i_EOImpl.java:2587)
         at com.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
         at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
         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)

    Hi Perianayagam,
    This error is fixed in weblogic 6.1SP4 and 7.0 SP3.
    Regards,
    Slava Imeshev
    "Perianayagam.T" <[email protected]> wrote in message
    news:[email protected]...
    >
    Hi Iam getting a LockTimedOutException while calling a bean method..whatcould
    be the reason and this is permenent..occuring all the time..
    Below I have given the stack trace..
    what could be the problem??
    Thanks
    Perianayagam.T
    ####<Jun 10, 2003 8:59:28 AM EDT> <Info> <EJB> <dssappsrv01> <myServer><ExecuteThread:
    '3' for queue: 'default'> <> <> <010051> <EJB Exception during invocationfrom
    home: com.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_HomeImpl@9c1ee threwexception:
    weblogic.ejb20.locks.LockTimedOutException: The lock request fromEJB:EnterpriseUser
    with primary key:<userdn="hnsuid=hsscsr,ou=people,ou=hub0001,hnscompanyid=dway,ou=business,o=hns.c
    om"/>
    timed-out after waiting 60,000 ms. The transaction or thread requestingthe lock
    was:Name=[EJBcom.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hn
    s.iag.framework.UserCredential)],Xid=11814:95f36eb4(3191949),Status=Active,n
    umRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=60,seconds left=0,activeThread=Thread[ExecuteThread: '3' for
    queue:> 'default',5,Thread Group for Queue:'default',SCInfo[acapulco+myServer]=(state=active),properties=({weblogic.transaction.name=[EJB
    >
    com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hn
    s.iag.framework.UserCredential)]}),OwnerTransactionManager=ServerTM[ServerCo
    ordinatorDescriptor=(CoordinatorURL=myServer+172.18.2.139:7003+acapulco+,
    Resources={})]).>
    weblogic.ejb20.locks.LockTimedOutException: The lock request fromEJB:EnterpriseUser
    with primary key:<userdn="hnsuid=hsscsr,ou=people,ou=hub0001,hnscompanyid=dway,ou=business,o=hns.c
    om"/>
    timed-out after waiting 60,000 ms. The transaction or thread requestingthe lock
    was:Name=[EJBcom.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hn
    s.iag.framework.UserCredential)],Xid=11814:95f36eb4(3191949),Status=Active,n
    umRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=60,seconds left=0,activeThread=Thread[ExecuteThread: '3' for
    queue:> 'default',5,Thread Group for Queue:'default',SCInfo[acapulco+myServer]=(state=active),properties=({weblogic.transaction.name=[EJB
    >
    com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hn
    s.iag.framework.UserCredential)]}),OwnerTransactionManager=ServerTM[ServerCo
    ordinatorDescriptor=(CoordinatorURL=myServer+172.18.2.139:7003+acapulco+,
    Resources={})]).
    atweblogic.ejb20.locks.ExclusiveLockManager$LockBucket.lock(ExclusiveLockManag
    er.java:528)
    atweblogic.ejb20.locks.ExclusiveLockManager.lock(ExclusiveLockManager.java:258
    atweblogic.ejb20.manager.ExclusiveEntityManager.acquireLock(ExclusiveEntityMan
    ager.java:164)
    atweblogic.ejb20.manager.ExclusiveEntityManager.getReadyBean(ExclusiveEntityMa
    nager.java:219)
    atweblogic.ejb20.manager.ExclusiveEntityManager.preInvoke(ExclusiveEntityManag
    er.java:198)
    at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
    atweblogic.ejb20.internal.EntityEJBObject.preInvoke(EntityEJBObject.java:89)
    atcom.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean_svris_EOImpl.ge
    tRoles(EnterpriseUserBean_svris_EOImpl.java:333)
    atcom.hns.iag.acapulco.ejb.elm.ELMBean.getEnterpriseUserRoles(ELMBean.java:139
    2)
    atcom.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_EOImpl.getEnterpriseUserRoles(ELMB
    ean_1h1i_EOImpl.java:2587)
    at com.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_EOImpl_WLSkel.invoke(UnknownSource)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
    atweblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
    :93)
    atweblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
    atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

  • Weblogic.ejb20.locks.LockTimedOutException and pb with weblogic-ejb-jar.xml

    Hello All,
    I get a strange problem when I try to log in to the J2EE application based on EJBs:
    weblogic.ejb20.locks.LockTimedOutException
    I see that I can add an option to the weblogic-ejb-jar.xml file, and I hope that can help for my previous problem:
    <weblogic-enterprise-bean><stateful-session-descriptor>
    <allow-concurrent-calls>true</allow-concurrent-calls>
    </stateful-session-descriptor></weblogic-enterprise-bean>
    But I can not edit the weblogic-ejb-jar.xml file under JBuilder ! the file is probably read-only, but I do not know how to change the property. I can not find this file directly under JBuilder directories.
    So I have tried to open the module.jar that contained this file. I have checked: the file is not read-only. I have modified directly manually the weblogic-ejb-jar.xml file, but now I get this error in Jbuilder when I open the weblogic-ejb-jar.xml file:
    URL: Transformation requires a XSL StyleSheetThe Node does not have a style sheet associated with itEither add a style sheet using the Add stylesheets button on the toolbar or add a valid XSL Processing instruction to the document directly
    In conclusion, what should I do to be able to modify the weblogic-ejb-jar.xml file properly ??

    Ok in a way I have solved my problem (even if I am not completely satisfied by the way on how to proceed...). So thanks to message "JBuilder7.0 and Weblogic6.1" on EJB sun forum :
    http://forum.java.sun.com/thread.jsp?thread=285735&forum=13&message=1255488
    I have tried the following actions (mentionned in the other forum messages):
    - To preserve changes to weblogic*.xml, the safest way is to change the ejb-borland.xml.
    (I am not sure that I have applied this advice correctly, because I suppose that syntax is not similar in weblogic file or borland file).
    And you can MANUALLY update the weblogic file in your JAR archive.
    1. Open the EJB JAR file in Winzip and extract the weblogic-ejb-jar.xml file, so that a copy exists in your
    project directory.
    2. Open this file (in Notepad), add the WebLogic specific information, and then save the file.
    3. Now, when you are finished with the build cycle and are ready to deploy, you may open the EJB jar file
    and swap in the weblogic-ejb-jar.xml file."
    Good Luck.

  • Petstore 1.3 on Weblogic 7.0 with Oracle 8.1.7

    Hi, I am trying to get petstore 1.3 working on Weblogic7.0
    with Oracle 8.1.7 database on HPUX. I made some modifications
    to the source files and regenerated the EAR files. When I copied
    the four EAR files to the applications sub-directory, two .ear
    files (petstoreadmin.ear & petstore.ear) deployed successfully
    but not the supplier.ear and opc.ear. I got the following messages from deploying
    supplier.ear:
    Any help would be greatly appreciated,
    Min-Shih
    =====================================================
    ####<Nov 7, 2002 5:09:30 PM PST> <Warning> <EJB> <cutst058.cup.hp.com> <examplesServer>
    <ExecuteThread: '9' for
    queue: 'default'> <kernel identity> <> <010061> <The Message-Driven EJB: supplier_OPC_MDB_QUEUE
    is unable to connect to the
    JMS destination: jms/opcApplication/SUPPLIER_PO_MDB_QUEUE. The EJB container will
    automatically attempt to re-establish the connection with the JMS server. This
    warning may occur during WebLogic Cluster start-up if the JMS destination is located
    on another WebLogic Server instance. When the JMS server connection is re-established,
    the Message-Driven EJB will again receive JMS messages.
    The Error was:
    The JMS destination with the JNDI name: jms/opcApplication/SUPPLIER_PO_MDB_QUEUE
    could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml
    is correct, and the JMS destination has been deployed.>
    ####<Nov 7, 2002 5:09:30 PM PST> <Error> <EJB> <cutst058.cup.hp.com> <examplesServer>
    <ExecuteThread: '9' for queue: 'default'> <kernel identity> <> <010072> <Error
    starting EJB Module : supplierEjb.jar
    Exception is :
    Unable to deploy EJB: supplierEjb.jar from supplierEjb.jar:
    weblogic.ejb20.WLDeploymentException: nulljava.lang.reflect.InvocationTargetException:
    javax.ejb.EJBException: Supp
    lier.MsgBean.ejbCreate: naming exceptionjavax.naming.LinkException: [Root exception
    is javax.naming.NameNotFoundEx
    ception: Unable to resolve 'jms.TopicConnectionFactory' Resolved: 'jms' Unresolved:'TopicConnectionFactory'
    ; remai
    ning name 'TopicConnectionFactory']; Link Remaining Name: 'jms/TopicConnectionFactory'

    Hi, I am trying to get petstore 1.3 working on Weblogic7.0
    with Oracle 8.1.7 database on HPUX. I made some modifications
    to the source files and regenerated the EAR files. When I copied
    the four EAR files to the applications sub-directory, two .ear
    files (petstoreadmin.ear & petstore.ear) deployed successfully
    but not the supplier.ear and opc.ear. I got the following messages from deploying
    supplier.ear:
    Any help would be greatly appreciated,
    Min-Shih
    =====================================================
    ####<Nov 7, 2002 5:09:30 PM PST> <Warning> <EJB> <cutst058.cup.hp.com> <examplesServer>
    <ExecuteThread: '9' for
    queue: 'default'> <kernel identity> <> <010061> <The Message-Driven EJB: supplier_OPC_MDB_QUEUE
    is unable to connect to the
    JMS destination: jms/opcApplication/SUPPLIER_PO_MDB_QUEUE. The EJB container will
    automatically attempt to re-establish the connection with the JMS server. This
    warning may occur during WebLogic Cluster start-up if the JMS destination is located
    on another WebLogic Server instance. When the JMS server connection is re-established,
    the Message-Driven EJB will again receive JMS messages.
    The Error was:
    The JMS destination with the JNDI name: jms/opcApplication/SUPPLIER_PO_MDB_QUEUE
    could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml
    is correct, and the JMS destination has been deployed.>
    ####<Nov 7, 2002 5:09:30 PM PST> <Error> <EJB> <cutst058.cup.hp.com> <examplesServer>
    <ExecuteThread: '9' for queue: 'default'> <kernel identity> <> <010072> <Error
    starting EJB Module : supplierEjb.jar
    Exception is :
    Unable to deploy EJB: supplierEjb.jar from supplierEjb.jar:
    weblogic.ejb20.WLDeploymentException: nulljava.lang.reflect.InvocationTargetException:
    javax.ejb.EJBException: Supp
    lier.MsgBean.ejbCreate: naming exceptionjavax.naming.LinkException: [Root exception
    is javax.naming.NameNotFoundEx
    ception: Unable to resolve 'jms.TopicConnectionFactory' Resolved: 'jms' Unresolved:'TopicConnectionFactory'
    ; remai
    ning name 'TopicConnectionFactory']; Link Remaining Name: 'jms/TopicConnectionFactory'

  • Unable to execute the cmp using the weblogic

    I was trying to execute cmp using weblogic server7.0.
    It a simple program,
    The remote interface-
    import javax.ejb.*;
    import java.rmi.RemoteException;
    public interface SportTeam extends EJBObject{
    public void setOwnerName(String ownerName) throws RemoteException;
    public String getOwnerName() throws RemoteException;
    public void setFranchiseName(String franchiseName) throws RemoteException;
    public String getFranchiseName() throws RemoteException;
    }The home interface
    import javax.ejb.*;
    import java.rmi.RemoteException;
    import java.util.Collection;
    public interface SportTeamHome extends EJBHome{
    SportTeam create(String sport,String nickName)throws RemoteException,CreateException;
    SportTeam create(String sport,String nickName,String ownerName,String franchisePlayer)throws RemoteException,CreateException;
    SportTeam findByPrimaryKey(SportTeamPK sportTeam) throws RemoteException,FinderException;
    Collection findByOwnerName(String ownerName) throws RemoteException,FinderException;
    }The bean
    import javax.ejb.*;
    import javax.naming.*;
    import java.rmi.RemoteException;
    import java.sql.*;
    import java.util.*;
    public abstract class SportTeamEJB implements EntityBean{
    public SportTeamPK ejbCreate(String sport,String nickName) throws CreateException {
    setSport(sport);
    setNickName(nickName);
    setOwnerName(null);
    setFranchiseName(null);
    return null;
    public void ejbPostCreate(String sport,String nickName){}
    public SportTeamPK ejbCreate(String sport,String nickName,String ownerName,String franchiseName) throws CreateException {
    setSport(sport);
    setNickName(nickName);
    setOwnerName(ownerName);
    setFranchiseName(franchiseName);
    return null;
    public void ejbPostCreate(String sport,String nickName,String ownerName,String franchiseName){}
    public void ejbLoad(){}
    public void ejbStore(){}
    public void ejbRemove(){}
    public void ejbActivate(){}
    public void ejbPassivate(){}
    public void setEntityContext(EntityContext ctx){}
    public void unsetEntityContext(){}
    abstract public String getSport();
    abstract public void setSport(String sport);
    abstract public String getNickName();
    abstract public void setNickName(String nickName);
    abstract public String getOwnerName();
    abstract public void setOwnerName(String ownerName);
    abstract public String getFranchiseName();
    abstract public void setFranchiseName(String franchiseName);
    }the client side program
    import java.rmi.RemoteException;
    import javax.ejb.*;
    import javax.naming.*;
    import javax.rmi.PortableRemoteObject;
    import java.util.Properties;
    import java.util.Collection;
    import java.util.Iterator;
    public class TestClient{
    public static void main(String[] args){
    try{
         Properties prop=new Properties();
         prop.setProperty(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
         prop.setProperty(Context.PROVIDER_URL,"t3://localhost:7001");
         InitialContext initial=new InitialContext(prop);
         Object objref=initial.lookup("CMPSportBean");
         SportTeamHome home=(SportTeamHome)PortableRemoteObject.narrow(objref,SportTeamHome.class);
         System.out.println("Creating a row.");
         home.create("basketball","Kings","Joe Maloof","Jason Williams");
         System.out.println("Looking up by primary key...");
         SportTeam team=home.findByPrimaryKey(new SportTeamPK("basketball","Kings"));
         System.out.println("Current franchise player:");
         System.out.println(team.getFranchiseName());
         System.out.println("Looking by by owner...");
         Collection col=home.findByOwnerName("Joe Maloof");
         if(     0 == col.size()     ){
              System.out.println("Found no such owner");
         }else {
              Iterator iter=col.iterator();
              while(iter.hasNext()){
              Object objref2=iter.next();
              SportTeam teamRef2=(SportTeam) PortableRemoteObject.narrow(objref2,SportTeam.class);
              System.out.println("Owner name:"+ teamRef2.getOwnerName());
    team.remove();
    }catch(RemoveException re){
         re.printStackTrace();
    }catch(NamingException ne){
         ne.printStackTrace();
    }catch(CreateException ce){
         ce.printStackTrace();
    }catch(FinderException fe){
         fe.printStackTrace();
    }catch(RemoteException re){
                  re.printStackTrace();
    }The primary key class
    //package sportBean.cmp;
    import java.io.Serializable;
    public class SportTeamPK implements Serializable{
    public String sport;
    public String nickName;
    public SportTeamPK(){}
    public SportTeamPK(String sport,String nickName){
    this.sport =sport;
    this.nickName=nickName;
    public String getSport(){
    return sport;
    public String getNickName(){
    return nickName;
    public int hashCode(){
    return (sport+nickName).hashCode();
    public boolean equals(Object other){
         if( (other == null) ||! (other instanceof SportTeamPK) ){
            return false;
         SportTeamPK otherPK=(SportTeamPK)other;
         return sport.equals(otherPK.sport) && nickName.equals(otherPK.nickName);
    The program has complied successfully .
    The META-INF directory has been created automatically
    the ejb-jar.xml file
    <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
    <!-- Generated XML! -->
    <ejb-jar>
      <enterprise-beans>
        <entity>
          <ejb-name>CMPSportBean</ejb-name>
          <home>SportTeamHome</home>
          <remote>SportTeam</remote>
          <ejb-class>SportTeamEJB</ejb-class>
          <persistence-type>Container</persistence-type>
          <prim-key-class>SportTeamPK</prim-key-class>
          <reentrant>False</reentrant>
          <abstract-schema-name>SportEJB</abstract-schema-name>
          <cmp-field>
            <field-name>sport</field-name>
          </cmp-field>
          <cmp-field>
            <field-name>nickName</field-name>
          </cmp-field>
          <cmp-field>
            <field-name>ownerName</field-name>
          </cmp-field>
          <cmp-field>
            <field-name>franchiseName</field-name>
          </cmp-field>
          <query>
            <query-method>
              <method-name>findByOwnerName</method-name>
              <method-params>
                <method-param>java.lang.String</method-param>
              </method-params>
            </query-method>
            <ejb-ql><![CDATA[SELECT OBJECT(o) FROM SportEJB AS o WHERE o.ownerName=?1]]></ejb-ql>
          </query>
        </entity>
      </enterprise-beans>
      <assembly-descriptor>
      </assembly-descriptor>
    </ejb-jar>the weblogic-ejb-jar.xml file
    <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB//EN' 'http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd'>
    <!-- Generated XML! -->
    <weblogic-ejb-jar>
      <weblogic-enterprise-bean>
        <ejb-name>CMPSportBean</ejb-name>
        <entity-descriptor>
          <pool>
          </pool>
          <entity-cache>
            <max-beans-in-cache>1000</max-beans-in-cache>
            <idle-timeout-seconds>600</idle-timeout-seconds>
            <read-timeout-seconds>600</read-timeout-seconds>
            <cache-between-transactions>False</cache-between-transactions>
          </entity-cache>
          <persistence>
            <persistence-use>
              <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
              <type-version>6.0</type-version>
              <type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
            </persistence-use>
          </persistence>
          <entity-clustering>
          </entity-clustering>
        </entity-descriptor>
        <transaction-descriptor>
          <trans-timeout-seconds>2</trans-timeout-seconds>
        </transaction-descriptor>
        <jndi-name>CMPSportBean</jndi-name>
      </weblogic-enterprise-bean>
    </weblogic-ejb-jar>the weblogic-cmp-rdbms-jar.xml file
    <!DOCTYPE weblogic-rdbms-jar PUBLIC  '-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB RDBMS Persistence//EN' 'http://www.bea.com/servers/wls700/dtd/weblogic-rdbms20-persistence-700.dtd'>
    <!-- Generated XML! -->
    <weblogic-rdbms-jar>
      <weblogic-rdbms-bean>
        <ejb-name>CMPSportBean</ejb-name>
        <data-source-name>myjdbcjndi</data-source-name>
        <table-map>
          <table-name>sportsteams</table-name>
          <field-map>
            <cmp-field>ownerName</cmp-field>
            <dbms-column>ownername</dbms-column>
          </field-map>
          <field-map>
            <cmp-field>franchiseName</cmp-field>
            <dbms-column>franchisename</dbms-column>
          </field-map>
          <field-map>
            <cmp-field>nickName</cmp-field>
            <dbms-column>nickname</dbms-column>
          </field-map>
          <field-map>
            <cmp-field>sport</cmp-field>
            <dbms-column>sport</dbms-column>
          </field-map>
        </table-map>
        <weblogic-query>
          <query-method>
            <method-name>findByOwnerName</method-name>
            <method-params>
              <method-param>java.lang.String</method-param>
            </method-params>
          </query-method>
        </weblogic-query>
        <check-exists-on-method>False</check-exists-on-method>
      </weblogic-rdbms-bean>
      <create-default-dbms-tables>True</create-default-dbms-tables>
    </weblogic-rdbms-jar>I tried to write config.xml file
    <JDBCDataSource
       Name=" "
       JNDIName="myjdbcjndi"
       PoolName="MyJDBC Connection Pool"
       Targets="myserver"
    />
    <JDBCConnectionPool
       Name="MyJDBC Connection Pool"
       Targets="myserver"
        URL="jdbc:odbc:test"
        DriverName="sun.jdbc.odbc.JdbcOdbcDriver"
        InitialCapacity="1"
        MaxCapacity="10"
    />When i tried to deploy, it showed me errors-
    weblogic.management.ApplicationException: activate failed forcmp
    Start server side stack trace:
    weblogic.management.ApplicationException: activate failed forcmp
    Module Name: cmp, Error: Exception activating module: EJBModule(cmp,status=PREPARED)
    Unable to deploy EJB: CMPSportBean from cmp:
    weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: myjdbcjndi could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:138)
         at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:211)
         at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:181)
         at weblogic.ejb20.manager.DBManager.setup(DBManager.java:162)
         at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:945)
         at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1296)
         at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:349)
         at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1592)
         at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1029)
         at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1016)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1112)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:732)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    TargetException:
    Unable to deploy EJB: CMPSportBean from cmp:
    weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: myjdbcjndi could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:138)
         at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:211)
         at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:181)
         at weblogic.ejb20.manager.DBManager.setup(DBManager.java:162)
         at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:945)
         at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1296)
         at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:349)
         at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1592)
         at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1029)
         at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1016)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1112)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:732)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
         at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1035)
         at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1016)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1112)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:732)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    End server side stack trace
    Module Name: cmp, Error: Exception activating module: EJBModule(cmp,status=PREPARED)
    Unable to deploy EJB: CMPSportBean from cmp:
    weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: myjdbcjndi could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:138)
         at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:211)
         at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:181)
         at weblogic.ejb20.manager.DBManager.setup(DBManager.java:162)
         at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:945)
         at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1296)
         at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:349)
         at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1592)
         at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1029)
         at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1016)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1112)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:732)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    TargetException:
    Unable to deploy EJB: CMPSportBean from cmp:
    weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: myjdbcjndi could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
    Start server side stack trace:
    weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: myjdbcjndi could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:138)
         at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:211)
         at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:181)
         at weblogic.ejb20.manager.DBManager.setup(DBManager.java:162)
         at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:945)
         at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1296)
         at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:349)
         at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1592)
         at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1029)
         at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1016)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1112)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:732)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    End server side stack trace
         <<no stack trace available>>
         <<no stack trace available>>
    I tried to put the file into the directory structure.
    I kept the class files into the WEB-INF/classess
    I could'nt understand whats wrong with it.
    Please help me it is urgent, if i could understand it i can proceed further

    Hi,
    I had the same error as you. I'm agree with arvind_India (previous). You must :
    1. Define a correct Connection Pool (warning: deploy it on your managed server).
    2. Test your connection Pool on your managed server.
    3. Create a DataSource from your connection Pool.
    4. Deploy your DataSource on your managed server.
    5. Verify the JNDI TREE of your managed server (Now, the JNDI name of your dataSource must appair).
    6. Deploy your Entity Bean (the error has disapeared).
    David (Paris-France).

  • Failed to load weblogic-ejb-jar.xml

    Hi,
    I try to deploy an EJB on Weblogic 9.1, but the weblogic-ejb-jar seems to cause this exception :
    ======================================================
    [wlappc] <30 oct. 2006 12 h 13 CET> <Error> <J2EE> <BEA-160187> <weblogic.appc failed to compile your application. Recompile with the -verbose option for more details. Please see the error message(s) below.>
    [wlappc] com.bea.xml.XmlException: failed to load java type corresponding to e=weblogic-ejb-jar@http://www.bea.com/ns/weblogic/910
    [wlappc] at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:325)
    [wlappc] at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:292)
    [wlappc] at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:302)
    [wlappc] at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:283)
    [wlappc] at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:153)
    [wlappc] at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
    [wlappc] at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:138)
    [wlappc] at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:271)
    [wlappc] at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:240)
    [wlappc] at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:300)
    [wlappc] at weblogic.application.descriptor.AbstractDescriptorLoader.createDescriptor(AbstractDescriptorLoader.java:344)
    [wlappc] at weblogic.application.descriptor.CachingDescriptorLoader.createDescriptor(CachingDescriptorLoader.java:188)
    [wlappc] at weblogic.application.descriptor.AbstractDescriptorLoader.createDescriptor(AbstractDescriptorLoader.java:328)
    [wlappc] at weblogic.application.descriptor.AbstractDescriptorLoader.getDescriptor(AbstractDescriptorLoader.java:237)
    [wlappc] at weblogic.application.descriptor.AbstractDescriptorLoader.getRootDescriptorBean(AbstractDescriptorLoader.java:217)
    [wlappc] at weblogic.ejb.spi.EjbJarDescriptor.parseWeblogicEjbJarBean(EjbJarDescriptor.java:171)
    [wlappc] at weblogic.ejb.container.dd.xml.DDUtils.processWLEjbJarXMLWithSchema(DDUtils.java:706)
    [wlappc] at weblogic.ejb.container.dd.xml.DDUtils.parseWLDD(DDUtils.java:535)
    [wlappc] at weblogic.ejb.container.dd.xml.DDUtils.createDescriptorFromJarFile(DDUtils.java:358)
    [wlappc] at weblogic.ejb.container.dd.xml.DDUtils.createReadOnlyDescriptorFromJarFile(DDUtils.java:141)
    [wlappc] at weblogic.ejb.container.ejbc.EJBCompiler.parseDescriptors(EJBCompiler.java:1345)
    [wlappc] at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:431)
    [wlappc] at weblogic.application.compiler.AppcUtils.compileEJB(AppcUtils.java:292)
    [wlappc] at weblogic.application.compiler.EJBCompiler.compile(EJBCompiler.java:95)
    [wlappc] at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:113)
    [wlappc] at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:43)
    [wlappc] at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:55)
    [wlappc] at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    [wlappc] at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:24)
    [wlappc] at weblogic.application.compiler.Appc.runBody(Appc.java:151)
    [wlappc] at weblogic.utils.compiler.Tool.run(Tool.java:158)
    [wlappc] at weblogic.utils.compiler.Tool.run(Tool.java:115)
    ======================================================
    Here is my weblogic-ejb-jar.xml file :
    ======================================================
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/910"
              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
              xsi:schemaLocation="http://www.bea.com/ns/weblogic/910
              http://www.bea.com/ns/weblogic/910/weblogic-ejb-jar.xsd">
    <weblogic-enterprise-bean>
    <ejb-name>MyMDB</ejb-name>
    <message-driven-descriptor>
         <resource-adapter-jndi-name>ActiveMQRA</resource-adapter-jndi-name>
         <connection-factory-jndi-name>myQCF</connection-factory-jndi-name>
    </message-driven-descriptor>
    <resource-description>
    <res-ref-name>jms/factory</res-ref-name>
    <jndi-name>myQCF</jndi-name>
    </resource-description>
    <resource-env-description>
    <resource-env-ref-name>jms/queue</resource-env-ref-name>
    <jndi-name>queue.out</jndi-name>
    </resource-env-description>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    ======================================================
    So, it looks like this problem : http://forums.bea.com/bea/message.jspa?messageID=600018030&tstart=0
    I just need a confirmation :
    - is the "res-ref-name" format incorrect with '/' character ?
    - is the jndi-name format incorrect with '.' character ?
    Else, what is the problem with this DD ?
    Thanks,
    Rudy

    "shubha" <[email protected]> wrote:
    >
    hi ,
    Ejb with ejb-name 'hellobean' in ejb-jar.xml
    should be specified in weblogic-ejb-jar.xml with <weblogic-enterprise-bean></weblogic-enterprise-bean>
    i am having problem in deploying the most simple bean on wls7.0 .
    when i try to open the bean module with the weblogic builder i get the
    following
    message
    weblogic.ejb20.WLDeploymentException: Could not locate bean with ejb-name
    'hellobean'
    in weblogic-ejb-jar.xml
         at weblogic.ejb20.deployer.CompositeMBeanDescriptor.initialize60(CompositeMBeanDescriptor.java:249)
         at weblogic.ejb20.deployer.CompositeMBeanDescriptor.init(CompositeMBeanDescriptor.java:180)
         at weblogic.ejb20.deployer.CompositeMBeanDescriptor.<init>(CompositeMBeanDescriptor.java:171)
         at weblogic.marathon.model.EJBJarCMBean.setup(EJBJarCMBean.java:408)
         at weblogic.marathon.tasks.OpenModuleTask.figureOutModule(OpenModuleTask.java:76)
         at weblogic.marathon.tasks.OpenModuleTask.figureOutModule(OpenModuleTask.java:109)
         at weblogic.marathon.tasks.OpenModuleTask.runBackground(OpenModuleTask.java:64)
         at weblogic.jellybeans.core.task.TaskThread.execute(TaskThread.java:114)
         at weblogic.jellybeans.core.task.TaskThread.run(TaskThread.java:55)
    Could not locate bean with ejb-name 'hellobean' in weblogic-ejb-jar.xml
    Module hello1 descriptors failed to load
    if anyone has come across the same problem and have debugged it please
    help me
    out
    thanks in advance

  • Deploying MDB on WebLogic server 8.1 (SP2) with Tibco JMS

    Hi,
              I am currently facing problems to deploy and run my MDB on weblogic connecting it to Tibco JMS as the foreign jms server.
              <br>
              <b>My ejb-jar.xml:</b>
              <br>
              <message-driven>
                        <ejb-name>DeAMMsgFactors</ejb-name>
                        <ejb-class>com.db.deam.mdb.DeAMMsgFactors</ejb-class>
                        <transaction-type>Container</transaction-type>
                        <message-driven-destination>
                             <destination-type>javax.jms.Topic</destination-type>
                        </message-driven-destination>
                   </message-driven>
                   </enterprise-beans>
                   <assembly-descriptor>
                        <security-role>
                                  <role-name>soiadmin</role-name>
                   </security-role>
                   </assembly-descriptor>
              <br>
              <b>weblogic-ejb-jar.xml:</b>
              <br>
              <weblogic-enterprise-bean>
              <ejb-name>DeAMMsgFactors</ejb-name>
              <message-driven-descriptor>
              <pool>
              <max-beans-in-free-pool>20</max-beans-in-free-pool>
              <initial-beans-in-free-pool>10</initial-beans-in-free-pool>
              </pool>
              <destination-jndi-name>WLFactorsTopic</destination-jndi-name>
              <connection-factory-jndi-name>WLFactorsCF</connection-factory-jndi-name>
              <jms-polling-interval-seconds>10</jms-polling-interval-seconds>
              </message-driven-descriptor>
              <transaction-descriptor>
              <trans-timeout-seconds>100000</trans-timeout-seconds>
              </transaction-descriptor>
                   </weblogic-enterprise-bean>
                   <security-role-assignment>
              <role-name>soiadmin</role-name>
              <principal-name>jmsusername</principal-name>
                   </security-role-assignment>
              <br>
              <b>Error:</b>
              weblogic.ejb20.WLDeploymentException: [EJB:011014]The Message-Driven EJB failed while creating a JMS Connection. The err
              or was:
              javax.jms.JMSSecurityException: invalid name or password.
              javax.jms.JMSSecurityException: invalid name or password
              at com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:395)
              at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:581)
              at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:1743)
              at com.tibco.tibjms.TibjmsTopicConnection.<init>(TibjmsTopicConnection.java:35)
              at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:92)
              at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:121)
              at com.tibco.tibjms.TibjmsTopicConnectionFactory.createTopicConnection(TibjmsTopicConnectionFactory.java:66)
              at weblogic.ejb20.internal.JMSConnectionPoller.getConnection(JMSConnectionPoller.java:607)
              at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1783)
              at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
              at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
              at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
              at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
              at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
              at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              at weblogic.ejb20.internal.JMSConnectionPoller.getConnection(JMSConnectionPoller.java:638)
              at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1783)
              at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
              at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
              at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
              at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
              at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
              at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              [JMSConnectionPoller] : ** Connect attempt for: WLFactorsTopic was: unsuccessful
              <br>
              <u><b>Any help would be appreciated.</b></u>
              <br>
              Thanks,<br>
              Kiran Kumar MV.

    I was able to use MDB to receive msg from a Tibco JMS queue. This is what you have to do: using WL console,
              - set up a foreign JMS Server. Make sure you specify the following correctly: jndi initial context factory (tibjms class), tibjms server url, username/password
              - create a foreign connection factory (if you are using CMT, make sure you create a XA compliant connection factory in Tibco JMS server). It seems that you have to specify URL again when creating XA connection factory in Tibjms.
              - create a foreign destination (queue/topic)
              In ejb-jar.xml and weblogic-ejb-jar.xml,
              - use resource-ref (wrapper) to specify the foreign connection factory
              - use resource-env-ref to specify the foreign destination.
              - In MDB ejb-jar.xml, specify destination-jndi-name and connection-factory-jndi-name.
              See Message Driven Beans chapter in Programming WebLogic EJB doc.
              Good luck.

Maybe you are looking for

  • Oracle JDBC driver does not handle Java empty strings correctly

    If you store a Java empty string in a VARCHAR column, then try to retrieve it, you get back a null. Can someone from Oracle JDBC development explain why this is not a bug? An empty string is not the same as a null.

  • SSD Upgrade Mac Mini (Late 2012)

    I have a Mac Mini (Late 2012) quad i7, 16gb ram, and 1tb HD. I would like to upgrade to an SSD, I currently have a 500GB Samsung Evo ready to install, but read that if you install a third party SSD, Yosemite does not boot. I got the 1TB hard drive re

  • Wbadmin System State Backup "Parameter is incorrect"

    Hello, We have two physical Windows Server 2008 R2 x64 Standard Domain Controllers and the system state backup on both fails with the same error. We issue the command: wbadmin start systemstatebackup -backuptarget:c: (NOTE: We did the REG fix to allo

  • LSO: Ensuring learner desktop is "LMS ready" & support plan for E-learning

    We are entering a time period with a significant rollouts planned for WBT's and on-line tests. Despite the efforts of our IT organization, our end user environment isn't quite as standardized as we would like. This creates the potential that when lea

  • OAB not updating on Mailbox Server 2010

    I have searched the forums and have not found a solution. Statistics: Two Mailbox servers with Exchange 2010 SP3 RU6. One CAS/HT with Exchange 2010 RU6. OAB last date modified on the generating Mailbox server is August 28 and today is September 8. Se