August 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1876) Generate PDFs before release

by Kevin Conner (JIRA)

Generate PDFs before release ---------------------------- Key: JBESB-1876 URL: https://jira.jboss.org/jira/browse/JBESB-1876 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 Reporter: 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: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1899) Test failures in CI environments

by Kevin Conner (JIRA)

Test failures in CI environments -------------------------------- Key: JBESB-1899 URL: https://jira.jboss.org/jira/browse/JBESB-1899 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 Something is not cleaning up correctly in the current builds. Both windows machines have just failed because the database cannot listen on the correct port [java] [junit] java.net.BindException: Address already in use: JVM_Bind [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 java.net.ServerSocket.<init>(ServerSocket.java:97) [java] [junit] at org.hsqldb.HsqlSocketFactory.createServerSocket(Unknown Source) [java] [junit] at org.hsqldb.Server.openServerSocket(Unknown Source) [java] [junit] at org.hsqldb.Server.run(Unknown Source) [java] [junit] at org.hsqldb.Server.access$000(Unknown Source) [java] [junit] at org.hsqldb.Server$ServerThread.run(Unknown Source) followed by [java] [junit] java.sql.SQLException: socket creation error [java] [junit] at org.hsqldb.jdbc.Util.sqlException(Unknown Source) [java] [junit] at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source) [java] [junit] at org.hsqldb.jdbcDriver.getConnection(Unknown Source) [java] [junit] at org.hsqldb.jdbcDriver.connect(Unknown Source) [java] [junit] at java.sql.DriverManager.getConnection(DriverManager.java:582) [java] [junit] at java.sql.DriverManager.getConnection(DriverManager.java:185) [java] [junit] at org.jboss.soa.esb.listeners.ListenerManagerBaseTest.runBeforeAllTests(ListenerManagerBaseTest.java:193) [java] [junit] at org.jboss.soa.esb.listeners.ListenerManagerFileUnitTest.setUp(ListenerManagerFileUnitTest.java:76) The linux box has an old application server process running (although seems to be passing) Hudson has just failed because of a JBossRemotingGatewayListener failure (again) [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:271) [java] [junit] at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener.doStart(JBossRemotingGatewayListener.java:234) [java] [junit] at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListenerUnitTest.test_lifecycle(JBossRemotingGatewayListenerUnitTest.java:136) [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.io.IOException: Address already in use:8887 [java] [junit] at org.jboss.remoting.transport.coyote.CoyoteInvoker.start(CoyoteInvoker.java:244) [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:262) -- 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, 9 months

1
7
0 / 0

[JBoss JIRA] Created: (JBESB-1898) Generate release notes and update document versions to 4.4 GA.

by Kevin Conner (JIRA)

Generate release notes and update document versions to 4.4 GA. -------------------------------------------------------------- Key: JBESB-1898 URL: https://jira.jboss.org/jira/browse/JBESB-1898 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 Reporter: Kevin Conner Assignee: 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: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1675) Possible Juddi Performance problems

by Tom Cunningham (JIRA)

Possible Juddi Performance problems ----------------------------------- Key: JBESB-1675 URL: http://jira.jboss.com/jira/browse/JBESB-1675 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2.1 Reporter: Tom Cunningham Assigned To: Tom Cunningham >From forum post : We are not using juddi directly, I do not know if it is a core required component of ESB. After a few runs, we are having performance problems that seems to be related to juddi. It happens only on shutdow/startup operations. The time spent to create the auth tokens (sorry, what are they used for anyway??) are taking longer and longer. JBoss takes over 2 minutes (in a 8 processor machine??) just to delete the template bindings for juddi on the shutdown process. -- 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, 9 months

5
19
0 / 0

[JBoss JIRA] Created: (JBESB-1896) InVM transaction resource causes heuristic exceptions

by Kevin Conner (JIRA)

InVM transaction resource causes heuristic exceptions ----------------------------------------------------- Key: JBESB-1896 URL: https://jira.jboss.org/jira/browse/JBESB-1896 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Priority: Critical Fix For: 4.4 The logic in the resource is wrong and will cause heuristic exception to be raised. -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1717) Support additional naming properties in JMS EPRs

by Kevin Conner (JIRA)

Support additional naming properties in JMS EPRs ------------------------------------------------ Key: JBESB-1717 URL: http://jira.jboss.com/jira/browse/JBESB-1717 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Reporter: Kevin Conner Fix For: 4.3, 4.4 Some JNDI providers require the specification of other properties in addition to the normal JNDI properties but, at present, we are restricting their inclusion. One example of this is SonicMQ which also requires properties such as com.sonicsw.jndi.mfcontext.domain and com.sonicsw.jndi.mfcontext.idleTimeout. We need to extend the JMS EPR so that it can include the specification of additional properties but without including all extensions. -- 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, 9 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2008