[JBoss JIRA] Created: (JBESB-3261) QS helloworld_file_notifier: wrong package name in build.xml
by Boris Belovic (JIRA)
QS helloworld_file_notifier: wrong package name in build.xml
------------------------------------------------------------
Key: JBESB-3261
URL: https://jira.jboss.org/jira/browse/JBESB-3261
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.4 CP4
Reporter: Boris Belovic
Priority: Trivial
ant sendesb target results in ClassNotFoundException. The cause is wrong package name for SendEsbMessage class in target definition. The line in build.xml contains:
<java fork="yes" classname="org.jboss.soa.esb.samples.quickstart.helloworld.test.SendEsbMessage" failonerror="true"> which is wrong and this should be replaced with:
<java fork="yes" classname="org.jboss.soa.esb.samples.quickstart.helloworldfilenotifier.test.SendEsbMessage" failonerror="true">.
--
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, 6 months
[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, 6 months