May 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1519) NotifyJMS creates sessions array but never uses anything other than element 0

by Mark Little (JIRA)

NotifyJMS creates sessions array but never uses anything other than element 0 ----------------------------------------------------------------------------- Key: JBESB-1519 URL: http://jira.jboss.com/jira/browse/JBESB-1519 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Mark Little Fix For: 4.3 In the code ... /** * The javax.jms.Session instance used to talk to JMS */ protected Session[] sessions; then ... if(obj == null) { // create a null payload message... jmsMessage = sessions[0].createObjectMessage(null); } else if(obj instanceof byte[]) { jmsMessage = sessions[0].createObjectMessage((byte[]) obj); but ... final int nrQueuesOrTopics = configTrees.length; producers = new MessageProducer[nrQueuesOrTopics]; connectionPools = new JmsConnectionPool[nrQueuesOrTopics]; sessions = new Session[nrQueuesOrTopics]; -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1625) The classpath in product\.classpath is not correct

by Jervis Liu (JIRA)

The classpath in product\.classpath is not correct -------------------------------------------------- Key: JBESB-1625 URL: http://jira.jboss.com/jira/browse/JBESB-1625 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 5.0 Reporter: Jervis Liu Hi, in an attempt to build JBoss EBS in Eclipse, I found the classpath in file product\.classpath is not uptodate. The version of following jars is not updated accordingly, they should be: lib/ext/juddi-2.0rc5.jar, lib/ext/juddi-client-2.0rc5.jar, lib/ext/xstream-1.2.2.jar also the codec.jar is missing: lib/ext/commons-codec-1.3.jar Cheers, Jervis Liu -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1342) 30 character limit of tablenames in Oracle

by Kurt Stam (JIRA)

30 character limit of tablenames in Oracle ------------------------------------------ Key: JBESB-1342 URL: http://jira.jboss.com/jira/browse/JBESB-1342 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Reporter: Kurt Stam Fix For: 4.2.1 CP1 The JBossESB console needs transformationresourceparameter and transformationresourceparameterspec tables, whos names are too long (tablename length limited into 30 characters in Oracle). -- 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, 9 months

5
6
0 / 0

[JBoss JIRA] Created: (JBESB-1727) Investigate intermittent failures for JBossRemotingGatewayListenerUnitTest

by Kevin Conner (JIRA)

Investigate intermittent failures for JBossRemotingGatewayListenerUnitTest -------------------------------------------------------------------------- Key: JBESB-1727 URL: http://jira.jboss.com/jira/browse/JBESB-1727 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 Reporter: Kevin Conner Fix For: 4.4 There is an intermittent failure in the unit test, when executed on linux. This causes the test run to terminate prematurely. [java] [junit] Testcase: test took 5.128 sec [java] [junit] Tests run: 4, Failures: 0, Errors: 1, Time elapsed: 1.33 sec [java] [junit] Testsuite: org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListenerUnitTest [java] [junit] Tests run: 4, Failures: 0, Errors: 1, Time elapsed: 1.33 sec [java] [junit] ------------- Standard Output --------------- [java] [junit] EMMA: collecting runtime coverage data ... [java] [junit] Calling remoting server with locator uri of: http://build:8888 [java] [junit] ------------- ---------------- --------------- [java] [junit] Testcase: unknown took 0.163 sec [java] [junit] Testcase: unknown took 0.273 sec [java] [junit] Testcase: unknown took 0.107 sec [java] [junit] Testcase: unknown took 0.059 sec [java] [junit] Caused an ERROR [java] [junit] Unable to start Remoting Listener instsance org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener [java] [junit] org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unable to start Remoting Listener instsance org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener [java] [junit] at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener.startJBRServer(JBossRemotingGatewayListener.java:254) [java] [junit] at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener.doStart(JBossRemotingGatewayListener.java:221) [java] [junit] at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListenerUnitTest.startServer(JBossRemotingGatewayListenerUnitTest.java:199) [java] [junit] at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListenerUnitTest.test_delivery(JBossRemotingGatewayListenerUnitTest.java:157) [java] [junit] at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListenerUnitTest.test_socket_(JBossRemotingGatewayListenerUnitTest.java:153) [java] [junit] at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) [java] [junit] at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) [java] [junit] at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) [java] [junit] at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) [java] [junit] at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) [java] [junit] at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:71) [java] [junit] at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35) [java] [junit] at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) [java] [junit] at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) [java] [junit] at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) [java] [junit] at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:32) [java] [junit] Caused by: java.net.BindException: Address already in use [java] [junit] at java.net.PlainSocketImpl.socketBind(Native Method) [java] [junit] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) [java] [junit] at java.net.ServerSocket.bind(ServerSocket.java:319) [java] [junit] at java.net.ServerSocket.<init>(ServerSocket.java:185) [java] [junit] at javax.net.DefaultServerSocketFactory.createServerSocket(ServerSocketFactory.java:169) [java] [junit] at org.jboss.remoting.transport.socket.SocketServerInvoker.createServerSocket(SocketServerInvoker.java:264) [java] [junit] at org.jboss.remoting.transport.socket.SocketServerInvoker.start(SocketServerInvoker.java:193) [java] [junit] at org.jboss.remoting.transport.Connector.start(Connector.java:322) [java] [junit] at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener.startJBRServer(JBossRemotingGatewayListener.java:249) [java] [junit] ... 22 more -- 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, 9 months

