Petals SE BPEL

Unstopped thread on component uninstallation

Details

  • Type: Bug Bug
  • Status: New New
  • Priority: Blocker Blocker
  • Resolution: Unresolved
  • Affects Version/s: 1.0.5
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    On an empty Petals instance, after to have installed, next uninstalled the SE BPEL, we can see in the thread list of the Petals node that a thread of the SE BPEL is not stopped. Following, its stack:

    "pool-2-thread-1" prio=10 tid=0x621f6400 nid=0xce3 waiting on condition [0x5fa57000]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
	at java.lang.Thread.sleep(Native Method)
	at com.ebmwebsourcing.easyviper.core.impl.engine.thread.service.AutoFlushMessageServiceImpl.run(AutoFlushMessageServiceImpl.java:55)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)

   Locked ownable synchronizers:
	- <0x745f58e0> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)

    Moreover, please replace calls to Thread.sleep by something else.

    Show
    On an empty Petals instance, after to have installed, next uninstalled the SE BPEL, we can see in the thread list of the Petals node that a thread of the SE BPEL is not stopped. Following, its stack: 
    "pool-2-thread-1" prio=10 tid=0x621f6400 nid=0xce3 waiting on condition [0x5fa57000]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
	at java.lang.Thread.sleep(Native Method)
	at com.ebmwebsourcing.easyviper.core.impl.engine.thread.service.AutoFlushMessageServiceImpl.run(AutoFlushMessageServiceImpl.java:55)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)

   Locked ownable synchronizers:
	- <0x745f58e0> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
    Moreover, please replace calls to Thread.sleep by something else.
  • Environment:
    -

Activity

There aren't workflow transitions executed yet.

People

Dates

  • Created:
    Wed, 3 Nov 2010 - 09:20:39 +0100
    Updated:
    Wed, 3 Nov 2010 - 09:22:54 +0100
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.