[jBPM] - jbpm 4.4 + Spring 3: can't deploy a jpdl
by Radu D.
Radu D. [http://community.jboss.org/people/rd210275] created the discussion
"jbpm 4.4 + Spring 3: can't deploy a jpdl"
To view the discussion, visit: http://community.jboss.org/message/607777#607777
--------------------------------------------------------------
I am getting the warning
"60421 [http-8443-1] WARN org.jbpm.pvm.internal.repository.DeployerManager - WARNING: no objects were deployed! Check if you have configured a correct deployer in your jbpm.cfg.xml file for the type of deployment you want to do." And I can't retrieve the process definition anymore.
The code is:
NewDeployment newDeployment = repositoryService.createDeployment();
newDeployment.addResourceFromFile(deploymentFile); // a jpdl.xml file
String id = newDeployment.deploy();
LOG.info("Deployed: '" + id + "'"); // gives the id in DB, somthing like '40001'
ProcessDefinitionQuery pdq = repositoryService.createProcessDefinitionQuery();
List<ProcessDefinition> processDefinitions = pdq.processDefinitionKey(id).list();
for (ProcessDefinition pd : processDefinitions) { // empty collection
LOG.info(pd.getId());
}
Where should I look for?
The jbpm.cfg.xml looks like:
<?xml version="1.0" encoding="UTF-8"?>
<jbpm-configuration xmlns=" http://jbpm.org/xsd/cfg http://jbpm.org/xsd/cfg">
<import resource="jbpm.jpdl.cfg.xml" />
<import resource="jbpm.identity.cfg.xml" />
<import resource="jbpm.jobexecutor.cfg.xml" />
<process-engine-context>
<repository-service />
<repository-cache />
<execution-service />
<history-service />
<management-service />
<identity-service />
<task-service />
<command-service name="newTxRequiredCommandService">
<retry-interceptor />
<environment-interceptor policy="requiresNew" />
<spring-transaction-interceptor />
</command-service>
<command-service name="txRequiredCommandService">
<retry-interceptor />
<environment-interceptor />
<spring-transaction-interceptor />
</command-service>
<object class="org.jbpm.pvm.internal.id.DatabaseDbidGenerator">
<field name="commandService">
<ref object="txRequiredCommandService" />
</field>
</object>
<object class="org.jbpm.pvm.internal.id.DatabaseIdComposer" init="eager">
</object>
<deployer-manager>
<jpdl-deployer />
</deployer-manager>
<!-- Added spring as read-context -->
<script-manager default-expression-language="juel" default-script-language="juel"
read-contexts="execution, environment, process-engine, spring" write-context="">
<script-language name="juel" factory="org.jbpm.pvm.internal.script.JuelScriptEngineFactory" />
</script-manager>
<authentication />
<id-generator />
<types resource="jbpm.variable.types.xml" />
<address-resolver />
</process-engine-context>
<transaction-context>
<repository-session />
<db-session />
<message-session />
<timer-session />
<history-session />
<transaction type="spring" />
<!-- Need to set explicitly that we don't want jbpm to create sessions -->
<hibernate-session current="true" close="false" />
</transaction-context>
</jbpm-configuration>
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/607777#607777]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[jBPM] - Timer Exception
by biett0
biett0 [http://community.jboss.org/people/biett0] created the discussion
"Timer Exception"
To view the discussion, visit: http://community.jboss.org/message/608127#608127
--------------------------------------------------------------
Hi there! I'm using jBPM 4.4 and I created a process that invoke a sub-process activity at startup. The sub-process contains a timer activity and raises the following exception when the timer is fired:
16:21:15,874 ERROR [AbstractFlushingEventListener] Could not synchronize database state with session
org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.pvm.internal.job.TimerImpl#34]
at org.hibernate.persister.entity.AbstractEntityPersister.check(AbstractEntityPersister.java:1792)
at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2435)
at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2335)
at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2635)
at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:115)
at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:263)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:168)
at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:321)
at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:50)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1027)
at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:365)
at org.hibernate.transaction.CacheSynchronization.beforeCompletion(CacheSynchronization.java:88)
at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:101)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:269)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:89)
at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177)
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1423)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:137)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:162)
at org.jbpm.pvm.internal.tx.JtaTransaction.commit(JtaTransaction.java:92)
at org.jbpm.pvm.internal.tx.JtaTransactionInterceptor.executeInNewTx(JtaTransactionInterceptor.java:85)
at org.jbpm.pvm.internal.tx.JtaTransactionInterceptor.execute(JtaTransactionInterceptor.java:62)
at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:56)
at org.jbpm.pvm.internal.tx.JtaRetryInterceptor.executeWithRetry(JtaRetryInterceptor.java:52)
at org.jbpm.pvm.internal.tx.JtaRetryInterceptor.execute(JtaRetryInterceptor.java:45)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.executeInNewEnvironment(EnvironmentInterceptor.java:53)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:40)
at org.jbpm.pvm.internal.svc.SkipInterceptor.execute(SkipInterceptor.java:43)
at org.jbpm.pvm.internal.jobexecutor.DispatcherThread.acquireJobs(DispatcherThread.java:126)
at org.jbpm.pvm.internal.jobexecutor.DispatcherThread.run(DispatcherThread.java:67)
Any idea?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/608127#608127]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[Beginner's Corner] - Client timeout JBoss AS 6
by Urs Rothenhäusler
Urs Rothenhäusler [http://community.jboss.org/people/braca] created the discussion
"Client timeout JBoss AS 6"
To view the discussion, visit: http://community.jboss.org/message/608081#608081
--------------------------------------------------------------
Hello,
my client program is getting a timeout when invoking a method (with a long lasting process) of a Stafeful Session Bean (SFSB) /EJB3.1. The client program is a just a simple java program "starting" the SFSB-process on a JBoss AS6, lasting about 40 minutes. What's a good solution to avoid this exception?
java.lang.reflect.UndeclaredThrowableException
at $Proxy8.doCheck(Unknown Source)
at org.client.aa.EDIControlProcessor.doCheck(EdiProcess.java:124)
at org.client.aa.EDIControlProcessor.processSingle(EDIControlProcessor.java:28)
at org.client.aa.EDIControlClient.main(EDIControlClient.java:12)
Caused by: org.jboss.remoting.InvocationFailureException: Socket timed out. Waited 300000 milliseconds for response while calling on InvokerLocator [socket://127.0.0.1:3873/?timeout=300000]; nested exception is:
java.net.SocketTimeoutException: Read timed out
at org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:137)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.handleOtherException(MicroSocketClientInvoker.java:1079)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:941)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:167)
at org.jboss.remoting.Client.invoke(Client.java:1961)
at org.jboss.remoting.Client.invoke(Client.java:804)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.security.client.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
...
Thanks for an answer
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/608081#608081]
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
[JBoss Web Services] - Endpoint does not contain operation meta data for Exception
by Gabriele Pezzini
Gabriele Pezzini [http://community.jboss.org/people/gptex] created the discussion
"Endpoint does not contain operation meta data for Exception"
To view the discussion, visit: http://community.jboss.org/message/608066#608066
--------------------------------------------------------------
Hi all,
I have deployed a web services in JBoss 4.2.3 GA jdk6, and I run JBoss using Jdk 6
I have generated the artifatcs using wsconsume and I have build a client to invoke my service.
If I invoke the service from a wm outside jboss, all goes well: my service is invoke and performs its job,
that means that wsdl, mapping and so on are fine.
But I need also to invoke the same service inside a JBoss's thread that polls on db and invokes the service.
To do so I have put the same artifact and the ws client in a jar located in .../WEB-INF/lib folder., and my thread
invokes for the client.
When ws is invoked I have the "Endpoint does not contain operation meta data for Exception" in JBoss log.
After some works around it, I have see that I use the same client outside JBoss, I have two scenarios:
1) If I run my vm without nothing in classpath the services (JBoss side) is invoked and performs its job
2) If I run my vm within the same classpath setted by wsconsume (that uses some JBoss's jars) I have the same exception
that I have running the client inside a JBoss's thread.
So I Imagine that are there some jars issue, so I have installed a clean JBoss 4.2.3 GA jdk6, within only my web service to test;
but nothing change: within the JBoss's jars in classpath (the one setted by wsconsume) I have always the exception and without
the jars all works fine.
So:
Are there some config to do to solve my problem?
Is there a way to call my service inside a JBoss's thread (that obviously has the JBoss's jar in class path)?
Thank you very much
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/608066#608066]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months