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

Kevin Conner (JIRA) jira-events at lists.jboss.org
Tue May 12 06:47:47 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBESB-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Conner updated JBESB-2558:
--------------------------------

        Fix Version/s: 4.4 CP3
                           (was: 4.6)
    Affects Version/s: 4.4 CP2


> 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
>    Affects Versions: 4.4 CP2
>            Reporter: Kevin Conner
>             Fix For: 4.4 CP3
>
>
> 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

        



More information about the esb-issues mailing list