[JBoss Messaging] - ClusteredConnectionFactory : Exception trace in starting second node using jboss messaging
by Vijay Rawat
Vijay Rawat [http://community.jboss.org/people/vijayraw] created the discussion
"ClusteredConnectionFactory : Exception trace in starting second node using jboss messaging"
To view the discussion, visit: http://community.jboss.org/message/564227#564227
--------------------------------------------------------------
Hi All,
I am using jboss 4.2.3-GA, jboss-messaging 1.4.0.SP3, jboss-remoting 2.2.2 SP11
I have cluster with 2 nodes. I am using *ClusteredConnectionFactory* with <attribute name="SupportsLoadBalancing">true</attribute>
I am able to start first node without any problems with all queues up. When I start second node , I get exception strace
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2010-09-29 18:45:43,468 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@13306ad started
2010-09-29 18:45:44,468 WARN [org.jboss.jms.server.security.SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
2010-09-29 18:45:45,203 ERROR [org.jboss.messaging.util.ExceptionUtil] SessionEndpoint[71-7v4rjoeg-1-xoeqjoeg-31o2zq-21o4c5] createConsumerDelegate [81-nv4rjoeg-1-xoeqjoeg-31o2zq-21o4c5]
javax.jms.InvalidDestinationException: No such destination: JBossQueue[CalendarMessage] has it been deployed?
at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createConsumerDelegateInternal(ServerSessionEndpoint.java:1838)
at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createConsumerDelegate(ServerSessionEndpoint.java:252)
at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$createConsumerDelegate$aop(SessionAdvised.java:94)
at org.jboss.jms.server.endpoint.advised.SessionAdvised$createConsumerDelegate_8721389917985689973.invokeNext(SessionAdvised$createConsumerDelegate_8721389917985689973.java)
at org.jboss.jms.server.container.SecurityAspect.handleCreateConsumerDelegate(SecurityAspect.java:123)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
at org.jboss.jms.server.endpoint.advised.SessionAdvised$createConsumerDelegate_8721389917985689973.invokeNext(SessionAdvised$createConsumerDelegate_8721389917985689973.java)
at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
at org.jboss.jms.server.endpoint.advised.SessionAdvised$createConsumerDelegate_8721389917985689973.invokeNext(SessionAdvised$createConsumerDelegate_8721389917985689973.java)
at org.jboss.jms.server.endpoint.advised.SessionAdvised.createConsumerDelegate(SessionAdvised.java)
at org.jboss.jms.wireformat.SessionCreateConsumerDelegateRequest.serverInvoke(SessionCreateConsumerDelegateRequest.java:100)
at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:866)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:420)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173)
-----------------------------------------------------------------------------------------------------------
If anyone knows to avoid exception trace.
Please let me know.
Regards,
Vijay Rawat
jboss-messaging 1.4.0.SP3
jboss-remoting 2.2.2 SP11
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/564227#564227]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 6 months
[jBPM] - JBPM 5, WorkItemHandler as a Spring Bean
by Michał Minicki
Michał Minicki [http://community.jboss.org/people/Valgoerad] created the discussion
"JBPM 5, WorkItemHandler as a Spring Bean"
To view the discussion, visit: http://community.jboss.org/message/577346#577346
--------------------------------------------------------------
Hello. Is there a way to register domain specific work item handlers via Spring configuration? There is an example in the manual on how to create such nodes: https://hudson.jboss.org/hudson/job/jBPM5/lastSuccessfulBuild/artifact/ta... https://hudson.jboss.org/hudson/job/jBPM5/lastSuccessfulBuild/artifact/ta...
But I would like to inject EmailService to NotificationWorkItemHandler via Spring instead of doing this call:
EmailService service = ServiceRegistry.getInstance().getEmailService();
In order to do so, I need to register this handler as a Spring bean and iject it via application context. My configuration at the moment is as follows:
<drools:kbase id="knowledgeBase">
<drools:resources>
<drools:resource type="BPMN2" source="classpath:jbpm/churn/PodpowiadaczOfert.bpmn" />
<drools:resource type="BPMN2" source="classpath:jbpm/simple01.bpmn" />
<drools:resource type="BPMN2" source="classpath:jbpm/simple02.bpmn" />
<drools:resource type="BPMN2" source="classpath:jbpm/simple03.bpmn" />
<drools:resource type="BPMN2" source="classpath:jbpm/simple04.jbpmn" />
</drools:resources>
<drools:configuration>
<!--<drools:multithread enabled="true" max-threads="5" /> -->
<!--<drools:consequenceExceptionHandler handler="pl.cyfrowypolsat.workflow.SimpleException" /> -->
</drools:configuration>
</drools:kbase>
<drools:ksession id="jpaSingleSessionCommandService" type="stateful" kbase="knowledgeBase">
<drools:configuration>
<drools:jpa-persistence>
<drools:transaction-manager ref="transactionManager" />
<drools:entity-manager-factory ref="entityManagerFactory" />
</drools:jpa-persistence>
</drools:configuration>
</drools:ksession> <drools:kbase id="knowledgeBase">
<drools:resources>
<drools:resource type="BPMN2" source="classpath:jbpm/churn/PodpowiadaczOfert.bpmn" />
<drools:resource type="BPMN2" source="classpath:jbpm/simple01.bpmn" />
<drools:resource type="BPMN2" source="classpath:jbpm/simple02.bpmn" />
<drools:resource type="BPMN2" source="classpath:jbpm/simple03.bpmn" />
<drools:resource type="BPMN2" source="classpath:jbpm/simple04.jbpmn" />
</drools:resources>
<drools:configuration>
<!--<drools:multithread enabled="true" max-threads="5" /> -->
<!--<drools:consequenceExceptionHandler handler="pl.cyfrowypolsat.workflow.SimpleException" /> -->
</drools:configuration>
</drools:kbase>
<drools:ksession id="jpaSingleSessionCommandService" type="stateful" kbase="knowledgeBase">
<drools:configuration>
<drools:jpa-persistence>
<drools:transaction-manager ref="transactionManager" />
<drools:entity-manager-factory ref="entityManagerFactory" />
</drools:jpa-persistence>
</drools:configuration>
</drools:ksession>
<drools:kbase id="knowledgeBase">
<drools:resources>
<drools:resource type="BPMN2" source="classpath:jbpm/simple01.bpmn" />
</drools:resources>
<drools:configuration>
<drools:multithread enabled="true" max-threads="5" />
</drools:configuration>
</drools:kbase>
<drools:ksession id="jpaSingleSessionCommandService" type="stateful" kbase="knowledgeBase">
<drools:configuration>
<drools:jpa-persistence>
<drools:transaction-manager ref="transactionManager" />
<drools:entity-manager-factory ref="entityManagerFactory" />
</drools:jpa-persistence>
</drools:configuration>
</drools:ksession>
How would I go about registering custom item handlers in the Session's WorkItemManger?
ksession.getWorkItemManager().registerWorkItemHandler("Notification", new NotificationWorkItemHandler());
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/577346#577346]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 6 months
[jBPM] - Re: JBPM5 - Process Versioning
by Michał Minicki
Michał Minicki [http://community.jboss.org/people/Valgoerad] created the discussion
"Re: JBPM5 - Process Versioning"
To view the discussion, visit: http://community.jboss.org/message/577252#577252
--------------------------------------------------------------
I'm not sure if I understand you correctly, Kris. As far as I know, current JBPM 5 implementation allows you to deploy processes from file system alone (yes, I know Guvnor integration is in the works). So, when you overwrite the old bpmn process file with a new version, you basically lose the previous version of the diagram. How the JBPM engine actually manages to "remember" old process definition? I haven't seen anything in the persistent storage (database).
Or is my assumption wrong and you have to deploy a new version of the process in a separate file with a different name (which actually makes the SCM versioning useless)? In that case how does the JBPM know the two are the newer and older version of the same business process? The name correlation is only cosmetic, isn't it? All in all, you start processes with a process id (which needs to be changed, according to your words).
I'm totally new to JBPM, so don't hesitate to send me to Drools or JBPM5 manual section where I can read more on that issue.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/577252#577252]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 6 months
[jBPM] - jBPM 4: Programmatically create Tasks and mapping them to process instance id
by Prachi M
Prachi M [http://community.jboss.org/people/mukh.prac] created the discussion
"jBPM 4: Programmatically create Tasks and mapping them to process instance id"
To view the discussion, visit: http://community.jboss.org/message/577303#577303
--------------------------------------------------------------
Hello Everyone,
I am using jBPM 4.3 and need to create a task using jBPM APIs. The number of tasks are not defined during process deployment, hence every execution of the process should be able to create some number of tasks dynamically.
As given in the developer guide, I am using the below snippet:
Task newTask = taskService.newTask();
newTask.setAssignee("manager");
newTask.setName("Dummy sub task");
taskService.saveTask(newTask);
The task gets created successfully, however in JBPM4_TASK table, the processinstance_id, execution_id etc parameters get saved as null.
I need to map the newly created task with the process instance id so that when I query the tasks for a particular execution id, I get this task listed as well.
Please provide some pointers on how can I avoid the null values getting persisted in the database.
Thanks in advance.
--
Prachi
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/577303#577303]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 6 months