August 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2794) Management console attribute.jsp shows no values

by Tom Cunningham (JIRA)

Management console attribute.jsp shows no values ------------------------------------------------ Key: JBESB-2794 URL: https://jira.jboss.org/jira/browse/JBESB-2794 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.6 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.7 See screenshots in SOA-1456. -- 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, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2449) The Get or Post request 'http://localhost:8080/jbossesb/httpgateway/serviceA' can not be passed in ESB service through HttpGateway

by Kevin Conner (JIRA)

The Get or Post request 'http://localhost:8080/jbossesb/httpgateway/serviceA' can not be passed in ESB service through HttpGateway ----------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-2449 URL: https://jira.jboss.org/jira/browse/JBESB-2449 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Jim Ma Assignee: Tom Fennelly Fix For: 4.4 FP1 When context value of <http-bus> is configured to "/jbossesb/httpgateway/serviceA" ,the HttpGatewayListener will use name "jbossesb/httpgateway/serviceA" to create web context and use "/" to create servlet mapping . The Get or Post request for "http://localhost:8080/jbossesb/httpgateway/serviceA" can not be passed in HttpDistpatchServlet. I think we can use "jbossesb/httpgateway" to create web context and use "/serviceA/*" to create servlet mapping , then all the following requests can be passed in ESB service. http://localhost:8080/jbossesb/httpgateway/serviceA/1234 http://localhost:8080/jbossesb/httpgateway/serviceA/5678 http://localhost:8080/jbossesb/httpgateway/serviceA?a=b http://localhost:8080/jbossesb/httpgateway/serviceA/ -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2562) Concurrency issues within HttpServerDelegate

by Kevin Conner (JIRA)

Concurrency issues within HttpServerDelegate -------------------------------------------- Key: JBESB-2562 URL: https://jira.jboss.org/jira/browse/JBESB-2562 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Tom Fennelly Fix For: 4.4 FP1 There are a number of concurrency issue in this class, they need tidying up. The obvious ones are singleton and MBean manipulation. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2436) Add test for new HttpGateway classes

by Daniel Bevenius (JIRA)

Add test for new HttpGateway classes ------------------------------------ Key: JBESB-2436 URL: https://jira.jboss.org/jira/browse/JBESB-2436 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta, Testing, Transports Reporter: Daniel Bevenius Fix For: 4.6 -- 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, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-2655) AS5 Deployer: Add support for subdeployments in subdirectories and not only the root or the esb archive

by Daniel Bevenius (JIRA)

AS5 Deployer: Add support for subdeployments in subdirectories and not only the root or the esb archive ------------------------------------------------------------------------------------------------------- Key: JBESB-2655 URL: https://jira.jboss.org/jira/browse/JBESB-2655 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.6 Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.6 There seems to be an issue where subdeployments, for example a .war archive, not being deployed if it is not placed in the root of the .esb archive. We need to test this and add support for this situation. -- 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, 3 months

4
18
0 / 0

[JBoss JIRA] Created: (JBESB-2724) Problem with ESB and ports configuration on AS 5

by Tom Cunningham (JIRA)

Problem with ESB and ports configuration on AS 5 ------------------------------------------------ Key: JBESB-2724 URL: https://jira.jboss.org/jira/browse/JBESB-2724 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.6 Reporter: Tom Cunningham Fix For: 4.6 Attachments: server.log Using jboss-5.1.0.GA, I'm seeing a problem using any other ports configuration other than ports-default. Are there additional steps we need to do on AS5 other than changing the conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml and then changing the line : <constructor>  <parameter>${jboss.service.binding.set:ports-default}</parameter> to <parameter>${jboss.service.binding.set:ports-01}</parameter> -- 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, 3 months

3
11
0 / 0

[JBoss JIRA] Created: (JBESB-2781) Fix systinet transport build

by Tom Cunningham (JIRA)

Fix systinet transport build ---------------------------- Key: JBESB-2781 URL: https://jira.jboss.org/jira/browse/JBESB-2781 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP3 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix the systinet transport build so it no longer compiles against the systinet JARs (they aren't needed currently). -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2782) Remove verbose printStackTrace from Systinet Transport

by Tom Cunningham (JIRA)

Remove verbose printStackTrace from Systinet Transport ------------------------------------------------------ Key: JBESB-2782 URL: https://jira.jboss.org/jira/browse/JBESB-2782 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 CP3 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.4 CP3 Remove verbose printStackTrace from Systinet transport. -- 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, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-2780) mep="OneWay" on a published webservice results in a zero-length wsdl returned by <web service URL>?wsdl

by Kevin Conner (JIRA)

mep="OneWay" on a published webservice results in a zero-length wsdl returned by <web service URL>?wsdl -------------------------------------------------------------------------------------------------------- Key: JBESB-2780 URL: https://jira.jboss.org/jira/browse/JBESB-2780 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4 CP2 Reporter: Len DiMaggio Assignee: Kevin Conner Fix For: 4.4 CP3 Project issue for SOA-P platform issue SOA-1186 -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2755) Patch to add Ingres support to JBoss ESB

by murray armfield (JIRA)

Patch to add Ingres support to JBoss ESB ---------------------------------------- Key: JBESB-2755 URL: https://jira.jboss.org/jira/browse/JBESB-2755 Project: JBoss ESB Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 4.5 Environment: N/A Reporter: murray armfield Hi Folks, I've been working with getting JBoss ESB and its test suite(qa directory of src tarball download) ported to use the Ingres database system. Interested users should use the most recent Ingres release. I am in a position where I am passing all the same tests as the hsqldb. The ones that fail, fail in the same way as the hsqldb db fails. The failing tests are 1/ JmsGatewayListenerUnit Test - I get 'the destination does not exist' errors when it tries to create the topic used in the test. 2/ BPMOrchestration2Test - The last action, shipping, doesn't occur - state seems to be the same as hslqdb upon inspection through jbpm web console. 3/ JMSecuredTest - No classloaders found for JDBCJMSUserManagerService. If I need to revisit any of these or run any other test suites, please let me know and I will get on top of it immediately. Currently, Ingres 9.2 which is the current Ingres release, does not support object names greater than 32 characters. This is being addressed in future versions of Ingres. In the community version of Ingres, you can download and build the source code with an appropriate flag switched which will turn on much bigger object names. Some of the drools code in JBossESB uses objects with names greater than this limit, but it has not affected any of the tests that run. I am looking at doing something with drools to work with Ingres temporarily Take care, Murray -- 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, 3 months

1
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2009