July 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1886) Update wise-core jar file

by Kevin Conner (JIRA)

Update wise-core jar file ------------------------- Key: JBESB-1886 URL: https://jira.jboss.org/jira/browse/JBESB-1886 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Stefano Maestri Fix For: 4.4 There is a concurrency issue in wise-core.jar that needs an update. -- 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

16 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1874) Merge the wise SOAP client work

by Kevin Conner (JIRA)

Merge the wise SOAP client work ------------------------------- Key: JBESB-1874 URL: https://jira.jboss.org/jira/browse/JBESB-1874 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.4 Stefano has been working on a SOAP client using wise, we should pull this into the release as an alternative to SOAPClient. -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1778) H2 remote database shutdown fails, STOP_SERVER not found

by Kevin Conner (JIRA)

H2 remote database shutdown fails, STOP_SERVER not found -------------------------------------------------------- Key: JBESB-1778 URL: http://jira.jboss.com/jira/browse/JBESB-1778 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2.1 CP2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP3 15:07:30,669 WARN [H2Database] Stopping failed jboss:service=HelloworldTxSqlDB org.h2.jdbc.JdbcSQLException: Function STOP_SERVER not found; SQL statement: CALL STOP_SERVER(?, ?, ?) [90022-68] -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1749) JMSCourier should protect against clean session in jmsConnectRetry

by Kevin Conner (JIRA)

JMSCourier should protect against clean session in jmsConnectRetry ------------------------------------------------------------------ Key: JBESB-1749 URL: http://jira.jboss.com/jira/browse/JBESB-1749 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 CP2, 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.3, 4.2.1 CP3 -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1698) SOA-P/ESB with IBM MQ 6 = javax.naming.NotContextException

by Len DiMaggio (JIRA)

SOA-P/ESB with IBM MQ 6 = javax.naming.NotContextException ---------------------------------------------------------- Key: JBESB-1698 URL: http://jira.jboss.com/jira/browse/JBESB-1698 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2.1 CP2 Reporter: Len DiMaggio Assigned To: Kevin Conner Project JIRA for SOA-P JIRA: http://jira.jboss.com/jira/browse/SOA-535 See user forum post for details: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=134669 -- 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, 4 months

3
9
0 / 0

[JBoss JIRA] Created: (JBESB-1873) JBoss messaging threads can still be created as non-daemon

by Kevin Conner (JIRA)

JBoss messaging threads can still be created as non-daemon ---------------------------------------------------------- Key: JBESB-1873 URL: https://jira.jboss.org/jira/browse/JBESB-1873 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 CP3, 4.3 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.2.1 CP4, 4.4 There is scenario in which the workaround for JBESB-1799 does not catch the JBoss Messaging thread creation. An example thread is as follows. Thread [main] (Suspended (breakpoint at line 290 in java.lang.Thread)) java.lang.Thread.init(java.lang.ThreadGroup, java.lang.Runnable, java.lang.String, long) line: 290 java.lang.Thread.<init>(java.lang.Runnable) line: 371 EDU.oswego.cs.dl.util.concurrent.ThreadFactoryUser$DefaultThreadFactory.newThread(java.lang.Runnable) line: 30 org.jboss.messaging.util.JBMExecutor(EDU.oswego.cs.dl.util.concurrent.QueuedExecutor).restart() line: 141 org.jboss.messaging.util.JBMExecutor(EDU.oswego.cs.dl.util.concurrent.QueuedExecutor).execute(java.lang.Runnable) line: 157 org.jboss.messaging.util.JBMExecutor.execute(java.lang.Runnable) line: 89 org.jboss.jms.client.container.ClientConsumer.waitForOnMessageToComplete() line: 699 org.jboss.jms.client.container.ClientConsumer.close(long) line: 363 org.jboss.jms.client.container.ConsumerAspect.handleClosing(org.jboss.aop.joinpoint.Invocation) line: 147 org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect53.invoke(org.jboss.aop.joinpoint.Invocation) line: not available org.jboss.jms.client.delegate.ClientConsumerDelegate$closing_2473194355759371067.invokeNext() line: not available org.jboss.jms.client.container.FailoverValveInterceptor.invoke(org.jboss.aop.joinpoint.Invocation) line: 92 org.jboss.aop.advice.PerInstanceInterceptor.invoke(org.jboss.aop.joinpoint.Invocation) line: 105 org.jboss.jms.client.delegate.ClientConsumerDelegate$closing_2473194355759371067.invokeNext() line: not available org.jboss.jms.client.container.ClosedInterceptor.invoke(org.jboss.aop.joinpoint.Invocation) line: 170 org.jboss.aop.advice.PerInstanceInterceptor.invoke(org.jboss.aop.joinpoint.Invocation) line: 105 org.jboss.jms.client.delegate.ClientConsumerDelegate$closing_2473194355759371067.invokeNext() line: not available org.jboss.jms.client.delegate.ClientConsumerDelegate.closing(long) line: not available org.jboss.jms.client.JBossMessageConsumer.close() line: 96 org.jboss.internal.soa.esb.couriers.JmsCourier.cleanup() line: 114 org.jboss.soa.esb.couriers.CourierUtil.cleanCourier(org.jboss.internal.soa.esb.couriers.PickUpOnlyCourier) line: 244 org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.cleanup() line: 249 org.jboss.soa.esb.couriers.CourierUtil.cleanCourier(org.jboss.soa.esb.couriers.TwoWayCourier) line: 276 org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDelivery(org.jboss.soa.esb.message.Message, org.jboss.soa.esb.addressing.EPR) line: 574 org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.access$200(org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker, org.jboss.soa.esb.message.Message, org.jboss.soa.esb.addressing.EPR) line: 452 org.jboss.soa.esb.client.ServiceInvoker.post(org.jboss.soa.esb.message.Message, org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker) line: 318 org.jboss.soa.esb.client.ServiceInvoker.deliverSync(org.jboss.soa.esb.message.Message, long) line: 198 org.jboss.soa.esb.samples.quickstart.timeout.test.SendEsbMessage.main(java.lang.String[]) line: 56 -- 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

