December 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-556) Make the webservice_bpel quickstart into a Trailblazer

by Tom Fennelly (JIRA)

Make the webservice_bpel quickstart into a Trailblazer ------------------------------------------------------ Key: JBESB-556 URL: http://jira.jboss.com/jira/browse/JBESB-556 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 This is really a Trailblazer - too much in it to be a QS -- 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

14 years, 7 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-1691) MRG/RHM support

by Mark Little (JIRA)

MRG/RHM support --------------- Key: JBESB-1691 URL: http://jira.jboss.com/jira/browse/JBESB-1691 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 CP2 Reporter: Mark Little -- 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

14 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-2558) monitoring.cfg.xml not found

by Kevin Conner (JIRA)

monitoring.cfg.xml not found ----------------------------- Key: JBESB-2558 URL: https://jira.jboss.org/jira/browse/JBESB-2558 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Reporter: Kevin Conner Fix For: 4.6 The configuration of the management services is currently broken, leaving an opportunity for the following exception to be thrown. org.hibernate.HibernateException: monitoring.cfg.xml not found at org.hibernate.util.ConfigHelper.getResourceAsStream(ConfigHelper.java:147) at org.hibernate.cfg.Configuration.getConfigurationInputStream(Configuration.java:1405) at org.hibernate.cfg.Configuration.configure(Configuration.java:1427) at org.jboss.soa.esb.monitoring.MonitoringSessionFactory.init(MonitoringSessionFactory.java:80) at org.jboss.soa.esb.monitoring.MonitoringSessionFactory.getInstance(MonitoringSessionFactory.java:68) at org.jboss.soa.esb.monitoring.client.OperationsCollector.getClassPatterns(OperationsCollector.java:84) at org.jboss.soa.esb.monitoring.client.OperationsCollector.collectData(OperationsCollector.java:165) at org.jboss.soa.esb.monitoring.client.OperationsCollectorAction.collectOperations(OperationsCollectorAction.java:72) The reason for this issue is that the monitoring services specified in jbossesb.esb have an implicit dependency on a jar provided in management.esb but management.esb has an explicit dependency on jbossesb.esb. This will, therefore, leave a window where the management configuration may be required *before* the jar has been loaded. The implicit dependency is caused by the requirement of jbossesb.esb/management-client.jar to access the monitoring.cfg.xml file included in management.esb/management-server.jar. -- 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, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-2846) bpm_orchestration2 process is not safe

by Kevin Conner (JIRA)

bpm_orchestration2 process is not safe -------------------------------------- Key: JBESB-2846 URL: https://jira.jboss.org/jira/browse/JBESB-2846 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 CP2 Reporter: Kevin Conner The bpm_orchestration2 quickstart is used to demonstrate fork/join operations in the business process but it is *not* safe. The forked actions are all configured to udpate the same process variable, providing an opportunity for contention. -- 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, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1429) Need an MBean for CronExpressions

by Tom Cunningham (JIRA)

Need an MBean for CronExpressions --------------------------------- Key: JBESB-1429 URL: http://jira.jboss.com/jira/browse/JBESB-1429 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.2.1 Reporter: Tom Cunningham Assigned To: Tom Cunningham Need a way of dynamically updating a cron expression at runtime. MBean probably would be the preferable method for this. -- 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

14 years, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (JBESB-2550) "local first" load balancing policy

by toby cabot (JIRA)

"local first" load balancing policy ----------------------------------- Key: JBESB-2550 URL: https://jira.jboss.org/jira/browse/JBESB-2550 Project: JBoss ESB Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: toby cabot Here's a patch that adds org.jboss.soa.esb.listeners.ha.LocalFirstRoundRobin which will choose a local EPR if there is one and fall back to RoundRobin if not. We like this because it keeps processing on a single host when that's possible and only goes off-host (which is relatively expensive) if necessary. -- 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, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (JBESB-1937) Document performance tuning parameters

by Kevin Conner (JIRA)

Document performance tuning parameters -------------------------------------- Key: JBESB-1937 URL: https://jira.jboss.org/jira/browse/JBESB-1937 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Jervis Liu Fix For: 4.5 We need to include documentation on tuning parameters that are available within the ESB. Jervis has made a good start to this as part of the recent work he has been doing, his experience should be used as the basis. -- 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, 8 months

4
14
0 / 0

[JBoss JIRA] Created: (JBESB-1121) JBoss Web Console integration (message alerter)

by Tom Cunningham (JIRA)

JBoss Web Console integration (message alerter) ----------------------------------------------- Key: JBESB-1121 URL: http://jira.jboss.com/jira/browse/JBESB-1121 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Cunningham Assigned To: Tom Cunningham According to their docs, the JBoss Web Console does console-based alerts and email-alerts. It'd be nice if there was also was an ESB option - where based off of a JMX Bean property, a message is sent to whatever ESB service the user specifies in their monitoring XML. -- 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

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2998) ServicesGuide missing all but one image

by Kevin Conner (JIRA)

ServicesGuide missing all but one image --------------------------------------- Key: JBESB-2998 URL: https://jira.jboss.org/jira/browse/JBESB-2998 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.8 We need find out what has happened and restore the missing images. -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2901) Can't deploy custom ScheduledListener configuration

by Thorsten Polster (JIRA)

Can't deploy custom ScheduledListener configuration --------------------------------------------------- Key: JBESB-2901 URL: https://jira.jboss.org/jira/browse/JBESB-2901 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.5 Reporter: Thorsten Polster ConfigurationException while configure custom ScheduledListener Can't use custom ScheduledListener like described in JBoss Wiki (see: http://www.jboss.org/community/wiki/WritingCustomListenersforJBossESB4x#S...) org.jboss.soa.esb.ConfigurationException: Can only use the org.jboss.soa.esb.listeners.config.mappers110.UntypedListenerMapper mapper on the base listener type. Cannot use on org.jboss.soa.esb.listeners.config.xbeanmodel110.impl.ScheduledListenerDocumentImpl$ScheduledListenerImpl at org.jboss.soa.esb.listeners.config.mappers110.UntypedListenerMapper.assertListenerConfigOK(UntypedListenerMapper.java:101) at org.jboss.soa.esb.listeners.config.mappers110.UntypedListenerMapper.map(UntypedListenerMapper.java:62) at org.jboss.soa.esb.listeners.config.mappers110.GatewayGenerator.addGatewayConfig(GatewayGenerator.java:146) at org.jboss.soa.esb.listeners.config.mappers110.GatewayGenerator.generate(GatewayGenerator.java:108) at org.jboss.soa.esb.listeners.config.mappers110.XMLBeansModel.generateGatewayConfig(XMLBeansModel.java:451) at org.jboss.soa.esb.listeners.config.model.Model110SchemaParser$Model110Adapter.generateGatewayConfig(Model110SchemaParser.java:138) at org.jboss.soa.esb.listeners.config.Generator.generate(Generator.java:116) at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:94) ... 46 more There might be a bug in the class org.jboss.soa.esb.listeners.config.mappers110.UntypedListenerMapper in the method assertListenerConfigOK, cause there is a check for that the mapped Listener must be a ListenerImpl, but is a ScheduledListenerImpl which is just a instance of ListenerImpl. -- 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, 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 December 2009