August 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1922) embedded-console needs java.awt.headless=true

by Tom Cunningham (JIRA)

embedded-console needs java.awt.headless=true --------------------------------------------- Key: JBESB-1922 URL: https://jira.jboss.org/jira/browse/JBESB-1922 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Cunningham The JON embedded-console requires java.awt.headless=true in the JAVA_OPTS - see JBMANCON-364. We'll need to add this to run.sh and run.bat. -- 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

14 years, 12 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-2427) UDDIv3 support

by Mark Little (JIRA)

UDDIv3 support -------------- Key: JBESB-2427 URL: https://jira.jboss.org/jira/browse/JBESB-2427 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Reporter: Mark Little Priority: Critical Fix For: 4.6 We'd like this for SOA-P 5.0, so this may not be in ESB 4.6 but a later 4.x release. -- 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

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2536) jUDDI local transport creates a new thread to handle every individual request

by Kevin Conner (JIRA)

jUDDI local transport creates a new thread to handle every individual request ----------------------------------------------------------------------------- Key: JBESB-2536 URL: https://jira.jboss.org/jira/browse/JBESB-2536 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 There are two classes used in jUDDI for local communication, org.apache.juddi.registry.local.InquiryService and org.apache.juddi.registry.local.PublishService. Every request passing through these classes, and there are many, results in the creation of a thread as follows Thread thread = new Thread(requestHandler, "WorkThread"); thread.start(); thread.join(); This has a big impact on performance. -- 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

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-2065) JMSGatewayListener: Add support for missing JMS Message types

by Tom Fennelly (JIRA)

JMSGatewayListener: Add support for missing JMS Message types ------------------------------------------------------------- Key: JBESB-2065 URL: https://jira.jboss.org/jira/browse/JBESB-2065 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 Reporter: Tom Fennelly Fix For: 4.x It's missing support for some of the JMS Message types e.g. MapMessage. Should support them all. -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2787) jbpm.esb causes AS 5 server to sometimes hang upon shutdown.

by Daniel Bevenius (JIRA)

jbpm.esb causes AS 5 server to sometimes hang upon shutdown. ------------------------------------------------------------- Key: JBESB-2787 URL: https://jira.jboss.org/jira/browse/JBESB-2787 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.7 Reporter: Daniel Bevenius The application server does not close down, well it hangs for a long while before finishing. Console log (a few mins after the thread dump) ============================================= 16:54:33,395 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_40] - Abort called on already aborted atomic action 7f000001:a6d0:4a82d3c0:3cb 16:54:33,395 ERROR [STDERR] Exception in thread "JbpmJobExector:127.0.0.1:1" 16:54:33,395 ERROR [STDERR] java.lang.StackOverflowError 16:54:33,400 ERROR [STDERR] at java.lang.Class.isPrimitive(Native Method) 16:54:33,400 ERROR [STDERR] at java.lang.Class.getEnclosingMethodInfo(Class.java:923) 16:54:33,400 ERROR [STDERR] at java.lang.Class.getEnclosingClass(Class.java:1077) 16:54:33,400 ERROR [STDERR] at java.lang.Class.getSimpleBinaryName(Class.java:1216) 16:54:33,401 ERROR [STDERR] at java.lang.Class.getSimpleName(Class.java:1108) 16:54:33,401 ERROR [STDERR] at org.jboss.classloader.spi.base.BaseClassLoader.toString(BaseClassLoader.java:926) 16:54:33,401 ERROR [STDERR] at java.lang.String.valueOf(String.java:2615) 16:54:33,401 ERROR [STDERR] at java.lang.StringBuilder.append(StringBuilder.java:116) 16:54:33,401 ERROR [STDERR] at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:138) 16:54:33,401 ERROR [STDERR] at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:620) 16:54:33,401 ERROR [STDERR] at org.jboss.system.JBossRMIClassLoader.loadClass(JBossRMIClassLoader.java:91) 16:54:33,401 ERROR [STDERR] at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:247) 16:54:33,401 ERROR [STDERR] at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:197) 16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544) 16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466) 16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699) 16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) 16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1634) 16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) 16:54:33,401 ERROR [STDERR] at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) 16:54:33,402 ERROR [STDERR] at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) 16:54:33,402 ERROR [STDERR] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) 16:54:33,402 ERROR [STDERR] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) 16:54:33,402 ERROR [STDERR] at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) 16:54:33,402 ERROR [STDERR] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215) 16:54:33,402 ERROR [STDERR] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126) 16:54:33,402 ERROR [STDERR] at org.jnp.server.NamingServer_Stub.lookup(Unknown Source) 16:54:33,402 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726) 16:54:33,402 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686) 16:54:33,402 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialContext.java:351) 16:54:33,402 ERROR [STDERR] at org.hibernate.transaction.JTATransactionFactory.getUserTransaction(JTATransactionFactory.java:162) 16:54:33,402 ERROR [STDERR] at org.hibernate.transaction.JTATransactionFactory.getUserTransaction(JTATransactionFactory.java:172) 16:54:33,402 ERROR [STDERR] at org.hibernate.transaction.JTATransactionFactory.getUserTransaction(JTATransactionFactory.java:172) 16:54:33,402 ERROR [STDERR] at org.hibernate.transaction.JTATransactionFactory.getUserTransaction(JTATransactionFactory.java:172) ... 16:54:33,996 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=JbpmDS' from JNDI name 'java:JbpmDS' 16:54:34,044 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down. 16:54:34,044 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED paused. 16:54:34,045 INFO [SimpleThreadPool] There are still 35 worker threads active. See javadoc runInThread(Runnable) for a possible explanation 16:54:34,045 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutdown complete. 16:54:34,528 INFO [TransactionManagerService] Stopping transaction recovery manager 16:54:34,530 INFO [TransactionManagerService] Destroying TransactionManagerService 16:54:34,685 INFO [HypersonicDatabase] Database standalone closed clean 16:54:38,218 INFO [DefaultEndpointRegistry] remove: jboss.ws:context=Quickstart_webservice_consumer2,endpoint=OrderProcessorWS 16:54:38,402 INFO [HypersonicDatabase] Database standalone closed clean 16:54:38,661 INFO [H2Database] Database standalone closed clean 16:54:48,022 INFO [ServerImpl] Shutdown complete Shutdown complete Halting VM Complete log will be attached with a thread dump. I found this jira: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3481 The version of hibernate that is shipped with AS 5.1.0.GA is 3.3.1. Perhaps an upgrade to 3.3.2 will take care of the issue with the hang, though I still think that we will in that case get an exception. Should the jbpm.esb/jbpm-service.xml's JbpmService depend on the TransactionManager?: <mbean code="org.jboss.soa.esb.services.jbpm.configuration.JbpmService" name="jboss.esb:service=JbpmService"> <depends>jboss.esb:service=JBPMDatabaseInitializer</depends> <depends>jboss:service=TransactionManager</depends> </mbean> Lets say the TransactionManager sometimes gets deployed before the jbpm.esb, then this would probably trigger this issue. Sort of difficult to test this as this does not happen every time. -- 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

