[jBPM] New message: "Re: jbpm 4.3 - org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update"
by Martin Porter
User development,
A new message was posted in the thread "jbpm 4.3 - org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update":
http://community.jboss.org/message/521622#521622
Author : Martin Porter
Profile : http://community.jboss.org/people/jedizippy
Message:
--------------------------------------------------------------
Hi,
This is basic plain vanilla jBPM 4.3 deployed as an EAR to a single standalone instance of WLS (not clustered). Our jbpm.cfg.xml is just importing the Job Executor so we have not changed any of the threads or lock values so it should be using the default 3 threads according to the docs-
<import resource="jbpm.jobexecutor.cfg.xml"/>
We are running in a JTA enviroment and reading the latest 4.3 docs we should be importing the jta config:-
<import resource="jbpm.tx.jta.cfg.xml"/>
I will try this as currently we have been using the basic hibernate tx config:-
<import resource="jbpm.tx.hibernate.cfg.xml"/>
I am not sure if this would have any bearing on this problem or not. I will look into it further today and see if this has any bearing.
We are running against Oracle 11g so its seems then that its not related to the DB according to Tians post.It would seem as you say the problem lies in the unique ID generation for the execution id.
Regards
Martin
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521622#521622
16 years, 3 months
[jBPM] New message: "Process definition deployment"
by Maarten G
User development,
A new message was posted in the thread "Process definition deployment":
http://community.jboss.org/message/521614#521614
Author : Maarten G
Profile : http://community.jboss.org/people/magoris
Message:
--------------------------------------------------------------
Hi,
I am developing a web app with JSF 1.2, Spring 2.5.6 and jBPM 4.3. I have integrated jBPM with Spring so I can use the jBPM 4.3 services as Spring beans.
I can't get the process definition deployment to work as I want though. When the app starts/restarts I deploy the process definition with the following code, as I want to be sure the process is deployed when the web app is running:
repositoryService.createDeployment().addResourceFromClasspath("process.jpdl.xml").deploy();
which works the first time, but on a following server start/restart i get the following exception:
org.jbpm.api.JbpmException: error: process 'process-1' already exists
I suppose this is because i have version="1" specified in the process definition. When I remove the version it works, but then it deploys a new version to the db every time, which seems illogical to me as it is the same process definition each time. Is this what is supposed to happen, or is there a way to check if a certain process version is already deployed, so it runs the deploy() code only when necessary?
Any help with this would be greatly appreciated, this is the first time I use jBPM in a project.
Greetings,
Maarten
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521614#521614
16 years, 3 months
[Beginner's Corner] New message: "How do I enable pass-by-reference for EJB3 in JBoss AS container?"
by Jerry Simone
User development,
A new message was posted in the thread "How do I enable pass-by-reference for EJB3 in JBoss AS container?":
http://community.jboss.org/message/521600#521600
Author : Jerry Simone
Profile : http://community.jboss.org/people/jlsimone
Message:
--------------------------------------------------------------
I am converting a somewhat large application from EJB2/WebSphere to EJB3/JBoss. In EJB2/WebSphere,I am able to configure the WebSphere container to use pass-by-reference between EJBs that coexist in the same JVM. I would like to do the same with the JBoss AS. I have done some research and saw some documentation that says you can use the <container-invoker-conf> tag in the jboss.xml file to optimize the calls within the container JVM. But I get the feeling that this is old, outdated information. So far, I have not been able to verify this with any information that I have found on the "current" (JBoss AS 5.1) jboss.xml file.
Can some one point me to an article or the documentation that might clarify this for me?
Thanks
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521600#521600
16 years, 3 months
[JBoss Cache] New message: "How do I avoid cluster collisions on the same subnet for cache invalidation?"
by Josh Long
User development,
A new message was posted in the thread "How do I avoid cluster collisions on the same subnet for cache invalidation?":
http://community.jboss.org/message/521581#521581
Author : Josh Long
Profile : http://community.jboss.org/people/starbuxman
Message:
--------------------------------------------------------------
Hello,
I have a setup with JBoss Seam. I'm using JBoss Cache as the backing caching framework for JPA (Hibernate).
I also accquire a reference to the Cache that HIbernate creates when it starts up and get at a few cache configurations of my own for other purposes (ie, theres enitty-cache, query-cache, etc, that are there for Hibernate, and theres another configuratio that I use for my own purposes.)
The effect is thatId ont have to create two cache instances in the same web application.
Now, my problem: jboss cache is clustered. It has a clusterName attribute. If i launch the jboss cache instance in two different environemtns but the same subnet (staging, test, for example) theres teh risk of collision - how do I ensure that thed query-cache from staging doesnt share /replicate/invalidate the query-cache for testing?
I looked at the cluster name attriute for each config in jbc2.xml (we have a custom one that's based on the default one), and that might work as long a I change the cluster names for each build. Id also need to bifurcate the persistence.xml into two separate configurations or do some sort of nasty property filtering so that I can confure stagins query cache as:
hibernate.cache.region.jbc2.cfg.query=staging-query-cache in staging, and hibernate.cache.region.jbc2.cfg.query=test-query-cache in test.
So, what Im asking is:
a) is cluster name the way to ensure two clusters dont trample on each other?
b) is there another way that doesnt leave me creating two diffrent jbc2.xml and persistence.xml files for each environment, or at least reduces it? I noticed that you can interpolae system properties in jbc2.xml - but not in persistence.xml, which means I couldnt just use a system property and cange it per environment in the tocat startup script.
Thanks, any and all insight's appreciated.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521581#521581
16 years, 3 months