[jBPM] - How to use ProcessInstance without accessing db
by honzag
honzag [http://community.jboss.org/people/honzag] created the discussion
"How to use ProcessInstance without accessing db"
To view the discussion, visit: http://community.jboss.org/message/586055#586055
--------------------------------------------------------------
Hi,
I would like to access DB only during the ProcessInstance creation (and in a task node). I have tried to set a "default-lazy" property in all hbm.xml files to "false" but still I end with LazyInitializationException.
There is a code of method which I use to retrieve ProcessInstance. I want to keep this instance in memory between process wait states.
JbpmContext context = JbpmConfiguration.getInstance().createJbpmContext();
try {
ProcessDefinition definition = context.getGraphSession().findLatestProcessDefinition(definitionName);
return definition.createProcessInstance(variables) ;
} finally {
context.close();
}
In process wait state I want to use in memory kept ProcessInstance and call signal method.
If I create definition by parsing xml then this works. But is this approach possible in case of loading from db? I use jbpm 3.2.9.
Thank you in advance for your reply?
Honza
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/586055#586055]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[JBoss Cache] - JBossCache
by Manik Surtani
Manik Surtani [http://community.jboss.org/people/manik.surtani%40jboss.com] modified the document:
"JBossCache"
To view the document, visit: http://community.jboss.org/docs/DOC-10242
--------------------------------------------------------------
> *NOTE:* If you use JBoss Cache, you really should consider migrating to Infinispan (http://ww.infinispan.org), which supercedes JBoss Cache. It does all JBoss Cache does, and much, much more, is more robust, performs better, and has a far more active community.
>
h2. What is JBoss Cache
h5. JBoss Cache consists of two +editions+
* *core* - a replicated, distributed, transactional tree-structured cache
* *pojo* (formerly JBossCacheAop) - a layer on top of the core cache, providing you with an API-less feature set and giving you a more 'pojo' feel to your application with minimal intrusion.
h5. Upcoming editions
* *searchable* - this edition bolts on a search indexer to the cache, allowing you to query the cache using efficient Lucene queries. See the http://community.jboss.org/docs/DOC-10286 JBoss Cache Searchable wiki page for more info.
h2. Versions
The current stable release, recommended for general use, is *JBoss Cache 3.2.2.GA +"Malagueta"+*. Note that this is *not* binary-compatible with *JBoss Cache 1.x* and if you need that level of binary compatibility the recommended version is *JBoss Cache 1.4.1 +"Cayenne"+*. Naga *+is+* compatible with *JBoss Cache 2.x* though.
h2. Learning about JBoss Cache
A http://community.jboss.org/docs/DOC-12843 tutorial and FAQ for both core and pojo editions are provided, along with the http://community.jboss.org/docs/DOC-12843 formal user guide- which should be considered *+required+* reading, +*before*+ asking questions on the users' forum! :)
JBoss Cache can be used either inside JBoss, with a different application server, or as a standalone product.
Here is http://community.jboss.org/docs/DOC-12843 official JBossCache main documentation page. This wiki page will serve for some additional materials.
+Want to help us translate JBoss Cache documentation to a language of your choice? See the http://community.jboss.org/docs/DOC-10261 JBossCacheDocI18n page!+
h2. Troubleshooting
Here is the page for some tips on http://community.jboss.org/docs/DOC-10288 troubleshooting JBoss Cache.
h2. More information
* *Migrating from JBoss Cache 1.x.x to 2.x.x?* Then read http://community.jboss.org/docs/DOC-10246 JBossCache200Migration
* *JBossCache on J2EE servers*:
* JBoss Cache 1.4.x is always available and runs transparently on JBoss AS 4.x.
* JBoss Cache 1.4.x has been tested on J2SE 1.4 and Java SE 5.0. While it +may+ work on Java SE 6, this hasn't been extensively tested.
* JBoss Cache 2.x is always available and runs transparently on the upcoming JBoss AS 5.x.
* JBoss Cache 2.x does not have support for J2SE 1.4 and +requires+ either Java SE 5.0 or Java SE 6, both of which are extensively tested with JBoss Cache 2.x.
* For information on running JBoss Cache 2.x under J2SE 1.4, see this wiki page: http://community.jboss.org/docs/DOC-10263 JBossCacheHabaneroJava1.4
* http://community.jboss.org/docs/DOC-10254 JBossCacheAsCompatibility - a HOWTO for running JBoss Cache 2.x under JBoss AS 4.x safely.
* http://community.jboss.org/docs/DOC-10252 JBossCacheAndWebLogic - for a quick HOWTO on running JBoss Cache under BEA WebLogic 8.1, utilising a startup and shutdown class to initialize the cluster-wide caching service.
* http://community.jboss.org/docs/DOC-10250 JBossCacheAndWAS For a quick overview on how to run JBossCache in WebSphere
* http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheAndWAS_6.x JBossCacheAndWAS_6.x - for a quick HOWTO on running JBoss Cache under WebSphere 6.x series
* *Hibernate integration:* See http://community.jboss.org/docs/DOC-10265 JBossCacheHibernate for information and tips on using JBossCache as a 2nd-level cache in http://www.hibernate.org Hibernate
* *Building JBossCache:* Check out the README files in the src distribution or SVN checkout.
* *MVCC:* With JBoss Cache 3 "+Naga+", we have deprecated *optimistic* and *pessimistic* locking in favour of *MVCC*. Read all about it http://jbosscache.blogspot.com/2008/07/mvcc-has-landed.html here.
* *Buddy Replication:* Have trouble replicating a lot of state to many machines in a cluster (whether using JBoss Cache, or other techs that use JBoss Cache such as http state replication)? Read http://community.jboss.org/docs/DOC-10255 JBossCacheBuddyReplication and http://community.jboss.org/docs/DOC-10256 JBossCacheBuddyReplicationDesign!
* *JDBC-based cache loader:* see http://community.jboss.org/docs/DOC-10864 JDBCCacheLoader for information and tips on how to configure JDBCCacheLoader with various DBMS.
* *Accessing and Monitoring JBoss Cache using JMX*: http://community.jboss.org/docs/DOC-10270 JBossCacheMBeans describes how to access JBoss Cache using its JMX MBeans. With JBoss Cache 1.3.0, this is also possible when running in a standalone (e.g., non-server) JDK 5.0 environment.
* *Clustering patterns library*: http://community.jboss.org/docs/DOC-10294 The clustering patterns library contains configuration strategies for high availability using JBoss Cache.
* *Running JBoss Cache with the JGroups Multiplexer* : See http://community.jboss.org/docs/DOC-10274 JBossCacheMultiplexer
* *Monitoring*: See http://community.jboss.org/docs/DOC-12832 Jopr - JBossCache plugin for monitoring JBoss Cache instances within JBoss AS.
* *Groovy*: Want to use JBoss Cache with Groovy and Grails? See this http://grails.org/JBossCache+Plugin plugin.
h2. Upgrading and Compatibility Information
h3. JBoss Cache developer's page
For *Subversion* information, tags and branches, and tips on developing and debugging JBoss Cache, see https://www.jboss.org/community/docs/DOC-10259 JBossCacheDevelopment.
h3. JBoss Cache & JGroups version compatibility
See http://labs.jboss.com/portal/jbosscache/compatibility/index.html http://labs.jboss.com/portal/jbosscache/compatibility/index.html for details
h3. JBoss Cache & JDK Requirements
|| JBoss Cache Version || JDK Compatibility ||
| 1.2, 1.2.1, 1.2.2, 1.2.3 | J2SE 1.3, J2SE 1.4, JavaSE 5.0 |
| 1.2.4.X | J2SE 1.4, JavaSE 5.0 |
| >= 1.3.0 | Runs with J2SE 1.4 and JavaSE 5.0. Needs JavaSE 5.0 to build. |
| >= 2.0.0 | J2SE 5.0, J2SE 6 |
h1. Other editions
Aside from JBoss Cache - Core Edition, we also ship:
* http://community.jboss.org/docs/DOC-11611 JBoss Cache - POJO Edition
* http://community.jboss.org/docs/DOC-10286 JBoss Cache - Searchable Edition
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-10242]
Create a new document in JBoss Cache at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
15 years, 2 months
[Beginner's Corner] - Re: The warning message stomp out.
by jaikiran pai
jaikiran pai [http://community.jboss.org/people/jaikiran] created the discussion
"Re: The warning message stomp out."
To view the discussion, visit: http://community.jboss.org/message/584529#584529
--------------------------------------------------------------
> Darryl Baker wrote:
>
> Now I'd like to fix some other message the first is this series:
> [ContextConfig] WARNING: Security role name nobody-has-this-role used in an <auth-constraint> without being defined in a <security-role>
> 16:14:43,566 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
> 16:14:43,676 INFO [ContextConfig] WARNING: Security role name nobody-has-this-role used in an <auth-constraint> without being defined in a <security-role>
> 16:14:43,770 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp3718574988013474295jbossws-context-exp.war/
> 16:14:43,879 INFO [ContextConfig] WARNING: Security role name nobody-has-this-role used in an <auth-constraint> without being defined in a <security-role>
> 16:14:44,035 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
> 16:14:44,113 INFO [ContextConfig] WARNING: Security role name nobody-has-this-role used in an <auth-constraint> without being defined in a <security-role>
> 16:14:45,145 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
> 16:14:45,363 INFO [ContextConfig] WARNING: Security role name nobody-has-this-role used in an <auth-constraint> without being defined in a <security-role>
>
> Which I think should be fixable by defining a security role in server/myserver/deploy/jbossweb-tomcat55.sar/conf/web.xml but I don't understand how to do that well enough. I'm also not sure how to debug my attempts.
>
Looks like someone has changed the web.xml files of web-console, jbossmq-httpil.war, ROOT.war and others. What does one of those web.xml look like? You'll have to do the changes to each of those web.xml to fix the WARN message.
> Darryl Baker wrote:
>
> The next error message is:
>
> [STDERR] The developer file [null] does not exist and will not be used.
>
> Obviously we are not using a developer file but what is it? What are the possible values? Where should it be set? Since we are not using it how do I set it to a value that does not break the applications yet has the eqivalent effect as now but without an error message.
This doesn't look like being logged by JBoss AS. It appears to be logged from the application deployed on that server. Do you see this error message on a clean installation, without any of your applications?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/584529#584529]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months