July 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-800) Provide in the documentation the links of the existing wiki pages for the quickstart samples.

by angel asencio (JIRA)

Provide in the documentation the links of the existing wiki pages for the quickstart samples. --------------------------------------------------------------------------------------------- Key: JBESB-800 URL: http://jira.jboss.com/jira/browse/JBESB-800 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: angel asencio Assigned To: Mark Little Priority: Minor To list any existing wiki quickstart sample link under the corresponding quickstart sample listed in the GettingStarted Guide and the readme.txt of that quickstart sample. For examples: There exist a wiki for the Hello World quickstart: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossESBHelloworld This should be listed under the listing of helloworld in the Getting Started Guide and in the readme.txt of the helloworld quickstart sample. -- 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, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1603) Should have a JMS clustering QS

by Tom Cunningham (JIRA)

Should have a JMS clustering QS ------------------------------- Key: JBESB-1603 URL: http://jira.jboss.com/jira/browse/JBESB-1603 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP1 Reporter: Tom Cunningham Assigned To: Tom Cunningham We should have a QS that demonstrates clustered JMS queues/topics, and ideally, that will help setup clustering as part of the setup. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1558) StringTemplateProcessor does not propagate message contents to template

by Jiri Pechanec (JIRA)

StringTemplateProcessor does not propagate message contents to template ----------------------------------------------------------------------- Key: JBESB-1558 URL: http://jira.jboss.com/jira/browse/JBESB-1558 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters, Documentation Affects Versions: 4.2.1 CP1 Reporter: Jiri Pechanec Fix For: 4.2.1 CP2 There is a StringTemplateProcessor action. I would expect that it will take the contents of the message (all positions) and will propagate it to string template for processing. But instead of it it expects that there is Map store in message default position and propagates only this one. As there is no documentation related to this action I raise it as bug. If it is WAD please close it. -- 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, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1349) ESB test suite hardcoded for hsqldb

by Len DiMaggio (JIRA)

ESB test suite hardcoded for hsqldb ----------------------------------- Key: JBESB-1349 URL: http://jira.jboss.com/jira/browse/JBESB-1349 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 Reporter: Len DiMaggio Assigned To: Kevin Conner ESB Project issue for SOA-150 ESB test suite seems hardcoded to use hsqldb. And I don't see it easily changing few properties and get it running against another database. Let Aleksandar Kostadinov <akostadi(a)redhat.com> know if you need access to databases in the QA Lab. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1241) test suite execute against server bound to specified local IP

by Aleksandar Kostadinov (JIRA)

test suite execute against server bound to specified local IP ------------------------------------------------------------- Key: JBESB-1241 URL: http://jira.jboss.com/jira/browse/JBESB-1241 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Reporter: Aleksandar Kostadinov Assigned To: Mark Little Currently test suite can execute only against server bound to "localhost". It makes sense to be able to execute it against a server running on a selected IP probably an ant property supplied. -- 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, 6 months

3
3
0 / 0

[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

14 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1571) Fix issues with junit tests running against external binary

by Tom Cunningham (JIRA)

