Urgent please!weblogic.ejb.extensions.LockTimedOutException

          Hi,
          We are using weblogic 5.1 with service pack 9.We get the following errors.Any
          idea what can be done to prevent these error messages and by which factor this
          time out of '300000 ms' is determined.How to change it/optimize it?
          weblogic.ejb.extensions.LockTimedOutException: Lock for
          primaryKey:users timed out after 300000 ms.
          at
          weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImp
          l.java:53)
          at
          weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(Stat
          efulEJBObject.java:162)
          at
          com.beasys.commerce.axiom.contact.GroupImplEOImpl.getUniqueId(Gr
          oupImplEOImpl.java:1322)

Yourt Tx timeout is lock timeout.
          The default is 5 mnts. YOu will see the following error/info
          when one thread might be holding a lock on primaryKey "users" and this
          second thread has to wait until the first thread releases the lock. You
          have to investigate why the first thread is holding lock for more than 5
          mnts. Otherwise you will have to increase the tx timeout
          Kumar
          Bharat Varma wrote:
          > Hi,
          >
          > We are using weblogic 5.1 with service pack 9.We get the following errors.Any
          > idea what can be done to prevent these error messages and by which factor this
          > time out of '300000 ms' is determined.How to change it/optimize it?
          >
          > weblogic.ejb.extensions.LockTimedOutException: Lock for
          > primaryKey:users timed out after 300000 ms.
          > at
          > weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImp
          > l.java:53)
          > at
          > weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(Stat
          > efulEJBObject.java:162)
          > at
          > com.beasys.commerce.axiom.contact.GroupImplEOImpl.getUniqueId(Gr
          > oupImplEOImpl.java:1322)
          >
          >

Similar Messages

Help: weblogic.ejb.extensions.LockTimedOutException

Dear All:
          I got this exception in our EJB app:
          weblogic.ejb.extensions.LockTimedOutException. Please see attached error
          message below. It is not happening every time you call the bean. It is
          reproducable with patience.
          Have you had this kind of problem and more importantly, how to avoid it?
          Our env is: Wl51 with sp 10, jdk1.3.02, Sun Solaris Unix, a cluster contains
          2 wl instance
          Thanks.
          Wed Jun 19 14:26:53 EDT 2002:<I> <TX> Transaction (TxC (5488304, xid =
          1024502557372_6636, timeout = 300, txState = Marked Rollback, root = null)
          rolled back after 300 sec.
          [GC 99080K->85533K(130688K), 0.0227977 secs]
          Wed Jun 19 14:26:54 EDT 2002:<I> <EJB JAR deployment
          /webapp/dtshc/dts/nmc/ejb/nmcejb.jar> Transaction: '1024502557372_6636'
          rolled back due to EJB exception:
          weblogic.ejb.extensions.LockTimedOutException: Lock for
          primaryKey:com.mm.nmc.entity.ProducerOneYearPlanPK@1700fc timed out after
          300000 ms.
          at
          weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:53)
          at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:146)
          at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
          at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:456)
          at
          weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
          t.java:162)
          at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:476)
          at
          com.mm.nmc.entity.ProducerOneYearPlanEJBEOImpl.getData(ProducerOneYearPlanEJ
          BEOImpl.java:979)
          at
          com.mm.nmc.session.PersonalTacticalSessionEJB.getTacticalPlanGoals(PersonalT
          acticalSessionEJB.java:200)
          at
          com.mm.nmc.session.PersonalTacticalSessionEJB.getPersonalTacticalPlan(Person
          alTacticalSessionEJB.java:165)
          at
          com.mm.nmc.session.PersonalTacticalSessionEJB.getPersonalTacticalPlan(Person
          alTacticalSessionEJB.java:155)
          at
          com.mm.nmc.session.PersonalTacticalSessionEJBEOImpl.getPersonalTacticalPlan(
          PersonalTacticalSessionEJBEOImpl.java:340)
          at
          com.mm.nmc.session.PersonalTacticalSessionEJBEOImpl_WLSkel.invoke(PersonalTa
          cticalSessionEJBEOImpl_WLSkel.java:167)
          at
          weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
          pter.java:347)
          at
          weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
          r.java:86)
          at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
          5)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
          Jiancai He
          http://www.hefamily.com


