[JBoss JIRA] Created: (JBRULES-2313) Tomcat memery leak with drools 4.0.7 or 5.0.1
by GREFFET Emmanuel (JIRA)
Tomcat memery leak with drools 4.0.7 or 5.0.1
----------------------------------------------
Key: JBRULES-2313
URL: https://jira.jboss.org/jira/browse/JBRULES-2313
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (expert)
Affects Versions: 5.0.1.FINAL, 4.0.7
Environment: XP tomcat 5.5.9
Reporter: GREFFET Emmanuel
Assignee: Mark Proctor
Priority: Critical
The memory is never released !!! (never ever ) when à Stop and Start or restart Tomcat.
A made this test with a simple Drools call with a simple webapp and i tried with 4.0.7 and 5.0.1 drools version. The problem is the same.
We need to stop tomcat process to release memory. Until this stop each Tomcat "Restart" with a drools call, will never release the memory.
I made graphic with VisualWM, and we can see this problem !
I made a zip of my simple Eclipse project (webapp + drools) and word file for more information and screen copy of VisualVM.
Thanks for help.
Emmanuel GREFFET ( FRANCE)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBAS-5515) Failed to load users/passwords/role files
by Heiko Braun (JIRA)
Failed to load users/passwords/role files
-----------------------------------------
Key: JBAS-5515
URL: http://jira.jboss.com/jira/browse/JBAS-5515
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Heiko Braun
Fix For: JBossAS-5.0.0.CR1
21:25:41,277 ERROR [UsersRolesLoginModule] Failed to load users/passwords/role files
java.io.IOException: No properties file: users.properties or defaults: defaultUsers.properties found
at org.jboss.security.auth.spi.Util.loadProperties(Util.java:366)
at org.jboss.security.auth.spi.UsersRolesLoginModule.loadUsers(UsersRolesLoginModule.java:186)
at org.jboss.security.auth.spi.UsersRolesLoginModule.createUsers(UsersRolesLoginModule.java:200)
at org.jboss.security.auth.spi.UsersRolesLoginModule.initialize(UsersRolesLoginModule.java:127)
When executing
one-test:
[junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase
[junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 2.421 sec
[junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase FAILED
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBRULES-681) Multi-threaded local search solving
by Geoffrey De Smet (JIRA)
Multi-threaded local search solving
-----------------------------------
Key: JBRULES-681
URL: http://jira.jboss.com/jira/browse/JBRULES-681
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Solver
Reporter: Geoffrey De Smet
Assigned To: Geoffrey De Smet
Priority: Optional
Use Future's to spread all possible moves in each step over a number of threads.
This number of threads is equal to the number of cpu's by default, as no IO is done during solving.
Problems:
- each thread will needs it own WorkingMemory and during a step, each working memory will need to be updated
- a bunch of classes will need to be thread safe, or at least visibility save, such as bestsolutionrecaller.
- Barriers will be needed to collect the result of each step
- decks might be a great way to spread out the load
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months