Unexpected shutdown of service
patrickawilson Dec 20, 2013 12:39 PMThings move along normally, sometimes for an hour or more ...
^[[0m^[[0m11:50:05,624 INFO [stdout] (http-/0.0.0.0:8088-1) Sent message to OpsCenter
^[[0m^[[0m11:55:03,924 INFO [stdout] (http-/0.0.0.0:8088-1) Sent message to OpsCenter
^[[0m^[[0m12:00:07,591 INFO [stdout] (http-/0.0.0.0:8088-1) Sent message to OpsCenter
^[[0m^[[0m12:05:03,937 INFO [stdout] (http-/0.0.0.0:8088-1) Sent message to OpsCenter
^[[0m^[[0m12:10:09,138 INFO [stdout] (http-/0.0.0.0:8088-1) Sent message to OpsCenter
Then the service is shut down, which is not desirable.
^[[0m^[[0m12:11:18,333 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010410: Unbound JCA ConnectionFactory [java:jboss/ConsertOpsCenterConnectionFactory]
^[[0m^[[0m12:11:18,327 INFO [org.apache.catalina.core] (MSC service thread 1-1) JBWEB001079: Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
^[[0m^[[0m12:11:18,340 INFO [org.apache.coyote.http11] (MSC service thread 1-3) JBWEB003075: Coyote HTTP/1.1 pausing on: http-/0.0.0.0:8088
^[[0m^[[0m12:11:18,346 INFO [org.apache.coyote.http11] (MSC service thread 1-3) JBWEB003077: Coyote HTTP/1.1 stopping on : http-/0.0.0.0:8088
^[[0m^[[0m12:11:18,386 INFO [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015540: Stopping service jboss.ws.endpoint."GenericGSCIMService.deployment".GenericGSCIMService
^[[0m^[[0m12:11:18,391 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022051: Endpoint unregistered: jboss.ws:context=GenericGSCIMService,endpoint=GenericGSCIMService
^[[0m^[[0m12:11:18,395 INFO [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015540: Stopping service jboss.ws.endpoint."OpsCenterUndeliveredMessagesService.deployment".OpsCenterUndeliveredMessagesService
^[[0m^[[0m12:11:18,396 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022051: Endpoint unregistered: jboss.ws:context=OpsCenterUndeliveredMessagesService,endpoint=OpsCenterUndeliveredMessagesService
etc. etc. etc. as shutdown proceeds.
It looks like the connection factory might have lost the connection, but why would that cause the entire service to collapse? What I want is for the service to remain up and running and for Switchyard to keep trying. I have code in place for failure handling, but that all gets shut down if the whole service is stopped. Is there something that I can configure to prevent this?
Thanks