July 2012 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3693) Remove connections properties and tests from jbossesb-properties.xml

by Tom Cunningham (JIRA)

Remove connections properties and tests from jbossesb-properties.xml -------------------------------------------------------------------- Key: JBESB-3693 URL: https://issues.jboss.org/browse/JBESB-3693 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 The connections part of the jbossesb-properties.xml is obsoleted (found nowhere in code). Remove it from jbossesb-properties.xml files and tests, as well as the "connection" entries in ModulePropertyManager <properties name="connection"> <property name="min-pool-size" value="5"/> <property name="max-pool-size" value="10"/> <property name="blocking-timeout-millis" value="5000"/> <property name="abandoned-connection-timeout" value="10000"/> <property name="abandoned-connection-time-interval" value="30000"/> </properties> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
2
0 / 0

[JBoss JIRA] (JBESB-3754) Scout 1.2.6 causes JBRIntegratedUnitTest to fail

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3754: ------------------------------------- Summary: Scout 1.2.6 causes JBRIntegratedUnitTest to fail Key: JBESB-3754 URL: https://issues.jboss.org/browse/JBESB-3754 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 Upgrading ESB from scout 1.2.5 -> 1.2.6 causes the second test of JBRIntegratedUnitTest (test_JBESB_1428_02) to fail. The first testcase in this test passes, but once the hsql database for the first test completes, it seems like hsql has a lot of problems creating a database for the second test and running any queries. With no changes, hsql's DatabaseManager thinks the Database state is DATABASE_ONLINE rather than DATABASE_SHUTDOWN, and no hsqldb.properties or hsqldb.log files are created in product/build. Below is a stack - the HttpClientInvoker call is failing because the services for this example aren't properly registered - hsql cannot create the juddi database, and hsql is throwing SQLExceptions within hibernate with a "java.sql.SQLException: Connection is broken: java.io.EOFException". [java] -esb.services.internal.integration.test.junit: [java] [junit] Listening for transport dt_socket at address: 8787 [java] [junit] Running org.jboss.soa.esb.listeners.gateway.JBRIntegratedUnitTest [java] [junit] Testsuite: org.jboss.soa.esb.listeners.gateway.JBRIntegratedUnitTest [java] [junit] Listening for transport dt_socket at address: 8787 [java] [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 18.054 sec [java] [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 18.054 sec [java] [junit] ------------- Standard Output --------------- [java] [junit] EMMA: collecting runtime coverage data ... [java] [junit] ------------- ---------------- --------------- [java] [junit] ------------- Standard Error ----------------- [java] [junit] java.lang.NullPointerException [java] [junit] at org.hsqldb.ServerConnection.close(ServerConnection.java:170) [java] [junit] at org.hsqldb.ServerConnection.run(ServerConnection.java:273) [java] [junit] at java.lang.Thread.run(Thread.java:662) [java] [junit] java.lang.NullPointerException [java] [junit] at org.hsqldb.ServerConnection.close(ServerConnection.java:170) [java] [junit] at org.hsqldb.ServerConnection.run(ServerConnection.java:273) [java] [junit] at java.lang.Thread.run(Thread.java:662) [java] [junit] org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Connection refused. [java] [junit] at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:348) [java] [junit] at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:137) [java] [junit] at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) [java] [junit] at org.jboss.remoting.Client.invoke(Client.java:1634) [java] [junit] at org.jboss.remoting.Client.invoke(Client.java:548) [java] [junit] at org.jboss.remoting.Client.invoke(Client.java:536) [java] [junit] at org.jboss.soa.esb.listeners.gateway.JBRIntegratedUnitTest.sendMessageToServer(JBRIntegratedUnitTest.java:68) [java] [junit] at org.jboss.soa.esb.listeners.gateway.JBRIntegratedUnitTest.access$000(JBRIntegratedUnitTest.java:31) [java] [junit] at org.jboss.soa.esb.listeners.gateway.JBRIntegratedUnitTest$2.test(JBRIntegratedUnitTest.java:53) [java] [junit] at org.jboss.soa.esb.testutils.AbstractTestRunner.run(AbstractTestRunner.java:84) [java] [junit] at org.jboss.soa.esb.listeners.gateway.JBRIntegratedUnitTest.test_JBESB_1428_02(JBRIntegratedUnitTest.java:51) [java] [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] [junit] at java.lang.reflect.Method.invoke(Method.java:597) [java] [junit] at junit.framework.TestCase.runTest(TestCase.java:164) [java] [junit] at junit.framework.TestCase.runBare(TestCase.java:130) [java] [junit] at junit.framework.TestResult$1.protect(TestResult.java:106) [java] [junit] at junit.framework.TestResult.runProtected(TestResult.java:124) [java] [junit] at junit.framework.TestResult.run(TestResult.java:109) [java] [junit] at junit.framework.TestCase.run(TestCase.java:120) [java] [junit] at junit.framework.TestSuite.runTest(TestSuite.java:230) [java] [junit] at junit.framework.TestSuite.run(TestSuite.java:225) [java] [junit] at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:35) [java] [junit] at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:32) [java] [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:422) [java] [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:931) [java] [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:785) [java] [junit] Caused by: java.net.ConnectException: Connection refused [java] [junit] at java.net.PlainSocketImpl.socketConnect(Native Method) [java] [junit] at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) [java] [junit] at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) [java] [junit] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) [java] [junit] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) [java] [junit] at java.net.Socket.connect(Socket.java:529) [java] [junit] at sun.net.NetworkClient.doConnect(NetworkClient.java:158) [java] [junit] at sun.net.www.http.HttpClient.openServer(HttpClient.java:395) [java] [junit] at sun.net.www.http.HttpClient.openServer(HttpClient.java:530) [java] [junit] at sun.net.www.http.HttpClient.<init>(HttpClient.java:234) [java] [junit] at sun.net.www.http.HttpClient.New(HttpClient.java:307) [java] [junit] at sun.net.www.http.HttpClient.New(HttpClient.java:324) [java] [junit] at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:970) [java] [junit] at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911) [java] [junit] at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:836) [java] [junit] at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1014) [java] [junit] at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:277) [java] [junit] ... 27 more [java] [junit] java.lang.NullPointerException [java] [junit] at org.hsqldb.ServerConnection.close(ServerConnection.java:170) [java] [junit] at org.hsqldb.ServerConnection.run(ServerConnection.java:273) [java] [junit] at java.lang.Thread.run(Thread.java:662) [java] [junit] ------------- ---------------- --------------- [java] [junit] [java] [junit] Testcase: test_JBESB_1428_01 took 14.685 sec [java] [junit] Testcase: test_JBESB_1428_02 took 3.022 sec [java] [junit] FAILED [java] [junit] Error making JBR Client invocation. [java] [junit] junit.framework.AssertionFailedError: Error making JBR Client invocation. [java] [junit] at org.jboss.soa.esb.listeners.gateway.JBRIntegratedUnitTest.sendMessageToServer(JBRIntegratedUnitTest.java:71) [java] [junit] at org.jboss.soa.esb.listeners.gateway.JBRIntegratedUnitTest.access$000(JBRIntegratedUnitTest.java:31) [java] [junit] at org.jboss.soa.esb.listeners.gateway.JBRIntegratedUnitTest$2.test(JBRIntegratedUnitTest.java:53) [java] [junit] at org.jboss.soa.esb.testutils.AbstractTestRunner.run(AbstractTestRunner.java:84) [java] [junit] at org.jboss.soa.esb.listeners.gateway.JBRIntegratedUnitTest.test_JBESB_1428_02(JBRIntegratedUnitTest.java:51) [java] [junit] [java] [java] BUILD FAILED [java] /home/tcunning/src/jbossesb/trunkthree/product/build.xml:217: The following error occurred while executing this line: [java] /home/tcunning/src/jbossesb/trunkthree/product/rosetta/build.xml:226: The following error occurred while executing this line: [java] /home/tcunning/src/jbossesb/trunkthree/product/rosetta/tests/build.xml:242: The following error occurred while executing this line: [java] /home/tcunning/src/jbossesb/trunkthree/product/rosetta/tests/build.xml:281: The following error occurred while executing this line: [java] /home/tcunning/src/jbossesb/trunkthree/product/rosetta/tests/build.xml:294: Test org.jboss.soa.esb.listeners.gateway.JBRIntegratedUnitTest failed [java] [java] Total time: 1 minute 6 seconds [java] Java Result: 1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
3
0 / 0

