I think what is happening is two security domains are being started at the same time, which results in two concurrent put() calls. 

Sometimes this will result in both items being put into the same place in the table, and one put() will essentially be lost. 

Using a sync map makes this problem go away. 

Stuart


On Sun, Dec 29, 2013 at 11:53 AM, Ales Justin <ales.justin@gmail.com> wrote:
How would proper map sync help here then?

Are you saying there is a put and get going on at the same time?
Imo, this then means WF' dependencies are not done right.

btw: when do you "corrupt" a HashMap? (wrt my diff manifestation)
With multiple concurrent puts/removes, or can it be mixture of puts/gets/removes?

On Dec 29, 2013, at 2:56, Jason Greene <jgreene@redhat.com> wrote:

It looks exactly how it would manifest. Something isn't in the map that should be, so an error is thrown.

On Dec 27, 2013, at 1:26 PM, Ales Justin <ales.justin@gmail.com> wrote:

That's one thing -- dunno how that did pop-up before. ;-)

But I doubt that just non-synchronised collections/maps cause this -- it would manifest differently.
Imo, it must also be a race-condition in WF.

On 27 Dec 2013, at 17:50, Anil Saldhana <Anil.Saldhana@redhat.com> wrote:

Stefan merged the fixes recently. I guess we need a PicketBox upgrade in WF.

On 12/27/2013 06:54 AM, Ales Justin wrote:
I often get this error: 


Do we have a JIRA for WF as well?

-Ales

 
_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev

_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev

_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev