[jBPM] - jBPM persistent session ids
by Jason Jho
Jason Jho [https://community.jboss.org/people/jasonjho] created the discussion
"jBPM persistent session ids"
To view the discussion, visit: https://community.jboss.org/message/730695#730695
--------------------------------------------------------------
I am using jBPM 5.2.0 and I have a question about ksession ids. My understanding is that this session ID is used to reload a persisted session, but there is no clear indication how this is supposed to work when a server is restarted. For example, if I have a session ID [1] for a workflow process that is persisted and the server goes down, I can reload the session back to it's previous state using this same ID. However, how am I guaranteed that any new session ID created by the same knowledge base will be uniquely different from the persisted ID?
Ex:
int id = ksession.getId() ...
startProcess(...)
// server shuts down - restarts
int savedId = geSavedId();
session = JPAKnowledgeService.+loadStatefulKnowledgeSession+(savedId, kbase, *null*, env);
newSession = kbase.newStatelessKnowledgeSession(...)
newSession.getId() = ???
In the above scenario, could it be possible for newSession.getId() to have the same integer value as the previously saved ID?
If so, how would one be able to distinguish the 2 different sessions?
Thanks for any help.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/730695#730695]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 4 months
[JBoss Remoting] - Re: WorkerThread exception occured .... InvocationTargetException / SocketTimeoutException
by Ron Sigal
Ron Sigal [https://community.jboss.org/people/ron_sigal] created the discussion
"Re: WorkerThread exception occured .... InvocationTargetException / SocketTimeoutException"
To view the discussion, visit: https://community.jboss.org/message/724880#724880
--------------------------------------------------------------
Hi Werner,
re: "For example with netstat I can see, that *2437* is a used port. I am wondering that I could recognize that this port is used by my testprogram istself"
It really wouldn't do any good. When you make a call on an EJB, it filters down to Remoting, which, if it can't find a pooled connection to reuse, will create a new socket, leading to ServerSocket.accept() returning a socket on the server.
It seems like something is preventing the client from completing the initialization of the connection, but I can't imagine what it is. You could use Wireshark to monitor what bytes, if any, get sent from the client to the server.
-Ron
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/724880#724880]
Start a new discussion in JBoss Remoting at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 4 months