January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5909) Upgrade Narayana to 5.2.11.Final

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5909?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-5909: -------------------------------- Comment: was deleted (was: WIP: https://github.com/wildfly/wildfly/compare/master...jbosstm:WFLY-5909?exp...) > Upgrade Narayana to 5.2.11.Final > -------------------------------- > > Key: WFLY-5909 > URL: https://issues.jboss.org/browse/WFLY-5909 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 10.0.0.Final > > > Release notes: (for .10 due to script failure) > https://issues.jboss.org/browse/JBTM/fixforversion/12329061/?selectedTab=... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5933) Upgrade Narayana to 5.2.11.Final

by Tom Jenkinson (JIRA)

Tom Jenkinson created WFLY-5933: ----------------------------------- Summary: Upgrade Narayana to 5.2.11.Final Key: WFLY-5933 URL: https://issues.jboss.org/browse/WFLY-5933 Project: WildFly Issue Type: Component Upgrade Components: Transactions Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 10.0.0.Final Release notes: (for .10 due to script failure) https://issues.jboss.org/browse/JBTM/fixforversion/12329061/?selectedTab=... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-400) Add support for realm mapping and identity lookup based on name, principal, and/or evidence

by David Lloyd (JIRA)

David Lloyd created ELY-400: ------------------------------- Summary: Add support for realm mapping and identity lookup based on name, principal, and/or evidence Key: ELY-400 URL: https://issues.jboss.org/browse/ELY-400 Project: WildFly Elytron Issue Type: Enhancement Components: API / SPI, Realms Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.1.0.Beta4 To support SSO and other use cases, we have to be able to look up identities based on any combination of: * User name (possibly derived from authentication principal) * Authentication principal (possibly derived from evidence) * Evidence Realms are not required to support more than just user name-based lookup, however for SSO support a realm will have to be able to look up and verify token Evidence in one step. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1018) bigdecimal field compare

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1018?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1018: ------------------------------------- Can you please clarify why did you open and then close this ticket? Was it a mistake on your side? > bigdecimal field compare > ------------------------ > > Key: DROOLS-1018 > URL: https://issues.jboss.org/browse/DROOLS-1018 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Final > Environment: windows 8, java 1.6 > Reporter: Sante Stanisci > Assignee: Mario Fusco > Labels: bigdecimal, compare, field > Attachments: check_cond.drl, CtbTitoli.java > > > Comparing two field of bigdecimal, rule not file -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1018) bigdecimal field compare

by Sante Stanisci (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1018?page=com.atlassian.jira.plugi... ] Sante Stanisci closed DROOLS-1018. ---------------------------------- Resolution: Done > bigdecimal field compare > ------------------------ > > Key: DROOLS-1018 > URL: https://issues.jboss.org/browse/DROOLS-1018 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Final > Environment: windows 8, java 1.6 > Reporter: Sante Stanisci > Assignee: Mario Fusco > Labels: bigdecimal, compare, field > Attachments: check_cond.drl, CtbTitoli.java > > > Comparing two field of bigdecimal, rule not file -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1018) bigdecimal field compare

by Sante Stanisci (JIRA)

Sante Stanisci created DROOLS-1018: -------------------------------------- Summary: bigdecimal field compare Key: DROOLS-1018 URL: https://issues.jboss.org/browse/DROOLS-1018 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.3.0.Final Environment: windows 8, java 1.6 Reporter: Sante Stanisci Assignee: Mario Fusco Attachments: check_cond.drl, CtbTitoli.java Comparing two field of bigdecimal, rule not file -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1017) NPE deleting an expired event in equality mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1017?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1017: ------------------------------------------------- Alessandro Lazarotti <alazarot(a)redhat.com> changed the Status of [bug 1295786|https://bugzilla.redhat.com/show_bug.cgi?id=1295786] from NEW to ASSIGNED > NPE deleting an expired event in equality mode > ---------------------------------------------- > > Key: DROOLS-1017 > URL: https://issues.jboss.org/browse/DROOLS-1017 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.4.x > > > Trying to delete an already expired event in equality mode causes the following NPE in the TMS: > {code} > java.lang.NullPointerException > at org.drools.core.common.NamedEntryPoint.delete(NamedEntryPoint.java:506) > at org.drools.core.common.NamedEntryPoint.delete(NamedEntryPoint.java:442) > at org.drools.core.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1120) > at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:121) > at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74) > at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1003) > at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1346) > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1284) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1303) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1293) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1274) > at org.drools.compiler.integrationtests.CepEspTest.testDeleteExpiredEventWithTimestampAndEqualityKey(CepEspTest.java:5682) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4790) Getting DirectBuffer OOM when sending fragmented binary message to websocket endpoint

by Junshik Jeon (JIRA)

[ https://issues.jboss.org/browse/WFLY-4790?page=com.atlassian.jira.plugin.... ] Junshik Jeon commented on WFLY-4790: ------------------------------------ [~swd847] I'm back porting this commit to 1.2.22.Final tag with fixed MAX_QUEUED_READ_BUFFERS size. I will report test results. Thanks ! > Getting DirectBuffer OOM when sending fragmented binary message to websocket endpoint > ------------------------------------------------------------------------------------- > > Key: WFLY-4790 > URL: https://issues.jboss.org/browse/WFLY-4790 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Alpha3 > Reporter: Radim Hatlapatka > Assignee: Stuart Douglas > Priority: Critical > Fix For: 10.0.0.Alpha6 > > > When sending fragmented binary message (message with message payload of length 4 * 2**20 (4M). Sent out in fragments of 64). The server throws {{java.lang.OutOfMemoryError: Direct buffer memory}} [1] > The memory for direct buffer by default depends on the size set by -Xmx, which is in EAP 7.0.0.DR4 by default set to -Xmx512m. Increasing it just increases the time before the limit is hit (it is enough to send those messages multiple times to hit the limit again). > I believe the issue is similar to the one for EAP 6.4: [https://bugzilla.redhat.com/show_bug.cgi?id=1223708] > [1] > {noformat} > 15:10:55,463 ERROR [org.xnio.listener] (default I/O-1) XNIO001007: A channel event listener threw an exception: java.lang.OutOfMemoryError: Direct buffer memory > at java.nio.Bits.reserveMemory(Bits.java:658) > at java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:123) > at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311) > at org.xnio.BufferAllocator$2.allocate(BufferAllocator.java:57) > at org.xnio.BufferAllocator$2.allocate(BufferAllocator.java:55) > at org.xnio.ByteBufferSlicePool.allocate(ByteBufferSlicePool.java:143) > at io.undertow.websockets.core.BufferedBinaryMessage$1.handleEvent(BufferedBinaryMessage.java:106) > at io.undertow.websockets.core.BufferedBinaryMessage$1.handleEvent(BufferedBinaryMessage.java:97) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at io.undertow.server.protocol.framed.AbstractFramedStreamSourceChannel$1.run(AbstractFramedStreamSourceChannel.java:264) > at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:560) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:462) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5484) Calling HttpServletRequest.logout() with single sign-on enabled only works every second time

by Richard Janík (JIRA)

[ https://issues.jboss.org/browse/WFLY-5484?page=com.atlassian.jira.plugin.... ] Richard Janík reopened WFLY-5484: --------------------------------- Logout still doesn't work for the first time with 10.0.0.CR5. I'm attaching a reproducer. Unzip the reproducer in a clean EAP/Wildfly installation and run the reproducer.sh script inside. > Calling HttpServletRequest.logout() with single sign-on enabled only works every second time > -------------------------------------------------------------------------------------------- > > Key: WFLY-5484 > URL: https://issues.jboss.org/browse/WFLY-5484 > Project: WildFly > Issue Type: Bug > Components: Clustering, Web (Undertow) > Reporter: Richard Janík > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 10.0.0.CR5 > > Attachments: reproducer-jbeap-1282.zip > > > See "Steps to Reproduce". Logging out from an application only works every second time, e.g. HttpRequestServlet.logout() has to be called twice in order to have any effect > This doesn't occur without <single-sign-on/> enabled - logout() has the expected effect. The issue is security related, thus I'm adding our security team members as watchers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5484) Calling HttpServletRequest.logout() with single sign-on enabled only works every second time

by Richard Janík (JIRA)

[ https://issues.jboss.org/browse/WFLY-5484?page=com.atlassian.jira.plugin.... ] Richard Janík updated WFLY-5484: -------------------------------- Attachment: reproducer-jbeap-1282.zip > Calling HttpServletRequest.logout() with single sign-on enabled only works every second time > -------------------------------------------------------------------------------------------- > > Key: WFLY-5484 > URL: https://issues.jboss.org/browse/WFLY-5484 > Project: WildFly > Issue Type: Bug > Components: Clustering, Web (Undertow) > Reporter: Richard Janík > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 10.0.0.CR5 > > Attachments: reproducer-jbeap-1282.zip > > > See "Steps to Reproduce". Logging out from an application only works every second time, e.g. HttpRequestServlet.logout() has to be called twice in order to have any effect > This doesn't occur without <single-sign-on/> enabled - logout() has the expected effect. The issue is security related, thus I'm adding our security team members as watchers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2016