Thanks for your message:
          In our case, it is entity EJB. The problem only happens in clustered env,
          and only happens in one of the servers.
          Question: can wl51 use database to manage the concurrent access of entity
          EJBs?
          Thanks.
          Jiancai
          Jiancai He
          http://www.hefamily.com
          "ludovic le goff" <[email protected]> wrote in message
          news:[email protected]...
          > Hello,
          >
          > Basically, it means two (or more) different threads are trying to get an
          > exclusive lock on the same entity bean or stateful session bean at the
          same
          > time. One of the locks eventually times out and this exception is thrown.
          >
          > There are several things that could cause this, for instance:
          >
          > - Two threads trying to invoke a method on the same stateful session bean
          at
          > the same time. The EJB 1.1 spec states that the server must detect this
          > condition and throw a RemoteException to all subsequent callers.
          > LockTimedOutException is a sub-class of java.rmi.RemoteException.
          >
          > - Two threads are trying to access the same entity bean instance inside a
          > single server in the cluster, and the caller holding the lock does not
          > finish fast enough.
          >
          > You might want to check if you have declared the Remote and home interface
          > in your jsp/servlet as global variable. And since it's global, instance
          > getting overridden every time. That's why both the two request end up in
          > using the same EJBObject.
          >
          > You should changed your code and make the remote/home interface variable
          > declaration as local i.e. within the scope of a single request.
          > Then you should not see any problem. Both the threads will use different
          > EJBObjects and hence you should not see any exceptions.
          >
          > You need to code in such a way as to avoid deadlocks. For instance, if
          > more than one client accesses the EJBs in different order, a deadlock may
          > occur. This deadlock is detected and after a certain timeout (5 minutes by
          > default), the deadlock is removed and one of the clients gets a
          > LockTimedOutException. For example, if one request in your application has
          > entity Account 1 (by doing an ejbFindByPrimaryKey) and is then about to
          get
          > Customer 1, and if at the same time another request in another business
          > method has got Customer 1 and is waiting for Account 1, you'll get a
          > deadlock and a LockTimedOutException after 5 minutes. You could avoid
          this
          > by include the code in a synchronized block. You could also get a
          deadlock
          > if you're making a reentrant call, e.g., A calls B which calls back to A.
          >
          > If you haven't already seen this, here's a blurb from "Locking Model for
          > Entity EJBs" at
          >
          http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_environment.html#108796
          > 7 that you might find interesting:
          >
          > The EJB 1.1 container in WebLogic Server Version 5.1 uses a pessimistic
          > locking mechanism for entity EJB instances. As clients enlist an EJB or
          EJB
          > method in a transaction, WebLogic Server places an exclusive lock on the
          EJB
          > instance or method for the duration of the transaction. Other clients
          > requesting the same EJB or method block until the current transaction
          > completes.
          >
          > This method of locking provides reliable access to EJB data, and avoids
          > unnecessary calls to ejbLoad() to refresh the EJB instance's persistent
          > fields. However, in certain circumstances pessimistic locking may not
          > provide the best model for concurrent access to the EJB's data. Once a
          > client has locked an EJB instance, other clients are blocked from the
          EJB's
          > data even if they intend only to read the persistent fields.
          >
          > In a Nutshell the first exception is a consequence of the second.
          >
          > Hope this helps,
          > Ludovic.
          > Developer Relations Engineer
          > BEA Customer Support
          > "newsgroups.bea.com" <[email protected]> a écrit dans le message news:
          > [email protected]...
          > > Dear All:
          > >
          > > I got this exception in our EJB app:
          > > weblogic.ejb.extensions.LockTimedOutException. Please see attached error
          > > message below. It is not happening every time you call the bean. It is
          > > reproducable with patience.
          > >
          > > Have you had this kind of problem and more importantly, how to avoid it?
          > >
          > > Our env is: Wl51 with sp 10, jdk1.3.02, Sun Solaris Unix, a cluster
          > contains
          > > 2 wl instance
          > >
          > > Thanks.
          > >
          > >
          > >
          > >
          > >
          > >
          > >
          > >
          > >
          > >
          > >
          > > Wed Jun 19 14:26:53 EDT 2002:<I> <TX> Transaction (TxC (5488304, xid =
          > > 1024502557372_6636, timeout = 300, txState = Marked Rollback, root =
          null)
          > > rolled back after 300 sec.
          > >
          > > [GC 99080K->85533K(130688K), 0.0227977 secs]
          > >
          > > Wed Jun 19 14:26:54 EDT 2002:<I> <EJB JAR deployment
          > > /webapp/dtshc/dts/nmc/ejb/nmcejb.jar> Transaction: '1024502557372_6636'
          > > rolled back due to EJB exception:
          > >
          > > weblogic.ejb.extensions.LockTimedOutException: Lock for
          > > primaryKey:com.mm.nmc.entity.ProducerOneYearPlanPK@1700fc timed out
          after
          > > 300000 ms.
          > >
          > > at
          > >
          weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:53)
          > >
          > > at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:146)
          > >
          > > at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
          > >
          > > at
          weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:456)
          > >
          > > at
          > >
          >
          weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
          > > t.java:162)
          > >
          > > at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:476)
          > >
          > > at
          > >
          >
          com.mm.nmc.entity.ProducerOneYearPlanEJBEOImpl.getData(ProducerOneYearPlanEJ
          > > BEOImpl.java:979)
          > >
          > > at
          > >
          >
          com.mm.nmc.session.PersonalTacticalSessionEJB.getTacticalPlanGoals(PersonalT
          > > acticalSessionEJB.java:200)
          > >
          > > at
          > >
          >
          com.mm.nmc.session.PersonalTacticalSessionEJB.getPersonalTacticalPlan(Person
          > > alTacticalSessionEJB.java:165)
          > >
          > > at
          > >
          >
          com.mm.nmc.session.PersonalTacticalSessionEJB.getPersonalTacticalPlan(Person
          > > alTacticalSessionEJB.java:155)
          > >
          > > at
          > >
          >
          com.mm.nmc.session.PersonalTacticalSessionEJBEOImpl.getPersonalTacticalPlan(
          > > PersonalTacticalSessionEJBEOImpl.java:340)
          > >
          > > at
          > >
          >
          com.mm.nmc.session.PersonalTacticalSessionEJBEOImpl_WLSkel.invoke(PersonalTa
          > > cticalSessionEJBEOImpl_WLSkel.java:167)
          > >
          > > at
          > >
          >
          weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
          > > pter.java:347)
          > >
          > > at
          > >
          >
          weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
          > > r.java:86)
          > >
          > > at
          > >
          >
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
          > > 5)
          > >
          > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
          > >
          > >
          > >
          > >
          > >
          > >
          > > --
          > > Jiancai He
          > > http://www.hefamily.com
          > >
          > >
          >
          >