2
19
0 / 0

[JBoss JIRA] Created: (JBESB-2093) Unexpected error from doRun() - java.util.concurrent.RejectedExecutionException during running manual cluster/failover tests.

by Pavel Macik (JIRA)

Unexpected error from doRun() - java.util.concurrent.RejectedExecutionException during running manual cluster/failover tests. ----------------------------------------------------------------------------------------------------------------------------- Key: JBESB-2093 URL: https://jira.jboss.org/jira/browse/JBESB-2093 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 CP1 Reporter: Pavel Macik Assignee: Kevin Conner Running manual cluster/filover test following the http://jboss-wiki.brq.redhat.com/Cluster/failover_tests and when I delete a *.esb archive (step 15 or 17) the exception arises. -- 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, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2785) Add synchronous service invocation action

by Kevin Conner (JIRA)

Add synchronous service invocation action ----------------------------------------- Key: JBESB-2785 URL: https://jira.jboss.org/jira/browse/JBESB-2785 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.6 Reporter: Kevin Conner Fix For: 4.7 Add an action to invoke an ESB service synchronously. It should be made clear in the documentation that this can only be used when there is no active transaction and that asynchronous invocations are to be preferred for reasons of performance/scaling. -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1810) There is no retry limit when using transacted SQL listener

by Jiri Pechanec (JIRA)

There is no retry limit when using transacted SQL listener ---------------------------------------------------------- Key: JBESB-1810 URL: http://jira.jboss.com/jira/browse/JBESB-1810 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Environment: FC8/PostgreSQL Reporter: Jiri Pechanec Assigned To: Kevin Conner Priority: Critical Fix For: 4.2.1 CP4 If the SQL listener is used and set to support transactions and an exception is thrown in pipeline the transaction is rolled back and the message is put back for processing. Unfortunately there is no retry limit so the same message is executed again and again and in case of more messages the performance goes down. There should be something like retry counter that after few unsuccessful execution will put the message to DLQ. -- 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, 1 month

5
19
0 / 0

[JBoss JIRA] Created: (JBESB-2585) Add management alerting mechanism

by Kevin Conner (JIRA)

Add management alerting mechanism --------------------------------- Key: JBESB-2585 URL: https://jira.jboss.org/jira/browse/JBESB-2585 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Tom Cunningham Fix For: 4.6 Add a mechanism whereby alerts can be specified based on the processing time or size of messages being processed. -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2440) Use JBoss tModel when saving bindings and services

by Tom Cunningham (JIRA)

Use JBoss tModel when saving bindings and services -------------------------------------------------- Key: JBESB-2440 URL: https://jira.jboss.org/jira/browse/JBESB-2440 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.5 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.6 Use the JBoss tModel when saving services and service bindings. -- 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, 1 month

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 2009