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..
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
> >
> >
>
>
-
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. -
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)
>
>
-
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.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 -
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 -
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. -
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.
-
Accessing WebLogic EJBs from Tomcat 3.2
Has anyone out there tried to access EJBs in a WebLogic 5.10 SP6 app
server from a servlet in Tomcat 3.2? I'm operating under Win2K. When I
try to create the initial naming context, the following exception is
thrown:
java.lang.NoClassDefFoundError: COM/rsa/jsafe/JSAFE_InvalidUseException
at weblogic.security.WLMessageDigest.getInstance
(WLMessageDigest.java:52)
at weblogic.security.MD5RandomBitsSource.seed
(MD5RandomBitsSource.java:56)
at weblogic.rjvm.LocalRJVM.<init>(LocalRJVM.java:108)
at weblogic.rjvm.LocalRJVM.getLocalRJVM(LocalRJVM.java:85)
at weblogic.rjvm.RJVMManager.getLocalRJVM(RJVMManager.java:89)
at weblogic.rjvm.RJVMManager.initialize(RJVMManager.java:78)
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:137)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:182)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(
WLInitialContextFactoryDelegate.java, Compiled Code)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(
WLInitialContextFactoryDelegate.java:148)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(
WLInitialContextFactory.java:123)
at javax.naming.spi.NamingManager.getInitialContext(
NamingManager.java:771)
at javax.naming.InitialContext.getDefaultInitCtx(
InitialContext.java:169)
at javax.naming.InitialContext.<init>(InitialContext.java:146)
From poking around in the WebLogic server directories, in appears that
the RSA-related classes are implemented as native methods in jsafe.dll.
Should I be trying to install this dll in Tomcat somehow? If so, where
should I be looking for information on how to do this?
-- Erik"Erik Horstkotte" <[email protected]> wrote in message news:[email protected]...
Has anyone out there tried to access EJBs in a WebLogic 5.10 SP6 app
server from a servlet in Tomcat 3.2? I'm operating under Win2K. When I
try to create the initial naming context, the following exception is
thrown:[Sigh. I know it's bad form to follow up your own posts, but...]
Ignore the exact problem description above. I wasn't including
\weblogic\classes and \weblogic\lib\weblogicaux.jar in Tomcat's
classpath. Now the same code connects to the app server:
Connected successfully using http to JIMBO/172.16.1.4:7001
But immediately after connecting, I get a new exception:
java.lang.NoSuchMethodError: java.lang.NoSuchMethodException:
getNameInNamespace
at weblogic.jndi.toolkit.BasicWLContext_WLStub.ensureInitialized
(BasicWLContext_WLStub.java:127)
at weblogic.jndi.toolkit.BasicWLContext_WLStub.<init>
(BasicWLContext_WLStub.java:146)
at java.lang.reflect.Constructor.newInstance(Native Method)
at weblogic.common.internal.ClassTableEntry.newInstance
(ClassTableEntry.java:86)
at weblogic.common.internal.WLObjectInputStreamBase.readLeftover
(WLObjectInputStreamBase.java:248)
at weblogic.common.internal.WLObjectInputStreamBase
.readObjectBody (WLObjectInputStreamBase.java:202)
at weblogic.common.internal.WLObjectInputStreamBase.readObject
(WLObjectInputStreamBase.java:949)
at weblogic.common.internal.WLObjectInputStreamBase.readObjectWL
(WLObjectInputStreamBase.java:308)
at weblogic.jndi.toolkit.WLContextStub.readExternal
(WLContextStub.java:79)
at weblogic.common.internal.WLObjectInputStreamBase
.readPublicSerializable(WLObjectInputStreamBase.java:269)
at weblogic.common.internal.WLObjectInputStreamBase.readLeftover
(WLObjectInputStreamBase.java:254)
at weblogic.common.internal.WLObjectInputStreamBase.readObjectBody
(WLObjectInputStreamBase.java:202)
at weblogic.common.internal.WLObjectInputStreamBase.readObject
(WLObjectInputStreamBase.java:949)
at weblogic.common.internal.WLObjectInputStreamBase.readObjectWL
(WLObjectInputStreamBase.java:308)
at weblogic.rmi.extensions.AbstractInputStream2.readObject
(AbstractInputStream2.java:25)
at weblogic.jndi.internal.RemoteContextFactoryImpl_WLStub
.getContext(RemoteContextFactoryImpl_WLStub.java:99)
at weblogic.jndi.WLInitialContextFactoryDelegate
.newRemoteContext(WLInitialContextFactoryDelegate.java:316)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext
(WLInitialContextFactoryDelegate.java:242)
at weblogic.jndi.WLInitialContextFactoryDelegate
.getInitialContext(WLInitialContextFactoryDelegate.java, Compiled
Code)
at weblogic.jndi.WLInitialContextFactoryDelegate
.getInitialContext(WLInitialContextFactoryDelegate.java:148)
at weblogic.jndi.WLInitialContextFactory.getInitialContext
(WLInitialContextFactory.java:123)
at javax.naming.spi.NamingManager.getInitialContext
(NamingManager.java:771)
at javax.naming.InitialContext.getDefaultInitCtx
(InitialContext.java:169)
at javax.naming.InitialContext.<init>(InitialContext.java:146)
getNameInNamespace isn't a method in any of my EJB's (that I wrote, at
least - it could be generated by weblogic.ejbc), and it's not a method
I'm calling directly. Presumably, something in the remote session bean
creation is calling this method (of what class?)
Am still I missing classpath entries in Tomcat? If so, which ones?
If you've successfully referenced EJBs in a WebLogic Server from a
Tomcat servlet, what setup changes did you have to make to Tomcat and
WLS to make it fly?
-- Erik -
Weblogic.ejb20.locks.LockTimedOutException ???
Hi Iam getting a LockTimedOutException while calling a bean method..what could
be the reason and this is permenent..occuring all the time..
Below I have given the stack trace..
what could be the problem??
Thanks
Perianayagam.T
####<Jun 10, 2003 8:59:28 AM EDT> <Info> <EJB> <dssappsrv01> <myServer> <ExecuteThread:
'3' for queue: 'default'> <> <> <010051> <EJB Exception during invocation from
home: com.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_HomeImpl@9c1ee threw exception:
weblogic.ejb20.locks.LockTimedOutException: The lock request from EJB:EnterpriseUser
with primary key:<user dn="hnsuid=hsscsr,ou=people,ou=hub0001,hnscompanyid=dway,ou=business,o=hns.com"/>
timed-out after waiting 60,000 ms. The transaction or thread requesting the lock
was:Name=[EJB com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hns.iag.framework.UserCredential)],Xid=11814:95f36eb4(3191949),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=60,seconds left=0,activeThread=Thread[ExecuteThread: '3' for queue:
'default',5,Thread Group for Queue: 'default'],SCInfo[acapulco+myServer]=(state=active),properties=({weblogic.transaction.name=[EJB
com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hns.iag.framework.UserCredential)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myServer+172.18.2.139:7003+acapulco+,
Resources={})]).>
weblogic.ejb20.locks.LockTimedOutException: The lock request from EJB:EnterpriseUser
with primary key:<user dn="hnsuid=hsscsr,ou=people,ou=hub0001,hnscompanyid=dway,ou=business,o=hns.com"/>
timed-out after waiting 60,000 ms. The transaction or thread requesting the lock
was:Name=[EJB com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hns.iag.framework.UserCredential)],Xid=11814:95f36eb4(3191949),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=60,seconds left=0,activeThread=Thread[ExecuteThread: '3' for queue:
'default',5,Thread Group for Queue: 'default'],SCInfo[acapulco+myServer]=(state=active),properties=({weblogic.transaction.name=[EJB
com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hns.iag.framework.UserCredential)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myServer+172.18.2.139:7003+acapulco+,
Resources={})]).
at weblogic.ejb20.locks.ExclusiveLockManager$LockBucket.lock(ExclusiveLockManager.java:528)
at weblogic.ejb20.locks.ExclusiveLockManager.lock(ExclusiveLockManager.java:258)
at weblogic.ejb20.manager.ExclusiveEntityManager.acquireLock(ExclusiveEntityManager.java:164)
at weblogic.ejb20.manager.ExclusiveEntityManager.getReadyBean(ExclusiveEntityManager.java:219)
at weblogic.ejb20.manager.ExclusiveEntityManager.preInvoke(ExclusiveEntityManager.java:198)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
at weblogic.ejb20.internal.EntityEJBObject.preInvoke(EntityEJBObject.java:89)
at com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean_svris_EOImpl.getRoles(EnterpriseUserBean_svris_EOImpl.java:333)
at com.hns.iag.acapulco.ejb.elm.ELMBean.getEnterpriseUserRoles(ELMBean.java:1392)
at com.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_EOImpl.getEnterpriseUserRoles(ELMBean_1h1i_EOImpl.java:2587)
at com.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)Hi Perianayagam,
This error is fixed in weblogic 6.1SP4 and 7.0 SP3.
Regards,
Slava Imeshev
"Perianayagam.T" <[email protected]> wrote in message
news:[email protected]...
>
Hi Iam getting a LockTimedOutException while calling a bean method..whatcould
be the reason and this is permenent..occuring all the time..
Below I have given the stack trace..
what could be the problem??
Thanks
Perianayagam.T
####<Jun 10, 2003 8:59:28 AM EDT> <Info> <EJB> <dssappsrv01> <myServer><ExecuteThread:
'3' for queue: 'default'> <> <> <010051> <EJB Exception during invocationfrom
home: com.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_HomeImpl@9c1ee threwexception:
weblogic.ejb20.locks.LockTimedOutException: The lock request fromEJB:EnterpriseUser
with primary key:<userdn="hnsuid=hsscsr,ou=people,ou=hub0001,hnscompanyid=dway,ou=business,o=hns.c
om"/>
timed-out after waiting 60,000 ms. The transaction or thread requestingthe lock
was:Name=[EJBcom.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hn
s.iag.framework.UserCredential)],Xid=11814:95f36eb4(3191949),Status=Active,n
umRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=60,seconds left=0,activeThread=Thread[ExecuteThread: '3' for
queue:> 'default',5,Thread Group for Queue:'default',SCInfo[acapulco+myServer]=(state=active),properties=({weblogic.transaction.name=[EJB
>
com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hn
s.iag.framework.UserCredential)]}),OwnerTransactionManager=ServerTM[ServerCo
ordinatorDescriptor=(CoordinatorURL=myServer+172.18.2.139:7003+acapulco+,
Resources={})]).>
weblogic.ejb20.locks.LockTimedOutException: The lock request fromEJB:EnterpriseUser
with primary key:<userdn="hnsuid=hsscsr,ou=people,ou=hub0001,hnscompanyid=dway,ou=business,o=hns.c
om"/>
timed-out after waiting 60,000 ms. The transaction or thread requestingthe lock
was:Name=[EJBcom.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hn
s.iag.framework.UserCredential)],Xid=11814:95f36eb4(3191949),Status=Active,n
umRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=60,seconds left=0,activeThread=Thread[ExecuteThread: '3' for
queue:> 'default',5,Thread Group for Queue:'default',SCInfo[acapulco+myServer]=(state=active),properties=({weblogic.transaction.name=[EJB
>
com.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean.getRoles(com.hn
s.iag.framework.UserCredential)]}),OwnerTransactionManager=ServerTM[ServerCo
ordinatorDescriptor=(CoordinatorURL=myServer+172.18.2.139:7003+acapulco+,
Resources={})]).
atweblogic.ejb20.locks.ExclusiveLockManager$LockBucket.lock(ExclusiveLockManag
er.java:528)
atweblogic.ejb20.locks.ExclusiveLockManager.lock(ExclusiveLockManager.java:258
atweblogic.ejb20.manager.ExclusiveEntityManager.acquireLock(ExclusiveEntityMan
ager.java:164)
atweblogic.ejb20.manager.ExclusiveEntityManager.getReadyBean(ExclusiveEntityMa
nager.java:219)
atweblogic.ejb20.manager.ExclusiveEntityManager.preInvoke(ExclusiveEntityManag
er.java:198)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:124)
atweblogic.ejb20.internal.EntityEJBObject.preInvoke(EntityEJBObject.java:89)
atcom.hns.iag.framework.ejb.user.enterprise.EnterpriseUserBean_svris_EOImpl.ge
tRoles(EnterpriseUserBean_svris_EOImpl.java:333)
atcom.hns.iag.acapulco.ejb.elm.ELMBean.getEnterpriseUserRoles(ELMBean.java:139
2)
atcom.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_EOImpl.getEnterpriseUserRoles(ELMB
ean_1h1i_EOImpl.java:2587)
at com.hns.iag.acapulco.ejb.elm.ELMBean_1h1i_EOImpl_WLSkel.invoke(UnknownSource)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
atweblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
:93)
atweblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120) -
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 -
Dynamic jndi-name in weblogic-ejb-jar.xml
Is there a way to create dynamic (i.e. runtime) jndi-names for EJBs instead of
(or in addition to) "hard coding" them in the weblogic-ejb-jar.xml file? What
I'm trying to do is have one WebLogic instance (JVM) host multiple environments
(our Beta and Training environments) and I simply want to deploy the same .ear
file twice but have each environment (application - .ear) reference a different
database schema (jdbc connection pool). I have everything working just fine for
this scenario except when I define jndi-names for our ejbs. The problem is that
I am really deploying the same ejbs (jndi-names and actually code base) in each
applicatoin instance and I get an exception when the WebLogic is trying to deploy
the second application (.ear) because the jndi-names in it have already been deployed
by the first application instance. I recieve a jndi error stating that the name
is already deployed.
Or is there a better path to go down for what I am trying to do to have one WebLogic
instance support our beta and training environments? Usually (but not always)
our code base is the for same for both of these environments, I simply need to
have each environment use a different database schema.
ThanksA little birdie tells me that BEA does this very thing. Looking at the
descriptors for WebLogic Portal I see:
<weblogic-enterprise-bean>
<ejb-name>LoaderEJB</ejb-name>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>${APPNAME}.BEA_content.LoaderHome</jndi-name>
</weblogic-enterprise-bean>
Yes, the ${APPNAME} token really is expanded into the J2EE application
name at deployment time!
Sincerely,
Daniel Selman
Bryan Dixon wrote:
Rewriting our build process isn't really much of an option for me. Our current
build process is too complex and time consuming right now to convert to Ant (we
eventually will do this but not for a while). So are there any other ideas that
aren't build related?
Thanks
"Eric Ma" <[email protected]> wrote:
You don't need run-time dynamism in JDNI names and it can't be done anyways.
You
need token substitution in XML configuration files when building the
app. If
you are using Ant for building, then it is a breeze. If not, first convert
your
build process to use Ant.
Also, a single WLS instance hosting multiple environments sounds really
INTRIGUING
to me.
Eric Ma
"Bryan Dixon" <[email protected]> wrote:
Is there a way to create dynamic (i.e. runtime) jndi-names for EJBsinstead
of
(or in addition to) "hard coding" them in the weblogic-ejb-jar.xml file?
What
I'm trying to do is have one WebLogic instance (JVM) host multiple environments
(our Beta and Training environments) and I simply want to deploy the
same .ear
file twice but have each environment (application - .ear) referencea
different
database schema (jdbc connection pool). I have everything working just
fine for
this scenario except when I define jndi-names for our ejbs. The problem
is that
I am really deploying the same ejbs (jndi-names and actually code base)
in each
applicatoin instance and I get an exception when the WebLogic is trying
to deploy
the second application (.ear) because the jndi-names in it have already
been deployed
by the first application instance. I recieve a jndi error stating that
the name
is already deployed.
Or is there a better path to go down for what I am trying to do to have
one WebLogic
instance support our beta and training environments? Usually (but not
always)
our code base is the for same for both of these environments, I simply
need to
have each environment use a different database schema.
Thanks -
Many procs results in: weblogic.jdbc.extensions.PoolDisabledSQLException
We have an issue whenever we submit say 100 or more processes at the same time to be started.
The first processes all start and work fine.
But at some point things go wrong.
In the log directory under our SOA project, we find these error messages:
Fault ID service:90091
Fault Time 26-Apr-2011 09:06:20
Non Recoverable System Fault :
Exception [TOPLINK-4002] (Oracle TopLink - 11g Release 1 (11.1.1.4.0) (Build 101210)): oracle.toplink.exceptions.DatabaseException Internal >Exception:
weblogic.jdbc.extensions.PoolDisabledSQLException: weblogic.common.resourcepool.ResourceDisabledException: Pool SOALocalTxDataSource is >Suspended, cannot allocate resources to applications..
Error Code: 0Followed a bit later by this:
Fault ID service:90101
Fault Time 26-Apr-2011 09:06:58
Non Recoverable System Fault :
Exception [TOPLINK-4002] (Oracle TopLink - 11g Release 1 (11.1.1.4.0) (Build 101210)): oracle.toplink.exceptions.DatabaseException >Internal Exception:
weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: >0:weblogic.common.ResourceException: Could not create pool connection.
The DBMS driver exception was: IO-fout: Socket read timed out Error Code: 0 Call:
SQLCall(INSERT INTO COMPOSITE_INSTANCE (ID, COMPOSITE_DN, CONVERSATION_ID, UPDATED_BY, PARENT_ID, CREATED_TIME, TAGS, ECID, INDEX6, TEST_RUN_NAME, INDEX4, TEST_RUN_ID, INDEX2, TEST_SUITE, BUSINESS_STATUS, TEST_CASE, BATCH_ID, SOURCE_NAME, UPDATED_TIME, SOURCE_TYPE, TITLE, SOURCE_ACTION_TYPE, INDEX3, SOURCE_ACTION_NAME, BATCH_INDEX, STATE, CREATED_BY, LIVE_INSTANCES, INDEX1, STATE_COUNT, INDEX5, VERSION, HAS_ASSOC, PARTITION_DATE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?))
Query: InsertObjectQuery([email protected]12d437)We have a feeling that we need to throttle the creation of these processes.
Appreciate any ideas we might try to fix this issue.We have set the 'maximum capacity' of that data source to 500.
When we submit 100 BPEL instances to be started, we see (by monitoring v$session inside the database) that the number of sessions opened by BPEL never goes beyond a few (5 to 10) database sessions.
Yet we still encounter this 'pool is suspended' error:
weblogic.jdbc.extensions.PoolDisabledSQLException: weblogic.common.resourcepool.ResourceDisabledException:
Pool SOALocalTxDataSource is uspended, cannot allocate resources to applications..We can then reset the status of this pool back to running. It then runs for a while, but after 5 - 10 minutes the status flips back to 'suspended' again.
In search of some kind of workaround, we have also set (in composite.xml) the minimumDelayBetweenMessages to 2 seconds, just to ensure that we throttle the creation of our BPEL processes:
<service name="ReceiveFlowEvent" ui:wsdlLocation="ReceiveFlowEvent.wsdl">
<interface.wsdl interface="http://xmlns.oracle.com/pcbpel/adapter/aq/PASSOA/WorkflowDispatcher/ReceiveFlowEvent#wsdl.interface(Dequeue_ptt)"/>
<binding.jca config="ReceiveFlowEvent_aq.jca">
<property name="jca.retry.count">3</property>
<property name="jca.retry.interval">5</property>
<!--property name="jca.retry.interval">20</property-->
<!--property name="jca.retry.backoff">2</property-->
<property name="minimumDelayBetweenMessages">2000</property>
<property name="adapter.aq.dequeue.threads">1</property>
</binding.jca>
</service>
...Any more clues are appreciated.
Edited by: Toon Koppelaars on May 9, 2011 4:45 PM
Maybe you are looking for
-
With the older version I was able to print a playlist of 24 songs that would fit on a case. The print was single-spaced on the older version, but on this version, the print is double spaced and it no longer fits on a case. Does anyone have an answe
-
Chnage background color of a region
Hi, How can we change or add a background color to a region in apex. thanks, tj
-
Setting default volume level for Java Desktop
Hello, I am running Sol 10 11/06 for sparc. How do I permanently set the default volume level for the Java desktop? If I change the volume manually and "save settings" on logoff, the saved setting is not saved after a reboot, after which I have to se
-
How do you connect sequences so that they are smooth
when connecting sequences how do we make it a smooth transition from one sequence to the next??
-
I love Bridge, I use it every day. But it's major weakness for me is the tagging system and filtering by keyword. Right now I'm using Bridge/ACR for my importing, sorting and viewing. But I actually open Windows Live Photo for tagging and filtering b