Petals Distribution

JBI Exception on re-Start component

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 4.2.1
  • Fix Version/s: 4.2.2
  • Component/s: Components
  • Security Level: Public
  • Description:
    Hide

    On platform Mac OSX, Petals ESB 4.2.1 StandAlone
    petals-cli@localhost:7700>version
    Petals JBI Container 3.5.0-SNAPSHOT
    Java(TM) SE Runtime Environment 20.4-b02-402 Apple Inc.
    Mac OS X 10.6.8 x86_64

    Starting a component: petals-se-pojo with auto-installer
    Then stopping it with Petals-CLI: stop-artifact -a petals-se-pojo SE

    When restarting the component:
    petals-cli@localhost:7700>start-artifact -a petals-se-pojo SE
    ERROR on command 'start-artifact': org.ow2.petals.admin.api.exception.ArtifactAdministrationException: org.ow2.petals.jmx.api.api.exception.ComponentErrorException: org.ow2.petals.jmx.api.impl.exception.PerformActionRemoteErrorException: javax.jbi.JBIException: An exception occured while starting the Component 'petals-se-pojo' : Life cycle exception on START

    On Petals ESB:

    sample-0 2014/06/11 10:14:04,872 GMT+0200 INFO [Petals.Container.Components.petals-se-activitibpmn] : Component initialized
sample-0 2014/06/11 10:14:04,874 GMT+0200 INFO [Petals.Container.Components.petals-se-activitibpmn] : Start component...
sample-0 2014/06/11 10:14:04,956 GMT+0200 INFO [Petals.Container.Components.petals-se-activitibpmn] : Component started
sample-0 2014/06/11 10:14:52,503 GMT+0200 INFO [Petals.Container.Components.petals-se-activitibpmn] : Stop component...
sample-0 2014/06/11 10:14:52,528 GMT+0200 INFO [Petals.Container.Components.petals-se-activitibpmn] : Component stopped
sample-0 2014/06/11 10:43:11,313 GMT+0200 INFO [Petals.Container.Components.petals-se-activitibpmn] : Start component...
sample-0 2014/06/11 10:43:11,384 GMT+0200 INFO [Petals.Container.Components.petals-se-activitibpmn] : Component started
sample-0 2014/06/11 10:43:11,386 GMT+0200 SEVERE [Petals.Container.Lifecycle.ComponentLifeCycle] : Life cycle exception on START
javax.jbi.JBIException: Life cycle exception on START
	at org.ow2.petals.microkernel.api.container.thread.ComponentLifeCycleThread.doTask(ComponentLifeCycleThread.java:118)
	at org.ow2.petals.microkernel.api.container.thread.AbstractThread.run(AbstractThread.java:106)
Caused by: java.lang.IllegalStateException: Task already scheduled or cancelled
	at java.util.Timer.sched(Timer.java:358)
	at java.util.Timer.schedule(Timer.java:222)
	at org.ow2.petals.probes.impl.DurationProbeImpl.doStart(DurationProbeImpl.java:392)
	at org.ow2.petals.probes.impl.AbstractProbe.start(AbstractProbe.java:102)
	at org.ow2.petals.component.framework.monitoring.Monitoring.start(Monitoring.java:311)
	at org.ow2.petals.component.framework.AbstractComponent.start(AbstractComponent.java:558)
	at org.ow2.petals.microkernel.api.container.thread.ComponentLifeCycleThread.doTask(ComponentLifeCycleThread.java:103)
	... 1 more
    Show
    On platform Mac OSX, Petals ESB 4.2.1 StandAlone petals-cli@localhost:7700>version Petals JBI Container 3.5.0-SNAPSHOT Java(TM) SE Runtime Environment 20.4-b02-402 Apple Inc. Mac OS X 10.6.8 x86_64 Starting a component: petals-se-pojo with auto-installer Then stopping it with Petals-CLI: stop-artifact -a petals-se-pojo SE When restarting the component: petals-cli@localhost:7700>start-artifact -a petals-se-pojo SE ERROR on command 'start-artifact': org.ow2.petals.admin.api.exception.ArtifactAdministrationException: org.ow2.petals.jmx.api.api.exception.ComponentErrorException: org.ow2.petals.jmx.api.impl.exception.PerformActionRemoteErrorException: javax.jbi.JBIException: An exception occured while starting the Component 'petals-se-pojo' : Life cycle exception on START On Petals ESB: 
    sample-0 2014/06/11 10:14:04,872 GMT+0200 INFO [Petals.Container.Components.petals-se-activitibpmn] : Component initialized
