March 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2274) reprt all fixes and new features from my workspace

by Stefano Maestri (JIRA)

reprt all fixes and new features from my workspace -------------------------------------------------- Key: JBESB-2274 URL: https://jira.jboss.org/jira/browse/JBESB-2274 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Web Services Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 4.5 It could be consider a merge of all related issues (I've fixed/develop in last months) I think it is a preliminary work before start wit wise 1.0 integration. -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2275) port of current implementation and samples

by Stefano Maestri (JIRA)

port of current implementation and samples ------------------------------------------ Key: JBESB-2275 URL: https://jira.jboss.org/jira/browse/JBESB-2275 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Stefano Maestri Assignee: Stefano Maestri -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-506) Consider Mina support

by Mark Little (JIRA)

Consider Mina support --------------------- Key: JBESB-506 URL: http://jira.jboss.com/jira/browse/JBESB-506 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Reporter: Mark Little Assigned To: Mark Little Priority: Optional Fix For: 5.0 http://mina.apache.org/ -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2499) Identify any issues with using IBM MQ and provide direct support within the ESB codebase

by Kevin Conner (JIRA)

Identify any issues with using IBM MQ and provide direct support within the ESB codebase ---------------------------------------------------------------------------------------- Key: JBESB-2499 URL: https://jira.jboss.org/jira/browse/JBESB-2499 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 CP4 Reporter: Kevin Conner Fix For: 4.2.1 CP5 TomF has already done some work on this task, in relation to a customer enquiry. The solution he created was to provide an adapter to the MQ ConnectionFactory/Connection classes which could then be referred to from within the ESB configuration. The main purpose of the adapter was to handle the requirement that there only be a single session per connection when executing within a transactional context. We need to move this requirement back into the ESB codebase and support it directly within the JMS connection pool. An additional part of this task will be to identify any further issues which arise and create appropriate JIRAs. -- 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

2
7
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

15 years, 1 month

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

15 years, 1 month

3
2
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

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2243) JmsSession should cache the acknowledge mode rather than deferring to the underlying session

by Kevin Conner (JIRA)

JmsSession should cache the acknowledge mode rather than deferring to the underlying session -------------------------------------------------------------------------------------------- Key: JBESB-2243 URL: https://jira.jboss.org/jira/browse/JBESB-2243 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4, 4.4 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.5, 4.4 CP2 The reason for this is to ensure that failed sessions do not remain in the 'in use' state if a subsequent call to getAcknowledgeMode generates an error. -- 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

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2476) Clarification of content for ESB Registry Guide

by Jim Ma (JIRA)

Clarification of content for ESB Registry Guide ----------------------------------------------- Key: JBESB-2476 URL: https://jira.jboss.org/jira/browse/JBESB-2476 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 CP4 Reporter: Jim Ma Fix For: 4.2.1 CP5 QE questions the correctness of the following statement from Chapter 1 - What is the Registry, page 3: "It may be updated dynamically when services first start-up, or statically by an external administrator. " Clarification needed. -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2487) incomplete example in ESB Registry Guide

by Jim Ma (JIRA)

incomplete example in ESB Registry Guide ---------------------------------------- Key: JBESB-2487 URL: https://jira.jboss.org/jira/browse/JBESB-2487 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 CP4 Reporter: Jim Ma Fix For: 4.2.1 CP5 The SOAP example from Chapter 3 is missing details required to implement. For example, removing the juddi-service.sar , adding the axis1.4.jar and commons-discovery-0.2.jar to {$profile}/lib. I found the scout configured with AxisTransport does not work with the juddi server running in same jbossesb instance . Do we need add a note in it ? -- 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

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2009