Bug 1069651

Summary: Multiple logins of the same user in cluster setup with mod_cluster load balancer results in IllegalAccessError: tried to access method org.jboss.solder.exception.control.ExceptionStack.dropCause()V
Product: [Retired] JBoss BPMS Platform 6 Reporter: Jiri Svitak <jsvitak>
Component: Business CentralAssignee: Roger Martínez <romartin>
Status: CLOSED DUPLICATE QA Contact: Jiri Svitak <jsvitak>
Severity: medium Docs Contact:
Priority: high    
Version: 6.0.1CC: mbaluch, rrajasek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-27 17:45:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
server.log none

Description Jiri Svitak 2014-02-25 13:22:31 UTC
Created attachment 867408 [details]
server.log

Multiple logins of the same user in cluster setup with mod_cluster load balancer results in Caused by: java.lang.IllegalAccessError: tried to access method org.jboss.solder.exception.control.ExceptionStack.dropCause()V from class org.jboss.solder.exception.control.ExceptionHandlerDispatch

My cluster setup was done in perflab on physical machines. I have httpd load balancer with mod_cluster 1.2.4 and two worker nodes configured in full-ha profile in domain mode (full for JMS and ha for mod_cluster loadbalancing support).

For more details please ask, or check blog post http://mswiderski.blogspot.com.br/2013/06/clustering-in-jbpm-v6.html

Just an exception is thrown in server.log and I experience sometimes slower responses. However, I am able to login and I have checked that when working via address of loadbalancer, both nodes seem to be correctly synchronized.

I have no reports that this issue occurs while running standalone business-central.


My env:
BPMS 6.0.1.ER1
EAP 6.1.1
jboss-ews 2.0 with mod_cluster 1.2.4

Comment 1 Kris Verlaenen 2014-02-25 13:42:26 UTC
Roger, this seems similar to other module issues we had, could you check this?

Comment 2 Roger Martínez 2014-02-25 21:05:01 UTC
Hi Jiri,

This issue has been fixed in
- https://bugzilla.redhat.com/show_bug.cgi?id=1067048

Please, take a look at the last comment for that issue which explains the problem and the solution.

I'm asking if it's easy for you to reproduce that issue using the modules version with the fix of the BZ 1067048, then we could consider this issue close and duplicate of BZ 1067048... :)

Thanks in advance.
Roger

(In reply to Jiri Svitak from comment #0)
> Created attachment 867408 [details]
> server.log
> 
> Multiple logins of the same user in cluster setup with mod_cluster load
> balancer results in Caused by: java.lang.IllegalAccessError: tried to access
> method org.jboss.solder.exception.control.ExceptionStack.dropCause()V from
> class org.jboss.solder.exception.control.ExceptionHandlerDispatch
> 
> My cluster setup was done in perflab on physical machines. I have httpd load
> balancer with mod_cluster 1.2.4 and two worker nodes configured in full-ha
> profile in domain mode (full for JMS and ha for mod_cluster loadbalancing
> support).
> 
> For more details please ask, or check blog post
> http://mswiderski.blogspot.com.br/2013/06/clustering-in-jbpm-v6.html
> 
> Just an exception is thrown in server.log and I experience sometimes slower
> responses. However, I am able to login and I have checked that when working
> via address of loadbalancer, both nodes seem to be correctly synchronized.
> 
> I have no reports that this issue occurs while running standalone
> business-central.
> 
> 
> My env:
> BPMS 6.0.1.ER1
> EAP 6.1.1
> jboss-ews 2.0 with mod_cluster 1.2.4

Comment 3 Jiri Svitak 2014-02-27 17:45:49 UTC
I was able to use the steps from the mentioned bugzilla as a workaround.

As this should be already fixed and tracked in a different BZ, I am closing this one as a duplicate.

*** This bug has been marked as a duplicate of bug 1067048 ***