[Jboss Portal] Lock timeout
by devone
Hi everyone,
I have a JEMS installation of Jboss portal, in a cluster with 2 members, in
the last period some nodes of the cluster logs an error due to a lock
timeout.
Is this a configuration problem? Is a known bug?
I think that some portlet spends a lot of time to elaborate data or to load
a content from jackrabbit, until a timeout occurs.
Jboss AS 4.0.5
Jbos portal 2.4
This is the error:
15:20:50,262 ERROR [ContentGetCommand] Cannot get content
java.lang.RuntimeException: org.jboss.cache.lock.TimeoutException: failure
acquiring lock: fqn=/wsp_node/0b6f4296-7cc2-4461-bdf8-a72a42a4475c,
caller=GlobalTransaction:<null>:883, lock=write
owner=GlobalTransaction:<null>:879 (activeReaders=0,
activeWriter=Thread[http-192.168.120.12-8080-9,5,jboss], waitingReaders=0,
waitingWriters=0, waitingUpgrader=0)
at
org.jboss.portal.cms.hibernate.state.JBossCachePersistenceManager.exists(JBo
ssCachePersistenceManager.java:435)
at
org.apache.jackrabbit.core.state.SharedItemStateManager.hasNonVirtualItemSta
te(SharedItemStateManager.java:811)
at
org.apache.jackrabbit.core.state.SharedItemStateManager.hasItemState(SharedI
temStateManager.java:244)
at
org.apache.jackrabbit.core.state.LocalItemStateManager.hasItemState(LocalIte
mStateManager.java:171)
at
org.apache.jackrabbit.core.state.XAItemStateManager.hasItemState(XAItemState
Manager.java:261)
at
org.apache.jackrabbit.core.state.SessionItemStateManager.getItemState(Sessio
nItemStateManager.java:126)
at
org.apache.jackrabbit.core.ItemManager.createItemInstance(ItemManager.java:4
62)
at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:320)
at org.apache.jackrabbit.core.PropertyImpl.getNode(PropertyImpl.java:655)
at
org.apache.jackrabbit.core.NodeImpl.getVersionHistory(NodeImpl.java:3091)
at
org.jboss.portal.cms.impl.jcr.command.ContentGetCommand.execute(ContentGetCo
mmand.java:107)
at
org.jboss.portal.cms.impl.jcr.JCRCommandContext.execute(JCRCommandContext.ja
va:63)
at
org.jboss.portal.cms.impl.jcr.command.FileGetCommand.execute(FileGetCommand.
java:112)
at org.jboss.portal.cms.impl.jcr.JCRCommand.dispatch(JCRCommand.java:62)
at org.jboss.portal.cms.impl.jcr.JCRCMS.execute(JCRCMS.java:457)
at org.jboss.portal.cms.impl.jcr.ha.HAJCRCMS.execute(HAJCRCMS.java:169)
at sun.reflect.GeneratedMethodAccessor829.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java
:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java
:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOpe
rationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:26
4)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
org.jboss.mx.util.JMXInvocationHandler.invoke(JMXInvocationHandler.java:287)
at $Proxy1009.execute(Unknown Source)
at
com.ecommy.portlets.CMSView.CMSAbstractViewPortlet.doView(CMSAbstractViewPor
tlet.java:167)
at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:133)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:306)
at
org.jboss.portal.portlet.container.PortletContainer.invokeRender(PortletCont
ainer.java:518)
Caused by: org.jboss.cache.lock.TimeoutException: failure acquiring lock:
fqn=/wsp_node/0b6f4296-7cc2-4461-bdf8-a72a42a4475c,
caller=GlobalTransaction:<null>:883, lock=write
owner=GlobalTransaction:<null>:879 (activeReaders=0,
activeWriter=Thread[http-192.168.120.12-8080-9,5,jboss], waitingReaders=0,
waitingWriters=0, waitingUpgrader=0)
at org.jboss.cache.Node.acquire(Node.java:500)
at
org.jboss.cache.interceptors.PessimisticLockInterceptor.acquireNodeLock(Pess
imisticLockInterceptor.java:379)
at
org.jboss.cache.interceptors.PessimisticLockInterceptor.lock(PessimisticLock
Interceptor.java:307)
at
org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLo
ckInterceptor.java:181)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at
org.jboss.cache.interceptors.CacheLoaderInterceptor.invoke(CacheLoaderInterc
eptor.java:212)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at
org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java
:32)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at
org.jboss.cache.interceptors.CacheStoreInterceptor.invoke(CacheStoreIntercep
tor.java:135)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at
org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.j
ava:365)
at
org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:160)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at
org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtIntercepto
r.java:138)
at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5863)
at org.jboss.cache.TreeCache.get(TreeCache.java:3627)
at org.jboss.cache.TreeCache.get(TreeCache.java:3608)
at org.jboss.cache.TreeCache.get(TreeCache.java:3595)
at sun.reflect.GeneratedMethodAccessor798.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java
:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:26
4)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy138.get(Unknown Source)
at
org.jboss.portal.cms.hibernate.state.JBossCachePersistenceManager.exists(JBo
ssCachePersistenceManager.java:403)
at
org.apache.jackrabbit.core.state.SharedItemStateManager.hasNonVirtualItemSta
te(SharedItemStateManager.java:811)
at
org.apache.jackrabbit.core.state.SharedItemStateManager.hasItemState(SharedI
temStateManager.java:244)
at
org.apache.jackrabbit.core.state.LocalItemStateManager.hasItemState(LocalIte
mStateManager.java:171)
at
org.apache.jackrabbit.core.state.XAItemStateManager.hasItemState(XAItemState
Manager.java:261)
at
org.apache.jackrabbit.core.state.SessionItemStateManager.getItemState(Sessio
nItemStateManager.java:126)
at
org.apache.jackrabbit.core.ItemManager.createItemInstance(ItemManager.java:4
62)
at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:320)
Caused by: org.jboss.cache.lock.TimeoutException: read lock for
/wsp_node/0b6f4296-7cc2-4461-bdf8-a72a42a4475c could not be acquired by
GlobalTransaction:<null>:883 after 15000 ms. Locks: Read lock owners: []
Write lock owner: GlobalTransaction:<null>:879
, lock info: write owner=GlobalTransaction:<null>:879 (activeReaders=0,
activeWriter=Thread[http-192.168.120.12-8080-9,5,jboss], waitingReaders=0,
waitingWriters=0, waitingUpgrader=0)
_______________________________________________
jboss-user mailing list
jboss-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
16 years, 4 months
[JNDI and Naming] New message: "EJB3 jndi lookup failed on JBOSS EAP only due to ProxyFactory not bound"
by Kevin Yuan
User development,
A new message was posted in the thread "EJB3 jndi lookup failed on JBOSS EAP only due to ProxyFactory not bound":
http://community.jboss.org/message/531485#531485
Author : Kevin Yuan
Profile : http://community.jboss.org/people/kevin.yuan
Message:
--------------------------------------------------------------
Hi,
My tests don't have problem with JBOSS 5.1.0 GA community version, it only happens on ENTERPRISE APPLICATION PLATFORM, tests failed during ejb3 sessionbean JNDI lookup, see message below:
<error message="Could not dereference object" type="javax.naming.NamingException">javax.naming.NamingException: Could not dereference object [Root exception is java.lang.RuntimeException: Exception while trying to locate proxy factory in JNDI, at key ProxyFactory/eclipselink-advanced-field-access-model/TestRunner/TestRunner]
at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1504)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:822)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at org.eclipse.persistence.testing.framework.junit.JUnitTestCase.runBareClient(JUnitTestCase.java:480)
at org.eclipse.persistence.testing.framework.junit.JUnitTestCase.runBare(JUnitTestCase.java:455)
Caused by: java.lang.RuntimeException: Exception while trying to locate proxy factory in JNDI, at key ProxyFactory/eclipselink-advanced-field-access-model/TestRunner/TestRunner
at org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getProxyFactoryFromJNDI(ProxyObjectFactory.java:235)
at org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance(ProxyObjectFactory.java:153)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1479)
at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1496)
Caused by: javax.naming.NameNotFoundException: ProxyFactory not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
at org.jnp.server.NamingServer.lookup(NamingServer.java:396)
at org.jnp.server.NamingServer.lookup(NamingServer.java:399)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getProxyFactoryFromJNDI(ProxyObjectFactory.java:226)
</error>
So does anyone know what's the real problem? Is there any special configuration for EAP version?
Thanks.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/531485#531485
16 years, 4 months
[JBoss Tools] New message: "Re: Tutorial for BPEL simple-invoke"
by Peter Johnson
User development,
A new message was posted in the thread "Tutorial for BPEL simple-invoke":
http://community.jboss.org/message/531481#531481
Author : Peter Johnson
Profile : http://community.jboss.org/people/peterj
Message:
--------------------------------------------------------------
Success! Yesterday I spent several hours, armed with the simple-invoke example, the JBoss Tools BPEL User's Guide and the mistakes that I make on an earlier attempt, and I successfully used the GUI editor to create a BPEL that invokes a web service. I took copious notes and screen shots (12 pages with 17 screen shots). My notes do not include any of the steps already documented in the User's Guide.
Here is a very high-level overview of the steps:
1) Create a project following chapter 3 in the User's Guide (but ignore the steps related to the Assign task at the start of section 3.2)
2) Copy the WSDL for the external web service into the project.
3) Add a *partner link type* with a role to the external WSDL
4) Add a *partner link* to the BPEL using the *partner link type* created in the prior step, and select the partner role
5) Add 2 variables to the BPEL - one for the external web parameters and the other for the return value
6) Add two Assign tasks to the BPEL work flow. In the first copy the BPEL input value(s) to the variable for the external web service parameters, and in the second do the same for the return value.
7) Add an Invoke task to the BPEL workflow (between the 2 Assigns added in the prior step), configure it to invoke the external web service and hook up the input and output variables
8) Follow the steps in the User's Guide, chapter 4, to add the PDE deployment descriptor to the project. But also identify the external web service partner link in the outbound interfaces
Now you can deploy the BPEL project (chapter 4 of the User's Guide) and test it using SoapUI.
The really interesting parts are steps 3 and 4. If you do step 4 without first doing step three you end up with problems that cannot be fixed by the GUI - you will need to edit the files in text. In fact, there are many situations where if you mess up the error cannot be corrected in the GUI.
Step 6 was also a challenge. Determining which of the various matches, on the Choose Type of Variable dilaog box, to select when copying the variable values was not obvious.
Step 3 required some manual editing of the WSDL file - the namespace for the partnerlinktype that was provided in the extenstion dialog was for xmlsoap not for wsbpel. I did not take the time to figure out how to get the wsbpel dded to the list. So I edited
Part of step 4 required that you edit the BPEL file via text - the "Initialize Role" check box, which you need to check, is greyed out. Nothing I did resulted in that check box being enabled. Even with editing the file by hand, the box remained greyed out and unchecked.
In step 2 I obtained the WSDL by going to http://localhost:8080/jbossws, following the link to the page of WSDLs, clicking on the WSDL link, and then asking the browser to save the result in a file. The file was missing the xml version line:
<?xml version="1.0" encoding="utf-8" ?>
Without this line, I got a "missing content-type" error when I deployed the BPEL.
Feng, now you know why I stated that your steps were too simplistic. And I will go even further than that - my steps, while complete, leave out a lot of details and it is some of those details that will mess you up. The GUI provides no help whatsoever with filling in the details - it pretty much expects that you already know what information is important and what is not. I suspect that anyone very familiar with BPEL will avoid the GUI and edit the text by hand. But anyone who is not intimately familiar with BPEL will soundly curse the GUI for not providing any clue as to how to appoach common tasks, such as invoking an external web service.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/531481#531481
16 years, 4 months
[Beginner's Corner] New message: "MySQL 5.1 with JBoss ESB 5.0.0"
by Tony Bryan
User development,
A new message was posted in the thread "MySQL 5.1 with JBoss ESB 5.0.0":
http://community.jboss.org/message/531478#531478
Author : Tony Bryan
Profile : http://community.jboss.org/people/fatllama
Message:
--------------------------------------------------------------
Hi, hope someone can help. I'm pretty new to building environments, so have posted this in Beginner's corner to avoid annoying people who know what they're doing!
I have successfully installed JBoss SOA Platform 5.0.0 on a Fedra platform, and verified that the server is up and running.
I have also successfully installed MySQL 5.1 and verified that this is working.
I would now like to configure JBoss SOA Platofrm to use MySQL as a datasource, but am finding it extremely difficult to work out how to do this. The best lead I have so far is:
http://soaengine.wordpress.com/2009/09/16/switch-jbossas-4-2-3-and-jbosse...
... but I can't seem to get anywhere with this.
Can someone outline the steps required to configure JBoss ESB 5.0.0 to use MySQL 5.1?
And yes, I've read the manuals but I'm afraid they didn't make much sense to me (and for the record I HAVE achieved a similar feat for the JBoss Portal server by following manuals!).
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/531478#531478
16 years, 4 months