July 2011 - jboss-user - Jboss List Archives

by bpmtest

bpmtest [http://community.jboss.org/people/bpmtest] created the discussion "Could not find process with id" To view the discussion, visit: http://community.jboss.org/message/598007#598007 -------------------------------------------------------------- Hi gurus, Following Kris's article about testing I was trying the debug process instance view. It worked fine with the evaluation sample but when debugging a simple process based on the hellow world sample, i get 'Could not find process with id' when double clicking on the instance in the 'Process Instances' view. Has anyone else run into this error? Thanks Tim -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/598007#598007] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 6 months

3
2
0 / 0

[Performance Tuning] - Re: Memory leak on org.jboss.classloader.spi.base.BaseClassLoader

by Felix Friedrich

Felix Friedrich [http://community.jboss.org/people/felix-friedrich] created the discussion "Re: Memory leak on org.jboss.classloader.spi.base.BaseClassLoader" To view the discussion, visit: http://community.jboss.org/message/572219#572219 -------------------------------------------------------------- Is there any way to invoke the Java garbage collection via command line (and not from within the application itself)? Thanks... Felix -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/572219#572219] Start a new discussion in Performance Tuning at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 6 months

4
3
0 / 0

[JBoss Tools] - Crazy Behavior After Adding a Dependency

by Rob Williams

Rob Williams [http://community.jboss.org/people/robwms63] created the discussion "Crazy Behavior After Adding a Dependency" To view the discussion, visit: http://community.jboss.org/message/616869#616869 -------------------------------------------------------------- This may not be a JBoss Tools problem at all, may be an m2Eclipse problem, but I figured I would post here since I did see JBoss Tools errors several times. Basically, when I add the 1.9.1 version of Amazon's aws java api as a dependency in my project, the environment goes totally nuts. It rambles along for a long time trying to build then fails saying it was unable to read the Artifact Descriptor of the guava project (a transitive dependency of aws). When I comment out the dependency in the pom, it builds fine. (Version info in tags.) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/616869#616869] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 6 months

3
9
0 / 0

[jBPM] - Variable Persistence Strategies in jBPM

by Harjot Narula

Harjot Narula [http://community.jboss.org/people/harjotnarula09] created the discussion "Variable Persistence Strategies in jBPM" To view the discussion, visit: http://community.jboss.org/message/605742#605742 -------------------------------------------------------------- I saw the different variable persistence strategies provided by drools in 5.1.1 ( http://planet.jboss.org/post/drools_flow_variable_persistence_strategies http://planet.jboss.org/post/drools_flow_variable_persistence_strategies). I dont find those classes anywhere when I downloaded the jBPM5.0.0 installer which comes with drools-persistence-jpa-5.2.0.M1.jar. The classes I am looking for are JPAPersistedVariable.class VariableInstanceInfo.class These used to be bundled in drools-persistence-jpa-5.1.1.jar. Does anyone know if I need some other jar file to get these classes? Also if you have an example of working variable persistence, please send me a link to it. Regards Harjot Narula -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/605742#605742] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 6 months

4
4
0 / 0

[JNDI and Naming] - Re: EJB 3.1 Global JNDI names

by jaikiran pai

jaikiran pai [http://community.jboss.org/people/jaikiran] created the discussion "Re: EJB 3.1 Global JNDI names" To view the discussion, visit: http://community.jboss.org/message/580587#580587 -------------------------------------------------------------- Looks like you are doing the lookup from the remote standalone application. There's a known issue with that http://lists.jboss.org/pipermail/jboss-development/2010-November/016685.html http://lists.jboss.org/pipermail/jboss-development/2010-November/016685.html -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/580587#580587] Start a new discussion in JNDI and Naming at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 6 months

6
10
0 / 0

[jBPM] - Jbpm 5 user form variables

by Nelson Pereira

Nelson Pereira [http://community.jboss.org/people/npereira] created the discussion "Jbpm 5 user form variables" To view the discussion, visit: http://community.jboss.org/message/573833#573833 -------------------------------------------------------------- Hi forum, I've investigation JBPM5, but I'm stuck with a variable problem. The problem is basically with accessing the variable in the user task form. I have a user task with an ftl, I'm using the "Parameter Mapping" but I'm not able to access the variable in the form. (I have attached the bpmn and the ftl files to the Discussion.) The interesting part is that thru the "Result Mapping" I'm able to change the process variable that is comming out od the form user task. Hope you can help. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/573833#573833] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 6 months

9
22
0 / 0

[jBPM] - jBPM Console and Execution History

by Cristiano Nicolai

Cristiano Nicolai [http://community.jboss.org/people/cristiano.nicolai] created the discussion "jBPM Console and Execution History" To view the discussion, visit: http://community.jboss.org/message/586813#586813 -------------------------------------------------------------- Hi all, I'm having the following excetion when I try to acces Execution History: [ERROR] No subscribers for: JBPM_HISTORY_SERVICE<br/>Additional details:<br/>Attempt to send message to subject for which there are no subscribers I also noticed that is a problem that happend in earlier releases: http://community.jboss.org/thread/152989?tstart=0 http://community.jboss.org/thread/152989?tstart=0 https://issues.jboss.org/browse/BPMC-68 https://issues.jboss.org/browse/BPMC-68 I'm wondering if there is some workaround or if it was fixed and the error returned. Environment: jBPM5-Final JbossAS 5.1 Thanks in advance! -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/586813#586813] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 6 months

3
2
0 / 0

[JBoss Messaging] - Get frozen sending a message

by Alexey Kamenchuk

Alexey Kamenchuk [http://community.jboss.org/people/kamenchuk] created the discussion "Get frozen sending a message" To view the discussion, visit: http://community.jboss.org/message/617961#617961 -------------------------------------------------------------- Hi Trying to send a message, the call JBossConnectionFactory.createTopicConnection() gets stuck and never returns. Threads dump shows that the thread infinitely waits for the MicroSocketClientInvoker.readVersion() to complete. Please find the full strack traces of the relevant threads below Looking at the MicroSocketClientInvoker.transport() line 895 it seems like there is no way to specify a timeout Do I incorrectly use the API? Or have misconfigured JBoss? Or is it a bug in Messaging/Remoting? Versions I use: jboss 5.1.0 GA jboss-messaging-1.4.6 jboss-remoting-2_5_4_SP2 Thanks Alexey Thread: WorkerThread#24[192.168.21.4:50313] : priority:5, demon:false, threadId:9437, threadState:BLOCKED - waiting on <0x57910c73> (a org.jboss.jms.server.connectionmanager.SimpleConnectionManager) org.jboss.jms.server.connectionmanager.SimpleConnectionManager.registerConnection(SimpleConnectionManager.java:104) org.jboss.jms.server.endpoint.ServerConnectionEndpoint.(ServerConnectionEndpoint.java:196) org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:273) org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:171) org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:108) org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java) org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:91) org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:157) org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:967) org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) org.jboss.remoting.Client.invoke(Client.java:2070) org.jboss.remoting.Client.invoke(Client.java:879) org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:178) org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeTarget(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:80) org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect_z_handleCreateConnectionDelegate_40792359.invoke(StateCreationAspect_z_handleCreateConnectionDelegate_40792359.java) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java) org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205) org.jboss.jms.client.JBossConnectionFactory.createTopicConnection(JBossConnectionFactory.java:115) org.jboss.jms.client.JBossConnectionFactory.createTopicConnection(JBossConnectionFactory.java:109) net.uk.topdog.td2.common.dao.server.objectchanges.JmsConnectionHelperBean.trySendJmsMessage(JmsConnectionHelperBean.java:126) net.uk.topdog.td2.common.dao.server.objectchanges.JmsConnectionHelperBean.publishJmsMessage(JmsConnectionHelperBean.java:80) -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Thread: Timer-7 : priority:5, demon:true, threadId:247, threadState:BLOCKED - waiting on <0x5854bbf> (a org.jboss.messaging.core.impl.MessagingQueue$DistributorWrapper) org.jboss.messaging.core.impl.MessagingQueue$DistributorWrapper.remove(MessagingQueue.java:621) org.jboss.jms.server.endpoint.ServerConsumerEndpoint.localClose(ServerConsumerEndpoint.java:524) org.jboss.jms.server.endpoint.ServerSessionEndpoint.localClose(ServerSessionEndpoint.java:1159) org.jboss.jms.server.endpoint.ServerConnectionEndpoint.close(ServerConnectionEndpoint.java:395) - locked <0x633e29b0> (a org.jboss.jms.server.endpoint.ServerConnectionEndpoint) org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$close$aop(ConnectionAdvised.java:63) org.jboss.jms.server.endpoint.advised.ConnectionAdvised$close_N4742752445160157748.invokeTarget(ConnectionAdvised$close_N4742752445160157748.java) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.jms.server.endpoint.advised.ConnectionAdvised.close(ConnectionAdvised.java) org.jboss.jms.server.connectionmanager.SimpleConnectionManager.cleanupForSessionID(SimpleConnectionManager.java:488) org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleClientFailure(SimpleConnectionManager.java:201) - locked <0x57910c73> (a org.jboss.jms.server.connectionmanager.SimpleConnectionManager) org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$close$aop(ConnectionAdvised.java:63) org.jboss.jms.server.endpoint.advised.ConnectionAdvised$close_N4742752445160157748.invokeTarget(ConnectionAdvised$close_N4742752445160157748.java) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.jms.server.endpoint.advised.ConnectionAdvised.close(ConnectionAdvised.java) org.jboss.jms.server.connectionmanager.SimpleConnectionManager.cleanupForSessionID(SimpleConnectionManager.java:488) org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleClientFailure(SimpleConnectionManager.java:201) - locked <0x57910c73> (a org.jboss.jms.server.connectionmanager.SimpleConnectionManager) org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleConnectionException(SimpleConnectionManager.java:241) org.jboss.remoting.ConnectionNotifier.connectionLost(ConnectionNotifier.java:60) org.jboss.remoting.Lease.notifyClientLost(Lease.java:342) org.jboss.remoting.Lease.access$600(Lease.java:41) org.jboss.remoting.Lease$LeaseTimerTask.run(Lease.java:413) java.util.TimerThread.mainLoop(Timer.java:512) java.util.TimerThread.run(Timer.java:462) -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Thread: WorkerThread#4[192.168.1.73:46363] : priority:5, demon:false, threadId:275, threadState:BLOCKED - waiting on <0x58b17978> (a org.jboss.messaging.core.impl.clusterconnection.MessageSucker) org.jboss.messaging.core.impl.clusterconnection.MessageSucker.setConsuming(MessageSucker.java:288) org.jboss.messaging.core.impl.MessagingQueue.informSuckers(MessagingQueue.java:566) org.jboss.messaging.core.impl.MessagingQueue.access$200(MessagingQueue.java:67) org.jboss.messaging.core.impl.MessagingQueue$DistributorWrapper.remove(MessagingQueue.java:641) - locked <0x5854bbf> (a org.jboss.messaging.core.impl.MessagingQueue$DistributorWrapper) org.jboss.jms.server.endpoint.ServerConsumerEndpoint.localClose(ServerConsumerEndpoint.java:524) org.jboss.jms.server.endpoint.ServerConsumerEndpoint.close(ServerConsumerEndpoint.java:388) org.jboss.jms.server.endpoint.advised.ConsumerAdvised.org$jboss$jms$server$endpoint$advised$ConsumerAdvised$close$aop(ConsumerAdvised.java:59) org.jboss.jms.server.endpoint.advised.ConsumerAdvised$close_N4742752445160157748.invokeTarget(ConsumerAdvised$close_N4742752445160157748.java) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.jms.server.endpoint.advised.ConsumerAdvised.close(ConsumerAdvised.java) org.jboss.jms.wireformat.CloseRequest.serverInvoke(CloseRequest.java:66) org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:157) org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:967) org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:791) - locked <0x3d2ac700> (a org.jboss.remoting.transport.socket.ServerThread) org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:744) org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:586) org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234) -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Thread: Thread-3350 : priority:5, demon:true, threadId:16865, threadState:RUNNABLE java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:129) java.io.BufferedInputStream.fill(BufferedInputStream.java:218) java.io.BufferedInputStream.read(BufferedInputStream.java:237) - locked <0x30830003> (a java.io.BufferedInputStream) java.io.FilterInputStream.read(FilterInputStream.java:66) org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1342) org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:895) org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:470) org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:169) org.jboss.remoting.Client.invoke(Client.java:2070) org.jboss.remoting.Client.invoke(Client.java:879) org.jboss.remoting.Client.invoke(Client.java:867) org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189) org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160) org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$close$aop(ClientConsumerDelegate.java:122) org.jboss.jms.client.delegate.ClientConsumerDelegate$close_N4742752445160157748.invokeTarget(ClientConsumerDelegate$close_N4742752445160157748.java) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92) org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.jms.client.delegate.ClientConsumerDelegate.close(ClientConsumerDelegate.java) org.jboss.messaging.core.impl.clusterconnection.MessageSucker.suspend(MessageSucker.java:225) - locked <0x58b17978> (a org.jboss.messaging.core.impl.clusterconnection.MessageSucker) org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager$ConnectionInfo.cleanupConnection(ClusterConnectionManager.java:804) - locked <0x77da9e35> (a org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager$ConnectionInfo) org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager$ConnectionInfo.onException(ClusterConnectionManager.java:785) org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:120) org.jboss.remoting.ConnectionValidator$3.run(ConnectionValidator.java:524) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/617961#617961] Start a new discussion in JBoss Messaging at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 6 months

2
3
0 / 0

[jBPM] - Custom Work Item Editor for eclipse

by Amin MC

Amin MC [http://community.jboss.org/people/aminmc] created the discussion "Custom Work Item Editor for eclipse" To view the discussion, visit: http://community.jboss.org/message/613335#613335 -------------------------------------------------------------- Hi I would like to create a custom editor similar to SampleCustomEditor/EmailCustomEditor for my domain specific node. Can someone point me to what are the maven dependencies? I couldn't see any maven dependencies where EmailCustomEditor is located. I presume there is some special set up? Any help would be appreciated. Cheers -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/613335#613335] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 6 months

4
5
0 / 0

[JBoss Web Services] - Rest Service deployment issue on JBossWS-CXF-3.4.0 and JBoss 5.1

by Kyle Bober

Kyle Bober [http://community.jboss.org/people/kyle.bober] created the discussion "Rest Service deployment issue on JBossWS-CXF-3.4.0 and JBoss 5.1" To view the discussion, visit: http://community.jboss.org/message/611037#611037 -------------------------------------------------------------- We have a war that contains some Rest Services using Apache CXF. When we try to deploy the wat to JBoss 5.1 using JBossWS-CFX-3.4.0 and using Spring 3.0.5 we run into the following deployment error: Unexpected exception parsing XML document from class path resource [spring/DocumentQueryRestContext.xml]; nested exception is org.springframework.beans.FatalBeanException: Class [org.apache.cxf.jaxrs.spring.NamespaceHandler] for namespace [ http://cxf.apache.org/jaxrs http://cxf.apache.org/jaxrs] does not implement the [org.springframework.beans.factory.xml.NamespaceHandler] interface I have noticed a similar thread related to this here (although this is related to JBoss 6 ): http://mail-archives.apache.org/mod_mbox//cxf-users/201104.mbox/%3CBANLkT... http://mail-archives.apache.org/mod_mbox//cxf-users/201104.mbox/%3CBANLkT... I have a feeling this might be a classloader issue of some sort related to an offending JAR. Does anyone have any thoughts??? I am loosing my mind trying to resolve this issue. Thanks, kyle -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/611037#611037] Start a new discussion in JBoss Web Services at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 6 months

3
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user July 2011