java.lang.OutOfMemoryError: Java heap space

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

java.lang.OutOfMemoryError: Java heap space

vdelbart
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: java.lang.OutOfMemoryError: Java heap space

vdelbart
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: java.lang.OutOfMemoryError: Java heap space

vdelbart
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: java.lang.OutOfMemoryError: Java heap space

Edson Tirelli-3
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: java.lang.OutOfMemoryError: Java heap space

lhorton
Has this issue been fixed, or is it still necessary to remove any event listeners so that the session is freed?
Reply | Threaded
Open this post in threaded view
|

Re: [rules-users] java.lang.OutOfMemoryError: Java heap space

Mark Proctor
Do you have a JIRA to reference for this? Without that it's hard to check.

Mark
On 12 Oct 2012, at 23:24, lhorton <[hidden email]> wrote:

> Has this issue been fixed, or is it still necessary to remove any event
> listeners so that the session is freed?
>
>
>
> --
> View this message in context: http://drools.46999.n3.nabble.com/java-lang-OutOfMemoryError-Java-heap-space-tp54778p4020267.html
> Sent from the Drools: User forum mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/rules-users


_______________________________________________
rules-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/rules-users
Reply | Threaded
Open this post in threaded view
|

Re: [rules-users] java.lang.OutOfMemoryError: Java heap space

lhorton
Sorry, there was a JIRA link in the message thread that I didn't notice.  https://issues.jboss.org/browse/JBRULES-1325 says the leak was fixed in 5.0