July 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1855) Upper / lower case problems in SqlTableGatewayListener

by Tom Cunningham (JIRA)

Upper / lower case problems in SqlTableGatewayListener ------------------------------------------------------ Key: JBESB-1855 URL: http://jira.jboss.com/jira/browse/JBESB-1855 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.3 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.4 There are a few upper/lower case problems in trunk in SqlTableGatewayListener, where we are either looking for the upper-cased column name but try to find the lower-cased version, or we are looking for the lower cased version and send in the upper-cased version. The Quickstart only uses upper-cased column names (something we should probably change), so these problems likely did not show up during integration testing. A workaround for now for users would be to use all upper-case letters in their column names in jboss-esb.xml. I don't see this problem in CP branch. Index: src/org/jboss/soa/esb/listeners/gateway/SqlTableGatewayListener.java =================================================================== --- src/org/jboss/soa/esb/listeners/gateway/SqlTableGatewayListener.java (revision 20835) +++ src/org/jboss/soa/esb/listeners/gateway/SqlTableGatewayListener.java (working copy) @@ -663,7 +663,7 @@ if (_currentRow.containsKey(sColName)) { val = String.valueOf(_currentRow.get(sColName)); } else { - val = String.valueOf(_upperCurrentRow.get(sColName)); + val = String.valueOf(_upperCurrentRow.get(sColName.toUpperCase())); } _PSdeleteRow.setString(iParm++, val); } @@ -740,7 +740,7 @@ for (String sColName : _keys) { Object oVal = null; if (_currentRow.containsKey(sColName)) { - oVal = String.valueOf(_currentRow.get(sColName.toUpperCase())); + oVal = String.valueOf(_currentRow.get(sColName)); } else { oVal = String.valueOf(_upperCurrentRow.get(sColName.toUpperCase())); } -- 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

16 years, 5 months

2
2
0 / 0

[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

16 years, 5 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

16 years, 5 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

16 years, 5 months

5
6
0 / 0

[JBoss JIRA] Created: (JBESB-1832) Remove transform_* quickstarts that use Smooks Profiling

by Tom Fennelly (JIRA)

Remove transform_* quickstarts that use Smooks Profiling -------------------------------------------------------- Key: JBESB-1832 URL: http://jira.jboss.com/jira/browse/JBESB-1832 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.3 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.4 Will add a list of them as a comment. -- 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

16 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1831) Upgrade the transform_* quickstarts to use the SmooksAction (Vs the SmooksTransformer)

by Tom Fennelly (JIRA)

Upgrade the transform_* quickstarts to use the SmooksAction (Vs the SmooksTransformer) -------------------------------------------------------------------------------------- Key: JBESB-1831 URL: http://jira.jboss.com/jira/browse/JBESB-1831 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.3 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.4 -- 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

16 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1868) business_ruleservice_ruleAgent quickstart path filtering (Ant) for the rule agent config file breaks on Windows

by Tom Fennelly (JIRA)

business_ruleservice_ruleAgent quickstart path filtering (Ant) for the rule agent config file breaks on Windows --------------------------------------------------------------------------------------------------------------- Key: JBESB-1868 URL: http://jira.jboss.com/jira/browse/JBESB-1868 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.3 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.4 -- 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

16 years, 5 months

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

16 years, 5 months

1
8
0 / 0

[JBoss JIRA] Created: (JBESB-1867) Merge CP3/FP2 updates across to trunk

by Kevin Conner (JIRA)

Merge CP3/FP2 updates across to trunk ------------------------------------- Key: JBESB-1867 URL: http://jira.jboss.com/jira/browse/JBESB-1867 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.3 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.4 -- 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

16 years, 5 months

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

16 years, 5 months

3
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2008