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.
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
> >
> >
>
>
-
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.. -
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)
>
>
-
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,
- RobertoHi 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?
Karsonweblogic-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 -
Product extension oracle.odi could not be loaded. The product cannot start.
Hi everybody!
i hava a problem in running odi on IBM AIX, when i write ./odi.sh. the odi can not start ,
"Product extension oracle.odi could not be loaded. The product cannot start." This is error message, why?
by the way IBM AIX's version is 5.3, ODI'S version is ofm_odi_generic_11.1.1.3.0_disk1_1of1 ,It is correct?
Pleass help me to solve it!user10795526 wrote:
hi,
Can you tell us how to solve this iusse??Wait for Oracle to certify the software on the platform in question. You can run the ODI Server components but will have to run Studio on a supported platform. -
Could not find selected item matching value "New" warning message in ADF
Hi,
I have a selectOneChoice1 for a field which has the following fixed values in it. And while creating it, I selected the 'SelctionRequired' option so that this field will always have a value.
New
Pending
Completed.
While navigating to this page, I am trying to set the value to 'New' (Retrieved from the DB) in the backing bean. But when the page is rendered, the above field is empty with the above options in the list and jdev has the follwing error message in its log.
WARNING: Could not find selected item matching value "New" in CoreSelectOneChoice[UIXEditableFacesBeanImpl, id=selectOneChoice1]
Can any one help me with this issue?
Thanks,
PriyaThe value of a list binding is the zero-based integer position in the list that is selected, not the actual underlying value.
The simplest way to set the value of an attribute is to use an attribute binding (which can be bound to the same attribute as the list binding). When you set the value of an attribute binding, it sets the value as you supply it. Otherwise, you'd need to set the list binding's value to the numerical "slot" number of the one you want to change the value to. -
Parent could not create lock ???
Hi,
Please Im testing the Apache plug-in mod_wl_20.so from Weblogic9.1.<br>
<br>
I've followed the instructions very carefully but still can not run it with an Apache2 server.<br>
<br>
I have tried for about 10 hours! <br>
<br>
I allways hit on this error in my apache log, when it loads the weblogic module:<br>
<br>
[Tue Dec 27 03:12:10 2005] [crit] (2)No such file or directory: mod_weblogic: Parent could not create lock
Configuration Failed<br>
<br>
<br>
Now, I dont know what this means?<br>
<br>
<br>
Is it the LOCKFILE ?? as in:
# ./apachectl -V<br>
Server version: Apache/2.0.52<br>
Server built: Jan 8 2005 01:51:11<br>
Server's Module Magic Number: 20020903:9<br>
Architecture: 32-bit<br>
Server compiled with....<br>
-D APACHE_MPM_DIR="server/mpm/prefork"<br>
-D APR_HAS_SENDFILE<br>
-D APR_HAS_MMAP<br>
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)<br>
-D APR_USE_FCNTL_SERIALIZE<br>
-D APR_USE_PTHREAD_SERIALIZE<br>
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT<br>
-D APR_HAS_OTHER_CHILD<br>
-D AP_HAVE_RELIABLE_PIPED_LOGS<br>
-D HTTPD_ROOT="/usr/apache2"<br>
-D SUEXEC_BIN="/usr/apache2/bin/suexec"<br>
-D DEFAULT_PIDLOG="/var/run/apache2/httpd.pid"<br>
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"<br>
<b> -D DEFAULT_LOCKFILE="/var/run/apache2/accept.lock"</b><br>
-D DEFAULT_ERRORLOG="logs/error_log"<br>
-D AP_TYPES_CONFIG_FILE="/etc/apache2/mime.types"<br>
-D SERVER_CONFIG_FILE="/etc/apache2/httpd.conf"<br>
<br>
Also my httpd.conf specify the:<br>
<b>LockFile /var/apache2/logs/accept.lock</b><br>
<br>
But in both cases, the directory exists and the user has write permission (Ive set the entire directory as 777 permission).<br>
<br>
I dont think it is the problem in it, but in weblogic_mod as it stops there. Everything run fine without the wls mod.
<br>
<br>
Please ADVICE.
<br>
Great thanks.<br><p>Hello,</p>
<p>Make that you remove any existing var/run/apache2/accept.lock file before restarting Apache.</p>
<p>If var/run/apache2/accept.lock is not created after you start Apache, then experiment with different locations for this file.</p>
<p>Make sure you do not give the location of an NFS share.</p>
<p>
Hussein Badakhchani</br>
</p> -
WL Server & apache 2 integration: mod_weblogic: could not create lock
Hi,
we're running Apache 2.0.50 as a front-end for WL Server 8.1 using mod_weblogic as the proxy.
We have to run Apache as a different user than the default LocalSystem account to be able to access a windows share. But when we set up Apache to run as a user (in the windows domain) the server will not start up. Looking at the error log I can see the following message:
[Wed Jan 26 16:10:37 2005] [crit] (OS 5)Access is denied. : mod_weblogic: could not create lock
The user has administrative rights on the server so I'm not really sure why mod_weblogic can not obtain a lock.
What is the lock it's trying to obtain?
Thanks.
RuairiHello,
has this been resolved by anyone in the meantime? I'm running into the same kind of problem. Here's my setup:
Apache 2.0.55, on Solaris 8
mod_wl_20.so, from Bea Weblogic Server 8.1 SP 2
When I have the following line in my httpd.conf file:
LoadModule weblogic_module modules/mod_wl_20.so
I receive the following error in Apache's error log file:
[timestamp] [crit] (13)Permission denied: mod_weblogic: could not create lock
I am currently not running Apache as root. Without the weblogic module, it works fine.
I guess my main question is: what kind of lock is it trying to obtain? Changing the AcceptMutex parameter in Apache does not seem to help.
Regards,
Ralf -
I set up a playlist in itunes and when I try so sync it to my iphone, I get an error message "itunes could not copy "x" to the iphone "x" because a timeout error occurred. Using itunes 10.5.2.11 and Windows Vista 64. Any help? Thanks in advance!
I have the same question and the only reply I've found on the forum was "change the USB hub", which HASN'T worked. So I am accepting new suggestions. Tks!
-
Document being distributed no changes not possible and btadminh could not be locked
Hi All,
I am getting ERROR: "document being distributed no changes not possible" & WARNING:"BTadminH could not be locked" in CRM WEBUI while trying to edit the order.
I checked all the BDOCs and smq1, smq2 ,smw01 here are no queues stuck here.
I also run distribution check FM, whenever i run it will be unlocked and able to edit. but this is not the solution for me because this error and warning getting to every new order (transaction) .
thanks,
Vinnu.Hi,
Check the initial status settings, there should not be any distribution lock maintained.
Award point if it is helpful
Regards,
D Singh -
Personnel number 00000000 could not be locked; lock 00000000 failed twice
Hi!
I'm trying to create new person to SAP HCM by using SAP ERP HCM Process and Forms functionality. Process is defined to be fast entry process: NO_WORKFLOW value in workflow template.
I have defined process' attributes CENTRAL_PERSON as blank and PERNR attribute to get default value from business process logic's (DEF) from SAP_PA (infotype 1: 0001-PERNR).
When process is trying to check values it gives me error "Perosnal number 00000000 could not be locked; lock 00000000 failed twice". Error's message class is HRASR00_FBD and message number is 011.
I debugged the ISR process and the actual error is raised in CL_HRPA_MASTERDATA_ENQ_DEQ class' method ENQUE_BY_PERNR.
ABAP call stack is this:
35 CL_HRASR00_PAITF_MAPPER=======CP CL_HRASR00_PAITF_MAPPER=======CM00F 14 METHOD IF_HRASR00_MAPPER~LOCK_OBJECT
34 CL_HRASR00_DISPATCHER=========CP CL_HRASR00_DISPATCHER=========CM00X 22 METHOD PROCESS_LOCKING
33 CL_HRASR00_DISPATCHER=========CP CL_HRASR00_DISPATCHER=========CM017 24 METHOD FSCN_DO_OPERATION
32 CL_HRASR00_DISPATCHER=========CP CL_HRASR00_DISPATCHER=========CM00R 803 METHOD PROCESS_DATA_CONTAINER
31 CL_HRASR00_DISPATCHER=========CP CL_HRASR00_DISPATCHER=========CM00G 178 METHOD DO_OPERATION
30 CL_HRASR00_DISPATCHER=========CP CL_HRASR00_DISPATCHER=========CM00I 24 METHOD IF_HRASR00_DISPATCHER~CHECK
29 CL_IM_HRASR00ISR==============CP CL_IM_HRASR00ISR==============CM004 496 METHOD IF_EX_QISR1~SCENARIO_PROCESS_USER_COMMAND
28 CL_EX_QISR1===================CP CL_EX_QISR1===================CM004 16 METHOD IF_EX_QISR1~SCENARIO_PROCESS_USER_COMMAND
27 SAPLQISR9 QISR_CL_ISR_WEB_UI_PROXY 2025 METHOD PROCESS_USER_COMMAND
26 SAPLQISR9 LQISR9U07 499 FUNCTION ISR_PROCESS_EVENT_INTERNAL
25 SAPLMPO_46CFF_ISR_SERVICE LMPO_46CFF_ISR_SERVICEU06 184 FUNCTION ISR_PROCESS_EVENT
24 SAPLMPO_46CFF_ISR_SERVICE LMPO_46CFF_ISR_SERVICEU12 157 FUNCTION ISR_PROCESS_EVENT_WD
23 CL_QISR_UI_PROCESS_EVENT_MODELCP CL_QISR_UI_PROCESS_EVENT_MODELCM003 6 METHOD IF_QISR_UI_DATA_MODEL~EXECUTE
22 /1BCWDY/9KIHZOTJM1O6VWFQPCJ4==CP /1BCWDY/B_9KIHZOTJM1O6VWIWGPVP 2032 METHOD CALL_RFC_ISR_PROCESS_EVENT
21 /1BCWDY/9KIHZOTJM1O6VWFQPCJ4==CP /1BCWDY/B_9KIHZOTJM1O6VWIWGPVP 1487 METHOD CALL_ISR_PROCESS_EVENT
20 /1BCWDY/9KIHZOTJM1O6VWFQPCJ4==CP /1BCWDY/B_9KIHZOTJM1O6VWIWGPVP 108 METHOD IWCI_QISR_UI~CALL_ISR_PROCESS_EVENT
19 /1BCWDY/9KIHZOTJM1MJA1NASP4F==CP /1BCWDY/B_9KIHZOTJM1MJA1SLVIT2 6357 METHOD _OVR_4T5KF0KFFIXZTMN23D48RVJME
18 /1BCWDY/9KIHZOTJM1MJA1NASP4F==CP /1BCWDY/B_9KIHZOTJM1MJA1SLVIT2 127 METHOD IF_PROCESS_START~NAVIGATE_TO_REVIEW_FORM
17 /1BCWDY/9KIHZOTJM1MJA1NASP4F==CP /1BCWDY/B_9KIHZOTJM1MJA1SLVIT2 5656 METHOD ONACTIONCHECK_AND_SEND
16 /1BCWDY/9KIHZOTJM1MJA1NASP4F==CP /1BCWDY/B_9KIHZOTJM1MJA1SLVIT2 976 METHOD IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER
15 CL_WDR_DELEGATING_VIEW========CP CL_WDR_DELEGATING_VIEW========CM005 6 METHOD INVOKE_EVENTHANDLER
14 CL_WDR_ACTION=================CP CL_WDR_ACTION=================CM00A 38 METHOD IF_WDR_ACTION~FIRE
13 CL_WDR_WINDOW_PHASE_MODEL=====CP CL_WDR_WINDOW_PHASE_MODEL=====CM00U 95 METHOD DO_HANDLE_ACTION_EVENTS
12 CL_WDR_WINDOW_PHASE_MODEL=====CP CL_WDR_WINDOW_PHASE_MODEL=====CM002 94 METHOD PROCESS_REQUEST
11 CL_WDR_WINDOW=================CP CL_WDR_WINDOW=================CM00V 12 METHOD PROCESS_REQUEST
10 CL_WDR_MAIN_TASK==============CP CL_WDR_MAIN_TASK==============CM00I 77 METHOD EXECUTE
9 CL_WDR_MAIN_TASK==============CP CL_WDR_MAIN_TASK==============CM00U 6 METHOD IF_WDR_RUNTIME~EXECUTE
8 CL_WDR_CLIENT_ABSTRACT_HTTP===CP CL_WDR_CLIENT_ABSTRACT_HTTP===CM01A 114 METHOD HANDLE_REQUEST
7 CL_WDR_MAIN_TASK==============CP CL_WDR_MAIN_TASK==============CM00J 85 METHOD IF_HTTP_EXTENSION~HANDLE_REQUEST
6 CL_HTTP_SERVER================CP CL_HTTP_SERVER================CM00D 594 METHOD EXECUTE_REQUEST
5 SAPLHTTP_RUNTIME LHTTP_RUNTIMEU02 1216 FUNCTION HTTP_DISPATCH_REQUEST
4 SAPMHTTP SAPMHTTP 13 MODULE (PBO) %_HTTP_START
3 2 PBO MODULE %_HTTP_START
2 SAPMHTTP 2 PBO SCREEN 10
1 0 TRANSACTION ()
Our SAP levels are these:
SAP_BASIS 731 0004 SAPKB73104
SAP_APPL 606 0004 SAPKH60604
SAP_HR 604 0049 SAPKE60449
SAP_HRRXX 604 0049 SAPK-60449INSAPHRRXX
So, I'm out of ideas. How to prevent locking for person number 00000000 when creating new employee by using SAP HCM Processes & Forms?
Best regards,
-TimoHi!
I asked this from SAP. I got following answer:
Error "Personnel number &1 could not be locked; lock & failed twice - HRASR00_FBD 011" is sometimes raised due to default value of field PERSG, PERSK, and WERKS. Can you please make sure that these fields have a manual default value assigned on your process to be sure that pernr can be generated?
You can also try to check whether standard hire processes like HIRE_01 or HIRE_10 are working correctly or same lock error is raised.
I valuated also PERSG, PERSK and WERKS and after that the process was valuated with new personnel number taken from number range.
So result was that new number was taken from number range immediatelly when my data entry form was shown (I use process without workflow = fast entry) --> If user uses to form without saving (= abort new employee creation), one number is taken from number range, but not used. I ended up with solution that system is not getting the number automatically in start of the process (= I don't valute those PERSG, PESK and WERKS, they are valuated in form by user anyway). Instead I take manually new number form employee's number range (RP_PREL) before the data checks by using function module NUMBER_GET_NEXT.
Hopefully the solution by valuating PERSG, PERSK and WERKS works for you.
-Timo
Message was edited by: Timo Saviahde
I tried to edit my answers text to contain readable formatting --> no matter what I do, it shows my text without correct line brakes and other stuff... -
Substance could not be locked "*'ENQUEUE_ESLX_ESTRH'*
Hello Team,
In the Production box i i'm getting the error "Substance could not be locked", in SM37
If i go to develoment box & display the object we are gettin the error during 'ENQUEUE_ESLX_ESTRH'
*Error : 'Substance could not be locked'.*
How we can correct this error can help
==========================
form lock_substances.
loop at it_estrh.
call function 'ENQUEUE_ESLX_ESTRH'
exporting
mode_estrh = 'E'
mandt = sy-mandt
recn = it_estrh-recn
actn = it_estrh-actn
x_recn = ' '
x_actn = ' '
_scope = '2'
_wait = ' '
_collect = ' '
exceptions
foreign_lock = 1
system_failure = 2
others = 3.
if sy-subrc ne 0.
message e208(00) with 'Substance could not be locked'.
endif.
endloop.
endform. " lock_substances
thanks
sandy
Edited by: mrSandy1981 on Dec 11, 2009 11:45 AM
Edited by: Rob Burbank on Dec 11, 2009 10:53 AMThanks Vishwa,
Particular document means you mean the table ESTRH',
How to check document is already opened
How to check locked by other user in the system
Could you pls tel me know
Thanks
sandeep
Maybe you are looking for
-
Adfs 2.0 issue with claims
Dear technet members, Our ADFS 2.0 (Windows 2008 R2) fails to obtains (retain after period of 20 hours) claims for "newly" created users (objects). Our AD has more than 14000 users. We see this our web applications when we query for claims (we see t
-
My wifi is not working and i have tried alot of stuff please help! It will look like its conected but not and the Router secton and the DNS does not have anything there. like i said please help! IOS 4.2.1 Baseband 6.15.00
-
Messages stuck in QRFC inbound and outbound queues by system error
Hi Experts, We faced a big problem in our PI server which stopped all the traffic in the iDoc to File interface. Both the QRFC queues (inbound - SMQ1 as outbound - SMQ2) where stuck by a system error. In IDX5 of PI we saw two inbound iDocs on exact t
-
Displaying fields in the body part
I have a feeling this is something that should be chrystal clear, but the only record information I'm able to view in Browse mode are the fields that are in the header. I can't get anything in the body part to display. Searched through help but can f
-
Make DropdownBox initial state to show blank
Hi! I need to set the initial value selected of sap.ui.commons.DropdownBox to be blank before user interaction, but without adding any empty items. Is this possible? If yes then how? Kind regards for your help Janis