[jBPM] - jBPM 5 in JBoss 5/6 appserver - start and resume
by Brian Wallis
Brian Wallis [http://community.jboss.org/people/bwallis42] created the discussion
"jBPM 5 in JBoss 5/6 appserver - start and resume"
To view the discussion, visit: http://community.jboss.org/message/583477#583477
--------------------------------------------------------------
I'm wondering what the best way to initialise/launch drools flow in an appserver would be. I need to be able to support persistent workflows with transactions so that if I kill the appserver I can restart back to where I was. Long term, cluster failover (which is a similar requirement) would also be required.
I suspect that I should probably use some sort of ejb (stateless session bean or message driven bean) that initialises or resumes the process instances in the ejbCreate() method (since I believe using an ejb can help me support cluster failover as well).
How do you resume a bunch of persisted workflows? They would all either be waiting on an event, the presence of a fact in their session or a return from a call out to a work item (either a domain specific node or a human task).
When you restart, how do you recover the old session objects? Do you create and load a new KnowledgeBase? If the session is persisted I suppose there must be a hibernate query I can make to find all the existing instances. What do I do with them then?
I'm actuallly struggling working out what the right question is :-)
In short, I want to use jBPM in the JBoss appserver and have workflow instances reliably span restarts.
thanks.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/583477#583477]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 5 months
[JBoss Cache] - How to handle an object's expiry in cache
by Prashanth ga
Prashanth ga [http://community.jboss.org/people/gaprashanth] created the discussion
"How to handle an object's expiry in cache"
To view the discussion, visit: http://community.jboss.org/message/583576#583576
--------------------------------------------------------------
We understand from the Jboss Cache userguide that either the object can be made to be available in the persistent store all the time as a superset because of passivation OR available in the persistence store only on using eviction along with class loading, passivation. Also eviction allows us to make the efficient use of memory by configuring timeToLive or maxAge kind of parameters which evict the obejcts and persist to the store while the memory is overloaded.
This means, the object is always available either from the memory or the persistent store. But how does the object permanently removed from the cache ( either memory or store). Do we need to have an additional algorithm to clean up the objects from the persistemt stores on some interval of expiry. Is there a way we can avoid this and just be able to achieve with the configurations of Jboss cache ?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/583576#583576]
Start a new discussion in JBoss Cache at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 5 months
[JBoss Cache] - High availability question on Jboss cache
by Prashanth rao
Prashanth rao [http://community.jboss.org/people/gaprashanth] created the discussion
"High availability question on Jboss cache"
To view the discussion, visit: http://community.jboss.org/message/583573#583573
--------------------------------------------------------------
We are having an all active node cluster where each node can receive requests for reading data and is expected to return identical data all the time. Now there is a requirement to introduce a caching framework which should fit into our architecture without changing the current design.
While we investigate Jboss cache arhictecture, we understand that it provides in-memory cache but also persistense based on some configurations with eviction and class loading. This suits our need of using eviction for the efficient use of memory and persisting only on memory overload. But we are having a requirement on deleting the cached data (permanetly) on its expiry. We may have to impelement a supplementary feature to implement this and this is not the issue.
We are evaluating the different cache loading techniques like shared class loaders, class loaders with each node having its own persistent store etc. But as made clear earlier, we also need to combine eviction along with class loading as we need to make best use of memory. Our concern is selecting the best class loading technique which suits our architecture.
A) If shared class loading is used,
if the object is evicted at different intervals from the different nodes of the cluster, whether the object passivated from node will be overwriiten from the other node ? But if this ok as the objects evicted/passivated are all same across the nodes due to replication ( used with synchronous option)
If one node is restarted, should it load the state from other node because it cant just rely on the persistent store as the other node can be ahead of the persistent store.
B) If we use different persistent stores for each node,
If the objects are evicted at different intervals from the different nodes of the cluster, we can assume that the objects will go into separate persistence stores. But again if a node is restarted, it has to load the entire state from the memory of other node and not its persistence store as the memory always has the actual data if used with eviction ?
If the persistent store one node is down, what happen to the requests on that node. Whether the object is automatically loaded from other nodes and returned back as well as updating the local cache?
Also one more concern is on the concurrent writes to the same object across the cluster. We understand that Jboss cache supports 2 phase commit, where the object is locked for writes on other nodes while it is being done on some node.
Please provide us some inputs at the earliest as it is URGENT.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/583573#583573]
Start a new discussion in JBoss Cache at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 5 months
[JBoss Tools] - JBoss Tools 3.2 CR1 - Killer Of Bugs!
by Max Rydahl Andersen
Max Rydahl Andersen [http://community.jboss.org/people/max.andersen%40jboss.com] modified the blog post:
"JBoss Tools 3.2 CR1 - Killer Of Bugs!"
To view the blog post, visit: http://community.jboss.org/community/tools/blog/2011/01/27/jboss-tools-32...
--------------------------------------------------------------
http://in.relation.to/service/File/10824 http://in.relation.to/service/File/10824
h4. 3.2.0.CR1
[ http://www.jboss.org/tools/download Download] [ http://download.jboss.org/jbosstools/updates/development Update Site] [ http://marketplace.eclipse.org/content/jboss-tools-1 Market Place] [ http://docs.jboss.org/tools/whatsnew What's New] [ http://docs.jboss.org/tools/3.2.0.Beta1/ Documentation] [ http://www.jboss.com/index.html?module=bb&op=viewforum&f=201 Forums] [ http://jira.jboss.com/jira/browse/JBIDE JIRA] [ http://twitter.com/jbosstools Twitter]
> *Note*: For now please use the Update Site or Eclipse Market Place - Sourceforge is having http://sourceforge.net/apps/wordpress/sourceforge/2011/01/27/service-down... issues with their download service.
This release is squashing https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=10020&version=... 400+ issues thus if you use JBoss Tools milestones it is time to upgrade and if you find remaining issues http://community.jboss.org/thread/159819 report them as soon as possible.
http://docs.jboss.org/tools/whatsnew What's New covers the usability fixes there have been added, and a few new additions/improvements.
h2. Top 6 on Eclipse Marketplace
Even though we haven't been on Eclipse Marketplace for long we are already the 6th most downloaded Eclipse plugin within 30 days on Eclipse Marketplace; and in 9th place of all time.
Thank you for the interest and usage - if you don't know Eclipse Marketplace, you can see how to use it http://community.jboss.org/en/tools/blog/2010/10/21/jboss-tools-on-eclips... here.
For those already using it, I encourage you to go and give us your star or even a review at our http://marketplace.eclipse.org/content/jboss-tools-1 Eclipse Market Place page
h2. Automatic Runtime Detection
First of all this release finally enables one of my favorite new features "Automatic Runtime Detection". It's been possible for a while now to use the "Search" button under JBoss Tools to find JBoss runtimes and have them configured and setup in the IDE for direct usage without having to set up all the individual parts.
In this release we have gone a bit further and allowed you to configure a set (one or many) of directories that JBoss Tools will scan on new workspaces or if you enable it at every startup; if anything new is found it will show the new items and you can then say if you want the runtimes to be installed or not.
This means when you install a new version of JBoss AS, Seam, Drools, EAP, SOA-P, etc. you can simply put in this "watched" directory and JBoss Tools will configure them for you in the IDE. In the future we will add more types of runtime distribution detection such as Java JDK's.
This feature is available under Eclipse Preferences in *JBoss Tools > JBoss Tools Runtime Detection*
h2. CDI Improvements
For Context Dependency Injection (CDI) we've added a few quick fixes against some of the more common issues our validator finds.
This allows you to use Ctrl+1 on warnings and fix issues. For example fixing @Produces annotations on non-static methods in a Session Bean by making the method static.
We've also added support for the Maven integration to enable CDI automatically if/when your pom.xml file referenes the CDI api jars. Making it simple to import a Maven based CDI project and have all features enabled.
h2. Feedback
There is more shown in http://docs.jboss.org/tools/whatsnew What's New, take a look, try the release and let us know how it goes! If nothing major is found we'll be releasing the final version within the next couple of weeks.
Have fun!
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/community/tools/blog/2011/01/27/jboss-tools-32...]
13 years, 5 months