[JBoss JIRA] Created: (JBESB-1313) There is no way to say, what edge to take, when asynchrously executed esb service fails (service action throws an exception)
by Pavel Kadlec (JIRA)
There is no way to say, what edge to take, when asynchrously executed esb service fails (service action throws an exception)
----------------------------------------------------------------------------------------------------------------------------
Key: JBESB-1313
URL: http://jira.jboss.com/jira/browse/JBESB-1313
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Process flow
Affects Versions: 4.2.1
Reporter: Pavel Kadlec
Imagine process graph.... I would like to have two edges going from the service node. One edge would mean that the work was done (service did its work correctly, without problems). The other edge would mean, that service action processing pipeline did not finish its work correctly (some action threw ActionProcessingPipeline exception). Can I model this behaviour?
If I take a look at EsbActionHandler.java, it seems to me, that jBPM can not be notified, when esb service throws exception, because message field "FaultTo" is never set. If I call esb service asynchronously, jBPM waits for signalCommand with name of the edge to take. But if esb service fails, esb service does not call signalCommand. ActionProcessingPipeline is terminated, I do not have opportunity to send signalCommand with the name of the fault edge...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 12 months
[JBoss JIRA] Created: (JBESB-659) 2 JBossAS instances cannot share the same JBossMQ service for JMS gateways if JMS is installed
by James Williams (JIRA)
2 JBossAS instances cannot share the same JBossMQ service for JMS gateways if JMS is installed
----------------------------------------------------------------------------------------------
Key: JBESB-659
URL: http://jira.jboss.com/jira/browse/JBESB-659
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: JBossAS 4.2GA, JBossESB - Head as of 07/05.2007.
Reporter: James Williams
Assigned To: Mark Little
I am trying to get 2 JBossAS instances to share the same JMS Server for gateways. There's a lot of moving parts, but I'll try to explain the configurations:
1. JBossAS 4.2.0-GA default config with all .ESB archives, minus the quickstart_helloworld.esb. This server is started using the "-b localhost -c node0" startup parameters.
2. JBossAS 4.2.0-GA default config with "jbossesb.sar" and "quickstart_helloworld.esb". All other .ESB archives are removed and my goal is to use the JMS service in server #1 for gateways/listeners. The quickstart_helloworld.esb archive in this server has its own gateway/listener queues. This server is started using the "-b 192.168.200.1 -c node1" startup parameters.
3. JBossAS 4.2-GA default config with "jbossesb.sar" and "quickstart_helloworld.esb". All other .ESB archives are removed and my goal is to use the JMS service in server #1 for gateways/listeners. The quickstart_helloworld.esb archive in this server has its own gateway/listener queues that are different from the gateways/listeners in #2. This server is started using the "-b 192.168.200.2 -c node2" startup parameters.
I'm not having any problems with nodes #2 and #3 sharing the JMS service that's running on #1, so long as JBossMQ isn't installed on node #2 or #3. If JMS is installed, quickstart_helloworld.esb archive fails to deploy on both #2 or #3. It complains that the Gateway queue does not exist, but it most certainly does. Worse yet, when I run the SendJMSMessage test class, it cannot find the queue either. It's as if jbossesb.sar is somehow screwing up all jndi lookups for the queue.
There are a couple things I've done to try to rule out other potential root causes:
1. I tried running #1, #2, #3 w/out any .ESB archives or jbossesb.sar to verify that a JMS client can indeed drop requests into queues on all servers. To me, this validates that 3 unclustered JBossAS instances can each have their own JMS queues that are all accessible on a single machine, like my test environment, just by having the app servers bootstrapped by unique config and ip address. I was worried that the JMS service might be the culprit, but that doesn't appear to be the case.
2. I removed JMS from #2 and #3 to verify that the queues are setup correctly on #1 and to verify that #2 and #3 can indeed share the same JMS service provided they do not have JMS running themselves.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 12 months
[JBoss JIRA] Created: (JBESB-1531) Sometimes the message delivery fails for the first time
by Jiri Pechanec (JIRA)
Sometimes the message delivery fails for the first time
-------------------------------------------------------
Key: JBESB-1531
URL: http://jira.jboss.com/jira/browse/JBESB-1531
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Adapters, Rosetta
Affects Versions: 4.2.1
Environment: standalone-soa-4.2.0.CR2.zip
Reporter: Jiri Pechanec
Assigned To: Mark Little
Attachments: server.log.gz
Sometimes it happens that message is sent to GW but it goes to RDLQ because of unresponsive EPR.
On the second attempt whel delivery is tried from RDLQ then it succeds. The log says
2008-02-05 11:17:58,037 DEBUG [org.jboss.soa.esb.client.ServiceInvoker] Badly formed EPR [JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_jca_bpm_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : XAConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ]] for Service [FirstServiceESB:SimpleListener] and Message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_jca_bpm_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : XAConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: ID:JBM-37377 ]]. java.lang.NullPointerException
Why there is NullPointerException thrown in the courrier first time bu not on redelivery?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBESB-807) JBossRemotingGateway doesn't support Http BASIC Auth (and probably more)
by Tom Fennelly (JIRA)
JBossRemotingGateway doesn't support Http BASIC Auth (and probably more)
------------------------------------------------------------------------
Key: JBESB-807
URL: http://jira.jboss.com/jira/browse/JBESB-807
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.2 Milestone Release 3
Reporter: Tom Fennelly
Assigned To: Tom Fennelly
Fix For: 4.2.1
Talked with Ron Sigal and he thinks we might have to explicitly use the Servlet transport (i.e. the CoyoteInvoker might not be configurable for BASIC auth).
Here's what Ron said exactly.....
"1. HTTPServerInvoker is obsolete. It's been replaced by CoyoteInvoker.
2. According to my O'Reilly Tomcat book, BASIC authorization is configured in the web.xml file by the <login-config> element. But CoyoteInvoker doesn't use the full Tomcat implementation, just the Coyote adapter. I'm really not sure if the Coyote adapter has anything to do with the web.xml file.
3. There is another Remoting transport, the servlet transport, which really does use Tomcat. It uses a servlet as a front end to the server invoker. There's even a web.xml file: src\etc\web\web.xml in the Remoting project directory."
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBESB-476) Make action, listener etc configuration setting by setter method the default
by Tom Fennelly (JIRA)
Make action, listener etc configuration setting by setter method the default
----------------------------------------------------------------------------
Key: JBESB-476
URL: http://jira.jboss.com/jira/browse/JBESB-476
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Mark Little
Fix For: 4.2
We currently configure everything by constructor. This is not great for a number of reasons:
1. It can't be compile time validated.
2. Not as "obvious" to someone developing against the API. If in an interface, their IDE (or at least compiler - if using a stone ax) will complain immediately that they're not implementing the interface correctly.
3. Makes our code a little bit more complicated re the reflection code that needs to be implemented.
So I suggest making the interface (that all these things implement) contain a setter method that takes the config. The mandate on the implementation is that they contain a public default constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBESB-2602) Exception Handling jBPM -> JBossESB does not work
by Jiri Pechanec (JIRA)
Exception Handling jBPM -> JBossESB does not work
-------------------------------------------------
Key: JBESB-2602
URL: https://jira.jboss.org/jira/browse/JBESB-2602
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Process flow, Rosetta
Affects Versions: 4.2.1 CP4, 4.2.1 CP5
Environment: embedded SOA 4.2 CP04 CR2
Reporter: Jiri Pechanec
Priority: Critical
See an attached example based on bpm_orchestration2. In one of the groovy scripts service7.groovy an exception is thrown. Thne associated jBPM node there is an exception transition defined <exceptionTransition>exception</exceptionTransition> and this point to another node that invokes exception handle ESB service. In 4.3 this functionality works flawlessly but in 4.2 CP4 the exception transition is ignored and the process flow goes to the next node. Compare the debug output of the logs
In case of 4.3
11:38:29,448 INFO [STDOUT] ** Begin Receive Order - Service 1 **
11:38:29,448 INFO [STDOUT] In: Getting Started
11:38:29,448 INFO [STDOUT] Out: Getting Started 'Receive Order'
11:38:29,449 INFO [STDOUT] ** End Receive Order - Service 1 **
11:38:29,651 INFO [STDOUT] ** Begin Credit Check - Service 3 **
11:38:29,651 INFO [STDOUT] In: Getting Started 'Receive Order'
11:38:29,652 INFO [STDOUT] Out: Getting Started 'Receive Order' 'Credit Check'
11:38:29,652 INFO [STDOUT] ** End Credit Check - Service 3 **
11:38:29,842 INFO [STDOUT] ** Begin Validate Order - Service 2 **
11:38:29,842 INFO [STDOUT] In: Getting Started 'Receive Order' 'Credit Check'
11:38:29,843 INFO [STDOUT] Out: Getting Started 'Receive Order' 'Credit Check' 'Validate Order'
11:38:29,843 INFO [STDOUT] ** End Validate Order - Service 2 **
11:38:30,021 INFO [STDOUT] ** Begin Inventory Check - Service 4 **
11:38:30,022 INFO [STDOUT] In: Getting Started 'Receive Order' 'Credit Check' 'Validate Order'
11:38:30,022 INFO [STDOUT] Out: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check'
11:38:30,022 INFO [STDOUT] ** End Inventory Check - Service 4 **
11:38:30,422 INFO [STDOUT] ** Begin Los Angeles - Service 5 **
11:38:30,422 INFO [STDOUT] In: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check'
11:38:30,423 INFO [STDOUT] Out: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check' 'Los Angeles'
11:38:30,423 INFO [STDOUT] ** End Los Angeles - Service 5 **
11:38:30,425 INFO [STDOUT] ** Begin Dallas - Service 6 **
11:38:30,425 INFO [STDOUT] In: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check'
11:38:30,426 INFO [STDOUT] Out: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check' 'Dallas'
11:38:30,426 INFO [STDOUT] ** End Dallas - Service 6 **
11:38:30,426 INFO [STDOUT] ** Begin Atlanta - Service 7 **
11:38:30,426 INFO [STDOUT] In: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check'
11:38:30,427 INFO [STDOUT] Out: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check' 'Atlanta'
11:38:30,427 INFO [STDOUT] ** Service 7 - EXCEPTION THROWN **
11:38:30,427 ERROR [GroovyActionProcessor] Error executing Groovy script.
java.lang.RuntimeException: Exception in Service 7
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at org.codehaus.groovy.runtime.MetaClassHelper.doConstructorInvoke(MetaClassHelper.java:562)
at groovy.lang.MetaClassImpl.doConstructorInvoke(MetaClassImpl.java:1756)
at groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:758)
at groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:688)
at org.codehaus.groovy.runtime.Invoker.invokeConstructorOf(Invoker.java:163)
at org.codehaus.groovy.runtime.InvokerHelper.invokeConstructorOf(InvokerHelper.java:140)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeNewN(ScriptBytecodeAdapter.java:243)
at Script1.run(Script1.groovy:13)
at org.jboss.soa.esb.actions.scripting.GroovyActionProcessor.process(GroovyActionProcessor.java:151)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:615)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:574)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:408)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
11:38:30,641 WARN [HSQLDialect] HSQLDB supports only READ_UNCOMMITTED isolation
11:38:30,655 INFO [STDOUT] ** Exception Handler **
11:38:30,655 INFO [STDOUT] In: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check'
11:38:30,655 INFO [STDOUT] Out: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check' 'Exception Handler'
11:38:30,656 INFO [STDOUT] ** End Exception Handler **
11:38:30,679 WARN [HSQLDialect] HSQLDB supports only READ_UNCOMMITTED isolation
11:38:30,762 WARN [HSQLDialect] HSQLDB supports only READ_UNCOMMITTED isolation
11:38:30,888 INFO [STDOUT] ***** Ship It *****
11:38:30,889 INFO [STDOUT] In: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check' 'Exception Handler'
11:38:30,889 INFO [STDOUT] Out: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check' 'Exception Handler' 'Shipped'
11:38:30,889 INFO [STDOUT] ***** End Ship It *****
11:38:30,901 INFO [STDOUT] SUCCESS!:
11:38:30,901 INFO [STDOUT] [Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check' 'Exception Handler' 'Shipped' ].
Note the Exception Handler service
In 4.2
11:51:05,191 INFO [STDOUT] ** Begin Receive Order - Service 1 **
11:51:05,248 INFO [STDOUT] In: Getting Started
11:51:05,248 INFO [STDOUT] Out: Getting Started 'Receive Order'
11:51:05,249 INFO [STDOUT] ** End Receive Order - Service 1 **
11:51:05,571 INFO [STDOUT] ** Begin Credit Check - Service 3 **
11:51:05,571 INFO [STDOUT] In: Getting Started 'Receive Order'
11:51:05,571 INFO [STDOUT] Out: Getting Started 'Receive Order' 'Credit Check'
11:51:05,572 INFO [STDOUT] ** End Credit Check - Service 3 **
11:51:05,898 INFO [STDOUT] ** Begin Validate Order - Service 2 **
11:51:05,898 INFO [STDOUT] In: Getting Started 'Receive Order' 'Credit Check'
11:51:05,899 INFO [STDOUT] Out: Getting Started 'Receive Order' 'Credit Check' 'Validate Order'
11:51:05,899 INFO [STDOUT] ** End Validate Order - Service 2 **
11:51:06,194 INFO [STDOUT] ** Begin Inventory Check - Service 4 **
11:51:06,194 INFO [STDOUT] In: Getting Started 'Receive Order' 'Credit Check' 'Validate Order'
11:51:06,195 INFO [STDOUT] Out: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check'
11:51:06,195 INFO [STDOUT] ** End Inventory Check - Service 4 **
11:51:06,620 INFO [STDOUT] ** Begin Atlanta - Service 7 **
11:51:06,620 INFO [STDOUT] In: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check'
11:51:06,620 INFO [STDOUT] Out: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check' 'Atlanta'
11:51:06,620 INFO [STDOUT] ** Service 7 - EXCEPTION THROWN **
11:51:06,640 INFO [STDOUT] ** Begin Dallas - Service 6 **
11:51:06,640 INFO [STDOUT] In: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check'
11:51:06,641 INFO [STDOUT] Out: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check' 'Dallas'
11:51:06,641 INFO [STDOUT] ** End Dallas - Service 6 **
11:51:06,645 ERROR [GroovyActionProcessor] Error executing Groovy script.
java.lang.RuntimeException: Exception in Service 7
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at org.codehaus.groovy.runtime.MetaClassHelper.doConstructorInvoke(MetaClassHelper.java:562)
at groovy.lang.MetaClassImpl.doConstructorInvoke(MetaClassImpl.java:1756)
at groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:758)
at groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:688)
at org.codehaus.groovy.runtime.Invoker.invokeConstructorOf(Invoker.java:163)
at org.codehaus.groovy.runtime.InvokerHelper.invokeConstructorOf(InvokerHelper.java:140)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeNewN(ScriptBytecodeAdapter.java:243)
at Script1.run(Script1.groovy:13)
at org.jboss.soa.esb.actions.scripting.GroovyActionProcessor.process(GroovyActionProcessor.java:148)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
11:51:06,647 INFO [STDOUT] ** Begin Los Angeles - Service 5 **
11:51:06,647 INFO [STDOUT] In: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check'
11:51:06,648 INFO [STDOUT] Out: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check' 'Los Angeles'
11:51:06,648 INFO [STDOUT] ** End Los Angeles - Service 5 **
11:51:06,814 WARN [HSQLDialect] HSQLDB supports only READ_UNCOMMITTED isolation
11:51:06,870 WARN [HSQLDialect] HSQLDB supports only READ_UNCOMMITTED isolation
11:51:06,927 WARN [HSQLDialect] HSQLDB supports only READ_UNCOMMITTED isolation
11:51:07,085 INFO [STDOUT] ***** Ship It *****
11:51:07,086 INFO [STDOUT] In: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check' 'Los Angeles'
11:51:07,086 INFO [STDOUT] Out: Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check' 'Los Angeles' 'Shipped'
11:51:07,086 INFO [STDOUT] ***** End Ship It *****
11:51:07,098 INFO [STDOUT] SUCCESS!:
11:51:07,098 INFO [STDOUT] [Getting Started 'Receive Order' 'Credit Check' 'Validate Order' 'Inventory Check' 'Los Angeles' 'Shipped' ].
The exception handler step is completely missing from the output
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years