[JBoss jBPM] - token is locked
by Pebbels
Hi guys,
I would like to compare a user entered date with the business calender if the entered value is a holiday. Depending if it is a holiday the node is supposed to be left on the regarding transition but it always throws an exception that the token is locked. Can somebody please help me?
xhtml-form:
<task-node name="Termincheck">
| <task name="Termincheck_Task">
| <assignment pooled-actors="leasingnehmer"></assignment>
| <controller></controller>
| </task>
| <event type="node-leave">
| <action name="Termin = Feiertag?" class="fahrzeug.actionHandler.TerminPruefen"></action>
| </event>
| <transition to="Terminvorschlag" name="Termin annehmen bzw ablehnen"></transition>
| <transition to="Pruefung Kontaktdaten" name="Kontaktdaten pruefen"></transition>
| <transition to="Termincheck" name="Datum aendern"></transition>
| </task-node>
action handler:
ProcessInstance processIns = executionContext.getProcessInstance();
| Token token = processIns.getRootToken();
| token.signal("Datum aendern");
Thanks, Tina
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150685#4150685
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150685
18 years, 2 months
Delivery Status Notification (Failure)
by postmaster＠lists.jboss.org
This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed.
3dtreilly(a)iplocks.com
18 years, 2 months
[JBoss jBPM] - Accessing remote Jbpm processes
by mike.jackson
Hi,
I'm experimenting with jboss-esb-server-4.3.CR1.
I want to be able to deploy and access Jbpm processes outside of my application context in order to try and separate business processes (the BA's domain) from the application (the developer's domain).
I had presumed that this would be possible given the existence of the JBPM web console but cannot work out how to access the JbpmConfiguration of the process host.
I noticed that the JbpmService MBean provided is essentially a stub, so I tried to bind the current JbpmConfiguration instance to JNDI by modifying the mbean implementation. However, despite JbpmConfiguration being marked as serializable I get a NotSerializableException on java.lang.ThreadLocal when I try to bind the configuration.
So I guess what I really want to ask is:
a) Is it possible to separate the process and application domains like I am trying to do?
b) If so, how should I go about it?
or
c) If not, what is the point of deploying anything using the JBPM Web Console?
Many thanks for any help,
Mike
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150664#4150664
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150664
18 years, 2 months
[JBoss jBPM] - Out Of Memory problem
by luiseterc
Hi,
I've been using my workflow process without problems so far but did some modifications to execute a node (which calls a bash script) in a loop until some conditions are asserted. The main source code of the node's ActionHandler class is this:
| Iterator<String> it = (Iterator<String>)sitesList.iterator();
|
| LogRedirectThread lgError = null;
| LogRedirectThread lgOutput = null;
|
| while(it.hasNext()) {
| String newSite = (String)it.next();
|
| Process proc = rt.exec(pathToCrawl + " " + newSite + " " + pathToData + "/crawl-data/" + topic + " " + (String)contextInstance.getVariable("path") + " " + typeOfSources +" " + depth );
|
| lgError = new LogRedirectThread(proc.getErrorStream(),pathToData + "/logs/" + topic + "/crawler_sites_stderr_cycle" + cycleID + ".log");
| lgOutput = new LogRedirectThread(proc.getInputStream(),pathToData + "/logs/" + topic + "/crawler_sites_stdout_cycle" + cycleID + ".log");
|
| lgError.start();
| lgOutput.start();
|
| int exitVal = proc.waitFor();
|
| sitesList.remove(newSite);
|
| if (exitVal != 0) {
| throw new CrawlerException(newSite);
|
| }
|
| }
|
that is, just call the script through the Runtime.exec() interface and creates two threads to read the stdout and stderr standard outputs.
The problem is that I'm getting a heap OutOfMemory error when the node is executed more than 5 times (btw, my JAVA_OPTS is -Xmx1500m so that should be ok). My question are:
How do jBPM and particularly the ActionHandler's invoker manage memory? and
Do I need to release manually the resources created inside the ActionHandler::execute method, in my case the threads?
Other useful information: some objects are also injected In my ActionHandler class from Spring framework. The OutOfMemory exception is thrown when, in a new cycle, the class is trying to get those beans from the spring context.
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150661#4150661
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150661
18 years, 2 months
Delivery Final Failure Notice
by postmaster＠lists.jboss.org
Can not deliver the message you sent. Will not retry.
Sender: <jboss-user(a)lists.jboss.org>
The following addresses had delivery problems
<www.recipes@tasteofhome.com> Reply from titanium.reimanpub.com[161.230.232.17]: 550 5.1.1 User unknown
18 years, 2 months
[EJB/JBoss] - Repeatedly Connecting to port 3873 in swing client
by Masterozz666
Hi,
i modifid my log4j settings for test reasons using debug at the root logger on client side. After starting my client swing application, which performs a lookup for a service (session bean in JBoss), i registered following: There are made connections/disconnections repeatedly.
The log output of my swing application looks like this (repeatedly infinte without doing any actions in my application):
| <snippet>
| [DEBUG] [14.05.2008 11:08:44] [ClientSocketWrapper] : reset timeout: 0
| [DEBUG] [14.05.2008 11:08:44] [InvokerRegistry] : removed SocketClientInvoker[883c86, socket://192.168.2.40:3873] from registry
| [DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[883c86, socket://192.168.2.40:3873] disconnecting ...
| [DEBUG] [14.05.2008 11:08:44] [SocketWrapper] : ClientSocketWrapper[Socket[addr=/192.168.2.40,port=3873,localport=1371].6822b0] closing
| [DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[bd7d21, socket://192.168.2.40:3873] constructed
| [DEBUG] [14.05.2008 11:08:44] [MicroRemoteClientInvoker] : SocketClientInvoker[bd7d21, socket://192.168.2.40:3873] connecting
| [DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[bd7d21, socket://192.168.2.40:3873] added new pool ([]) as ServerAddress[192.168.2.40:3873, NO enableTcpNoDelay timeout 0 ms]
| [DEBUG] [14.05.2008 11:08:44] [MicroRemoteClientInvoker] : SocketClientInvoker[bd7d21, socket://192.168.2.40:3873] connected
| [DEBUG] [14.05.2008 11:08:44] [ClientSocketWrapper] : reset timeout: 0
| [DEBUG] [14.05.2008 11:08:44] [InvokerRegistry] : removed SocketClientInvoker[bd7d21, socket://192.168.2.40:3873] from registry
| [DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[bd7d21, socket://192.168.2.40:3873] disconnecting ...
| [DEBUG] [14.05.2008 11:08:44] [SocketWrapper] : ClientSocketWrapper[Socket[addr=/192.168.2.40,port=3873,localport=1372].10a7910] closing
| [DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[923822, socket://192.168.2.40:3873] constructed
| [DEBUG] [14.05.2008 11:08:44] [MicroRemoteClientInvoker] : SocketClientInvoker[923822, socket://192.168.2.40:3873] connecting
| [DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[923822, socket://192.168.2.40:3873] added new pool ([]) as ServerAddress[192.168.2.40:3873, NO enableTcpNoDelay timeout 0 ms]
| [DEBUG] [14.05.2008 11:08:44] [MicroRemoteClientInvoker] : SocketClientInvoker[923822, socket://192.168.2.40:3873] connected
| [DEBUG] [14.05.2008 11:08:44] [ClientSocketWrapper] : reset timeout: 0
| [DEBUG] [14.05.2008 11:08:44] [InvokerRegistry] : removed SocketClientInvoker[923822, socket://192.168.2.40:3873] from registry
| [DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[923822, socket://192.168.2.40:3873] disconnecting ...
| [DEBUG] [14.05.2008 11:08:44] [SocketWrapper] : ClientSocketWrapper[Socket[addr=/192.168.2.40,port=3873,localport=1373].1f374e5] closing
| [DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[7f906b, socket://192.168.2.40:3873] constructed
| [DEBUG] [14.05.2008 11:08:44] [MicroRemoteClientInvoker] : SocketClientInvoker[7f906b, socket://192.168.2.40:3873] connecting
| [DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[7f906b, socket://192.168.2.40:3873] added new pool ([]) as ServerAddress[192.168.2.40:3873, NO enableTcpNoDelay timeout 0 ms]
| [DEBUG] [14.05.2008 11:08:44] [MicroRemoteClientInvoker] : SocketClientInvoker[7f906b, socket://192.168.2.40:3873] connected
| [DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[7f906b, socket://192.168.2.40:3873] got Exception java.net.BindException: Address already in use: connect, creation attempt took 15 ms
| [DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[7f906b, socket://192.168.2.40:3873] got Exception java.net.BindException: Address already in use: connect, creation attempt took 0 ms
| [DEBUG] [14.05.2008 11:08:44] [ClientSocketWrapper] : reset timeout: 0
| [DEBUG] [14.05.2008 11:08:44] [InvokerRegistry] : removed SocketClientInvoker[7f906b, socket://192.168.2.40:3873] from registry
| </snippet>
|
Is this normal. Why does the client connect to port 3873?
Thanks in advance, Markus
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150658#4150658
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150658
18 years, 2 months
