November 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1314) hellowworld quickstart - sendesb ant target fails

by Len DiMaggio (JIRA)

hellowworld quickstart - sendesb ant target fails ------------------------------------------------- Key: JBESB-1314 URL: http://jira.jboss.com/jira/browse/JBESB-1314 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP1 Environment: At revision 16412 - trunk Reporter: Len DiMaggio Assigned To: Kevin Conner 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: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/quickstart_helloworld_Request_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 : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ]] to Service [JBossESB-Internal:DeadLetterService]. Check for er! rors. [java] at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:279) [java] at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:184) [java] at org.jboss.soa.esb.client.ServiceInvoker.deliverToDeadLetterService(ServiceInvoker.java:226) [java] at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:194) [java] at org.jboss.soa.esb.samples.quickstart.helloworld.test.SendEsbMessage.main(SendEsbMessage.java:55) BUILD FAILED /opt/ESB/trunk/product/build/jbossesb-server-4.2.1GA/samples/quickstarts/helloworld/build.xml:23: Java returned: 1 -- 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

18 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1125) Possible bug in Notifier processing

by Richard Achmatowicz (JIRA)

Possible bug in Notifier processing ------------------------------------ Key: JBESB-1125 URL: http://jira.jboss.com/jira/browse/JBESB-1125 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2.1 IR1 Reporter: Richard Achmatowicz Assigned To: Kevin Conner Priority: Minor Don't know if this is intended or unintended - but the name of the property used to enclose NotificationList elements in the <action> target is not validated. For example, this list of notifications works perfectly well: <action name="notificationTest" class="org.jboss.soa.esb.actions.Notifier"> <property name="okMethod" value="notifyOK" /> <property name="THIS-NAME-IS-NOT-VALIDATED"> <NotificationList type="OK">  <target class="NotifyConsole" /> </NotificationList> </property> </action> This raises the question of how to document the property name in the documentation. The name "notification-details" is being used in quickstarts, but that string does not exist in the codebase. -- 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

18 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1177) Console tools contain old version of drools

by Kevin Conner (JIRA)

Console tools contain old version of drools ------------------------------------------- Key: JBESB-1177 URL: http://jira.jboss.com/jira/browse/JBESB-1177 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2.1 IR2 Reporter: Kevin Conner Assigned To: Mark Little Priority: Minor Fix For: 4.2.1 We need to find out why this is included and remove if possible. -- 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

18 years, 5 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-1351) Load balancing documantation: deploying service in a clustered environment

by Martin Vecera (JIRA)

Load balancing documantation: deploying service in a clustered environment -------------------------------------------------------------------------- Key: JBESB-1351 URL: http://jira.jboss.com/jira/browse/JBESB-1351 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 Environment: ESB 4.2.1GA, Programmers guide Reporter: Martin Vecera While we were trying to run performance tests in a clustered ESB (clustering & load balancing via ServiceInvoker) we realized that we have to wait for service cache revalidation after esb archive deployment. In our opinion the documentation should say something like this: If you would like to run the same service on more than one node in a cluster you have to wait for service registry cache revalidation before the service is fully working in the clustered environment. You can setup this cache revalidation timeout in deploy/jbossesb.sar/jbossesb-properties.xml: <properties name="core"> <property name="org.jboss.soa.esb.registry.cache.life" value="60000"/> </properties> 60 seconds is the default timeout. We should also reconsider moving the load balancing documentation to Administration guide. -- 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

18 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1328) Add system property support in ESB deployment.xml files

by Kevin Conner (JIRA)

Add system property support in ESB deployment.xml files ------------------------------------------------------- Key: JBESB-1328 URL: http://jira.jboss.com/jira/browse/JBESB-1328 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2.1 Reporter: Kevin Conner Fix For: 4.3 We should support system property replacement within the dependency section of the deployment.xml file. -- 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

18 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1352) ...message.format.xml.AttachmentImpl should provide more meaningful exception messages

by Tom Fennelly (JIRA)

...message.format.xml.AttachmentImpl should provide more meaningful exception messages -------------------------------------------------------------------------------------- Key: JBESB-1352 URL: http://jira.jboss.com/jira/browse/JBESB-1352 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Tom Fennelly Fix For: 4.2.1 CP1 Example of current exceptions... throw new IllegalArgumentException("value must be Serializable"); Easy to add the actual type of "value" and would be of great use to the developer in tracking down the cause of such errors. -- 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

18 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1353) Typo in quickstarts' base-build.xml

by Kevin Conner (JIRA)

Typo in quickstarts' base-build.xml ----------------------------------- Key: JBESB-1353 URL: http://jira.jboss.com/jira/browse/JBESB-1353 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP1, 4.3 The path entries for commons-logging.jar and jboss-system.jar are incorrect. They currently refer to the lib directory within the server directory but should refer to the top level lib directory. They need changing to <pathelement location="${org.jboss.esb.server.home}/lib/commons-logging.jar"/> <pathelement location="${org.jboss.esb.server.home}/lib/jboss-system.jar"/> -- 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

18 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1341) ESB Build script does not deploy all the consoles into the EAP

by Christopher Brock (JIRA)

ESB Build script does not deploy all the consoles into the EAP -------------------------------------------------------------- Key: JBESB-1341 URL: http://jira.jboss.com/jira/browse/JBESB-1341 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Reporter: Christopher Brock Priority: Critical ESB Build script does not deploy all the consoles into the EAP server configurations. the ESB management and ESB configuration consoles are missing. -- 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

18 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1340) JUDDI Configuration Documentation

by toby (JIRA)

JUDDI Configuration Documentation --------------------------------- Key: JBESB-1340 URL: http://jira.jboss.com/jira/browse/JBESB-1340 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 Reporter: toby Priority: Trivial There was a good point made by Kurt in the following post, regarding changing the path to the juddi database creation script in esb.juddi.xml. It may be worth including this in PDFs: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=123176 -- 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

18 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1347) Make sure documentation is clear on gateways and load-balancing

by Mark Little (JIRA)

Make sure documentation is clear on gateways and load-balancing --------------------------------------------------------------- Key: JBESB-1347 URL: http://jira.jboss.com/jira/browse/JBESB-1347 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 CP1 -- 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

18 years, 5 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2007