Fix issues with junit tests running against external binary ----------------------------------------------------------- Key: JBESB-1571 URL: http://jira.jboss.com/jira/browse/JBESB-1571 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 CP1 Reporter: Tom Cunningham When trying to run the qa/junit tests against an external binary (SOA-P or JBoss AS+ESB) there are issues : [java] execute: [java] [mkdir] Created dir: /Users/tcunning/src/esb/JBESB_4_2_1_GA_CP/qa/build/junit/report [java] [junit] 00:13:04,409 INFO [main][DeploymentArchive] Deployment archive '/Users/tcunning/src/esb/JBESB_4_2_1_GA_CP/qa/build/lib/LogicalEPRUnitTest.esb' created. [java] [junit] Running org.jboss.soa.esb.epr.LogicalEPRUnitTest [java] [junit] Testsuite: org.jboss.soa.esb.epr.LogicalEPRUnitTest [java] [junit] Found log4j.xml: file:/Users/tcunning/src/esb/JBESB_4_2_1_GA_CP/qa/log4j.xml [java] [junit] 00:13:04,510 DEBUG [main][LogicalEPRUnitTest] ==== setUp org.jboss.soa.esb.epr.LogicalEPRUnitTest ==== [java] [junit] 00:13:04,510 DEBUG [main][LogicalEPRUnitTest] JBossTestServices.setUp() [java] [junit] 00:13:04,559 DEBUG [main][LogicalEPRUnitTest] initialContext.getEnvironment()={jnp.parsedName=, java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.provider.url=localhost:1099, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces} [java] [junit] 00:13:04,559 INFO [main][LogicalEPRUnitTest] jbosstest.beancount: ${jbosstest.beancount} [java] [junit] 00:13:04,563 INFO [main][LogicalEPRUnitTest] jbosstest.iterationcount: ${jbosstest.iterationcount} [java] [junit] 00:13:04,563 INFO [main][LogicalEPRUnitTest] jbosstest.threadcount: ${jbosstest.threadcount} [java] [junit] 00:13:04,563 INFO [main][LogicalEPRUnitTest] jbosstest.nodeploy: null [java] [junit] 00:13:04,564 INFO [main][LogicalEPRUnitTest] jbosstest.jndiurl: localhost:1099 [java] [junit] 00:13:04,564 INFO [main][LogicalEPRUnitTest] jbosstest.jndifactory: org.jnp.interfaces.NamingContextFactory [java] [junit] 00:13:04,564 DEBUG [main][LogicalEPRUnitTest] LogicalEPRUnitTest.esb is not a valid URL, no protocol: LogicalEPRUnitTest.esb [java] [junit] 00:13:04,564 DEBUG [main][LogicalEPRUnitTest] Testing file: /Users/tcunning/src/esb/JBESB_4_2_1_GA_CP/qa/build/lib/LogicalEPRUnitTest.esb [java] [junit] 00:13:04,564 DEBUG [main][LogicalEPRUnitTest] /Users/tcunning/src/esb/JBESB_4_2_1_GA_CP/qa/build/lib/LogicalEPRUnitTest.esb is a valid file [java] [junit] 00:13:04,564 DEBUG [main][LogicalEPRUnitTest] Deploying LogicalEPRUnitTest.esb, url=file:/Users/tcunning/src/esb/JBESB_4_2_1_GA_CP/qa/build/lib/LogicalEPRUnitTest.esb [java] [junit] 00:13:04,763 DEBUG [main][LogicalEPRUnitTest] Invoking jboss.system:service=MainDeployer method=redeploy [java] [junit] 00:13:04,763 DEBUG [main][LogicalEPRUnitTest] args=[file:/Users/tcunning/src/esb/JBESB_4_2_1_GA_CP/qa/build/lib/LogicalEPRUnitTest.esb] [java] [junit] 00:13:05,569 DEBUG [main][LogicalEPRUnitTest] deployed package: LogicalEPRUnitTest.esb [java] [junit] 00:13:05,746 DEBUG [main][LifecycleResource] Creating resource using factory: org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPoolContainer$JmsConnectionPoolFactory@78743b with identity ID-DEFAULT [java] [junit] 00:13:05,753 DEBUG [main][LifecycleResource] Creating resource using factory: org.jboss.soa.esb.helpers.NamingContextPool$NamingContextPoolFactory@6c14e7 with identity ID-DEFAULT [java] [junit] 00:13:08,163 DEBUG [main][RegistryFactory] Going to load org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl [java] [junit] 00:13:08,179 ERROR [main][JAXRRegistryImpl] Could not set up a connection to the Registry. Invalid queryManagerURL: jnp://localhost:1099/InquiryService?org.apache.juddi.registry.rmi.Inquiry#inquire [java] [junit] javax.xml.registry.InvalidRequestException: Invalid queryManagerURL: jnp://localhost:1099/InquiryService?org.apache.juddi.registry.rmi.Inquiry#inquire [java] [junit] at org.apache.ws.scout.registry.ConnectionFactoryImpl.createConnection(ConnectionFactoryImpl.java:77) [java] [junit] at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.getConnection(JAXRRegistryImpl.java:121) [java] [junit] at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:336) [java] [junit] at org.jboss.soa.esb.listeners.RegistryUtil.getEprs(RegistryUtil.java:226) [java] [junit] at org.jboss.soa.esb.client.ServiceInvoker.loadServiceClusterInfo(ServiceInvoker.java:411) [java] [junit] at org.jboss.soa.esb.client.ServiceInvoker.<init>(ServiceInvoker.java:146) [java] [junit] at org.jboss.soa.esb.addressing.eprs.LogicalEPR.getServiceInvoker(LogicalEPR.java:98) [java] [junit] at org.jboss.soa.esb.epr.LogicalEPRUnitTest.test_logical_extension(LogicalEPRUnitTest.java:79) [java] [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] [junit] at java.lang.reflect.Method.invoke(Method.java:585) [java] [junit] at junit.framework.TestCase.runTest(TestCase.java:164) [java] [junit] at junit.framework.TestCase.runBare(TestCase.java:130) [java] [junit] at junit.framework.TestResult$1.protect(TestResult.java:110) [java] [junit] at junit.framework.TestResult.runProtected(TestResult.java:128) [java] [junit] at junit.framework.TestResult.run(TestResult.java:113) [java] [junit] at junit.framework.TestCase.run(TestCase.java:120) [java] [junit] at junit.framework.TestSuite.runTest(TestSuite.java:228) [java] [junit] at junit.framework.TestSuite.run(TestSuite.java:223) [java] [junit] at junit.framework.TestSuite.runTest(TestSuite.java:228) [java] [junit] at junit.framework.TestSuite.run(TestSuite.java:223) [java] [junit] at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) [java] [junit] at junit.extensions.TestSetup$1.protect(TestSetup.java:23) [java] [junit] at junit.framework.TestResult.runProtected(TestResult.java:128) [java] [junit] at junit.extensions.TestSetup.run(TestSetup.java:27) [java] [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421) [java] [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:912) [java] [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:766) [java] [junit] Caused by: java.net.MalformedURLException: unknown protocol: jnp [java] [junit] at java.net.URL.<init>(URL.java:574) [java] [junit] at java.net.URL.<init>(URL.java:464) [java] [junit] at java.net.URL.<init>(URL.java:413) [java] [junit] at org.apache.ws.scout.registry.ConnectionFactoryImpl.createConnection(ConnectionFactoryImpl.java:74) [java] [junit] ... 28 more [java] [junit] 00:13:08,182 ERROR [main][JAXRRegistryImpl] Could not set up a connection to the Registry. Invalid queryManagerURL: jnp://localhost:1099/InquiryService?org.apache.juddi.registry.rmi.Inquiry#inquire [java] [junit] javax.xml.registry.InvalidRequestException: Invalid queryManagerURL: jnp://localhost:1099/InquiryService?org.apache.juddi.registry.rmi.Inquiry#inquire [java] [junit] at org.apache.ws.scout.registry.ConnectionFactoryImpl.createConnection(ConnectionFactoryImpl.java:77) [java] [junit] at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.getConnection(JAXRRegistryImpl.java:121) [java] [junit] at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findService(JAXRRegistryImpl.java:477) [java] [junit] at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:338) [java] [junit] at org.jboss.soa.esb.listeners.RegistryUtil.getEprs(RegistryUtil.java:226) [java] [junit] at org.jboss.soa.esb.client.ServiceInvoker.loadServiceClusterInfo(ServiceInvoker.java:411) [java] [junit] at org.jboss.soa.esb.client.ServiceInvoker.<init>(ServiceInvoker.java:146) [java] [junit] at org.jboss.soa.esb.addressing.eprs.LogicalEPR.getServiceInvoker(LogicalEPR.java:98) [java] [junit] at org.jboss.soa.esb.epr.LogicalEPRUnitTest.test_logical_extension(LogicalEPRUnitTest.java:79) [java] [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] [junit] at java.lang.reflect.Method.invoke(Method.java:585) [java] [junit] at junit.framework.TestCase.runTest(TestCase.java:164) [java] [junit] at junit.framework.TestCase.runBare(TestCase.java:130) [java] [junit] at junit.framework.TestResult$1.protect(TestResult.java:110) [java] [junit] at junit.framework.TestResult.runProtected(TestResult.java:128) [java] [junit] at junit.framework.TestResult.run(TestResult.java:113) [java] [junit] at junit.framework.TestCase.run(TestCase.java:120) [java] [junit] at junit.framework.TestSuite.runTest(TestSuite.java:228) [java] [junit] at junit.framework.TestSuite.run(TestSuite.java:223) [java] [junit] at junit.framework.TestSuite.runTest(TestSuite.java:228) [java] [junit] at junit.framework.TestSuite.run(TestSuite.java:223) [java] [junit] at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) [java] [junit] at junit.extensions.TestSetup$1.protect(TestSetup.java:23) [java] [junit] at junit.framework.TestResult.runProtected(TestResult.java:128) [java] [junit] at junit.extensions.TestSetup.run(TestSetup.java:27) [java] [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421) [java] [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:912) [java] [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:766) [java] [junit] Caused by: java.net.MalformedURLException: unknown protocol: jnp [java] [junit] at java.net.URL.<init>(URL.java:574) [java] [junit] at java.net.URL.<init>(URL.java:464) [java] [junit] at java.net.URL.<init>(URL.java:413) [java] [junit] at org.apache.ws.scout.registry.ConnectionFactoryImpl.createConnection(ConnectionFactoryImpl.java:74) [java] [junit] ... 29 more [java] [junit] 00:13:08,198 DEBUG [main][LogicalEPRUnitTest] LogicalEPRUnitTest.esb is not a valid URL, no protocol: LogicalEPRUnitTest.esb [java] [junit] 00:13:08,198 DEBUG [main][LogicalEPRUnitTest] Testing file: /Users/tcunning/src/esb/JBESB_4_2_1_GA_CP/qa/build/lib/LogicalEPRUnitTest.esb [java] [junit] 00:13:08,198 DEBUG [main][LogicalEPRUnitTest] /Users/tcunning/src/esb/JBESB_4_2_1_GA_CP/qa/build/lib/LogicalEPRUnitTest.esb is a valid file [java] [junit] 00:13:08,199 DEBUG [main][LogicalEPRUnitTest] Undeploying LogicalEPRUnitTest.esb, url=file:/Users/tcunning/src/esb/JBESB_4_2_1_GA_CP/qa/build/lib/LogicalEPRUnitTest.esb [java] [junit] 00:13:08,199 DEBUG [main][LogicalEPRUnitTest] Invoking jboss.system:service=MainDeployer method=undeploy [java] [junit] 00:13:08,199 DEBUG [main][LogicalEPRUnitTest] args=[file:/Users/tcunning/src/esb/JBESB_4_2_1_GA_CP/qa/build/lib/LogicalEPRUnitTest.esb] [java] [junit] 00:13:08,508 DEBUG [main][LogicalEPRUnitTest] undeployed package: LogicalEPRUnitTest.esb [java] [junit] 00:13:08,508 DEBUG [main][LogicalEPRUnitTest] JBossTestServices.tearDown() [java] [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.083 sec [java] [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.083 sec -- 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, 6 months

2
1
0 / 0

[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

14 years, 6 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-502) Blocking Gateway - in and out.

by Kurt Stam (JIRA)

Blocking Gateway - in and out. ------------------------------ Key: JBESB-502 URL: http://jira.jboss.com/jira/browse/JBESB-502 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 1 Environment: any Reporter: Kurt Stam Assigned To: Mark Little Fix For: 4.2 Milestone Release 2 I do think we should make an option for a blocking gateway, where the gateway waits for a a reply from an ESB Service. Basically we set the 'replyTO' on the message and route to a 'replyTO' service which replies back to the gateway. This is another argument for gateways to be in and out. -- 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, 6 months

4
8
0 / 0

[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, 7 months

4
16
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2008