[JBoss JIRA] (SECURITY-772) SPNEGOLoginModule does not always respect removeRealmFromPrincipal
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/SECURITY-772?page=com.atlassian.jira.plug... ]
RH Bugzilla Integration commented on SECURITY-772:
--------------------------------------------------
Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1039989|https://bugzilla.redhat.com/show_bug.cgi?id=1039989] from MODIFIED to ON_QA
> SPNEGOLoginModule does not always respect removeRealmFromPrincipal
> ------------------------------------------------------------------
>
> Key: SECURITY-772
> URL: https://issues.jboss.org/browse/SECURITY-772
> Project: PicketBox
> Issue Type: Bug
> Components: Negotiation
> Affects Versions: Negotiation_2_2_6
> Reporter: Tom Fonteyne
> Assignee: Tom Fonteyne
> Priority: Minor
> Fix For: Negotiation_2_2_7
>
>
> org.jboss.security.negotiation.spnego.SPNEGOLoginModule
> private class AcceptSecContext:
> if (gssContext.isEstablished())
> {
> log.warn("Authentication was performed despite already being authenticated!");
> // TODO - Refactor to only do this once.
> setIdentity(new KerberosPrincipal(gssContext.getSrcName().toString()));
> The last line should obey the "removeRealmFromPrincipal" flag similarly as a bit further down:
> setIdentity(createIdentity(gssContext.getSrcName().toString()));
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (DROOLS-701) Drools audit log eclipse not opening
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-701?page=com.atlassian.jira.plugin... ]
Mario Fusco commented on DROOLS-701:
------------------------------------
No problem, it's far better to have a duplicated error report than a uncaught bug :)
Thanks a lor for your unvaluable help.
> Drools audit log eclipse not opening
> ------------------------------------
>
> Key: DROOLS-701
> URL: https://issues.jboss.org/browse/DROOLS-701
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.CR3
> Environment: Eclipse Audit log view
> Reporter: Matteo Mortari
> Assignee: Mario Fusco
> Fix For: 6.2.0.Final
>
> Attachments: 20150129.drools6test_auditlog_eclipse.zip
>
>
> With reference to drools-setup discussion thread, I'm don't have the same scenario of Gergely which is open as DROOLS-672:
> {quote}
> First of all: this problem can be reproduced with only a single audit file.
> {quote}
> but I got a reproducer for the scenario I describe:
> {quote}
> I'm experiencing similar behavior and stacktrace in the Eclipse log, when I get as a result several Audit logs file ( because of the many insert/fire etc therefore many audit records results in automatic file splits ).
> When I have several audit logs, some logs do open in the Audit view correctly; other log files in the sequence do not open and as you describe Audit view is empty and that stacktrace output is produced in the Eclipse log.
> Do you have the same experience?
> I'm asking as you seem to mention about a single log file but I was wondering if it's actually one in a sequence of audit log.
> I'm also wondering if this is due to the log containing some cross-reference to other log records not appearing in this file instance but the previous/next, making the java code which is constructing the items in the Audit log treeview fail with that stacktrace.
> {quote}
> It could be the solution to this bug/reproducer will solve the same issue as Gergely, but I cannot tell if our cases are really the same hence I prefer to raise this as a new separate JIRA bug record.
> h5. Steps to reproduce
> With reference to attached reproducer
> the first sessionlog.log log file opens correctly.
> From log file sessionlog1.log it will no longer open, Audit view blank, causing the stacktrace error in Eclipse workspace log (ref. below).
> The log file sessionlog1.log starts with event:
> {code}
> <org.drools.core.audit.event.ObjectLogEvent>
> <type>3</type
> {code}
> No other log files in the sequence 1-22 will open.
> Until sessionlog23.log, which starts with event:
> {code}
> <org.drools.core.audit.event.ActivationLogEvent>
> <type>4</type>
> {code}
> The log files in the sequence 23-44 will open again.
> Until stop to display again from log file sessionlog45.log, which starts with
> {code}
> <org.drools.core.audit.event.ActivationLogEvent>
> <type>7</type>
> {code}
> when Audit view blank, in the Eclipse workspace log (under workspace/.metadata) will display this or analogous:
>
> The eclipse workspace log stacktrace when trying to open in Audit view one "out of sequence" log
> {code}
> !ENTRY org.eclipse.ui 4 0 2015-01-29 15:04:06.339
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.util.EmptyStackException
> at java.util.Stack.peek(Unknown Source)
> at java.util.Stack.pop(Unknown Source)
> at org.drools.eclipse.debug.AuditView.createPhreakEventList(AuditView.java:238)
> at org.drools.eclipse.debug.AuditView.refresh(AuditView.java:150)
> at org.drools.eclipse.debug.AuditView.setLogFile(AuditView.java:104)
> at org.drools.eclipse.debug.actions.FileAuditDropAdapter.performDrop(FileAuditDropAdapter.java:39)
> at org.eclipse.jface.viewers.ViewerDropAdapter.drop(ViewerDropAdapter.java:254)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (DROOLS-701) Drools audit log eclipse not opening
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-701?page=com.atlassian.jira.plugin... ]
Matteo Mortari commented on DROOLS-701:
---------------------------------------
Good news - sorry "suggestimate" looks like only to pull possible duplicate from JIRA, not RH's bugzilla ...but to be honest also this case would have been too different descriptions for me to notice =)
Sorry and thanks again.
> Drools audit log eclipse not opening
> ------------------------------------
>
> Key: DROOLS-701
> URL: https://issues.jboss.org/browse/DROOLS-701
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.CR3
> Environment: Eclipse Audit log view
> Reporter: Matteo Mortari
> Assignee: Mario Fusco
> Fix For: 6.2.0.Final
>
> Attachments: 20150129.drools6test_auditlog_eclipse.zip
>
>
> With reference to drools-setup discussion thread, I'm don't have the same scenario of Gergely which is open as DROOLS-672:
> {quote}
> First of all: this problem can be reproduced with only a single audit file.
> {quote}
> but I got a reproducer for the scenario I describe:
> {quote}
> I'm experiencing similar behavior and stacktrace in the Eclipse log, when I get as a result several Audit logs file ( because of the many insert/fire etc therefore many audit records results in automatic file splits ).
> When I have several audit logs, some logs do open in the Audit view correctly; other log files in the sequence do not open and as you describe Audit view is empty and that stacktrace output is produced in the Eclipse log.
> Do you have the same experience?
> I'm asking as you seem to mention about a single log file but I was wondering if it's actually one in a sequence of audit log.
> I'm also wondering if this is due to the log containing some cross-reference to other log records not appearing in this file instance but the previous/next, making the java code which is constructing the items in the Audit log treeview fail with that stacktrace.
> {quote}
> It could be the solution to this bug/reproducer will solve the same issue as Gergely, but I cannot tell if our cases are really the same hence I prefer to raise this as a new separate JIRA bug record.
> h5. Steps to reproduce
> With reference to attached reproducer
> the first sessionlog.log log file opens correctly.
> From log file sessionlog1.log it will no longer open, Audit view blank, causing the stacktrace error in Eclipse workspace log (ref. below).
> The log file sessionlog1.log starts with event:
> {code}
> <org.drools.core.audit.event.ObjectLogEvent>
> <type>3</type
> {code}
> No other log files in the sequence 1-22 will open.
> Until sessionlog23.log, which starts with event:
> {code}
> <org.drools.core.audit.event.ActivationLogEvent>
> <type>4</type>
> {code}
> The log files in the sequence 23-44 will open again.
> Until stop to display again from log file sessionlog45.log, which starts with
> {code}
> <org.drools.core.audit.event.ActivationLogEvent>
> <type>7</type>
> {code}
> when Audit view blank, in the Eclipse workspace log (under workspace/.metadata) will display this or analogous:
>
> The eclipse workspace log stacktrace when trying to open in Audit view one "out of sequence" log
> {code}
> !ENTRY org.eclipse.ui 4 0 2015-01-29 15:04:06.339
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.util.EmptyStackException
> at java.util.Stack.peek(Unknown Source)
> at java.util.Stack.pop(Unknown Source)
> at org.drools.eclipse.debug.AuditView.createPhreakEventList(AuditView.java:238)
> at org.drools.eclipse.debug.AuditView.refresh(AuditView.java:150)
> at org.drools.eclipse.debug.AuditView.setLogFile(AuditView.java:104)
> at org.drools.eclipse.debug.actions.FileAuditDropAdapter.performDrop(FileAuditDropAdapter.java:39)
> at org.eclipse.jface.viewers.ViewerDropAdapter.drop(ViewerDropAdapter.java:254)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (WFLY-4298) DatabaseServerLoginModule doesn't support SHA-512 with Java 8
by Markus Eisele (JIRA)
Markus Eisele created WFLY-4298:
-----------------------------------
Summary: DatabaseServerLoginModule doesn't support SHA-512 with Java 8
Key: WFLY-4298
URL: https://issues.jboss.org/browse/WFLY-4298
Project: WildFly
Issue Type: Feature Request
Components: Security
Affects Versions: 8.2.0.Final
Environment: Win 7, x64
java version "1.8.0_20"
Java(TM) SE Runtime Environment (build 1.8.0_20-b26)
Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode)
Reporter: Markus Eisele
Assignee: Darran Lofthouse
I tried to use the following security domain configuration:
<security-domain name="secureDomain" cache-type="default">
<authentication>
<login-module code="Database" flag="required">
<module-option name="dsJndiName" value="java:jboss/datsources/MySQLTestDS"/>
<module-option name="principalsQuery" value="SELECT password FROM user WHERE email=?"/>
<module-option name="rolesQuery" value="select role, 'Roles' from role where email=?"/>
<module-option name="hashAlgorithm" value="SHA-512"/>
<module-option name="hashEncoding" value="base64"/>
</login-module>
</authentication>
</security-domain>
And never got a user successfully authenticated. Works with hashAlgorithm SHA-256
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (DROOLS-701) Drools audit log eclipse not opening
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-701?page=com.atlassian.jira.plugin... ]
Mario Fusco resolved DROOLS-701.
--------------------------------
Fix Version/s: 6.2.0.Final
Resolution: Duplicate Issue
This issue has been already reported here https://bugzilla.redhat.com/show_bug.cgi?id=1117954 and fixed with this commit https://github.com/droolsjbpm/drools/commit/5e05721f4a81d9f80285c0dc1216d...
> Drools audit log eclipse not opening
> ------------------------------------
>
> Key: DROOLS-701
> URL: https://issues.jboss.org/browse/DROOLS-701
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.CR3
> Environment: Eclipse Audit log view
> Reporter: Matteo Mortari
> Assignee: Mario Fusco
> Fix For: 6.2.0.Final
>
> Attachments: 20150129.drools6test_auditlog_eclipse.zip
>
>
> With reference to drools-setup discussion thread, I'm don't have the same scenario of Gergely which is open as DROOLS-672:
> {quote}
> First of all: this problem can be reproduced with only a single audit file.
> {quote}
> but I got a reproducer for the scenario I describe:
> {quote}
> I'm experiencing similar behavior and stacktrace in the Eclipse log, when I get as a result several Audit logs file ( because of the many insert/fire etc therefore many audit records results in automatic file splits ).
> When I have several audit logs, some logs do open in the Audit view correctly; other log files in the sequence do not open and as you describe Audit view is empty and that stacktrace output is produced in the Eclipse log.
> Do you have the same experience?
> I'm asking as you seem to mention about a single log file but I was wondering if it's actually one in a sequence of audit log.
> I'm also wondering if this is due to the log containing some cross-reference to other log records not appearing in this file instance but the previous/next, making the java code which is constructing the items in the Audit log treeview fail with that stacktrace.
> {quote}
> It could be the solution to this bug/reproducer will solve the same issue as Gergely, but I cannot tell if our cases are really the same hence I prefer to raise this as a new separate JIRA bug record.
> h5. Steps to reproduce
> With reference to attached reproducer
> the first sessionlog.log log file opens correctly.
> From log file sessionlog1.log it will no longer open, Audit view blank, causing the stacktrace error in Eclipse workspace log (ref. below).
> The log file sessionlog1.log starts with event:
> {code}
> <org.drools.core.audit.event.ObjectLogEvent>
> <type>3</type
> {code}
> No other log files in the sequence 1-22 will open.
> Until sessionlog23.log, which starts with event:
> {code}
> <org.drools.core.audit.event.ActivationLogEvent>
> <type>4</type>
> {code}
> The log files in the sequence 23-44 will open again.
> Until stop to display again from log file sessionlog45.log, which starts with
> {code}
> <org.drools.core.audit.event.ActivationLogEvent>
> <type>7</type>
> {code}
> when Audit view blank, in the Eclipse workspace log (under workspace/.metadata) will display this or analogous:
>
> The eclipse workspace log stacktrace when trying to open in Audit view one "out of sequence" log
> {code}
> !ENTRY org.eclipse.ui 4 0 2015-01-29 15:04:06.339
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.util.EmptyStackException
> at java.util.Stack.peek(Unknown Source)
> at java.util.Stack.pop(Unknown Source)
> at org.drools.eclipse.debug.AuditView.createPhreakEventList(AuditView.java:238)
> at org.drools.eclipse.debug.AuditView.refresh(AuditView.java:150)
> at org.drools.eclipse.debug.AuditView.setLogFile(AuditView.java:104)
> at org.drools.eclipse.debug.actions.FileAuditDropAdapter.performDrop(FileAuditDropAdapter.java:39)
> at org.eclipse.jface.viewers.ViewerDropAdapter.drop(ViewerDropAdapter.java:254)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (DROOLS-701) Drools audit log eclipse not opening
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-701?page=com.atlassian.jira.plugin... ]
Mario Fusco reassigned DROOLS-701:
----------------------------------
Assignee: Mario Fusco (was: Mark Proctor)
> Drools audit log eclipse not opening
> ------------------------------------
>
> Key: DROOLS-701
> URL: https://issues.jboss.org/browse/DROOLS-701
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.CR3
> Environment: Eclipse Audit log view
> Reporter: Matteo Mortari
> Assignee: Mario Fusco
> Attachments: 20150129.drools6test_auditlog_eclipse.zip
>
>
> With reference to drools-setup discussion thread, I'm don't have the same scenario of Gergely which is open as DROOLS-672:
> {quote}
> First of all: this problem can be reproduced with only a single audit file.
> {quote}
> but I got a reproducer for the scenario I describe:
> {quote}
> I'm experiencing similar behavior and stacktrace in the Eclipse log, when I get as a result several Audit logs file ( because of the many insert/fire etc therefore many audit records results in automatic file splits ).
> When I have several audit logs, some logs do open in the Audit view correctly; other log files in the sequence do not open and as you describe Audit view is empty and that stacktrace output is produced in the Eclipse log.
> Do you have the same experience?
> I'm asking as you seem to mention about a single log file but I was wondering if it's actually one in a sequence of audit log.
> I'm also wondering if this is due to the log containing some cross-reference to other log records not appearing in this file instance but the previous/next, making the java code which is constructing the items in the Audit log treeview fail with that stacktrace.
> {quote}
> It could be the solution to this bug/reproducer will solve the same issue as Gergely, but I cannot tell if our cases are really the same hence I prefer to raise this as a new separate JIRA bug record.
> h5. Steps to reproduce
> With reference to attached reproducer
> the first sessionlog.log log file opens correctly.
> From log file sessionlog1.log it will no longer open, Audit view blank, causing the stacktrace error in Eclipse workspace log (ref. below).
> The log file sessionlog1.log starts with event:
> {code}
> <org.drools.core.audit.event.ObjectLogEvent>
> <type>3</type
> {code}
> No other log files in the sequence 1-22 will open.
> Until sessionlog23.log, which starts with event:
> {code}
> <org.drools.core.audit.event.ActivationLogEvent>
> <type>4</type>
> {code}
> The log files in the sequence 23-44 will open again.
> Until stop to display again from log file sessionlog45.log, which starts with
> {code}
> <org.drools.core.audit.event.ActivationLogEvent>
> <type>7</type>
> {code}
> when Audit view blank, in the Eclipse workspace log (under workspace/.metadata) will display this or analogous:
>
> The eclipse workspace log stacktrace when trying to open in Audit view one "out of sequence" log
> {code}
> !ENTRY org.eclipse.ui 4 0 2015-01-29 15:04:06.339
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.util.EmptyStackException
> at java.util.Stack.peek(Unknown Source)
> at java.util.Stack.pop(Unknown Source)
> at org.drools.eclipse.debug.AuditView.createPhreakEventList(AuditView.java:238)
> at org.drools.eclipse.debug.AuditView.refresh(AuditView.java:150)
> at org.drools.eclipse.debug.AuditView.setLogFile(AuditView.java:104)
> at org.drools.eclipse.debug.actions.FileAuditDropAdapter.performDrop(FileAuditDropAdapter.java:39)
> at org.eclipse.jface.viewers.ViewerDropAdapter.drop(ViewerDropAdapter.java:254)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (DROOLS-701) Drools audit log eclipse not opening
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-701?page=com.atlassian.jira.plugin... ]
Matteo Mortari updated DROOLS-701:
----------------------------------
Attachment: 20150129.drools6test_auditlog_eclipse.zip
The reproducer as described. I've left log files in the log directory, for the ease.
> Drools audit log eclipse not opening
> ------------------------------------
>
> Key: DROOLS-701
> URL: https://issues.jboss.org/browse/DROOLS-701
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.CR3
> Environment: Eclipse Audit log view
> Reporter: Matteo Mortari
> Assignee: Mark Proctor
> Attachments: 20150129.drools6test_auditlog_eclipse.zip
>
>
> With reference to drools-setup discussion thread, I'm don't have the same scenario of Gergely which is open as DROOLS-672:
> {quote}
> First of all: this problem can be reproduced with only a single audit file.
> {quote}
> but I got a reproducer for the scenario I describe:
> {quote}
> I'm experiencing similar behavior and stacktrace in the Eclipse log, when I get as a result several Audit logs file ( because of the many insert/fire etc therefore many audit records results in automatic file splits ).
> When I have several audit logs, some logs do open in the Audit view correctly; other log files in the sequence do not open and as you describe Audit view is empty and that stacktrace output is produced in the Eclipse log.
> Do you have the same experience?
> I'm asking as you seem to mention about a single log file but I was wondering if it's actually one in a sequence of audit log.
> I'm also wondering if this is due to the log containing some cross-reference to other log records not appearing in this file instance but the previous/next, making the java code which is constructing the items in the Audit log treeview fail with that stacktrace.
> {quote}
> It could be the solution to this bug/reproducer will solve the same issue as Gergely, but I cannot tell if our cases are really the same hence I prefer to raise this as a new separate JIRA bug record.
> h5. Steps to reproduce
> With reference to attached reproducer
> the first sessionlog.log log file opens correctly.
> From log file sessionlog1.log it will no longer open, Audit view blank, causing the stacktrace error in Eclipse workspace log (ref. below).
> The log file sessionlog1.log starts with event:
> {code}
> <org.drools.core.audit.event.ObjectLogEvent>
> <type>3</type
> {code}
> No other log files in the sequence 1-22 will open.
> Until sessionlog23.log, which starts with event:
> {code}
> <org.drools.core.audit.event.ActivationLogEvent>
> <type>4</type>
> {code}
> The log files in the sequence 23-44 will open again.
> Until stop to display again from log file sessionlog45.log, which starts with
> {code}
> <org.drools.core.audit.event.ActivationLogEvent>
> <type>7</type>
> {code}
> when Audit view blank, in the Eclipse workspace log (under workspace/.metadata) will display this or analogous:
>
> The eclipse workspace log stacktrace when trying to open in Audit view one "out of sequence" log
> {code}
> !ENTRY org.eclipse.ui 4 0 2015-01-29 15:04:06.339
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.util.EmptyStackException
> at java.util.Stack.peek(Unknown Source)
> at java.util.Stack.pop(Unknown Source)
> at org.drools.eclipse.debug.AuditView.createPhreakEventList(AuditView.java:238)
> at org.drools.eclipse.debug.AuditView.refresh(AuditView.java:150)
> at org.drools.eclipse.debug.AuditView.setLogFile(AuditView.java:104)
> at org.drools.eclipse.debug.actions.FileAuditDropAdapter.performDrop(FileAuditDropAdapter.java:39)
> at org.eclipse.jface.viewers.ViewerDropAdapter.drop(ViewerDropAdapter.java:254)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (DROOLS-701) Drools audit log eclipse not opening
by Matteo Mortari (JIRA)
Matteo Mortari created DROOLS-701:
-------------------------------------
Summary: Drools audit log eclipse not opening
Key: DROOLS-701
URL: https://issues.jboss.org/browse/DROOLS-701
Project: Drools
Issue Type: Bug
Affects Versions: 6.2.0.CR3
Environment: Eclipse Audit log view
Reporter: Matteo Mortari
Assignee: Mark Proctor
With reference to drools-setup discussion thread, I'm don't have the same scenario of Gergely which is open as DROOLS-672:
{quote}
First of all: this problem can be reproduced with only a single audit file.
{quote}
but I got a reproducer for the scenario I describe:
{quote}
I'm experiencing similar behavior and stacktrace in the Eclipse log, when I get as a result several Audit logs file ( because of the many insert/fire etc therefore many audit records results in automatic file splits ).
When I have several audit logs, some logs do open in the Audit view correctly; other log files in the sequence do not open and as you describe Audit view is empty and that stacktrace output is produced in the Eclipse log.
Do you have the same experience?
I'm asking as you seem to mention about a single log file but I was wondering if it's actually one in a sequence of audit log.
I'm also wondering if this is due to the log containing some cross-reference to other log records not appearing in this file instance but the previous/next, making the java code which is constructing the items in the Audit log treeview fail with that stacktrace.
{quote}
It could be the solution to this bug/reproducer will solve the same issue as Gergely, but I cannot tell if our cases are really the same hence I prefer to raise this as a new separate JIRA bug record.
h5. Steps to reproduce
With reference to attached reproducer
the first sessionlog.log log file opens correctly.
>From log file sessionlog1.log it will no longer open, Audit view blank, causing the stacktrace error in Eclipse workspace log (ref. below).
The log file sessionlog1.log starts with event:
{code}
<org.drools.core.audit.event.ObjectLogEvent>
<type>3</type
{code}
No other log files in the sequence 1-22 will open.
Until sessionlog23.log, which starts with event:
{code}
<org.drools.core.audit.event.ActivationLogEvent>
<type>4</type>
{code}
The log files in the sequence 23-44 will open again.
Until stop to display again from log file sessionlog45.log, which starts with
{code}
<org.drools.core.audit.event.ActivationLogEvent>
<type>7</type>
{code}
when Audit view blank, in the Eclipse workspace log (under workspace/.metadata) will display this or analogous:
The eclipse workspace log stacktrace when trying to open in Audit view one "out of sequence" log
{code}
!ENTRY org.eclipse.ui 4 0 2015-01-29 15:04:06.339
!MESSAGE Unhandled event loop exception
!STACK 0
java.util.EmptyStackException
at java.util.Stack.peek(Unknown Source)
at java.util.Stack.pop(Unknown Source)
at org.drools.eclipse.debug.AuditView.createPhreakEventList(AuditView.java:238)
at org.drools.eclipse.debug.AuditView.refresh(AuditView.java:150)
at org.drools.eclipse.debug.AuditView.setLogFile(AuditView.java:104)
at org.drools.eclipse.debug.actions.FileAuditDropAdapter.performDrop(FileAuditDropAdapter.java:39)
at org.eclipse.jface.viewers.ViewerDropAdapter.drop(ViewerDropAdapter.java:254)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (JGRP-1907) ENCRYPT: asymmetric encryption fails on merge
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JGRP-1907?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated JGRP-1907:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1187193
> ENCRYPT: asymmetric encryption fails on merge
> ---------------------------------------------
>
> Key: JGRP-1907
> URL: https://issues.jboss.org/browse/JGRP-1907
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.6.2
>
> Attachments: encrypt.xml, EncryptKeyStore.xml
>
>
> {{ENCRYPT}} fails to communicate after a network split and subsequent merge with asymmetric encryption. This works with symmetric encryption.
> To reproduce:
> * Members A and B
> * Add {{<DISCARD use_gui="true"/>}} on top of {{UDP}}
> * Form cluster {{(A,B)}}
> * Create a network split: {{(A)}} and {{(B)}}
> * Remove the network split
> * Observe that with both symmetric and asymmetric encryption, the merge forms cluster {{(A,B)}}
> * However, with asymmetric encryption, {{ENCRYPT}} fails to process any messages and rejects all messages, whereas with symmetric encryption, this works.
> * Symmetric encryption: {{EncryptKeyStore.xml}}
> * Asymmetric encryption: {{encrypt.xml}}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (DROOLS-700) ClassCastException using collect accumulator
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-700?page=com.atlassian.jira.plugin... ]
Mario Fusco resolved DROOLS-700.
--------------------------------
Fix Version/s: 6.2.0.Final
Resolution: Done
Fixed by 815ff8fa32b3f1868ae30ec3117ca2dbdc5f26f4
> ClassCastException using collect accumulator
> --------------------------------------------
>
> Key: DROOLS-700
> URL: https://issues.jboss.org/browse/DROOLS-700
> Project: Drools
> Issue Type: Bug
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 6.2.0.Final
>
>
> When a collect accumulator is in a subnetwork the left tuple is unwrapped twice causing a ClassCastException like the following:
> java.lang.RuntimeException: java.lang.ClassCastException: ExpectedMessage cannot be cast to org.drools.core.reteoo.LeftTuple
> at org.drools.core.rule.SingleAccumulate.accumulate(SingleAccumulate.java:90)
> at org.drools.core.phreak.PhreakAccumulateNode.reaccumulateForLeftTuple(PhreakAccumulateNode.java:833)
> at org.drools.core.phreak.PhreakAccumulateNode.doLeftUpdatesProcessChildren(PhreakAccumulateNode.java:401)
> at org.drools.core.phreak.PhreakAccumulateNode.doLeftUpdates(PhreakAccumulateNode.java:301)
> at org.drools.core.phreak.PhreakAccumulateNode.doNode(PhreakAccumulateNode.java:72)
> at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:562)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:533)
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:334)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalStackEntry(RuleNetworkEvaluator.java:224)
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:166)
> at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:116)
> at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:231)
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:106)
> at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1008)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1294)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1289)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1262)
> at org.drools.core.command.runtime.rule.FireAllRulesCommand.execute(FireAllRulesCommand.java:109)
> at org.drools.core.command.runtime.rule.FireAllRulesCommand.execute(FireAllRulesCommand.java:34)
> at org.drools.core.command.runtime.BatchExecutionCommandImpl.execute(BatchExecutionCommandImpl.java:155)
> at org.drools.core.command.runtime.BatchExecutionCommandImpl.execute(BatchExecutionCommandImpl.java:76)
> at org.drools.core.impl.StatelessKnowledgeSessionImpl.execute(StatelessKnowledgeSessionImpl.java:321)
> Caused by: java.lang.ClassCastException: ExpectedMessage cannot be cast to org.drools.core.reteoo.LeftTuple
> at org.drools.core.base.accumulators.CollectAccumulator.accumulate(CollectAccumulator.java:95)
> at org.drools.core.rule.SingleAccumulate.accumulate(SingleAccumulate.java:82)
> ... 50 more
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months