Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: ESB-6
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Bruce Snyder
Reporter: Bruce Snyder
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
FUSE ESB

Fixes to match newer Spring APIs when setting an object name.

Created: 20/Jul/07 12:25 PM   Updated: 31/Jul/07 07:08 PM
Component/s: None
Affects Version/s: fuse-3.2.0.0
Fix Version/s: fuse-3.2.0.1


 Description  « Hide
This issue prevented the Fuse ESB from starting up due to the following error:

Caught: org.springframework.beans.factory.BeanCreationException: Error creating bean with name
'org.apache.servicemix.jbi.jmx.ConnectorServerFactoryBean' defined in class path resource [jmx.xml]: Invocation of init method failed; nested exception is
javax.management.MalformedObjectNameException: Invalid ObjectName value type [javax.xml.namespace.QName]: only ObjectName and String
supported.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.servicemix.jbi.jmx.ConnectorServerFactoryBean'
defined in class path resource [jmx.xml]: Invocation of init method failed; nested exception is javax.management.MalformedObjectNameException: Invalid
ObjectName value type [javax.xml.namespace.QName]: only ObjectName and String supported.
Caused by: javax.management.MalformedObjectNameException: Invalid ObjectName value type [javax.xml.namespace.QName]: only ObjectName and
String supported.
at org.springframework.jmx.support.ObjectNameManager.getInstance(ObjectNameManager.java:58)
at org.springframework.jmx.support.ConnectorServerFactoryBean.setObjectName(ConnectorServerFactoryBean.java:104)
at org.apache.servicemix.jbi.jmx.ConnectorServerFactoryBean.afterPropertiesSet(ConnectorServerFactoryBean.java:186)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1201)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1171)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:425)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:284)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352)
at org.apache.xbean.spring.context.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:161)
at org.apache.xbean.spring.context.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:51)
at org.apache.servicemix.Main.main(Main.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchStandard(Launcher.java:410)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:344)
at org.codehaus.classworlds.Launcher.main(Launcher.java:461)

Fixed in 15525



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.