October 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2439) Use JBoss tModel when saving bindings and services

by Tom Cunningham (JIRA)

Use JBoss tModel when saving bindings and services -------------------------------------------------- Key: JBESB-2439 URL: https://jira.jboss.org/jira/browse/JBESB-2439 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.4 FP1 Use the JBoss tModel when saving services and service bindings. -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2768) Aggregator meta data in properties

by Kevin Conner (JIRA)

Aggregator meta data in properties ---------------------------------- Key: JBESB-2768 URL: https://jira.jboss.org/jira/browse/JBESB-2768 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.4 CP3 Reporter: Kevin Conner Fix For: 4.4 CP4 The MessageMulticaster creates an aggregation id and stores this value in message properties. Normally this does not prove to be an issue but when using invm transport it may cause issues. When the message is sent to multiple services, using pass by reference semantics, then all services will see the *same* properties and may, depending on timing, see the same aggregation id. The aggregation value should really be in the message context as this section is always duplicated when creating a reference, never shared. The problem we face is that users may already be referencing the property, especially if they are creating a fresh response message, so we need to think about handling this. -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2466) SecureFtpImpl is missing logging and is silently hiding exceptions

by Martin Vecera (JIRA)

SecureFtpImpl is missing logging and is silently hiding exceptions ------------------------------------------------------------------ Key: JBESB-2466 URL: https://jira.jboss.org/jira/browse/JBESB-2466 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.4 CP2 Reporter: Martin Vecera Priority: Minor We experienced a difficulty with SFTP gateway which did not read any files. No information was present in server log. Due to the following block of code, we were not able to find out, that the server has wrong configuration of it's root path and thus not able to access the files. catch (SftpException ex) { if (ex.id == ChannelSftp.SSH_FX_NO_SUCH_FILE) { return null ; <-- this is the problem } throw new RemoteFileSystemException(ex); } At least DEBUG level log information would be highly appreciated. All in all, I don't like that the class uses logging only at 3 places. -- 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

16 years

4
5
0 / 0

[JBoss JIRA] Created: (JBESB-2281) Error while deploying a standalone ws endpoint in war outside an ear using soaprocessor

by Daniel F?rberg (JIRA)

Error while deploying a standalone ws endpoint in war outside an ear using soaprocessor --------------------------------------------------------------------------------------- Key: JBESB-2281 URL: https://jira.jboss.org/jira/browse/JBESB-2281 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.4 Environment: JBoss ESB 4.4 and/or Soa Platform 4.3 Reporter: Daniel F?rberg Fix For: 4.4 Error while deploying a standalone ws endpoint in war outside an ear using SoapProcessor -- 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

16 years

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1485) Project bug for SOA-P JIRA SOA-311

by Len DiMaggio (JIRA)

Project bug for SOA-P JIRA SOA-311 ---------------------------------- Key: JBESB-1485 URL: http://jira.jboss.com/jira/browse/JBESB-1485 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Len DiMaggio Assigned To: Mark Little ESB project bug for SOA-P JIRA: http://jira.jboss.com/jira/browse/SOA-311 OutOfMemory Errors on webservice_bpel quickstart -- 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

4
12
0 / 0

[JBoss JIRA] Created: (JBESB-834) Include Smooks documentation in release

by Mark Little (JIRA)

Include Smooks documentation in release --------------------------------------- Key: JBESB-834 URL: http://jira.jboss.com/jira/browse/JBESB-834 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Tom Fennelly On behalf of intern: "It would be nice if the Smooks docs were included in the distribution. In general, it would be nice if all 3rd party libs that the user may need to play with have some form of self-contained docs." -- 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

3
7
0 / 0

[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

16 years

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

16 years

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

16 years

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

16 years

2
3
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 2009