JMSBC on OpenESB SE 3.0.5 Cannot start

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

JMSBC on OpenESB SE 3.0.5 Cannot start

OpenESB Community Forum mailing list
Hi All,

Just playing arround with OpenESB on a linux machine with JDK 1.8 installed,
just tring to get the JMSBC working,  I can install the JMSBC fine using the
web console,  but when I try to start the JMSBC fails to start,  looking at
the system log durring install it throws the following error,  so I don't
think it installs correctly in the first place.

Am I doing something really stupid or do I need an earlier JDK?

2017-12-26T12:38:15.674+0000 INFO
[sun-jms-binding.com.sun.jbi.jmsbc.JMSBindingBootstrap] (Grizzly(4))
JMSBC-I0701: Bootstrap has been initialized (init)
2017-12-26T12:38:15.678+0000 INFO
[sun-jms-binding.com.sun.jbi.jmsbc.JMSBindingBootstrap] (Grizzly(4))
JMSBC-I0702: Bootstrap has been installed (onInstall)
2017-12-26T12:38:15.678+0000 INFO
[sun-jms-binding.com.sun.jbi.jmsbc.JMSBindingBootstrap] (Grizzly(4))
JMSBC-I0704: Bootstrap has been cleaned up (cleanUp)
2017-12-26T12:38:15.682+0000 INFO [com.sun.jbi.framework] (Grizzly(4))
JBIFW1106: Binding sun-jms-binding has been installed.
2017-12-26T12:38:15.814+0000 SEVERE [net.openesb.management.jmx]
(Grizzly(3)) REST-0017: Exception caught while getting component
configuration attributes for component sun-jms-binding (MBean =
com.sun.jbi:Target=server,ServiceType=Configuration,ComponentName=sun-jms-binding).
javax.management.MBeanException
        at
com.sun.jbi.management.facade.ComponentConfiguration.getAttribute(ComponentConfiguration.java:198)
        at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:647)
        at
com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678)
        at
net.openesb.management.jmx.AbstractServiceImpl.getComponentConfigurationProperties(AbstractServiceImpl.java:615)
        at
net.openesb.management.jmx.ConfigurationServiceImpl.getComponentConfiguration(ConfigurationServiceImpl.java:45)
        at
net.openesb.rest.api.resources.ComponentConfigurationResource.getComponentConfiguration(ComponentConfigurationResource.java:45)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at
org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
        at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:151)
        at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:172)
        at
org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:195)
        at
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:104)
        at
org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:384)
        at
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:342)
        at
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:101)
        at
org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:271)
        at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
        at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
        at
org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:297)
        at
org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:254)
        at
org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1030)
        at
org.glassfish.jersey.grizzly2.httpserver.GrizzlyHttpContainer.service(GrizzlyHttpContainer.java:378)
        at
org.glassfish.grizzly.http.server.HttpHandler$1.run(HttpHandler.java:222)
        at
org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:565)
        at
org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:545)
        at java.lang.Thread.run(Thread.java:748)
Caused by: javax.jbi.JBIException: <?xml version="1.0" encoding="UTF-8"
standalone="yes"?><jbi-task version="1.0"
xmlns="http://java.sun.com/xml/ns/jbi/management-message"><jbi-task-result><frmwk-task-result><frmwk-task-result-details><task-result-details><task-id>componentStartedOrStoppedOnTargetCheck</task-id><task-result>FAILED</task-result><message-type>ERROR</message-type><task-status-msg><msg-loc-info><loc-token>JBIMA1803</loc-token><loc-message>Component
sun-jms-binding is in the Shutdown state. Cannot create, update, list or
delete configuration for a component which is not in Started or Stopped
state.</loc-message><loc-param>sun-jms-binding</loc-param><loc-param>Shutdown</loc-param><loc-param>server</loc-param></msg-loc-info></task-status-msg></task-result-details><locale>en_GB</locale></frmwk-task-result-details></frmwk-task-result></jbi-task-result></jbi-task>
        at
com.sun.jbi.management.facade.ComponentConfiguration.componentStartedOrStoppedOnTargetCheck(ComponentConfiguration.java:2225)
        at
com.sun.jbi.management.facade.ComponentConfiguration.getAttribute(ComponentConfiguration.java:180)
        ... 31 more




--
Sent from: http://openesb-community-forum.794670.n2.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: JMSBC on OpenESB SE 3.0.5 Cannot start

Paul Perez
Administrator
Hello
Having a look on your traces, it seems to be a deployment problem. It looks
like a component not well install properly previously.
I would suggest you if you can, to switch off your OpenESB instance, then go
to
OE-Instance/server/components and erase the sun-jms-binding. Then restart
the instance and try to Resinstall the component.

Let me know

regards

Paul



-----
www.pymma.com
The best services on OpenESB
--
Sent from: http://openesb-community-forum.794670.n2.nabble.com/
www.pymma.com The best services on OpenESB