April 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2540) Add unit tests for caching registry interceptor

by Kevin Conner (JIRA)

Add unit tests for caching registry interceptor ----------------------------------------------- Key: JBESB-2540 URL: https://jira.jboss.org/jira/browse/JBESB-2540 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 -- 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

17 years

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2541) Caching registry interceptor findEPR fails on empty response

by Kevin Conner (JIRA)

Caching registry interceptor findEPR fails on empty response ------------------------------------------------------------ Key: JBESB-2541 URL: https://jira.jboss.org/jira/browse/JBESB-2541 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.4 CP2 Reporter: Kevin Conner Priority: Minor Fix For: 4.4 CP3 Minor because we do not call this method but it does need to be fixed. -- 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

17 years

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1507) Odd jUDDI behaviour when under the load for longer time

by Jiri Pechanec (JIRA)

Odd jUDDI behaviour when under the load for longer time ------------------------------------------------------- Key: JBESB-1507 URL: http://jira.jboss.com/jira/browse/JBESB-1507 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2.1 Reporter: Jiri Pechanec Priority: Critical Attachments: server.log I have run something like performance/stress test simulating access to jUDDI by many clients. After few runs the jUDDI started to generate exceptions. See attached log -- 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

6
30
0 / 0

[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

17 years

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-2530) Update build version to 4.2.1-CP5

by Kevin Conner (JIRA)

Update build version to 4.2.1-CP5 --------------------------------- Key: JBESB-2530 URL: https://jira.jboss.org/jira/browse/JBESB-2530 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.2.1 CP4 Reporter: Kevin Conner Assignee: Kevin Conner Priority: Trivial Fix For: 4.2.1 CP5 -- 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

17 years

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2502) Fix JMSEpr address encoding

by Kevin Conner (JIRA)

Fix JMSEpr address encoding --------------------------- Key: JBESB-2502 URL: https://jira.jboss.org/jira/browse/JBESB-2502 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP2 Reporter: Kevin Conner Fix For: 4.4 CP3 The JMSEpr encodes the JNDI URI/destination name but the code currently assumes that the URI consists of just a host:port pair rather than a full URI. As a consequence, addresses such as jms://localhost:1414/SYSTEM.DEF.SVRCONN/queue/pt_bpmo1_start_esb are interpreted with a queue name of SYSTEM.DEF.SVRCONN/queue/pt_bpmo1_start_esb. We need to modify the address encoding to make sure that the URI/destination name can be correctly encoded and retrieved from this information. -- 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

17 years

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2505) Fix JMSEpr address encoding

by Kevin Conner (JIRA)

Fix JMSEpr address encoding --------------------------- Key: JBESB-2505 URL: https://jira.jboss.org/jira/browse/JBESB-2505 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 The JMSEpr encodes the JNDI URI/destination name but the code currently assumes that the URI consists of just a host:port pair rather than a full URI. As a consequence, addresses such as jms://localhost:1414/SYSTEM.DEF.SVRCONN/queue/pt_bpmo1_start_esb are interpreted with a queue name of SYSTEM.DEF.SVRCONN/queue/pt_bpmo1_start_esb. We need to modify the address encoding to make sure that the URI/destination name can be correctly encoded and retrieved from this information. -- 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

17 years

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2244) Lifecycle MBean names should be unique

by Kevin Conner (JIRA)

Lifecycle MBean names should be unique -------------------------------------- Key: JBESB-2244 URL: https://jira.jboss.org/jira/browse/JBESB-2244 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1 At present these can clash between deployments -- 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

17 years

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2514) CourierFactory synchronizes around access to lifecycle resource

by Kevin Conner (JIRA)

CourierFactory synchronizes around access to lifecycle resource --------------------------------------------------------------- Key: JBESB-2514 URL: https://jira.jboss.org/jira/browse/JBESB-2514 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 The courier factory has synchronized, static methods for registering and deregistering the couriers with its lifecycle resource. This can lead to deadlock during shutdown as a write lock is held by the lifecycle resource when destroying. -- 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

17 years

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2509) JMS JCA mapper sets maxMessages instead of maxSession

by Kevin Conner (JIRA)

JMS JCA mapper sets maxMessages instead of maxSession ----------------------------------------------------- Key: JBESB-2509 URL: https://jira.jboss.org/jira/browse/JBESB-2509 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 The JMS/JCA adapter initialises some variables in the activation spec and, until now, mapped the max threads count onto maxMessages. This was the wrong attribute to specify but has worked so far due to a bug in the base app server jms-ra.rar code, now fixed in JBPAPP-1045. We should have been setting the maxSession attribute instead. -- 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

17 years

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues April 2009