January 2007 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Redelivery caused by System.exit()? urgent!!!!

by timfox

You are in the wrong forum. Please post in the messaging user forum (I already had to move your last message). This is a forum for design discussions View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999485#3999485 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999485

19 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Redelivery caused by System.exit()? urgent!!!!

by longfangq＠hotmail.com

Hi, When our program receives a JMS message which instructs it to shut down, it calls System.exit(0). It works well with another application server. When we try to migrate to JBoss, we found that JMS message will not be consumed, which means the program does receive the message and exit but when it restarts, that JMS message will be redelievered and cause it to exit again and therefor an infinite loop. We use non-transactional messaging and auto acknolowledge: QueueSession qSession = qCon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE); Can anyone kindly help? many thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999479#3999479 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999479

19 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Re: PojoCache uses a special node factory

by manik.surtani＠jboss.com

Just a thought, a hash bucket approach (that I suggested to Hibernate some while back) to reduce contention on a parent node may help here as well. This may be encapsulated into an 'InternalNode' or wired manually in PojoCache code (for now, maybe). The basic idea is that when you need to create /_JBossInternal_/Node1 /_JBossInternal_/Node2 /_JBossInternal_/Node10 /_JBossInternal_/Node11 you actually create: /_JBossInternal_/Bucket0-9/Node1 /_JBossInternal_/Bucket0-9/Node2 /_JBossInternal_/Bucket10-19/Node10 /_JBossInternal_/Bucket10-19/Node11 which will reduce the contention on _JBossInternal_ as a direct parent. Perhaps this is behaviour we could add (in the 3.0 timeframe?) to JBoss Cache's core Node impls, so all user data gets to benefit from this as well? Cheers, Manik View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999478#3999478 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999478

19 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: user based process versioning ?

by tom.baeyens＠jboss.com

we shouldn't rely on enterprise java. the more i think about it, the more i'm convinced that we cannot put the users in charge of versioning. so if we want an auto-deploy directory, full copies of the process archive files will have to be stored for comparison upon next directory scan. This full copy could potentially be stored on the filesystem or in the database. that doesn't really matter. but since jbpm already depends on a db in most deployments, this would be the first thing i implement. david, i don't yet see the point of having a table separation for process definition versions and process definitions. now there is only a process definition version table and the name and version are columns. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999465#3999465 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999465

19 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: direct navigation when starting a new process instance

by david.lloyd＠jboss.com

"tom.baeyens(a)jboss.com" wrote : if there is one or more tasks created assigned to the authenticated user, select an arbitrary one from that list and navigate to that task form. otherwise, navigate to the task list home page. People aren't going to like that, I'm sure. The rule should at least be predictable so that process designers (the people) can have some idea of what will happen. If you're dead-set against a created task list like we have now, what about just always choosing the first task. That will at least be predictable. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999450#3999450 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999450

19 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: simplified process instance view

by tom.baeyens＠jboss.com

I intended that for tasks, variables, tokens, there would only be one line of information. Optionally with a link to a more detailed information page. So as far as i can see we are all in agreement here. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999447#3999447 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999447

19 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: one central search page

by david.lloyd＠jboss.com

Sounds OK... are you sure you want to use "Executions" though? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999445#3999445 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999445

19 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: direct navigation when starting a new process instance

by tom.baeyens＠jboss.com

yes. i agree with ronald. if there is one or more tasks created assigned to the authenticated user, select an arbitrary one from that list and navigate to that task form. otherwise, navigate to the task list home page. i don't think it's necessary to do anything specific for pooled actors. cause after starting a process instance and if there is no task assigned to the authenticated user, the user should navigate to the task list home page. If there are group tasks, he/she'll see them instantly in the group task list (which i think should be on that same page) and the user can instantly perform the 'take' operation on that task. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999444#3999444 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999444

19 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: one central search page

by bazoo

Sounds good to me. One small point - personally I would prefer the menu item to be entitled "Instances" rather than "Executions". The word is slightly less technical and therefore more instantly understandable to the end user. Regarding the two separate search pages. To keep navigation simple, how about having one menu item "Search" then two tabs, one "Tasks" another "Processes"? Regarding starting a new process. To me that is an important operation, and deserves its own place in the main menu structure. Perhaps you would click the "Start process" menu item, which would result in a page listing all the process definitions available to be started. The user would then click a button "Start" next to the one they want. Just an idea. Cheers Matt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999439#3999439 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999439

19 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: new simplified menu structure

by david.lloyd＠jboss.com

"tom.baeyens(a)jboss.com" wrote : Wouldn't this be nicer solved by a checkbox in the search criteria "Show all versions" which by default is unchecked ? The problem isn't the UI. We can do a checkbox, that's no problem. The problem is that the query cannot be made efficient, because it is not possible to know the latest version of a process without reading all rows of the process definition table with that process' name. That's why I recommend that the tables be normalized, with one table for Processes and one for ProcessVersions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999438#3999438 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999438

19 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums January 2007