October 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1177) Console tools contain old version of drools

by Kevin Conner (JIRA)

Console tools contain old version of drools ------------------------------------------- Key: JBESB-1177 URL: http://jira.jboss.com/jira/browse/JBESB-1177 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2.1 IR2 Reporter: Kevin Conner Assigned To: Mark Little Priority: Minor Fix For: 4.2.1 We need to find out why this is included and remove if possible. -- 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, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-1003) jBPM log facilities are not properly configured in some cases

by Jiri Pechanec (JIRA)

jBPM log facilities are not properly configured in some cases ------------------------------------------------------------- Key: JBESB-1003 URL: http://jira.jboss.com/jira/browse/JBESB-1003 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Process flow Affects Versions: 4.2 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Minor When stopping ESB, the following error messages are printed to console 08:48:12,833 ERROR [STDERR] java.lang.NullPointerException 08:48:12,855 ERROR [STDERR] at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:82) The problem is that log facility is set to null. The JBMP internaly uses commons logging which apparently is not properly configured at least for this instance. Moreover the error happends when another exception has to be logged - this can contain another problem. -- 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, 8 months

6
12
0 / 0

[JBoss JIRA] Created: (JBESB-1240) ObjectToZStream, add support for namespaces.

by Daniel Bevenius (JIRA)

ObjectToZStream, add support for namespaces. -------------------------------------------- Key: JBESB-1240 URL: http://jira.jboss.com/jira/browse/JBESB-1240 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Minor Add support so that namespaces can be configured for ObjectToXstream -- 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, 8 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-1185) XStreamToObject. Add support for Atribute aliases and enum types

by Daniel Bevenius (JIRA)

XStreamToObject. Add support for Atribute aliases and enum types ---------------------------------------------------------------- Key: JBESB-1185 URL: http://jira.jboss.com/jira/browse/JBESB-1185 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Minor When using attributes in xml they are left empty after xstream has converted the xml to a java object model. The same goes for enums 1. Add support to configure attribute aliases including supporting SimpleValueConverter. 2. Add support for enum types. -- 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, 8 months

1
7
0 / 0

[JBoss JIRA] Created: (JBESB-1212) bpm_orchestration : deployProcess should be cleaner

by Tom Cunningham (JIRA)

bpm_orchestration : deployProcess should be cleaner --------------------------------------------------- Key: JBESB-1212 URL: http://jira.jboss.com/jira/browse/JBESB-1212 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR2 Reporter: Tom Cunningham Assigned To: Mark Little Fix For: 4.2.1 In bpm_orchestration3 (and I think in the other bpm_orchestration examples) deployProcess depends on the appserver running to work correctly. If we deployProcess gets a java.naming.CommunicationException, we should catch it and throw a log message telling the user that they need to start their app server. Here's the exception thrown if the app server isn't running: deployProcess: [echo] Sends a message to deploy the process definition [java] javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]] [java] Exception in thread "main" java.lang.NullPointerException [java] at org.jboss.soa.esb.samples.quickstart.bpm_orchestration3.test.SendJMSMessage.stop(SendJMSMessage.java:52) [java] at org.jboss.soa.esb.samples.quickstart.bpm_orchestration3.test.SendJMSMessage.main(SendJMSMessage.java:80) -- 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, 8 months

5
5
0 / 0

[JBoss JIRA] Created: (JBESB-1265) Using DSL XPathLanguage requires explicit imports in CBR DRL files

by Jiri Pechanec (JIRA)

Using DSL XPathLanguage requires explicit imports in CBR DRL files ------------------------------------------------------------------ Key: JBESB-1265 URL: http://jira.jboss.com/jira/browse/JBESB-1265 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.2.1 IR2 Reporter: Jiri Pechanec Assigned To: Mark Little Fix For: 4.2.1 triage The XPathLanguage.dsl uses not fully qualified type names. It means that if this file is in use the using DRL file must import those types. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-719) The messages can be lost in case of ESB termination

by Jiri Pechanec (JIRA)

The messages can be lost in case of ESB termination --------------------------------------------------- Key: JBESB-719 URL: http://jira.jboss.com/jira/browse/JBESB-719 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little Even if the ESB is using internally reliable JMS as a transport the messages can be lost during ESB termination. The reasons for this behaviour are two 1) ESB uses internally queue sessions with AUTO_ACK flag 2) Pick-up and deliver couriers works in different session Proposed solution 1) Change flag to CLIENT_ACK 2) JMS sessions are allocated from the pool using JMSConnectionPool.getQueueSession(). If the allocated session is stored into ThreadLocal variable and returned by the subsequent calls by the same thread and get commited on call JMSConnectionPool.closeSession() then all internal message transfers via JMS will be done in transaction - one transfer/one transaction. -- 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, 8 months

4
10
0 / 0

[JBoss JIRA] Created: (JBESB-1106) Need a console page displaying both operations and properties per object

by Tom Cunningham (JIRA)

Need a console page displaying both operations and properties per object ------------------------------------------------------------------------ Key: JBESB-1106 URL: http://jira.jboss.com/jira/browse/JBESB-1106 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2 Reporter: Tom Cunningham Assigned To: Tom Cunningham Need a console page that displays both properties and operations on one page, per object. Currently, monitoring and management are split out from each other - it'd be nice if you could go to one place like in jmx-console. -- 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, 8 months

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-1035) jbpm admin console throws exceptions on shutdown of App Server/ESB Server

by Burr Sutter (JIRA)

jbpm admin console throws exceptions on shutdown of App Server/ESB Server ------------------------------------------------------------------------- Key: JBESB-1035 URL: http://jira.jboss.com/jira/browse/JBESB-1035 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2.1 IR1 12:08:56,040 ERROR [JDBCExceptionReporter] You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.; - nested throwable: (javax.resource.ResourceException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is nul l.) 12:08:56,041 ERROR [JobExecutorThread] exception in job executor thread. waiting 5000 milliseconds org.hibernate.exception.GenericJDBCException: Cannot open connection at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.j ava:103) -- 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, 8 months

5
7
0 / 0

[JBoss JIRA] Created: (JBESB-1253) Aggregator should be using the ServiceInvoker

by Kurt Stam (JIRA)

Aggregator should be using the ServiceInvoker --------------------------------------------- Key: JBESB-1253 URL: http://jira.jboss.com/jira/browse/JBESB-1253 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Reporter: Kurt Stam Assigned To: Mark Little Fix For: 4.2.1 triage The aggregator is still using the Couriers directly. We should use the ServiceInvoker instead. -- 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, 8 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 October 2007