November 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2202) WARNING on OracleDialect used with Management console

by Kevin Conner (JIRA)

WARNING on OracleDialect used with Management console ----------------------------------------------------- Key: JBESB-2202 URL: https://jira.jboss.org/jira/browse/JBESB-2202 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 CP3 Reporter: Kevin Conner Assignee: Tom Cunningham Fix For: 4.2.1 CP4 4.2.1 CP project issue for SOA-857. -- 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

17 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1164) Crash creates multiple EPRs for same service in JUDDI

by Tom Cunningham (JIRA)

Crash creates multiple EPRs for same service in JUDDI ----------------------------------------------------- Key: JBESB-1164 URL: http://jira.jboss.com/jira/browse/JBESB-1164 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2.1 IR1 Reporter: Tom Cunningham Assigned To: Mark Little If the AS or ESB server crashes or does not cleanly shut down, JUDDI will duplicate EPR records in its database table. For the monitoring/management console, this is a real problem because it depends on the fact that there will be only one EPR for its services per ESB server. Post-crash, every time the console tries to collect data, it is getting back results from multiple EPRs on the same machine, which is causing ConstraintViolations when we try to store results. This is causing JBESB-1139. JUDDI should probably clean up EPR records post-crash. -- 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

17 years, 5 months

4
3
0 / 0

[JBoss JIRA] Created: (JBESB-2194) Move jbossesb-config-editor.war out of deploy directory

by Kevin Conner (JIRA)

Move jbossesb-config-editor.war out of deploy directory ------------------------------------------------------- Key: JBESB-2194 URL: https://jira.jboss.org/jira/browse/JBESB-2194 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2.1 CP3 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.2.1 CP4 Move the jbossesb-config-editor.war out of the deploy directory but still ship it. The servlets should really be secured if deployed by default in the platform. -- 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

17 years, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-2197) Default JMS ReplyTo address can be based on the wrong uri

by Kevin Conner (JIRA)

Default JMS ReplyTo address can be based on the wrong uri --------------------------------------------------------- Key: JBESB-2197 URL: https://jira.jboss.org/jira/browse/JBESB-2197 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP1 Reporter: Kevin Conner Fix For: 4.2.1 CP4 The JMS reply address can default to the JNDI server URL configured in the local VM if the EPR does not specify the jndi-URL. In normal JMS processing this has no effect but it does look strange when debugging. This will confuse InVM, however, although InVM should not be used for services which can be accessed inter-vm. -- 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

17 years, 5 months

1
6
0 / 0

[JBoss JIRA] Created: (JBESB-2191) JmsRouter should handle reconnects

by Kevin Conner (JIRA)

JmsRouter should handle reconnects ---------------------------------- Key: JBESB-2191 URL: https://jira.jboss.org/jira/browse/JBESB-2191 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP1, 4.2.1 CP3 Reporter: Kevin Conner Fix For: 4.2.1 CP4, 4.4 CP2 At present a fault in the JMS connection will result in the sessions/providers being closed by the pooling mechanism. JmsRouter retains a reference to the initial provider acquired from the session and continues to use it after faults have been identified. -- 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

17 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2190) Fix JmsRouter's use of JMS session/providers

by Kevin Conner (JIRA)

Fix JmsRouter's use of JMS session/providers -------------------------------------------- Key: JBESB-2190 URL: https://jira.jboss.org/jira/browse/JBESB-2190 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP1, 4.2.1 CP3 Reporter: Kevin Conner Fix For: 4.2.1 CP4, 4.4 CP2 At present the JmsRouter is obtaining a single session/provider and using it in a concurrent fashion. JMS sessions/providers are intended to be single threaded objects and cannot be shared in this manner. -- 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

17 years, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-1658) Project layout for Quickstarts

by Mark Little (JIRA)

Project layout for Quickstarts ------------------------------ Key: JBESB-1658 URL: http://jira.jboss.com/jira/browse/JBESB-1658 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration, Examples Affects Versions: 4.2.1 CP2 Reporter: Mark Little Fix For: 4.3 -- 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

17 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2013) Create Inbound and Outbound routers for JMS

by Tom Fennelly (JIRA)

Create Inbound and Outbound routers for JMS ------------------------------------------- Key: JBESB-2013 URL: https://jira.jboss.org/jira/browse/JBESB-2013 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 5.0 initial development Reporter: Tom Fennelly Assignee: Daniel Bevenius -- 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

17 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-2158) Generator.getService(Listener) not protecting itself from NPE

by Kevin Conner (JIRA)

Generator.getService(Listener) not protecting itself from NPE ------------------------------------------------------------- Key: JBESB-2158 URL: https://jira.jboss.org/jira/browse/JBESB-2158 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Fennelly Assignee: Tom Fennelly Priority: Critical Fix For: 4.4 Which can happen when a service doesn't define any listeners (e.g. an InVM service) -- 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

17 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-1590) Review File lifecycle management in the FileGateway

by Tom Fennelly (JIRA)

Review File lifecycle management in the FileGateway --------------------------------------------------- Key: JBESB-1590 URL: http://jira.jboss.com/jira/browse/JBESB-1590 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 CP1 Reporter: Tom Fennelly Fix For: 4.2.1 CP2 Task JBESB-1568 identified an issue thrown up by the scheduler code, but in doing so also highlighted a secondary issue in the way that the gateway itself manages the lifecycles of the files it is processing. Specifically... when a file "disappears" while that instance of the gateway is processing it (or about to process it). This could happen through a single FileGateway config before JBESB-1568 was fixed, but can still happen when multiple gateways are configured to process the same fileset in the same directory. The gateway should handle such contention issue more cleanly. Should it support multiple gateway instances processing a single fileset in a single directory? This could be a head wrecker to get right *and prove right* on all platforms! We could just document this as something that's not supported. It should def be able to handle different filesets in the same dir using multiple gateway instances! -- 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

17 years, 5 months

3
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2008