[jBPM Development] - Re: Issue #JBPM-2537
by jbarrez
"sebastian.s" wrote :
| 1) I don't understand the test case you've supplied. What's the reason for task2 and the second end state? They are not even connected to the start?? At first I thought I had misread the definition and so I copied it into a process definition file to visualize it with the GPD.
|
The test process is just the one that is attached to the issue you mention. So it may not make sense, but I didn't want to change it because I wanted to replicate the issue as the poster intended
"sebastian.s" wrote :
| 2) I did not know you've started to work on this and I tried to resolve this issue with my limited knowledge on my own right now. Within TimerImpl I checked if the activity of the execution was of type task and in case of this was true I retrieved the task-object and called OpenTask.delete().
|
I didn't start working on the issue, I only made a test case to verify if the issue was correct. Which is the case.
"sebastian.s" wrote :
| Afterwards I saw your test case failing since the task was now deleted and not completed but your test case checks if the task is closed/completed when the timer fires.
|
So the test was almost perfect ... almost ;-)
"sebastian.s" wrote :
| Wouldn't it make more sense to delete the task? Completing it does not seem right since it was open and not completed when the timer fired. Especially in from a reporting perspective it does not make sense, does it?
| When you run a report on the gathered process data it seems as if this task was completed by its assignee although it was not.
|
At first, I indeed assumed deleting the task was enough. But now I'm thinking about it: from a history perspective, the task existed for a while. So the task may be deleted (runtime data), but the history should reflect that the task has been open for a while, but a timer interrupted it.
I triggered Tom to take a look at the issue.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263431#4263431
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4263431
16 years, 1 month
[JBoss Messaging Development] - Re: Sending messages from jboss to other application server(
by mnenchev
HI, thanks for the response. Actually the other server will be websphere as i first said. I found some tutorial
on IBM:
http://www.ibm.com/developerworks/websphere/library/techarticles/0710_rit...
and
on JBOSS:
http://209.85.135.132/search?q=cache:KyhQ6p2pV6oJ:www.jboss.org/community...
I am trying the one from ibm and i installed test server and WMQ. After that I deployed the RAR and wmq.jmsra-ds.xml:
<?xml version="1.0" encoding="UTF-8"?>
|
| <connection-factories>
| <!-- connection factory definition -->
| <tx-connection-factory>
|
| <jndi-name>IVTCF</jndi-name>
| <xa-transaction />
| <rar-name>wmq.jmsra.rar</rar-name>
|
| <connection-definition>
| javax.jms.ConnectionFactory
| </connection-definition>
|
| <config-property name="channel" type="java.lang.String">
| SYSTEM.DEF.SVRCONN
| </config-property>
| <config-property name="hostName" type="java.lang.String">
| localhost
| </config-property>
| <config-property name="port" type="java.lang.String">
| 1414
| </config-property>
| <config-property name="queueManager" type="java.lang.String">
| ExampleQM
| </config-property>
| <config-property name="transportType" type="java.lang.String">
| CLIENT
| </config-property>
|
| <security-domain-and-application>JmsXARealm</security-domain-and-application>
| </tx-connection-factory>
|
| <!-- admin object definition -->
| <mbean code="org.jboss.resource.deployment.AdminObject"
| name="jca.wmq:name=ivtqueue">
|
| <attribute name="JNDIName">
| IVTQueue
| </attribute>
| <depends optional-attribute-name="RARName">
| jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'
| </depends>
| <attribute name="Type">javax.jms.Queue</attribute>
|
| <attribute name="Properties">
| baseQueueManagerName=ExampleQM
| baseQueueName=SYSTEM.DEFAULT.LOCAL.QUEUE
| </attribute>
| </mbean>
| </connection-factories>
|
But when i try to run some IVT i get
javax.resource.ResourceException: MQJCA1012:Failed to create a JMS connection factory.
| at com.ibm.mq.connector.services.JCAExceptionBuilder.buildException(JCAExceptionBuilder.java:101)
| at com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl.createConnection(ManagedConnectionFactoryImpl.java:331)
| at com.ibm.mq.connector.outbound.ManagedConnectionImpl.<init>(ManagedConnectionImpl.java:108)
| at com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:144)
| at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:633)
| at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:267)
| at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:622)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)
| at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:381)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)
| at com.ibm.mq.connector.outbound.ConnectionFactoryImpl.createManagedJMSConnection(ConnectionFactoryImpl.java:174)
| at com.ibm.mq.connector.outbound.ConnectionFactoryImpl.createConnectionInternal(ConnectionFactoryImpl.java:133)
| at com.ibm.mq.connector.outbound.ConnectionFactoryImpl.createConnection(ConnectionFactoryImpl.java:118)
| at com.ibm.mq.connector.outbound.ConnectionFactoryImpl.createConnection(ConnectionFactoryImpl.java:103)
| at IVT.doGet(IVT.java:290)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
| at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
| at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
| at org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn.invoke(ClusteredSingleSignOn.java:672)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:619)
| Caused by: javax.jms.JMSException: MQJMS1006: invalid value for channel:
| SYSTEM.DEF.SVRCONN
|
| at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:634)
| at com.ibm.mq.jms.MQConnectionFactory.setChannel(MQConnectionFactory.java:1788)
| at com.ibm.mq.connector.ConnectionFactoryBuilder.createConnectionFactory(ConnectionFactoryBuilder.java:240)
| at com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl.createConnectionFactory(ManagedConnectionFactoryImpl.java:363)
| at com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl.createConnection(ManagedConnectionFactoryImpl.java:327)
| ... 37 more
|
Any ideas what to do next? Seems that this wmq.jmsra-ds.xml does not create this JMS channel(i never used any channels for jms with jboss!). Am i doing something wrong?
Regards.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263426#4263426
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4263426
16 years, 1 month