1:54 p.m.
I often get this error:
* https://gist.github.com/alesj/8146623
I guess it's related to https://issues.jboss.org/browse/SECURITY-777 ?
Do we have a JIRA for WF as well?
-Ales
5:50 p.m.
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:
* https://gist.github.com/alesj/8146623
I guess it's related to https://issues.jboss.org/browse/SECURITY-777 ?
Do we have a JIRA for WF as well?
-Ales
8:26 p.m.
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(a)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:
> * https://gist.github.com/alesj/8146623
>
> I guess it's related to https://issues.jboss.org/browse/SECURITY-777 ?
>
> Do we have a JIRA for WF as well?
>
> -Ales
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
2:56 a.m.
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(a)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(a)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:
>> * https://gist.github.com/alesj/8146623
>>
>> I guess it's related to https://issues.jboss.org/browse/SECURITY-777 ?
>>
>> Do we have a JIRA for WF as well?
>>
>> -Ales
>>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
11:53 a.m.
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(a)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(a)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(a)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:
>>> * https://gist.github.com/alesj/8146623
>>>
>>> I guess it's related to https://issues.jboss.org/browse/SECURITY-777 ?
>>>
>>> Do we have a JIRA for WF as well?
>>>
>>> -Ales
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
2:12 a.m.
Memory visibility would be guaranteed. If there is no happens-before ordering then one
thread's put is not always visible to another thread's get even if they happen in
the proper order. Also corruption of the table could result in a dead table.
E.g.
1. Thread A -> put Kz
2. Other stuff
3. Thread B -> get Kz
(Returns cached stale value, null)
Granted there could still be some ordering problem. Like we are allowing requests to get
handled before the server is started.
Sent from my iPhone
On Dec 29, 2013, at 4:54 AM, Ales Justin
<ales.justin(a)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(a)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(a)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(a)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:
>>>> * https://gist.github.com/alesj/8146623
>>>>
>>>> I guess it's related to https://issues.jboss.org/browse/SECURITY-777
?
>>>>
>>>> Do we have a JIRA for WF as well?
>>>>
>>>> -Ales
>>>
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
12:13 p.m.
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(a)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(a)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(a)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(a)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:
* https://gist.github.com/alesj/8146623
I guess it's related to https://issues.jboss.org/browse/SECURITY-777 ?
Do we have a JIRA for WF as well?
-Ales
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
3769
days inactive
3773
days old
6 comments
4 participants
participants (4)
-
Ales Justin -
Anil Saldhana -
Jason Greene -
Stuart Douglas