[JBoss JIRA] (JBESB-3835) Only include tools.jar in soap.esb build if on Windows

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3835: ------------------------------------- Summary: Only include tools.jar in soap.esb build if on Windows Key: JBESB-3835 URL: https://issues.jboss.org/browse/JBESB-3835 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Cunningham -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
5
0 / 0

[JBoss JIRA] (JBESB-3834) test-util.jar contains duplicate class

by Kevin Conner (JIRA)

Kevin Conner created JBESB-3834: ----------------------------------- Summary: test-util.jar contains duplicate class Key: JBESB-3834 URL: https://issues.jboss.org/browse/JBESB-3834 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kevin Conner -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
4
0 / 0

[JBoss JIRA] (JBESB-3833) Lifecycle resources need to handle redeploy using same ClassLoader

by Kevin Conner (JIRA)

Kevin Conner created JBESB-3833: ----------------------------------- Summary: Lifecycle resources need to handle redeploy using same ClassLoader Key: JBESB-3833 URL: https://issues.jboss.org/browse/JBESB-3833 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.11 Reporter: Kevin Conner Fix For: 4.11 CP1 ESB artifacts can go through a redeployment (stop, destroy, create, start) without replacing the ClassLoader. As such the lifecycle resources will be marked as destroyed and will no longer be usable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
5
0 / 0

