September 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1081) Make jbossesb.esb dependency implicit

by Kevin Conner (JIRA)

Make jbossesb.esb dependency implicit ------------------------------------- Key: JBESB-1081 URL: http://jira.jboss.com/jira/browse/JBESB-1081 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 IR1 Every esb has an implicit dependency on the core jbossesb.esb service. We should have the deployer enforce this dependency instead of requiring an explicit declaration. -- 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, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1080) Management Console: verbose console logging

by Kevin Conner (JIRA)

Management Console: verbose console logging ------------------------------------------- Key: JBESB-1080 URL: http://jira.jboss.com/jira/browse/JBESB-1080 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2 Reporter: Kevin Conner Assigned To: Tom Cunningham Fix For: 4.2.1 IR1 The management console logging has become verbose of late, the main reasons are the following: - monitoring.cfg.xml specifies hibernate.show_sql as true - DataCollector.java logs matches/does not match at INFO level instead of DEBUG - DataCollectorAction.java includes a call to data.print() Tidying these up dramatically reduces the amount of output on the console. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Closed: (JBESB-440) Remote management of services

by Tom Cunningham (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-440?page=all ] Tom Cunningham closed JBESB-440. -------------------------------- > Remote management of services > ----------------------------- > > Key: JBESB-440 > URL: http://jira.jboss.com/jira/browse/JBESB-440 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Management > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Tom Cunningham > Fix For: 4.2.1 IR1 > > > Remotely start/stop/suspend/resume services. Via JMX and via lifecycle messages (as per original architecture). -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBESB-440) Remote management of services

by Tom Cunningham (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-440?page=all ] Tom Cunningham resolved JBESB-440. ---------------------------------- Fix Version/s: 4.2.1 IR1 (was: 5.0) Resolution: Done In 4.2.1IR1, the second part of this (administration by command messages) is now possible. You can send a bean with information on the operation you wish to invoke and it will start / stop / initialize / destroy a service. See product/tools/console/management-web/src/main/webapp/invoke.jsp for details on how to do this. > Remote management of services > ----------------------------- > > Key: JBESB-440 > URL: http://jira.jboss.com/jira/browse/JBESB-440 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Management > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Tom Cunningham > Fix For: 4.2.1 IR1 > > > Remotely start/stop/suspend/resume services. Via JMX and via lifecycle messages (as per original architecture). -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1096) Remove compiled classes from Tomcat install war

by Kevin Conner (JIRA)

Remove compiled classes from Tomcat install war ----------------------------------------------- Key: JBESB-1096 URL: http://jira.jboss.com/jira/browse/JBESB-1096 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Minor Fix For: 4.2.1 IR1 There are compiled classes in the tomcat/war/WEB-INF directory. -- 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, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-1097) Create a lifecycle resource management framework and rework courier/JMS pooling to fit

by Kevin Conner (JIRA)

Create a lifecycle resource management framework and rework courier/JMS pooling to fit -------------------------------------------------------------------------------------- Key: JBESB-1097 URL: http://jira.jboss.com/jira/browse/JBESB-1097 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 IR1 We need a proper resource management framework for handling contextualised data. At the moment there are two services which do this in an ad-hoc manner, Couriers and JMS Pooling, with a third requiring this (JBoss rules). -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1098) Remove ConfigurationControllerService and associated MBean definition from the codebase

by Kevin Conner (JIRA)

Remove ConfigurationControllerService and associated MBean definition from the codebase --------------------------------------------------------------------------------------- Key: JBESB-1098 URL: http://jira.jboss.com/jira/browse/JBESB-1098 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 IR1 The ConfigurationControllerService has not been necessary since the ESB deployer was written, this should be removed. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1079) Type of java.lang.String found for StartTime

by Tom Cunningham (JIRA)

Type of java.lang.String found for StartTime -------------------------------------------- Key: JBESB-1079 URL: http://jira.jboss.com/jira/browse/JBESB-1079 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.2.1 >From Burr: this message pops up "04:59:44,531 ERROR [DataFiler] ERROR - found type of java.lang.String for StartTime" Should make sure the correct data type is being used here. -- 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, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-1065) Add Peristent, Priority, and TimeToLive to NotifyJMS and JMSRouter

by Daniel Bevenius (JIRA)

Add Peristent, Priority, and TimeToLive to NotifyJMS and JMSRouter ------------------------------------------------------------------ Key: JBESB-1065 URL: http://jira.jboss.com/jira/browse/JBESB-1065 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Rosetta Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Minor Fix For: 4.2.1 IR1 Add the following properties to JMSRouter: <action name="route" class="org.jboss.soa.esb.actions.routing.JMSRouter"> <property name="jndiName" value="queue/queueName"/> <property name="unwrap" value="true"/> <property name="persistent" value="true"/> <property name="priority" value="10"/> <property name="time-to-live" value="60000"/> </action> And top NotifyJMS: <action name="notify" class="org.jboss.soa.esb.actions.Notifier"> <property name="okMethod" value="notifyOK" /> <property name="notification-details"> <NotificationList type="OK"> <target class="NotifyQueues"> <queue jndiName="queue/queueName" persistent="false" priority="3" time-to-live="60000" connection-factory="ConnectionFactory"> <messageProp name="propName" value="val"/> </queue> </target> </NotificationList> </property> </action> Update the MessageActionGuide to reflect 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

17 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1095) make DefaultJMSPropertiesSetter set the JMSCorrelationID

by Daniel Bevenius (JIRA)

make DefaultJMSPropertiesSetter set the JMSCorrelationID --------------------------------------------------------- Key: JBESB-1095 URL: http://jira.jboss.com/jira/browse/JBESB-1095 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Minor Fix For: 4.2.1 IR1 add a setJMSCorrelationID method and add a call to that method in setJMSProperties: public void setJMSProperties( final org.jboss.soa.esb.message.Message fromESBMessage , final Message toJMSMessage ) throws JMSException { setJMSMessageID( fromESBMessage, toJMSMessage ); setJMSCorrelationID( fromESBMessage,toJMSMessage ); setJMSExpiration( fromESBMessage,toJMSMessage ); setProperties( fromESBMessage, toJMSMessage ); } This is will let clients that have set a custom JMS correlation id, have that id passed along when the JMS Message leaves the ESB. This was need because of the following bug in JBM : http://jira.jboss.org/jira/browse/JBMESSAGING-1063. This bug has now been fixed but as we are not using the latest version of JBM yet this might be needed by other users. -- 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, 2 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2007