sample-0 2014/06/11 10:14:04,874 GMT+0200 INFO [Petals.Container.Components.petals-se-activitibpmn] : Start component...
sample-0 2014/06/11 10:14:04,956 GMT+0200 INFO [Petals.Container.Components.petals-se-activitibpmn] : Component started
sample-0 2014/06/11 10:14:52,503 GMT+0200 INFO [Petals.Container.Components.petals-se-activitibpmn] : Stop component...
sample-0 2014/06/11 10:14:52,528 GMT+0200 INFO [Petals.Container.Components.petals-se-activitibpmn] : Component stopped
sample-0 2014/06/11 10:43:11,313 GMT+0200 INFO [Petals.Container.Components.petals-se-activitibpmn] : Start component...
sample-0 2014/06/11 10:43:11,384 GMT+0200 INFO [Petals.Container.Components.petals-se-activitibpmn] : Component started
sample-0 2014/06/11 10:43:11,386 GMT+0200 SEVERE [Petals.Container.Lifecycle.ComponentLifeCycle] : Life cycle exception on START
javax.jbi.JBIException: Life cycle exception on START
	at org.ow2.petals.microkernel.api.container.thread.ComponentLifeCycleThread.doTask(ComponentLifeCycleThread.java:118)
	at org.ow2.petals.microkernel.api.container.thread.AbstractThread.run(AbstractThread.java:106)
Caused by: java.lang.IllegalStateException: Task already scheduled or cancelled
	at java.util.Timer.sched(Timer.java:358)
	at java.util.Timer.schedule(Timer.java:222)
	at org.ow2.petals.probes.impl.DurationProbeImpl.doStart(DurationProbeImpl.java:392)
	at org.ow2.petals.probes.impl.AbstractProbe.start(AbstractProbe.java:102)
	at org.ow2.petals.component.framework.monitoring.Monitoring.start(Monitoring.java:311)
	at org.ow2.petals.component.framework.AbstractComponent.start(AbstractComponent.java:558)
	at org.ow2.petals.microkernel.api.container.thread.ComponentLifeCycleThread.doTask(ComponentLifeCycleThread.java:103)
	... 1 more
  • Environment:
    Mac OS X 10.6.8 x86_64

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Thu, 12 Jun 2014 - 10:19:44 +0200

When restarting a JBI component a error occurs into the restart of monitoring probes because a TimerTask is re-used on scheduling instead of using a new one.

Show
Christophe DENEUX added a comment - Thu, 12 Jun 2014 - 10:19:44 +0200 When restarting a JBI component a error occurs into the restart of monitoring probes because a TimerTask is re-used on scheduling instead of using a new one.
Hide
Permalink
Christophe DENEUX added a comment - Thu, 12 Jun 2014 - 15:30:42 +0200

Set to resolved as PETALSCDK-116 is resolved

Show
Christophe DENEUX added a comment - Thu, 12 Jun 2014 - 15:30:42 +0200 Set to resolved as PETALSCDK-116 is resolved

People

Dates

  • Created:
    Wed, 11 Jun 2014 - 10:51:53 +0200
    Updated:
    Thu, 12 Jun 2014 - 15:30:42 +0200
    Resolved:
    Thu, 12 Jun 2014 - 15:30:42 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.