[JBoss JIRA] Created: (JBESB-2060) ServiceInvoker fails to find HAJNDI when invoked in clustered environment
by Magesh Kumar B (JIRA)
ServiceInvoker fails to find HAJNDI when invoked in clustered environment
-------------------------------------------------------------------------
Key: JBESB-2060
URL: https://jira.jboss.org/jira/browse/JBESB-2060
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Registry and Repository, Rosetta, Transports
Affects Versions: 4.2.1 CP2
Environment: SOA-P and Fedora9 Linux
Reporter: Magesh Kumar B
Create two instances of SOA-P in Linux platform using the ports binding service. Start the two instances. Change the InquiryURI and PublishURI as below in jbossesb-properties.xml inside samples/quickstarts/helloworld:
<property name="org.jboss.soa.esb.registry.queryManagerURI"
value="jnp://127.0.0.1:1100/InquiryService?org.apache.juddi.registry.rmi.Inquiry#inquire"/>
<property name="org.jboss.soa.esb.registry.lifeCycleManagerURI"
value="jnp://127.0.0.1:1100/PublishService?org.apache.juddi.registry.rmi.Publish#publish" />
Notice they use HAJNDI ports. Deploy Quicktsart_helloworld_esb and run "ant sendesb", the test fails with exception:
sendesb:
[echo] Runs Test ESB Message Sender
[java] Exception in thread "main" org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message [header: [ ]] to Service [JBossESB-Internal:DeadLetterService]. Check for errors.
[java] at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:356)
[java] at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:225)
[java] at org.jboss.soa.esb.client.ServiceInvoker.deliverToDeadLetterService(ServiceInvoker.java:267)
[java] at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:235)
[java] at org.jboss.soa.esb.samples.quickstart.helloworld.test.SendEsbMessage.main(SendEsbMessage.java:55)
However, this only happens in Linux enviornment (Fedora9 in my test) and passes in Windows. Also the HAJNDI port 1100 works if only one instance is running in that cluster partition.
When we use these ports 1100/1200 in JMS client and do "ant runtest", they connect seamlessly.
--
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
15 years, 1 month
[JBoss JIRA] Created: (JBESB-1695) jBPM datasource should be XA datasource
by Jiri Pechanec (JIRA)
jBPM datasource should be XA datasource
---------------------------------------
Key: JBESB-1695
URL: http://jira.jboss.com/jira/browse/JBESB-1695
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Process flow, Rosetta
Affects Versions: 4.2.1 CP2
Reporter: Jiri Pechanec
Assigned To: Kevin Conner
Fix For: 4.2.1 CP3
If the SQL listener with transactions is used configured according helloworld_tx_sql and is enhanced with jBPM use - start service, it fails because both datasources are local.
To prevent the issue these steps should be done
1) Change the jBPM DS to be XA datasource - this means that schme toll must be also modified
2) Change QS to use H2 database and XA datasource - it serves users as guidline
3) Switch to h2 database for all datasources
--
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
15 years, 1 month
[JBoss JIRA] Created: (JBESB-1650) Clean up OracleAQ documentation
by Tom Cunningham (JIRA)
Clean up OracleAQ documentation
-------------------------------
Key: JBESB-1650
URL: http://jira.jboss.com/jira/browse/JBESB-1650
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Message Store
Affects Versions: 4.2.1 CP2
Reporter: Tom Cunningham
Assigned To: Tom Cunningham
Fix For: 4.2.1 CP3
Got some notes from Narayanan Raghavan about his experience with the OracleAQ message provider. They are using it and it is working well but the experience getting it configured could be a little smoother :
- they didn't need ojdbc14.jar (need to double check this)
- they needed the "full version" of cglib.jar (the full version is in the EAP)
- they found the sample jboss-esb.xml confusing - it talks about moving a message from one OracleAQ -> another OracleAQ, and there should be a sample provided of moving a message from OracleAQ - > JBoss Messaging
--
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
15 years, 1 month