16 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1885) Update helloworld_ftp quickstart to use H2.

by Daniel Bevenius (JIRA)

Update helloworld_ftp quickstart to use H2. ------------------------------------------- Key: JBESB-1885 URL: https://jira.jboss.org/jira/browse/JBESB-1885 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Daniel Bevenius Fix For: 4.x When the quickstart is deployed with 'ant deploy-readonly' the following deployment error is thrown: 07:39:23,062 ERROR [JDBCCacheLoader] Failed to get connection for url=jdbc:hsqldb:hsql://localhost:9001/ftpcache, user=sa, password= java.sql.SQLException: socket creation error at org.hsqldb.jdbc.Util.sqlException(Unknown Source) at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source) at org.hsqldb.jdbcDriver.getConnection(Unknown Source) at org.hsqldb.jdbcDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:525) at java.sql.DriverManager.getConnection(DriverManager.java:171) at org.jboss.cache.loader.JDBCCacheLoader$NonManagedConnectionFactory.getConnection(JDBCCacheLoader.java:1459) at org.jboss.cache.loader.JDBCCacheLoader.start(JDBCCacheLoader.java:753) at org.jboss.cache.loader.CacheLoaderManager.startCacheLoader(CacheLoaderManager.java:353) at org.jboss.cache.TreeCache.startService(TreeCache.java:1535) at org.jboss.soa.esb.listeners.gateway.remotestrategies.cache.FtpFileCache.start(FtpFileCache.java:130) at org.jboss.soa.esb.listeners.gateway.remotestrategies.ReadOnlyRemoteFileSystemStrategy.init(ReadOnlyRemoteFileSystemStrategy.java:59) at org.jboss.soa.esb.listeners.gateway.ReadOnlyRemoteGatewayListener.createRemoteFileSystemStrategy(ReadOnlyRemoteGatewayListener.java:205) at org.jboss.soa.esb.listeners.gateway.ReadOnlyRemoteGatewayListener.<init>(ReadOnlyRemoteGatewayListener.java:83) -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1777) helloworld_tx_sql_action 'Database already closed' error

by Kevin Conner (JIRA)

helloworld_tx_sql_action 'Database already closed' error -------------------------------------------------------- Key: JBESB-1777 URL: http://jira.jboss.com/jira/browse/JBESB-1777 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP3 The quickstart ds.xml does not specify the DB_CLOSE_ON_EXIT flag which is needed on the first connection in order to prevent the h2 shutdown hook from prematurely closing the DB. org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-68] -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1839) Missing dependency for queue/OperationsCollectorQueue in jbossesb.esb

by Len DiMaggio (JIRA)

Missing dependency for queue/OperationsCollectorQueue in jbossesb.esb --------------------------------------------------------------------- Key: JBESB-1839 URL: http://jira.jboss.com/jira/browse/JBESB-1839 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2.1 CP2 Reporter: Len DiMaggio Project issue for SOA-P JIRA-589 -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1821) JmsCourier holds JNDI contexts over calls to JmsConnectionPool

by Kevin Conner (JIRA)

JmsCourier holds JNDI contexts over calls to JmsConnectionPool -------------------------------------------------------------- Key: JBESB-1821 URL: http://jira.jboss.com/jira/browse/JBESB-1821 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP3 Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Blocker Fix For: 4.2.1 CP3 The JmsCourier obtains a naming context from the pool but, before it has used it, makes a call to the JmsConnectionPool. The result of this is that there are now two naming contexts being obtained in the same thread. This is a problem if you have already used up all the contexts, for example if you had 20 JmsCouriers with a context trying to obtain their JmsSession (no more contexts). This will cause the first thread to deadlock for 30 seconds (the current timeout) and possibly others before the contexts have been released. The JmsCourier should not be holding the naming context for longer than is necessary, we need to reduce the scope. -- 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, 4 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2008