Why throws the "weblogic.ejb.extensions.LockTimedOutException" `s exception?

When a statusful session bean be called frequencely in weblogic 5.1, weblogic throws
"weblogic.ejb.extensions.LockTimedOutException", why?
please help me!!thanks!!

Hmmm, this exception occurs when two or more threads are trying to get an
exclusive lock on a session(not permitted) or entity bean(times out) at the
same time. Is it possible that two threads are accessing your session bean
at the same time?
"xiaoniao" <[email protected]> wrote in message
news:3d96cde6$[email protected]..
>
When a statusful session bean be called frequencely in weblogic 5.1,weblogic throws
"weblogic.ejb.extensions.LockTimedOutException", why?
please help me!!thanks!!

Weblogic.ejb.extensions.LockTimedOutException

Hi,
I am running an application on wl4.5.1 and the app server seems to hang and average of about once a week and we have to restart it it seems really random. The only pattern we've noticed from looking at the log files is that just before we go down we get a lot of weblogic.ejb.extensions.LockTimedOutException ' s. There seems to be a deadlock for access to one of the entity beans and the requesting transactions timeout. Is it possible that the appserver hangs because of these exceptions getting thrown and all the appservers resouces get used up so it doesn't take any more requests? Does any one have any ideas/experience with this issue?
Thanks for any help in advance,
R..

Hi Rukus,
AFAIK 4.5.1 was EOL-ed quite some time ago, so it may be
pretty hard to get support for this version.
You may find a solution by searching newsgroups
archive. I've done some preliminary work for you,
hopefully it will help:
http://makeashorterlink.com/?M29D32364
Regards,
Slava Imeshev
"Rukus" <[email protected]> wrote in message
news:3eaf0172$[email protected]..
Hi,
I am running an application on wl4.5.1 and the app server seems to hangand average of about once a week and we have to restart it it seems really
random. The only pattern we've noticed from looking at the log files is
that just before we go down we get a lot of
weblogic.ejb.extensions.LockTimedOutException ' s. There seems to be a
deadlock for access to one of the entity beans and the requesting
transactions timeout. Is it possible that the appserver hangs because of
these exceptions getting thrown and all the appservers resouces get used up
so it doesn't take any more requests? Does any one have any
ideas/experience with this issue?
>
Thanks for any help in advance,
R..

Weblogic.ejb.extensions.LockTimedOutException: Bean could not be locked, current owner: '1068220908390_17680', new owner: '1068220908390_17748', timeout: '300000' ms

Hi All,
Again, Since yesterday (11/11/2003) , I started getting the Bean Lock error as
below (I am using weblogic 4.5.1) :
Note: We are using Stateless beans.
Tue Nov 11 14:15:11 CET 2003:<I> <EJB> Transaction: '1068220908390_17748' rolled
back due to EJB exception:
com.sgs.common.framework.exception.EPlatformSystemException: An unexpected error
occurs when trying to perform your request (RemoteException).
weblogic.ejb.extensions.LockTimedOutException: Bean could not be locked, current
owner: '1068220908390_17680', new owner: '1068220908390_17748', timeout: '300000'
ms
     at com.sgs.ecertificate.CertificateSessionBean.getCertificate(CertificateSessionBean.java:1866)
     at com.sgs.ecertificate.CertificateSessionBean.approveCertificate(CertificateSessionBean.java:2617)
     at com.sgs.ecertificate.CertificateSessionBeanEOImpl.approveCertificate(CertificateSessionBeanEOImpl.java:936)
     at com.sgs.ecertificate.CertificateSessionBeanEOImpl_ServiceStub.approveCertificate(CertificateSessionBeanEOImpl_ServiceStub.java:1761)
     at com.sgs.ecertificate.ProcessApproveCertificateServlet.processRequest(ProcessApproveCertificateServlet.java:219)
     at com.sgs.common.framework.servlet.EPlatformServlet.doPost(EPlatformServlet.java:189)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:840)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:99)
     at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:311)
     at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:257)
     at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:550)
     at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:284)
     at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:105)
Tue Nov 11 14:15:11 CET 2003: ERR #-3# com.sgs.ecertificate.ProcessApproveCertificateServlet
An unexpected error occurs when trying to perform your request (RemoteException).
com.sgs.common.framework.exception.EPlatformSystemException: An unexpected error
occurs when trying to perform your request (RemoteException).
weblogic.ejb.extensions.LockTimedOutException: Bean could not be locked, current
owner: '1068220908390_17680', new owner: '1068220908390_17748', timeout: '300000'
ms
     at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:310)
     at weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:128)
     at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:182)
     at com.sgs.ecertificate.entity.CertificateEntityBeanEOImpl.getData(CertificateEntityBeanEOImpl.java:4645)
     at com.sgs.ecertificate.CertificateSessionBean.getCertificate(CertificateSessionBean.java:1743)
     at com.sgs.ecertificate.CertificateSessionBean.approveCertificate(CertificateSessionBean.java:2617)
     at com.sgs.ecertificate.CertificateSessionBeanEOImpl.approveCertificate(CertificateSessionBeanEOImpl.java:936)
     at com.sgs.ecertificate.CertificateSessionBeanEOImpl_ServiceStub.approveCertificate(CertificateSessionBeanEOImpl_ServiceStub.java:1761)
     at com.sgs.ecertificate.ProcessApproveCertificateServlet.processRequest(ProcessApproveCertificateServlet.java:219)
     at com.sgs.common.framework.servlet.EPlatformServlet.doPost(EPlatformServlet.java:189)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:840)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:99)
     at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:311)
     at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:257)
     at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:550)
     at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:284)
     at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:105)
Thanks a lot in advance.
Regards,
Nilesh.

Hi All,
Again, Since yesterday (11/11/2003) , I started getting the Bean Lock error as
below (I am using weblogic 4.5.1) :
Note: We are using Stateless beans.
Tue Nov 11 14:15:11 CET 2003:<I> <EJB> Transaction: '1068220908390_17748' rolled
back due to EJB exception:
com.sgs.common.framework.exception.EPlatformSystemException: An unexpected error
occurs when trying to perform your request (RemoteException).
weblogic.ejb.extensions.LockTimedOutException: Bean could not be locked, current
owner: '1068220908390_17680', new owner: '1068220908390_17748', timeout: '300000'
ms
     at com.sgs.ecertificate.CertificateSessionBean.getCertificate(CertificateSessionBean.java:1866)
     at com.sgs.ecertificate.CertificateSessionBean.approveCertificate(CertificateSessionBean.java:2617)
     at com.sgs.ecertificate.CertificateSessionBeanEOImpl.approveCertificate(CertificateSessionBeanEOImpl.java:936)
     at com.sgs.ecertificate.CertificateSessionBeanEOImpl_ServiceStub.approveCertificate(CertificateSessionBeanEOImpl_ServiceStub.java:1761)
     at com.sgs.ecertificate.ProcessApproveCertificateServlet.processRequest(ProcessApproveCertificateServlet.java:219)
     at com.sgs.common.framework.servlet.EPlatformServlet.doPost(EPlatformServlet.java:189)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:840)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:99)
     at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:311)
     at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:257)
     at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:550)
     at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:284)
     at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:105)
Tue Nov 11 14:15:11 CET 2003: ERR #-3# com.sgs.ecertificate.ProcessApproveCertificateServlet
An unexpected error occurs when trying to perform your request (RemoteException).
com.sgs.common.framework.exception.EPlatformSystemException: An unexpected error
occurs when trying to perform your request (RemoteException).
weblogic.ejb.extensions.LockTimedOutException: Bean could not be locked, current
owner: '1068220908390_17680', new owner: '1068220908390_17748', timeout: '300000'
ms
     at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:310)
     at weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:128)
     at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:182)
     at com.sgs.ecertificate.entity.CertificateEntityBeanEOImpl.getData(CertificateEntityBeanEOImpl.java:4645)
     at com.sgs.ecertificate.CertificateSessionBean.getCertificate(CertificateSessionBean.java:1743)
     at com.sgs.ecertificate.CertificateSessionBean.approveCertificate(CertificateSessionBean.java:2617)
     at com.sgs.ecertificate.CertificateSessionBeanEOImpl.approveCertificate(CertificateSessionBeanEOImpl.java:936)
     at com.sgs.ecertificate.CertificateSessionBeanEOImpl_ServiceStub.approveCertificate(CertificateSessionBeanEOImpl_ServiceStub.java:1761)
     at com.sgs.ecertificate.ProcessApproveCertificateServlet.processRequest(ProcessApproveCertificateServlet.java:219)
     at com.sgs.common.framework.servlet.EPlatformServlet.doPost(EPlatformServlet.java:189)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:840)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:99)
     at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:311)
     at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:257)
     at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:550)
     at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:284)
     at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:105)
Thanks a lot in advance.
Regards,
Nilesh.

Weblogic.ejb.extensions.LockTimeOutException HELP!

Hi,
We're seeing weblogic.ejb.extensions.LockTimeOutException when we try
to access some Entity Bean's data member. I'm wondering someone could
help us?
There is some background:
WL server 5.1, SP10 (almost sure:)
Running in Solaris w/ Oracle 8i
The sequence of calls is:
IWorkspaceRemote workspace = (IWorkspaceRemote)
getEntityBean(EJBConstants.JNDI_NAME_WORKSPACE, new
Long(workspaceID));
WorkspaceDetailData wsData = workspace.getWorkspaceDetailData();
( the EJB home is cached in memory ***)
Inside ejbLoad() we're using the Composite Entity EJB pattern (for
lazy loading) and looks something like this:
void ejbLoad() {
m_baseData = loadBaseData();
if (m_detailData != null) {
m_detailData = loadDetailData();
DetailData getWorkspaceDetailData() {
if (m_detailData == null) {
m_detailData = loadDetailData();
THe stack trace I get is:
weblogic.ejb.extensions.LockTimedOutException: Lock for
primaryKey:21071 timed out after 60000 ms.
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:53)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:146)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:456)
at weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:162)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:476)
at com.intralinks.wsadmin.entity.WorkspaceBeanEOImpl.getWorkspaceDetailData(WorkspaceBeanEOImpl.java:155)
at com.intralinks.util.IntralinksServlet.setWorkspaceIDNoEventLogging(Unknown
Source)
at com.intralinks.util.IntralinksServlet.setWorkspaceID(Unknown
Source)
at com.intralinks.servlets.html.workspaces.EnterWorkspaceServlet.process(Unknown
Source)
Any ideas?
Thanks,
- Roberto

Hi Roberto,
Check CP, data sources (if they are available in 5.1) etc for oracle instance
parameters like servers, user ids, passwords, urls etc.
S
[email protected] (Roberto) wrote:
Hi,
We're seeing weblogic.ejb.extensions.LockTimeOutException when we try
to access some Entity Bean's data member. I'm wondering someone could
help us?
There is some background:
WL server 5.1, SP10 (almost sure:)
Running in Solaris w/ Oracle 8i
The sequence of calls is:
IWorkspaceRemote workspace = (IWorkspaceRemote)
getEntityBean(EJBConstants.JNDI_NAME_WORKSPACE, new
Long(workspaceID));
WorkspaceDetailData wsData = workspace.getWorkspaceDetailData();
( the EJB home is cached in memory ***)
Inside ejbLoad() we're using the Composite Entity EJB pattern (for
lazy loading) and looks something like this:
void ejbLoad() {
m_baseData = loadBaseData();
if (m_detailData != null) {
m_detailData = loadDetailData();
DetailData getWorkspaceDetailData() {
if (m_detailData == null) {
m_detailData = loadDetailData();
THe stack trace I get is:
weblogic.ejb.extensions.LockTimedOutException: Lock for
primaryKey:21071 timed out after 60000 ms.
at weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:53)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:146)
at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:456)
at weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObject.java:162)
at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:476)
at com.intralinks.wsadmin.entity.WorkspaceBeanEOImpl.getWorkspaceDetailData(WorkspaceBeanEOImpl.java:155)
at com.intralinks.util.IntralinksServlet.setWorkspaceIDNoEventLogging(Unknown
Source)
at com.intralinks.util.IntralinksServlet.setWorkspaceID(Unknown
Source)
at com.intralinks.servlets.html.workspaces.EnterWorkspaceServlet.process(Unknown
Source)
Any ideas?
Thanks,
- Roberto

Weblogic-ejb-extensions.xml not producing desired effect

weblogic-ejb-extensions.xml seems to have no effect on the output pstore
location when deploying a stateful bean.
i get the following errors...
weblogic.ejb.common.DeploymentException: ; nested exception is:
java.io.IOException: Could not make directory
/usr/local/weblogic/pstore/stateful.Browse
java.io.IOException: Could not make directory
/usr/local/weblogic/pstore/stateful.Browse
in the extensions xml i have the following:
<persistence-store-descriptor>
<persistence-store-file>
<persistence-store-directory-root>
/usr/local/weblogic/karson/pstore
</persistence-store-directory-root>
</persistence-store-file>
</persistence-store-descriptor>
as you can see from the above error the deployer is not using this
information.
any help is much appreciated.
i also do not see a dtd for the weblogic-ejb-extensions.xml install, but i
do for the more typical files such as weblogic-ejb-jar.xml . where is this
dtd located?
Karson

weblogic-ejb-extensions.xml seems to have no effect on the output pstore
location when deploying a stateful bean.
i get the following errors...
weblogic.ejb.common.DeploymentException: ; nested exception is:
java.io.IOException: Could not make directory
/usr/local/weblogic/pstore/stateful.Browse
java.io.IOException: Could not make directory
/usr/local/weblogic/pstore/stateful.Browse
in the extensions xml i have the following:
<persistence-store-descriptor>
<persistence-store-file>
<persistence-store-directory-root>
/usr/local/weblogic/karson/pstore
</persistence-store-directory-root>
</persistence-store-file>
</persistence-store-descriptor>
as you can see from the above error the deployer is not using this
information.
any help is much appreciated.
i also do not see a dtd for the weblogic-ejb-extensions.xml install, but i
do for the more typical files such as weblogic-ejb-jar.xml . where is this
dtd located?
Karson

Weblogic EJB Cache full exception

For my application i am using weblogic 4.5.1, and while running the server i am getting
an exception "weblogic.ejb.extensions.CacheFullException:".
Though i have restarted the server still the problem persists, can you give suggestion
how i can resolve this.
[exception.doc]

You'll get a CacheFullException if you exceed the max-beans-in-cache
4.5.1 is pretty old right now, and I don't believe it's even supported anymore. I'd
suggest upgrading if possible.
-- Rob
Vetriselvan wrote:
For my application i am using weblogic 4.5.1, and while running the server i am getting
an exception "weblogic.ejb.extensions.CacheFullException:".
Though i have restarted the server still the problem persists, can you give suggestion
how i can resolve this.
Name: exception.doc
exception.doc Type: Microsoft Word Document (application/msword)
Encoding: base64

Please check this ejb-jar.xml, weblogic-ejb-jar.xml,weblogic-cmp-rdbms.xml

i am getting a classcast exception.My Stateless and stateful session bean works
fine .. problem only with Entity bean. Please check these xml files and let me
know if i have missed anything.
ejb-jar.xml
<?xml version="1.0"?>
<!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>
<enterprise-beans>
<entity>
<ejb-name>stores</ejb-name>
<home>Ejb.Stores.storesHome</home>
<remote>Ejb.Stores.storesRemote</remote>
<ejb-class>Ejb.Stores.storesBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>storesBean</abstract-schema-name>
<cmp-field>
<field-name>productId</field-name>
</cmp-field>
<cmp-field>
<field-name>descrip</field-name>
</cmp-field>
<cmp-field>
<field-name>price</field-name>
</cmp-field>
<primkey-field>productId</primkey-field>
<query>
<query-method>
<method-name>findPriceGreaterThan</method-name>
<method-params>
<method-param>double</method-param>
</method-params>
</query-method>
<ejb-ql>
<![CDATA[SELECT OBJECT(a) FROM storesBean AS a WHERE a.price > ?1]]>
</ejb-ql>
</query>
</entity>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>stores</ejb-name>
     <method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
------------- end of ejb-ar.xml---------------------
weblogic-jar.xml
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN"
"http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd" >
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>stores</ejb-name>
<entity-descriptor>
<persistence>
<persistence-type>
     <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-type>
     <persistence-use>
     <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
     <type-version>6.0</type-version>
     </persistence-use>
</persistence>
</entity-descriptor>
<jndi-name>storesEntity</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
------------- end of weblogic-jar.xml----------
weblogic-cmp-rdbms-jar.xml
<!DOCTYPE weblogic-rdbms-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 6.0.0
EJB RDBMS Persistence//EN' 'http://www.bea.com/servers/wls600/dtd/weblogic-rdbms20-persistence-600.dtd'>
<weblogic-rdbms-jar>
<weblogic-rdbms-bean>
<ejb-name>stores</ejb-name>
<data-source-name>sqlTX</data-source-name>
<table-name>ProductEJBTable</table-name>
<field-map>
<cmp-field>productId</cmp-field>
<dbms-column>productId</dbms-column>
</field-map>
<field-map>
<cmp-field>descrip</cmp-field>
<dbms-column>descrip</dbms-column>
</field-map>
<field-map>
<cmp-field>price</cmp-field>
<dbms-column>price</dbms-column>
</field-map>
</weblogic-rdbms-bean>
<create-default-dbms-tables>false</create-default-dbms-tables>
</weblogic-rdbms-jar>
---------------- end of weblogic-cmp-rdbms-jar.xml----------
Do i have to mention the connection Pool name anywhere .. My connection Pool name
is sql7Pool and my datasource name which i have mentioned is sqlTx. I am using
Sql server 7. I am deploying a jar file(not a war file) and accessng the EJB through
a Servlet. Please any help would definitely be appreciated.
Cheers
Ashish.

I thought you were getting a class cast exception but the stack trace shows
a NullPointerException on line 38 of your servlet code. I am not sure if the
code that you have attached is the complete code or just snippets of your
complete code. Anyways, counting 38 lines in the code you attached points to
the line "mr =
mh.create(request.getParameter("login"),request.getParameter("name"));"
which could be because "mh" is null. Can you verify "mh" is not null and
also "objRef" is not null.
Attaching the stack trace for ClassCastException would be useful.
-- Anand
"Ashish Suvarna" <[email protected]> wrote in message
news:[email protected]...
>
Hey Anand,
Thanks for your reply. I have attached the StackTrace,Servlet code andmy
location and settings of my servlet .
This is the StackTrace which i get :
pl.java:265)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
before create
java.lang.NullPointerException
at trialweblogic.webServlet.doGet(webServlet.java:38)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
-------------- end of StackTrace---------------------
My Servlet Code is
package trialweblogic;
import javax.servlet.*;
import javax.servlet.http.*;
import java.io.*;
import java.util.*;
import java.sql.*;
import javax.naming.InitialContext;
import javax.rmi.PortableRemoteObject;
import javax.ejb.ObjectNotFoundException;
import javax.ejb.DuplicateKeyException;
import javax.ejb.EJBException;
import java.rmi.RemoteException;
import java.rmi.Remote;
import trialweblogic.*;
public class webServlet extends HttpServlet {
masterHome mh;
masterRemote mr;
OutputStream out;
private static final String CONTENT_TYPE = "text/html";
public void init(ServletConfig config) throws ServletException {
super.init(config);
public void doGet(HttpServletRequest request, HttpServletResponseresponse)
throws ServletException, IOException {
response.setContentType(CONTENT_TYPE);
PrintWriter out = response.getWriter();
// out = response.getOutputStream();
try{
InitialContext ic = new InitialContext();
Object objRef = ic.lookup("masterBeanJNDI");
mh =(masterHome)PortableRemoteObject.narrow(objRef,masterHome.class);
>
mr =mh.create(request.getParameter("login"),request.getParameter("name"));
out.println("after create");
}catch(Exception ex){
ex.printStackTrace();
public void destroy() {
--------- end of servlet--------------
I am using Weblogic 6.1. I have included the following in my web.xml filewhich
is located atC:\bea\wlserver6.1\config\examples\applications\examplesWebApp\WEB-INF
>
>
<servlet>
<servlet-name>webServlet</servlet-name>
<servlet-class>trialweblogic.webServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>webServlet</servlet-name>
<url-pattern>/webServlet/*</url-pattern>
</servlet-mapping>
My Servlet is located atC:\bea\wlserver6.1\config\examples\applications\examplesWebApp\WEB-INF\class
es\trialweblogic\
folder. In this folder i also have the supporting files (home,remote &bean tooo).
>
>
I call this servlet when te user submits the info from a JSP page.
Hope this info helps in solving my problem. Do i have to mention theconnection
Pool name anywhere in the xml descriptor or am i missing anything here. iguess
Connection Pool name is not required since we are mentioning the JNDI namein
the xml descriptor. Bye for now.Awaiting your reply.
Cheers
Ashish.
"Anand Byrappagari" <[email protected]> wrote:
It is unlikely that your xml descriptors can cause class cast exceptions.
How did you install the servlet? Can you attach the servlet code that
might
help. Also complete stack trace of the exceptions would be helpful.
-- Anand
"Ashish Suvarna" <[email protected]> wrote in message
news:[email protected]...
Hi Anand,
Thanks for quic reply.Hey i am using weblogic6.1. I am Not usinga WAR
and
ear file.I have created a jar file and deployed it.now i have createda
servlet
to access entity bean.Is a war file neccessary for accesing an entitybean
through
Servlet or JSP ???I am using sql server 7. The error that it givesis -----
java.lang.ClassCastException: Cannot narrow remote object<br>
"inside lookup method aaaaaaa" java.lang.NullPointerException. <br>
Hope to get ur reply soon. in another entity bean i am getting thiserror ---
java.lang.ClassCastException:
weblogic.jdbc.common.internal.RmiDataSource
.. I
can't understand wots this error. I feel i am missing something inmy xml
descriptor.
Bye for now.
Cheers
Ashish.
"Anand Byrappagari" <[email protected]> wrote:
Can you attach the stack trace for the exception? Also please describe
you
environment - are the war and jar files installed separately? Are
they
composed into a ear? Also when are you getting a classcast exception?
-- Anand
"Ashish Suvarna" <[email protected]> wrote in message
news:[email protected]...
i am getting a classcast exception.My Stateless and stateful sessionbean
works
fine .. problem only with Entity bean. Please check these xml filesand
let me
know if i have missed anything.
ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD EnterpriseJavaBeans
2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<entity>
<ejb-name>stores</ejb-name>
<home>Ejb.Stores.storesHome</home>
<remote>Ejb.Stores.storesRemote</remote>
<ejb-class>Ejb.Stores.storesBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>storesBean</abstract-schema-name>
<cmp-field>
<field-name>productId</field-name>
</cmp-field>
<cmp-field>
<field-name>descrip</field-name>
</cmp-field>
<cmp-field>
<field-name>price</field-name>
</cmp-field>
<primkey-field>productId</primkey-field>
<query>
<query-method>
<method-name>findPriceGreaterThan</method-name>
<method-params>
<method-param>double</method-param>
</method-params>
</query-method>
<ejb-ql>
<![CDATA[SELECT OBJECT(a) FROM storesBean AS a WHERE
a.price> >> >>> >> >?1]>
</ejb-ql>
</query>
</entity>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>stores</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
------------- end of ejb-ar.xml---------------------
weblogic-jar.xml
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD
WebLogic
6.0.0 EJB//EN"
"http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd" >
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>stores</ejb-name>
<entity-descriptor>
<persistence>
<persistence-type>
<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-type>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
</persistence-use>
</persistence>
</entity-descriptor>
<jndi-name>storesEntity</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
------------- end of weblogic-jar.xml----------
weblogic-cmp-rdbms-jar.xml
<!DOCTYPE weblogic-rdbms-jar PUBLIC '-//BEA Systems, Inc.//DTD
WebLogic
6.0.0
EJB RDBMS Persistence//EN'
'http://www.bea.com/servers/wls600/dtd/weblogic-rdbms20-persistence-600.dt
d
<weblogic-rdbms-jar>
<weblogic-rdbms-bean>
<ejb-name>stores</ejb-name>
<data-source-name>sqlTX</data-source-name>
<table-name>ProductEJBTable</table-name>
<field-map>
<cmp-field>productId</cmp-field>
<dbms-column>productId</dbms-column>
</field-map>
<field-map>
<cmp-field>descrip</cmp-field>
<dbms-column>descrip</dbms-column>
</field-map>
<field-map>
<cmp-field>price</cmp-field>
<dbms-column>price</dbms-column>
</field-map>
</weblogic-rdbms-bean>
<create-default-dbms-tables>false</create-default-dbms-tables>
</weblogic-rdbms-jar>
---------------- end of weblogic-cmp-rdbms-jar.xml----------
Do i have to mention the connection Pool name anywhere .. My
connection
Pool name
is sql7Pool and my datasource name which i have mentioned is sqlTx.I am
using
Sql server 7. I am deploying a jar file(not a war file) and accessngthe
EJB through
a Servlet. Please any help would definitely be appreciated.
Cheers
Ashish.

Error parsing weblogic-ejb-jar. HELP please :(

When I have added the transaction-descriptor into weblogic-ejb-jar.xml I start getting next error:
[java] ERROR: Error parsing 'META-INF/weblogic-ejb-jar.xml' line 18: The content of element type "weblogic-enterprise-bean" must match "(ejb-name,caching-descriptor?,persistence-descriptor?,clustering-descriptor?,transaction-descriptor?,reference-descriptor?,enable-call-by-reference?,jndi-name?,transaction-isolation*)".
The weblogic-ejb.jar.xml is the next:
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB//EN' 'http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
     <weblogic-enterprise-bean>
     <ejb-name>statelessSession</ejb-name>
     <caching-descriptor>
          <max-beans-in-free-pool>100</max-beans-in-free-pool>
          <idle-timeout-seconds>1200</idle-timeout-seconds>
     </caching-descriptor>
     <transaction-descriptor>
     <trans-timeout-seconds>50</trans-timeout-seconds>
     </transaction-descriptor>
     <jndi-name>statelessSession.EcasServicesHome</jndi-name>
     </weblogic-enterprise-bean>
</weblogic-ejb-jar>
Please tell me what did I do wrong and how to fix the problem.
Thnx.
VG.

I suspect you are using a version of WebLogic higher than 5.1. Coz, your XML is invalid if I use the following DOCTYPE.
<!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">
You can try this
<?xml version="1.0" encoding="UTF-8"?>
<!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">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>statelessSession</ejb-name>
<stateless-session-descriptor>
<pool>
<max-beans-in-free-pool>100</max-beans-in-free-pool>
<initial-beans-in-free-pool>20</initial-beans-in-free-pool>
</pool>
</stateless-session-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>50</trans-timeout-seconds>
</transaction-descriptor>
<jndi-name>statelessSession.EcasServicesHome</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
cheers !
Dips

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.

EJBs with .ejb extension

Please let me know when/how/where can i have EJBs with .ejb extension?

It's a Weblogic thing. The tool mentioned in the linked post, EJBgen, is similar to XDoclet in that you use special annotations in a single file that is parsed to generate all of the EJB interfaces. The .ejb suffix is commonly used for these files.

Weblogic-ejb-jar

Hi
The code is as follows:
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB//EN" "http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>CustomerController</ejb-name>
<stateful-session-descriptor>
    </stateful-session-descriptor>
<local-jndi-name>CustomerJNDI</local-jndi-name>
<ejb-name>TransactionController</ejb-name>
<stateful-session-descriptor>
    </stateful-session-descriptor>
<local-jndi-name>TransactionJNDI</local-jndi-name>
<ejb-name>PayeeController</ejb-name>
<stateful-session-descriptor>
    </stateful-session-descriptor>
<local-jndi-name>PayeeJNDI</local-jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>I got the following error:
ERROR: Error from ejbc: Error parsing file 'META-INF/weblogic-ejb-jar.xml' at line: 17 column: 28. The content of element type "weblogic-enterprise-bean" must match "(ejb-name,(entity-descriptor|stateless-session-descriptor|stateful-sessio
n-descriptor|message-driven-descriptor)?,transaction-descriptor?,iiop-security-d
escriptor?,reference-descriptor?,enable-call-by-reference?,clients-on-same-serve
r?,run-as-identity-principal?,jndi-name?,local-jndi-name?,dispatch-policy?)".
Please give urgent solution to it.
Thanks

weblogic-ejb-jar.xml jndi-name (instead of local-jndi-name) is with JDeveloper version 10.1.2 & 10.1.3

Kernel panics, message saying "You need to restart your computer.Hold down the Power..." I am in the middle of HSC very URGENT please help!! Mac keeps needing to restart!!

Kernel panics, message saying "You need to restart your computer.Hold down the Power..." I am in the middle of HSC very URGENT please help!! Mac keeps needing to restart!!
I looked in console and its saying that it may be because of Sophos Anti-Virus, i deleted and uninstalled all traces of Sophos but looked in console and this is some of the lines coming up:
26/09/13 10:11:17.945 PM com.apple.launchd: (com.sophos.intercheck[6460]) posix_spawn("/Library/Sophos Anti-Virus/InterCheck.app/Contents/MacOS/InterCheck", ...): No such file or directory
26/09/13 10:11:17.945 PM com.apple.launchd: (com.sophos.autoupdate[6461]) posix_spawn("/Library/Sophos Anti-Virus/SophosAutoUpdate.app/Contents/MacOS/SophosAutoUpdate", ...): No such file or directory
26/09/13 10:11:17.945 PM com.apple.launchd: (com.sophos.notification[6462]) posix_spawn("/Library/Sophos Anti-Virus/SophosAntiVirus.app/Contents/MacOS/SophosAntiVirus", ...): No such file or directory
26/09/13 10:11:17.946 PM com.apple.launchd: (com.sophos.intercheck[6460]) Exited with code: 1
26/09/13 10:11:17.946 PM com.apple.launchd: (com.sophos.intercheck) Throttling respawn: Will start in 10 seconds
26/09/13 10:11:17.946 PM com.apple.launchd: (com.sophos.autoupdate[6461]) Exited with code: 1
26/09/13 10:11:17.946 PM com.apple.launchd: (com.sophos.autoupdate) Throttling respawn: Will start in 10 seconds
26/09/13 10:11:17.946 PM com.apple.launchd: (com.sophos.notification[6462]) Exited with code: 1
26/09/13 10:11:17.946 PM com.apple.launchd: (com.sophos.notification) Throttling respawn: Will start in 10 seconds
26/09/13 10:11:18.291 PM Safari: self <TabContentView: 0x7f8d5dd1aa50>
26/09/13 10:11:22.617 PM Safari: self <TabContentView: 0x7f8d5db7bb00>
26/09/13 10:11:27.866 PM Safari: self <TabContentView: 0x7f8d5c331a70>
26/09/13 10:12:19.939 PM com.apple.launchd.peruser.501: (com.sophos.uiserver[6487]) posix_spawn("/Library/Sophos Anti-Virus/SophosUIServer.app/Contents/MacOS/SophosUIServer", ...): No such file or directory
26/09/13 10:12:19.939 PM com.apple.launchd.peruser.501: (com.sophos.uiserver[6487]) Exited with code: 1
26/09/13 10:12:19.939 PM com.apple.launchd.peruser.501: (com.sophos.uiserver) Throttling respawn: Will start in 10 seconds"
Looked all over computer and cant find anything of Sophos please help very urgent!

That was all that there was in the most recent one, how long do you think it could take to fix?
Here is the second most recent:
Wed Sep 25 15:39:39 2013
panic(cpu 0 caller 0xffffff80002c4794): Kernel trap at 0xffffff7f81757965, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0xffffff81acc397fe, CR3: 0x000000001e2b5025, CR4: 0x00000000000606e0
RAX: 0x000000001d31a000, RBX: 0x0000000000000000, RCX: 0x0000000000000000, RDX: 0x0000000000000000
RSP: 0xffffff80b0dbb710, RBP: 0xffffff80b0dbb820, RSI: 0x0000000000000000, RDI: 0x0000000000000001
R8: 0x000000000000000a, R9: 0x0000000000000378, R10: 0x0000000000000128, R11: 0x0000000000000378
R12: 0xffffff800c626400, R13: 0x0000000000000000, R14: 0x0000000000000000, R15: 0xffffff81acc39802
RFL: 0x0000000000010246, RIP: 0xffffff7f81757965, CS: 0x0000000000000008, SS: 0x0000000000000010
CR2: 0xffffff81acc397fe, Error code: 0x0000000000000000, Faulting CPU: 0x0
Backtrace (CPU 0), Frame : Return Address
0xffffff80b0dbb3c0 : 0xffffff8000220792
0xffffff80b0dbb440 : 0xffffff80002c4794
0xffffff80b0dbb5f0 : 0xffffff80002da55d
0xffffff80b0dbb610 : 0xffffff7f81757965
0xffffff80b0dbb820 : 0xffffff7f817667a0
0xffffff80b0dbb840 : 0xffffff7f8173a58e
0xffffff80b0dbb870 : 0xffffff7f8177fb6f
0xffffff80b0dbb8a0 : 0xffffff7f81779632
0xffffff80b0dbb8d0 : 0xffffff7f8177d7d5
0xffffff80b0dbb900 : 0xffffff7f8177c6db
0xffffff80b0dbb9e0 : 0xffffff7f817412b8
0xffffff80b0dbba10 : 0xffffff7f81778684
0xffffff80b0dbba30 : 0xffffff7f817449ce
0xffffff80b0dbbb60 : 0xffffff7f81741a4c
0xffffff80b0dbbbc0 : 0xffffff8000655f3e
0xffffff80b0dbbbe0 : 0xffffff800065681a
0xffffff80b0dbbc40 : 0xffffff8000656fbb
0xffffff80b0dbbd80 : 0xffffff80002a3f08
0xffffff80b0dbbe80 : 0xffffff8000223096
0xffffff80b0dbbeb0 : 0xffffff80002148a9
0xffffff80b0dbbf10 : 0xffffff800021bbd8
0xffffff80b0dbbf70 : 0xffffff80002aef10
0xffffff80b0dbbfb0 : 0xffffff80002daec3
      Kernel Extensions in backtrace:
         com.apple.driver.AppleIntelHD3000Graphics(7.3.2)[A2328231-E577-32FF-B20F-D08BDC FE9C51]@0xffffff7f81738000->0xffffff7f8179bfff
            dependency: com.apple.iokit.IOPCIFamily(2.7)[5C23D598-58B2-3204-BC03-BC3C0F00BD32]@0xffffff 7f80889000
            dependency: com.apple.iokit.IONDRVSupport(2.3.4)[7C8672C4-8B0D-3CCF-A79A-23C62E90F895]@0xff ffff7f80d2e000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.4)[D0A1F6BD-E66E-3DD8-9913-A3AB8746F422]@0 xffffff7f80cf5000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
11G63b
Kernel version:
Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64
Kernel UUID: FF3BB088-60A4-349C-92EA-CA649C698CE5
System model name: MacBookPro8,1 (Mac-94245B3640C91C81)
System uptime in nanoseconds: 1866666823698
last loaded kext at 480357661446: com.apple.filesystems.smbfs          1.7.2 (addr 0xffffff7f80795000, size 241664)
last unloaded kext at 303348424187: com.apple.driver.AppleUSBUHCI          5.1.0 (addr 0xffffff7f80af7000, size 65536)
loaded kexts:
com.sophos.kext.sav          8.0.14
org.virtualbox.kext.VBoxNetAdp          4.2.16
org.virtualbox.kext.VBoxNetFlt          4.2.16
org.virtualbox.kext.VBoxUSB          4.2.16
org.virtualbox.kext.VBoxDrv          4.2.16
com.logmein.driver.LogMeInSoundDriver          1.0.2
com.Greatdy.driver.SystemAudioCapture          1.0.0
com.apple.filesystems.smbfs          1.7.2
com.apple.driver.AppleHWSensor          1.9.5d0
com.apple.driver.AppleMikeyHIDDriver          122
com.apple.iokit.IOBluetoothSerialManager          4.0.8f17
com.apple.driver.AudioAUUC          1.59
com.apple.driver.AppleHDA          2.2.5a5
com.apple.driver.AppleMikeyDriver          2.2.5a5
com.apple.driver.AGPM          100.12.75
com.apple.driver.AppleUpstreamUserClient          3.5.9
com.apple.driver.SMCMotionSensor          3.0.2d6
com.apple.driver.AppleSMCPDRC          5.0.0d8
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.AudioIPCDriver          1.2.3
com.apple.driver.AppleSMCLMU          2.0.1d2
com.apple.driver.ApplePolicyControl          3.1.33
com.apple.driver.ACPI_SMC_PlatformPlugin          5.0.0d8
com.apple.driver.AppleIntelHD3000Graphics          7.3.2
com.apple.driver.AppleBacklight          170.2.2
com.apple.driver.AppleLPC          1.6.0
com.apple.driver.AppleMCCSControl          1.0.33
com.apple.filesystems.autofs          3.0
com.apple.driver.AppleUSBTCButtons          227.6
com.apple.driver.BroadcomUSBBluetoothHCIController          4.0.8f17
com.apple.driver.AppleUSBTCKeyboard          227.6
com.apple.driver.AppleIRController          312
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.BootCache          33
com.apple.iokit.SCSITaskUserClient          3.2.1
com.apple.driver.XsanFilter          404
com.apple.iokit.IOAHCISerialATAPI          2.0.3
com.apple.iokit.IOAHCIBlockStorage          2.1.0
com.apple.driver.AppleUSBHub          5.1.0
com.apple.driver.AppleFWOHCI          4.9.0
com.apple.driver.AirPort.Brcm4331          561.7.22
com.apple.driver.AppleSDXC          1.2.2
com.apple.iokit.AppleBCM5701Ethernet          3.2.4b8
com.apple.driver.AppleEFINVRAM          1.6.1
com.apple.driver.AppleSmartBatteryManager          161.0.0
com.apple.driver.AppleAHCIPort          2.3.1
com.apple.driver.AppleUSBEHCI          5.1.0
com.apple.driver.AppleACPIButtons          1.5
com.apple.driver.AppleRTC          1.5
com.apple.driver.AppleHPET          1.7
com.apple.driver.AppleSMBIOS          1.9
com.apple.driver.AppleACPIEC          1.5
com.apple.driver.AppleAPIC          1.6
com.apple.driver.AppleIntelCPUPowerManagementClient          195.0.0
com.apple.nke.applicationfirewall          3.2.30
com.apple.security.quarantine          1.4
com.apple.security.TMSafetyNet          8
com.apple.driver.AppleIntelCPUPowerManagement          195.0.0
com.apple.iokit.IOSerialFamily          10.0.5
com.apple.driver.DspFuncLib          2.2.5a5
com.apple.iokit.IOSurface          80.0.2
com.apple.iokit.IOFireWireIP          2.2.5
com.apple.driver.AppleHDAController          2.2.5a5
com.apple.iokit.IOHDAFamily          2.2.5a5
com.apple.iokit.IOAudioFamily          1.8.6fc18
com.apple.kext.OSvKernDSPLib          1.3
com.apple.driver.AppleGraphicsControl          3.1.33
com.apple.driver.AppleSMC          3.1.3d10
com.apple.driver.IOPlatformPluginLegacy          5.0.0d8
com.apple.driver.AppleSMBusPCI          1.0.10d0
com.apple.driver.AppleBacklightExpert          1.0.4
com.apple.driver.IOPlatformPluginFamily          5.1.1d6
com.apple.iokit.IONDRVSupport          2.3.4
com.apple.driver.AppleSMBusController          1.0.10d0
com.apple.driver.AppleIntelSNBGraphicsFB          7.3.2
com.apple.iokit.IOGraphicsFamily          2.3.4
com.apple.kext.triggers          1.0
com.apple.driver.AppleUSBBluetoothHCIController          4.0.8f17
com.apple.iokit.IOBluetoothFamily          4.0.8f17
com.apple.driver.AppleThunderboltDPInAdapter          1.8.5
com.apple.driver.AppleThunderboltDPAdapterFamily          1.8.5
com.apple.driver.AppleThunderboltPCIDownAdapter          1.2.5
com.apple.driver.AppleUSBMultitouch          230.5
com.apple.iokit.IOUSBHIDDriver          5.0.0
com.apple.driver.AppleUSBMergeNub          5.1.0
com.apple.driver.AppleUSBComposite          5.0.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.2.1
com.apple.iokit.IOBDStorageFamily          1.7
com.apple.iokit.IODVDStorageFamily          1.7.1
com.apple.iokit.IOCDStorageFamily          1.7.1
com.apple.iokit.IOSCSIArchitectureModelFamily          3.2.1
com.apple.driver.AppleThunderboltNHI          1.6.0
com.apple.iokit.IOThunderboltFamily          2.0.3
com.apple.iokit.IOUSBUserClient          5.0.0
com.apple.iokit.IOFireWireFamily          4.4.8
com.apple.iokit.IO80211Family          420.3
com.apple.iokit.IOEthernetAVBController          1.0.1b1
com.apple.iokit.IONetworkingFamily          2.1
com.apple.iokit.IOAHCIFamily          2.0.8
com.apple.iokit.IOUSBFamily          5.1.0
com.apple.driver.AppleEFIRuntime          1.6.1
com.apple.iokit.IOHIDFamily          1.7.1
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          177.11
com.apple.kext.AppleMatch          1.0.0d1
com.apple.driver.DiskImages          331.7
com.apple.iokit.IOStorageFamily          1.7.2
com.apple.driver.AppleKeyStore          28.18
com.apple.driver.AppleACPIPlatform          1.5
com.apple.iokit.IOPCIFamily          2.7
com.apple.iokit.IOACPIFamily          1.4

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

Urgent please!weblogic.ejb.extensions.LockTimedOutException

Similar Messages

Maybe you are looking for