We are not running solaris we are on Centos with a Sun JVM. However I believe
the issue is the same and am working on upgrading the JVM on our boxes.
Mario Fusco wrote
I think this is definitively related with the version of the JVM you're
using. Exactly the same problem has been already reported on a JVM running
on Solaris (
https://issues.jboss.org/browse/JBRULES-3534 ) and fixed by
this commit:
https://github.com/droolsjbpm/drools/commit/caf0d24f53f263e06af17ffcb2f72...
The fix will be available with the 5.4.1, but I am pretty sure that
updating your JVM (unless you are not on Solaris too) will work for you.
Mario
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-5-4-DSLR-Stack-Overflow-tp401855...
Sent from the Drools: User forum mailing list archive at
Nabble.com.