October 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2130) High level docs

by Tom Fennelly (JIRA)

High level docs --------------- Key: JBESB-2130 URL: https://jira.jboss.org/jira/browse/JBESB-2130 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 5.0 initial development -- 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
3
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

17 years, 5 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

17 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-2146) Scheduling: Multiple cron schedules not supported

by Tom Fennelly (JIRA)

Scheduling: Multiple cron schedules not supported ------------------------------------------------- Key: JBESB-2146 URL: https://jira.jboss.org/jira/browse/JBESB-2146 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4, 4.4 CP1 Reporter: Tom Fennelly Assignee: Kevin Conner If you define multiple cron schedules, or just one cron schedule with associated multiple listeners/jobs.... only the first job gets executed. I stepped into the code and the jobs are getting registered, started etc. -- 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

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-2114) inVM information is out of date in Programmers Guide

by Darrin Mison (JIRA)

inVM information is out of date in Programmers Guide ---------------------------------------------------- Key: JBESB-2114 URL: https://jira.jboss.org/jira/browse/JBESB-2114 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.3 Reporter: Darrin Mison The InVM transport information in the programmers guide is out of date regards to configured defaults. -- 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

4
10
0 / 0

[JBoss JIRA] Created: (JBESB-2120) JaasSecurityService configured multiple times

by Kevin Conner (JIRA)

JaasSecurityService configured multiple times --------------------------------------------- Key: JBESB-2120 URL: https://jira.jboss.org/jira/browse/JBESB-2120 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP1 The JaasSecurityService is initalised and refreshed with every action processing pipeline that contains a security configuration. This should really be a one-off configuration. Also, the service is also modifying the JAAS configuration by setting properties and then creating an instance of a SUN private class. We should be using the normal mechanism to specify these policies, i.e. through login-config.xml. -- 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
9
0 / 0

[JBoss JIRA] Created: (JBESB-2072) Add TModel through JAXR, rather than manually or through SQL

by Tom Cunningham (JIRA)

Add TModel through JAXR, rather than manually or through SQL ------------------------------------------------------------ Key: JBESB-2072 URL: https://jira.jboss.org/jira/browse/JBESB-2072 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.4 CP1 Currently we add the TModel we need through a SQL script in jUDDI and we ask that the user use the SOA Software GUI to add a TModel in the SOA Software UDDI instructions. It'd be nice if we handled this automatically if the ClassificationScheme query fails, and then we retry that query. -- 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-2086) JON plugin: negative AVG metrics after redeploying an esb archive

by Jaroslaw Kijanowski (JIRA)

JON plugin: negative AVG metrics after redeploying an esb archive ----------------------------------------------------------------- Key: JBESB-2086 URL: https://jira.jboss.org/jira/browse/JBESB-2086 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 Reporter: Jaroslaw Kijanowski Assignee: Tom Cunningham details in SOA-904 -- 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

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-2121) Replace crypto util with sealed object

by Kevin Conner (JIRA)

Replace crypto util with sealed object -------------------------------------- Key: JBESB-2121 URL: https://jira.jboss.org/jira/browse/JBESB-2121 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP1 The crypto util classes are used to encrypt the SecurityContext but we should be able to use a SealedObject. The util also relies on having a keystore configured but it would be sufficient to have the key(s) automatically generated on startup and use this to encrypt the session information. Another issue with the class is that the encrypt/decrypt methods repeatedly encrypt the serialised data in chunks but the encrypt/decrypt sizes are very dependent on the block cipher in use (currently RSA). If the configuration specifies a different cipher then this is likely to fail. If we can move to a SealedObject then this should no longer be an issue. -- 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
13
0 / 0

[JBoss JIRA] Created: (JBESB-2090) Getting Started Guide not in sync with helloworld QS

by Jaroslaw Kijanowski (JIRA)

Getting Started Guide not in sync with helloworld QS ---------------------------------------------------- Key: JBESB-2090 URL: https://jira.jboss.org/jira/browse/JBESB-2090 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 CP1 Reporter: Jaroslaw Kijanowski In both pictures, following changes should be applied: queue/quickstart_helloworld_Request -> queue/quickstart_helloworld_Request_gw queue/B -> queue/quickstart_helloworld_Request_esb FirstService:JMSService -> FirstServiceESB:SimpleListener page 10: The "FirstService:SimpleListener" ESB Aware Service Listener... -> The "FirstServiceESB:SimpleListener" ESB Aware Service Listener... listens for "ESB Aware" messages on "queue/quickstart_helloworld_Request_gw". -> listens for "ESB Aware" messages on "queue/quickstart_helloworld_Request_esb". -> page 12: ... messages are put on the bus, the "FirstService:SimpleJMSService" Service is registered ... -> ... messages are put on the bus, the "FirstServiceESB:SimpleListener" Service is registered ... This works out to be JMS Queue "queue/quickstart_helloworld_Request_gw" -> This works out to be JMS Queue "queue/quickstart_helloworld_Request_esb" The JMS Gateway Listener "adapts" the message into an ESB Aware message and places it into JMS Queue "queue/=quickstart_helloworld_Request_gw" -> The JMS Gateway Listener "adapts" the message into an ESB Aware message and places it into JMS Queue "queue/quickstart_helloworld_Request_esb" -- 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

4
9
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2008