[jboss-jira] [JBoss JIRA] (DROOLS-520) Drool Workbench possible memory leak in Tomcat corrupting future sessions

[Zack Webb (JIRA)]

Zack Webb created DROOLS-520:
--------------------------------

             Summary: Drool Workbench possible memory leak in Tomcat corrupting future sessions
                 Key: DROOLS-520
                 URL: https://issues.jboss.org/browse/DROOLS-520
             Project: Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 6.1.0.CR1
         Environment: Windows 7, Tomcat 7
            Reporter: Zack Webb
            Assignee: Mark Proctor


We noticed this issue because we are converting a large existing spreadsheet into a Guided Decision Table, which we push directly to the workbench's repository by accessing it in the \bin\.niogit directory in the Tomcat folder. We have been continually starting and stopping Tomcat 7 on a laptop and accessing it in the browser by using localhost.

The first time we started Workbench and did this, the table loaded just fine and everything worked. On subsequent startups, we would get this error in Workbench: http://i4.minus.com/ibnfmFrIsmzdWZ.PNG, and this error in the Tomcat window: http://i5.minus.com/iZE2caRBg44eA.PNG

When running Tomcat's shutdown script, we get these errors: http://i7.minus.com/ikJ2oTbFcJlyI.PNG and it hangs at this point rather than eventually closing.

We investigated with JConsole. This is just after running shutdown: http://i3.minus.com/ihxb21FORhPjh.PNG, this is after letting it sit for about 15 minutes: http://i1.minus.com/ibelS7GCS7U7ra.PNG, this is after trying the garbage collection button twice in the Memory tab of JConsole: http://i1.minus.com/iPeseFsRYTWKx.PNG, and this is the list of threads that were still running at the end: http://i2.minus.com/iiVPSNZjHftze.PNG

We have tried completely reinstalling Tomcat and Workbench to fix this problem but it doesn't have any effect. Even after completely replacing the files for both, the newly started instances are still corrupted.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)