November 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2164) ScheduleListener should include service category/name in config

by Kevin Conner (JIRA)

ScheduleListener should include service category/name in config --------------------------------------------------------------- Key: JBESB-2164 URL: https://jira.jboss.org/jira/browse/JBESB-2164 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1 -- 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, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2150) Config Generator should normalise all listener, bus, provider name values.

by Kevin Conner (JIRA)

Config Generator should normalise all listener, bus, provider name values. -------------------------------------------------------------------------- Key: JBESB-2150 URL: https://jira.jboss.org/jira/browse/JBESB-2150 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.4 Because these are used as element names in the generated config. If there are invalid chars in there (spaces etc) the generator throws a totaly useless error. Improve the error handling there too :-) -- 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, 6 months

2
4
0 / 0

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

by Kevin Conner (JIRA)

Possible Juddi Performance problems ----------------------------------- Key: JBESB-2155 URL: https://jira.jboss.org/jira/browse/JBESB-2155 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2.1 Reporter: Tom Cunningham Assignee: Kevin Conner Fix For: 4.4 >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: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
7
0 / 0

[JBoss JIRA] Created: (JBESB-1930) ServiceInvoker synchronous delivery can lead to deadlock

by Kevin Conner (JIRA)

ServiceInvoker synchronous delivery can lead to deadlock -------------------------------------------------------- Key: JBESB-1930 URL: https://jira.jboss.org/jira/browse/JBESB-1930 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.5, 4.4 CP1 The synchronous delivery does not release the courier used for delivery before acquiring one for pickup, leaving a window during which a deadlock can occur. -- 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, 6 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-539) Config Generator should normalise all listener, bus, provider name values.

by Tom Fennelly (JIRA)

Config Generator should normalise all listener, bus, provider name values. -------------------------------------------------------------------------- Key: JBESB-539 URL: http://jira.jboss.com/jira/browse/JBESB-539 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 Because these are used as element names in the generated config. If there are invalid chars in there (spaces etc) the generator throws a totaly useless error. Improve the error handling there too :-) -- 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, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-2169) business_rules_service QS is missing an action

by Kevin Conner (JIRA)

business_rules_service QS is missing an action ---------------------------------------------- Key: JBESB-2169 URL: https://jira.jboss.org/jira/browse/JBESB-2169 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP2 Reporter: Jaroslaw Kijanowski Assignee: Daniel Bevenius Fix For: 4.4 >From the readme file in the business_rules_service QS: The customer status is actually set in the jboss-esb.xml via the SetupMessage action since it is not provided with the inbound XML. There's no SetupMessage which would initialize the status of a customer. This has an impact on business rules, which won't fire (besides the logging rules), because they depend on the status value of a customer. Moreover when deploying I get this: 15:07:15,372 INFO [ContentBasedWiretap] Missing or empty destination list - This action class won't have any effect 15:07:15,372 INFO [ContentBasedWiretap] Missing or empty destination list - This action class won't have any effect I guess it's because there are two business rules files, both not used for routing... But that's already filed: JBESB-986 -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2171) Update version to 4.2.1 CP4

by Kevin Conner (JIRA)

Update version to 4.2.1 CP4 --------------------------- Key: JBESB-2171 URL: https://jira.jboss.org/jira/browse/JBESB-2171 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.2.1 CP4 -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2166) jUDDI fails to parse XML correctly

by Kevin Conner (JIRA)

jUDDI fails to parse XML correctly ---------------------------------- Key: JBESB-2166 URL: https://jira.jboss.org/jira/browse/JBESB-2166 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Priority: Blocker Fix For: 4.4 CP1 jUDDI can fail to parse the XML messages sent between scout and jUDDI, the result of which can be indeterminate. One manifestation of this problem is the inability to register clean EPRs, resulting in the following exception. org.jboss.soa.esb.services.registry.RegistryException: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col {unknown-source}]: [1,0] at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPR(JAXRRegistryImpl.java:344) The reason for the failure is the inability of jUDDI to handle CDATA sections within the XML. Instead of parsing the section correctly it will generate an empty string, hence the above exception when trying to parse the EPR. I believe this issue exists in *all* releases to date. -- 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, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2157) RegistryFactory recreates the registry on every call

by Kevin Conner (JIRA)

RegistryFactory recreates the registry on every call ---------------------------------------------------- Key: JBESB-2157 URL: https://jira.jboss.org/jira/browse/JBESB-2157 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.3 Reporter: Kevin Conner Assignee: Mark Little Fix For: 4.4 The factory should be initialising the registry singleton instead of recreating on every invocation. It should also be made thread-safe, the comment about no synchronization is invalid (even if it was initialised from a 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

15 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-2165) FileGatewayListener renameFile method deletes target

by Kevin Conner (JIRA)

FileGatewayListener renameFile method deletes target ---------------------------------------------------- Key: JBESB-2165 URL: https://jira.jboss.org/jira/browse/JBESB-2165 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1 The FileGatewayListener renameFile method is deleting the target file before attempting to execute the rename. This is not correct when multiple listeners are executing within the same directory, for example in a cluster, as it could lead to the removal of the successfully renamed file from another listener. -- 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, 6 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 November 2008