[JBoss Messaging] - Re: where can I config the timeout of jboss clustering, very urgent, waiting online
by Bond Chan
Bond Chan [https://community.jboss.org/people/bondchan921] created the discussion
"Re: where can I config the timeout of jboss clustering, very urgent, waiting online"
To view the discussion, visit: https://community.jboss.org/message/742915#742915
--------------------------------------------------------------
Thanks,
found it, and it's 3 minutes in our cases.
2 another questions
Q1: As I found this FD timeout have been configure to 'Jgroup', 'Postoffice's DataChannel, Postoffice's ControlChannel',each of the timeout will cause node drop? and should be the shortest timeout will be the trigger in the majority of the cases?
--Cache timeout
Q2.1: Jboss TreeCache have been configure FD timeout too, is this the real timeout or is the value of parameter SyncReplTimeout ? I think is the former one according to your last reply
Q2.2: in the following cache log clip, it seems node lost in the JGroup, cause the node lost in the CacheView, my question is the CacheView maintainance combined by the answer of Q2.1 and the JGroupView ?
(1099 is JNDI port, 7930 is replication cache port, 7920 is invalidation cache port, 7910 is the ControlChannel port, 7900 is the DataChannel port 7800 is JGroup port)
2012-06-14 03:28:01,049 New cluster view for partition PRODPartition_HA: 12 ([10.164.107.69:1099, 10.164.218.18:1099, 10.164.107.65:1099] delta: -1)
2012-06-14 03:28:01,091 viewAccepted(): [10.164.107.69:7930|12] [10.164.107.69:7930, 10.164.218.18:7930, 10.164.107.65:7930]
2012-06-14 03:28:01,057 I am (10.164.107.65:1099) received membershipChanged event:
2012-06-14 03:28:02,047 Dead members: 1 ([10.164.218.14:1099])
2012-06-14 03:28:02,161 New Members : 0 ([])
2012-06-14 03:28:02,161 All Members : 3 ([10.164.107.69:1099, 10.164.218.18:1099, 10.164.107.65:1099])
2012-06-14 03:28:02,161 Suspected member: 10.164.218.14:7800
2012-06-14 03:28:02,293 viewAccepted(): [10.164.107.69:7920|12] [10.164.107.69:7920, 10.164.218.18:7920, 10.164.107.65:7920
Bond
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/742915#742915]
Start a new discussion in JBoss Messaging at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 3 months
[jBPM] - Re: JBPM Timers behaviour
by Bira Neto
Bira Neto [https://community.jboss.org/people/biraneto] created the discussion
"Re: JBPM Timers behaviour"
To view the discussion, visit: https://community.jboss.org/message/742862#742862
--------------------------------------------------------------
Adding some more info on the subject. It appears the problem happens with persistence enabled only. Is this a bug? Should I code something else when using persistence for timers to work properly?
I'm using version 5.3.
The workflow is an start event with timer event definition with a cycle of 1 second... going to a script system out hello world and then to an end event.
Executing with *JPA*.... loading ksession with JPAKnowledgeService.loadStatefulKnowledgeSession( sessionId, kbase, null, env ).startProcess("testTimer");
The execution is shown below
163745 [http-8080-1] WARN bitronix.tm.twopc.Preparer - executing transaction with 0 enlisted resource
Hibernate: select nextval ('hibernate_sequence')
Hello World
Hibernate: select processins0_.InstanceId as col_0_0_ from ProcessInstanceInfo processins0_ inner join EventTypes eventtypes1_ on processins0_.InstanceId=eventtypes1_.InstanceId where eventtypes1_.eventTypes=?
Hibernate: update SessionInfo set lastModificationDate=?, rulesByteArray=?, startDate=?, OPTLOCK=? where id=? and OPTLOCK=?
Hibernate: insert into ProcessInstanceInfo (id, lastModificationDate, lastReadDate, processId, processInstanceByteArray, startDate, state, OPTLOCK, InstanceId) values (?, ?, ?, ?, ?, ?, ?, ?, ?)
Hibernate: delete from ProcessInstanceInfo where InstanceId=? and OPTLOCK=?
Executing with a *simple stateful* session... Loading ksession with *kbase.newStatefulKnowledgeSession().startProcess("testTimer");*
Hello World
Hello World
Hello World
Hello World
Hello World
Hello World
Hello World
Hello World
Hello World
Hello World
Hello World
*(forever untill I cancel execution)
*
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/742862#742862]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 3 months