January 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1239) 4.2.1GA should be 4.2.1.GA

by Kurt Stam (JIRA)

4.2.1GA should be 4.2.1.GA -------------------------- Key: JBESB-1239 URL: http://jira.jboss.com/jira/browse/JBESB-1239 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Mark Little That is if we want to follow the convention used by AS. -- 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

17 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-666) Create a separate common module/jar

by Mark Little (JIRA)

Create a separate common module/jar ----------------------------------- Key: JBESB-666 URL: http://jira.jboss.com/jira/browse/JBESB-666 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Packaging Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little Priority: Optional -- 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

17 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1386) Review Exceptions on the EPR types

by Tom Fennelly (JIRA)

Review Exceptions on the EPR types ---------------------------------- Key: JBESB-1386 URL: http://jira.jboss.com/jira/browse/JBESB-1386 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.0 Reporter: Tom Fennelly Fix For: 4.3 We're throwing exceptions on getter methods??? Example... throwing a URISyntaxException on JDBCEpr.getSQL()??? It's all over the place. This might all fall back under a more general review of the whole API! -- 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

17 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-875) Comparision performance tests

by Mark Little (JIRA)

Comparision performance tests ----------------------------- Key: JBESB-875 URL: http://jira.jboss.com/jira/browse/JBESB-875 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Tom Fennelly Priority: Optional Intern: "Are there any performance tests in the release that someone could use to check Smooks versus XSLT? Does that even make sense?" -- 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

17 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1378) JBossRemotingGatewayListener not disconnecting properly on undeploy

by Tom Fennelly (JIRA)

JBossRemotingGatewayListener not disconnecting properly on undeploy -------------------------------------------------------------------- Key: JBESB-1378 URL: http://jira.jboss.com/jira/browse/JBESB-1378 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 Reporter: Tom Fennelly Fix For: 4.2.1 CP1 Looks as though the jbr-listener is not closing/stopping/disconnecting properly on the doStop event. -- 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

17 years, 11 months

7
24
0 / 0

[JBoss JIRA] Created: (JBESB-777) Create some wiki pages around SOA patterns for the ESB

by Mark Little (JIRA)

Create some wiki pages around SOA patterns for the ESB ------------------------------------------------------ Key: JBESB-777 URL: http://jira.jboss.com/jira/browse/JBESB-777 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Reporter: Mark Little Assigned To: Mark Little Ones that don't rely on exposing individual objects on to the bus. Conform to recognised SOA patterns. It'll be hard without all of the supporting tools, but it's still 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

17 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1425) Refactor JMSRouter and NotifyJMS to use JmsConnectionPoolContainer

by Daniel Bevenius (JIRA)

Refactor JMSRouter and NotifyJMS to use JmsConnectionPoolContainer ------------------------------------------------------------------ Key: JBESB-1425 URL: http://jira.jboss.com/jira/browse/JBESB-1425 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.3 Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Fix For: 4.3 JMSRouter and NotifyJMS currently create their own JMS connections and sessions. This is done for every invokation which is not very efficient. Plus that there is code duplication here. -- 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

17 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1486) jUDDI using BRMS as repository

by Mark Little (JIRA)

jUDDI using BRMS as repository ------------------------------ Key: JBESB-1486 URL: http://jira.jboss.com/jira/browse/JBESB-1486 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Kurt Stam Fix For: 5.0 -- 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

17 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1460) jms-jca-provider doesn't read from queues on different node

by Martin Vecera (JIRA)

jms-jca-provider doesn't read from queues on different node ----------------------------------------------------------- Key: JBESB-1460 URL: http://jira.jboss.com/jira/browse/JBESB-1460 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters, Rosetta Affects Versions: 4.2.1 Environment: 2x RHEL5, SOA-P 4.2.0 beta 1, Oracle 10g Reporter: Martin Vecera Priority: Blocker While I was trying ESB load balancing and failover I found out the following issue... Scenario: 1. Two nodes (hostnames: jawa02, jawa04), sharing the same DB, different ServerPeerIDs but no JMS clustering. 2. I generated a message backlog on jawa02 queue/A (10,000 messages). 3. See my simple service configuration: <providers> <jms-jca-provider name="JBossMessaging" connection-factory="XAConnectionFactory" jndi-URL="jnp://jawa02:1099" jndi-context-factory="org.jnp.interfaces.NamingContextFactory" jndi-pkg-prefix="org.jboss.naming:org.jnp.interfaces" transacted="false"> <jms-bus busid="quickstartGwChannel"> <jms-message-filter dest-type="QUEUE" dest-name="queue/A" /> </jms-bus> </jms-jca-provider> <jms-jca-provider name="JBossMessaging" connection-factory="XAConnectionFactory" jndi-URL="jnp://jawa04:1099" jndi-context-factory="org.jnp.interfaces.NamingContextFactory" jndi-pkg-prefix="org.jboss.naming:org.jnp.interfaces" transacted="false"> <jms-bus busid="quickstartEsbChannel"> <jms-message-filter dest-type="QUEUE" dest-name="queue/C" /> </jms-bus> </jms-jca-provider> </providers> <services> <service category="FirstServiceESB" name="SimpleListener" description="Hello World"> <listeners> <jms-listener name="ESB-Gateway" busidref="quickstartGwChannel" maxThreads="4" is-gateway="true" /> <jms-listener name="helloWorld" busidref="quickstartEsbChannel" maxThreads="4" /> </listeners> <actions mep="OneWay"> <action name="notificationAction" class="org.jboss.soa.esb.actions.Notifier"> <property name="okMethod" value="notifyOK" /> <property name="notification-details"> <NotificationList type="OK"> <target class="NotifyConsole" /> </NotificationList> </property> </action> </actions> </service> </services> 4. I deployed the described service to jawa04 and expected it to start processing the messages from jawa02 queue/A but this didn't happen. 5. When I changed the GW provider from jms-jca-provider to jms-provider: <jms-provider name="JBossMessaging" connection-factory="XAConnectionFactory" jndi-URL="jnp://jawa02:1099" jndi-context-factory="org.jnp.interfaces.NamingContextFactory" jndi-pkg-prefix="org.jboss.naming:org.jnp.interfaces"> It worked as expected. Unfortunatelly jms-provider doesn't use ServiceInvoker and thus no load balancing/failover is possible. This makes the ESB failover impossible using JMS. Solution: 1) make jms-jca-provider read the messages from different nodes in the way jms-provider does it. or 2) make jms-provider use ServiceInvoker -- 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

4
13
0 / 0

[JBoss JIRA] Created: (JBESB-1412) Ability to send message payload as an attachment

by Kenneth Larsen (JIRA)

Ability to send message payload as an attachment ------------------------------------------------ Key: JBESB-1412 URL: http://jira.jboss.com/jira/browse/JBESB-1412 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Kenneth Larsen Attachments: NotifyEmailPatch.patch It would be nice to have the option of sending the message payload as an attachment when using the EMailNotifier instead of always having to include the message payload into the mail body. In some cases the payload might be binary content which is inappropriate in the mail body. By specifying an additional attribute for the target the payload should be attached to the mail: <target class="NotifyEmail" from="sender(a)domain.com" sendTo="recipient(a)anotherdomain.com" subject="subject for message" msgAttachmentName="attachmentname.ext"> In the example above a new attribute has been introduced (msgAttachmentName). If specified the payload is created as an attachment with the specified filename instead of being part of the mail body. -- 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

2
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2008