1
8
0 / 0

[JBoss JIRA] Created: (JBESB-1674) Update build to support JDK6

by Kevin Conner (JIRA)

Update build to support JDK6 ---------------------------- Key: JBESB-1674 URL: http://jira.jboss.com/jira/browse/JBESB-1674 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2.1 CP2, 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP3, 4.3 We need to look at running our codebase on JDK6 as well as JDK5. As a first step we need to modify the build to allow the use of JDK6 and create hudson runs to verify. -- 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, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-1660) Improved Spring integration

by Mark Little (JIRA)

Improved Spring integration --------------------------- Key: JBESB-1660 URL: http://jira.jboss.com/jira/browse/JBESB-1660 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.2.1 CP2 Reporter: Mark Little Fix For: 4.3 -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1365) Make an Eclipse plugin for ESB configuration editor

by Mark Little (JIRA)

Make an Eclipse plugin for ESB configuration editor ---------------------------------------------------- Key: JBESB-1365 URL: http://jira.jboss.com/jira/browse/JBESB-1365 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Daniel Bevenius Fix For: 4.3 -- 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, 9 months

4
16
0 / 0

[JBoss JIRA] Created: (JBESB-498) Allow Registry registrations to include a flag to indicate whether the endpoint is message aware/unaware.

by Tom Fennelly (JIRA)

Allow Registry registrations to include a flag to indicate whether the endpoint is message aware/unaware. --------------------------------------------------------------------------------------------------------- Key: JBESB-498 URL: http://jira.jboss.com/jira/browse/JBESB-498 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2 Milestone Release 1 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.2 Milestone Release 2 This will also mean adding query capability against this. This requirement could be generalised to simply allow registrations to be decorated with attributes, and have these same attributes returned in the lookups. -- 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, 9 months

3
12
0 / 0

[JBoss JIRA] Created: (JBESB-1784) MessagePersister does not work with "RequestResponse" pipelines

by Mika Leino (JIRA)

MessagePersister does not work with "RequestResponse" pipelines --------------------------------------------------------------- Key: JBESB-1784 URL: http://jira.jboss.com/jira/browse/JBESB-1784 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Message Store Affects Versions: 4.3, 4.2.1 CP1 Environment: Windows Server 2003 Reporter: Mika Leino When adding an audit trail action to a "RequestResponse" action pipeline the message is set as null and the service causes an error. There is currently no action in the JBossESB that would allow a message to be persisted and would return the message for further processing. A TwoWay MessagePersister would eliminate this problem. -- 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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1470) Webservice QS CI tests need debugging

by Tom Cunningham (JIRA)

Webservice QS CI tests need debugging ------------------------------------- Key: JBESB-1470 URL: http://jira.jboss.com/jira/browse/JBESB-1470 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.3 The webservice* QS CI tests are excluded currently because they do not find a record after their wait period when run within the test harness. When run individually under the "ant internal-one-test" target, these tests all work fine. -- 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, 9 months

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