[JBoss JIRA] (JBESB-3830) Add ActionHandler equivalent and correlation checks to jbpm5 integration

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3830: ------------------------------------- Summary: Add ActionHandler equivalent and correlation checks to jbpm5 integration Key: JBESB-3830 URL: https://issues.jboss.org/browse/JBESB-3830 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Cunningham -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
10
0 / 0

[JBoss JIRA] (JBESB-3745) JON event logging / ESB MVEL action

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3745: ------------------------------------- Summary: JON event logging / ESB MVEL action Key: JBESB-3745 URL: https://issues.jboss.org/browse/JBESB-3745 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.11 Reporter: Tom Cunningham Fix For: 4.11 Investigate the creation of a custom log which will then be fed into JON through the event stream. Try to see what sort of filtering and aggregation that JON provides that will allow us to provide a nicer view than just the log entry (i.e. X number of events within the past 3 hours, whether we can trigger notifications off of groups of events, etc). Possibly add an additional Quickstart around this area. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
5
0 / 0

[JBoss JIRA] (JBESB-3793) Make jbpm5.esb optional install, upgrade to jbpm 5.3.0.CR1

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3793: ------------------------------------- Summary: Make jbpm5.esb optional install, upgrade to jbpm 5.3.0.CR1 Key: JBESB-3793 URL: https://issues.jboss.org/browse/JBESB-3793 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.11 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP1 Make jbpm5.esb optional install, upgrade to jbpm 5.3.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
2
0 / 0

[JBoss JIRA] (JBESB-3708) XsltAction cannot handle org.w3c.dom.Document

by David Tucker (Created) (JIRA)

XsltAction cannot handle org.w3c.dom.Document --------------------------------------------- Key: JBESB-3708 URL: https://issues.jboss.org/browse/JBESB-3708 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.10 Reporter: David Tucker Currently the XsltAction can handle the following objects: String, byte[], Reader, InputStream, File, or Source The output from the XsltAction, when choosing DOM, is an object that implements the interface org.w3c.dom.Document. The action can't accept the document it created to run another transformation on it. While this scenario is remote at best, it is not unlikely that we would want to run a transformation on a Document. I was able to create a custom action that would allow me to put a Document into a DOMSource object. This requires extra work anytime I want to use a Document in an XSLT and the Document interface should be an accepted way of sending a document to be transformed. The following code was all it took in my custom action: DOMSource domSource = new DOMSource(); domSource.setNode(doc.getFirstChild()); //doc is an object implementing org.w3c.dom.Document -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

7
15
0 / 0

[JBoss JIRA] (JBESB-3832) Eliminate double quotes in interceptor section of jbossesb-properties.xml

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3832: ------------------------------------- Summary: Eliminate double quotes in interceptor section of jbossesb-properties.xml Key: JBESB-3832 URL: https://issues.jboss.org/browse/JBESB-3832 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Cunningham -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2012