<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Activiti thread blocked at the startup of Websphere Application Server in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/activiti-thread-blocked-at-the-startup-of-websphere-application/m-p/144293#M100906</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello Hermes,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;it's indeed pretty tricky to see anything in the log. You should consider that WebSphere does not like the long running Job Executor Thread. In Java EE environments you are discouraged to create new threads on your own - but that's exactly what's done in the default Activiti JobExecutor implementation.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Have a look at this thread (&lt;/SPAN&gt;&lt;A href="http://forums.activiti.org/comment/9783" rel="nofollow noopener noreferrer"&gt;http://forums.activiti.org/comment/9783&lt;/A&gt;&lt;SPAN&gt;) and consider the implementation Heiko (bardioc) posted:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.activiti.org/comment/9783#comment-9783" rel="nofollow noopener noreferrer"&gt;http://forums.activiti.org/comment/9783#comment-9783&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Sebastian&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 10 May 2013 20:06:19 GMT</pubDate>
    <dc:creator>sebastian_s</dc:creator>
    <dc:date>2013-05-10T20:06:19Z</dc:date>
    <item>
      <title>Activiti thread blocked at the startup of Websphere Application Server</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-thread-blocked-at-the-startup-of-websphere-application/m-p/144291#M100904</link>
      <description>Got the below error at at the startup of Websphere Application Server:2013-04-16 10:31:02Full thread dump IBM J9 VM (2.4 JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr10fp1-20120202_101568 (JIT enabled, AOT enabled)J9VM - 20120202_101568JIT&amp;nbsp; - r9_20111107_21307ifx1GC&amp;nbsp;&amp;nbsp; - 20120202_AA_CMPRSS): "P=54365</description>
      <pubDate>Mon, 29 Apr 2013 09:23:47 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-thread-blocked-at-the-startup-of-websphere-application/m-p/144291#M100904</guid>
      <dc:creator>hermes</dc:creator>
      <dc:date>2013-04-29T09:23:47Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti thread blocked at the startup of Websphere Application Server</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-thread-blocked-at-the-startup-of-websphere-application/m-p/144292#M100905</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Honestly, it's pretty tricky to see anything in these logs (they're quite extensive to say the least).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Can you pinpoint exactly why it is blocking.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Apr 2013 09:06:11 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-thread-blocked-at-the-startup-of-websphere-application/m-p/144292#M100905</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2013-04-30T09:06:11Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti thread blocked at the startup of Websphere Application Server</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-thread-blocked-at-the-startup-of-websphere-application/m-p/144293#M100906</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello Hermes,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;it's indeed pretty tricky to see anything in the log. You should consider that WebSphere does not like the long running Job Executor Thread. In Java EE environments you are discouraged to create new threads on your own - but that's exactly what's done in the default Activiti JobExecutor implementation.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Have a look at this thread (&lt;/SPAN&gt;&lt;A href="http://forums.activiti.org/comment/9783" rel="nofollow noopener noreferrer"&gt;http://forums.activiti.org/comment/9783&lt;/A&gt;&lt;SPAN&gt;) and consider the implementation Heiko (bardioc) posted:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.activiti.org/comment/9783#comment-9783" rel="nofollow noopener noreferrer"&gt;http://forums.activiti.org/comment/9783#comment-9783&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Sebastian&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 May 2013 20:06:19 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-thread-blocked-at-the-startup-of-websphere-application/m-p/144293#M100906</guid>
      <dc:creator>sebastian_s</dc:creator>
      <dc:date>2013-05-10T20:06:19Z</dc:date>
    </item>
  </channel>
</rss>

