February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBWEB-258) DigestAuthenticator generates duplicate nonces

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWEB-258?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWEB-258: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1188744|https://bugzilla.redhat.com/show_bug.cgi?id=1188744] from MODIFIED to ON_QA > DigestAuthenticator generates duplicate nonces > ---------------------------------------------- > > Key: JBWEB-258 > URL: https://issues.jboss.org/browse/JBWEB-258 > Project: JBoss Web > Issue Type: Bug > Affects Versions: JBossWeb-2.1.12.GA, JBossWeb-7.0.16.GA, JBossWeb-7.2.0.Alpha3 > Reporter: Aaron Ogburn > Assignee: Remy Maucherat > Attachments: 21x.diff, 70x.diff, 72x.diff > > > DigestAuthenticator currently generates nonces as a hash of the client's remote ip, the current time at generation time, and an internal server key. With high concurrent load in a scenario where many clients show a single ip (such as behind a loadbalancer/proxy), then it is very easy for DigestAuthenticator to give out duplicate nonces when they are generated at the same time. > This then leads to authentication failues as counts for the duplicate nonces get out of whack. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4313) Clean-up tests which use Kerberos in the WildFly testsuite

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4313?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4313: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1189141|https://bugzilla.redhat.com/show_bug.cgi?id=1189141] from MODIFIED to ON_QA > Clean-up tests which use Kerberos in the WildFly testsuite > ---------------------------------------------------------- > > Key: WFLY-4313 > URL: https://issues.jboss.org/browse/WFLY-4313 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > > Clean up Kerberos tests and add an unified logic for skipping Kerberos test configurations which proved to be unstable/buggy. By a configuration here is meant combination of Java vendor, version and IP stack. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4354) EJBs can't inherit a JDK8 default method

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4354?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4354: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1193109|https://bugzilla.redhat.com/show_bug.cgi?id=1193109] from MODIFIED to ON_QA > EJBs can't inherit a JDK8 default method > ---------------------------------------- > > Key: WFLY-4354 > URL: https://issues.jboss.org/browse/WFLY-4354 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Jan Martiska > Assignee: David Lloyd > Attachments: defaultmethodejb.jar > > > If an EJB bean inherits a default method from an interface and doesn't override it, attempt to call this method fails with: > {noformat} > org.jboss.invocation.CannotProceedException: INV000002: Invocation cannot proceed (end of interceptor chain has been hit) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1244) LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1244?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1244: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1181132|https://bugzilla.redhat.com/show_bug.cgi?id=1181132] from MODIFIED to ON_QA > LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification > ---------------------------------------------------------------------------------------------- > > Key: JBJCA-1244 > URL: https://issues.jboss.org/browse/JBJCA-1244 > Project: IronJacamar > Issue Type: Bug > Affects Versions: 1.0.30.Final > Reporter: Tom Jenkinson > Assignee: Jesper Pedersen > Fix For: 1.0.31.Final, 1.2.3.Final > > > The XA specification states the following about the RBROLLBACK error code for xa_commit(): > {quote} > [XA_RB∗] > The resource manager did not commit the work done on behalf of the transaction branch. Upon return, the resource manager has rolled back the branch’s work and has released all held resources. These values may be returned only if TMONEPHASE is set in flags: > [XA_RBROLLBACK] > The resource manager rolled back the transaction branch for an unspecified reason > {quote} > It is clear that the RBROLLBACK code may only be returned if the branch is known to have rolled back (and indeed if the onePhase flag is set to true). > To cater for scenarios where the XAResource is not able to determine the outcome of the resource managers commit. In those scenarios the XA specification is clear that the only legal error code to return is: > {quote} > [XAER_RMFAIL] > An error occurred that makes the resource manager unavailable. > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4272) Data inconsistency for CMR when connection is broken after database resource commits

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4272?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4272: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1181132|https://bugzilla.redhat.com/show_bug.cgi?id=1181132] from MODIFIED to ON_QA > Data inconsistency for CMR when connection is broken after database resource commits > ------------------------------------------------------------------------------------ > > Key: WFLY-4272 > URL: https://issues.jboss.org/browse/WFLY-4272 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Tom Jenkinson > Assignee: Jesper Pedersen > > Cloned from: > https://bugzilla.redhat.com/show_bug.cgi?id=1181132 > Ondrej Chaloupka 2015-01-12 08:21:45 EST wrote: > We've found issue for CMR where data inconsistency occurs. This happens when CMR db resource successfully commits but the connection is broken before TM receives confirmation about such state. As connection got broken XAException.XA_RBROLLBACK is thrown and TM decides to rollback whole XA transaction. > That ends in situation where db resource was committed and other XA participants are rollbacked. > This is test flow: > - prepare DB xa resource > - prepare test xa resource > - commit DB xa resource > - DB commits > - before confirmation is received by TM the connection crashes > - jdbc driver returns XAException.XA_RBROLLBACK as connection is down > - doAbort is called for the transaction > - test xa resource is rollbacked > - doForget is called and no information about the inconsistent transaction remains in object store > - recovery manager does nothing -- This message was sent by Atlassian JIRA (v6.3.11#6341)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1245) Custom URL selector doesn't take effect

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1245?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1245: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1182879|https://bugzilla.redhat.com/show_bug.cgi?id=1182879] from MODIFIED to ON_QA > Custom URL selector doesn't take effect > --------------------------------------- > > Key: JBJCA-1245 > URL: https://issues.jboss.org/browse/JBJCA-1245 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.30.Final, 1.1.9.Final, 1.2.2.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.31.Final, 1.1.10.Final, 1.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4324) While starting Jboss AS getting IllegalStateException.

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-4324?page=com.atlassian.jira.plugin.... ] Stuart Douglas closed WFLY-4324. -------------------------------- Resolution: Out of Date This was fixed a while back. You need to either move to Wildfly, or update the version of Jandex that AS7 is using to something more recent. > While starting Jboss AS getting IllegalStateException. > ------------------------------------------------------ > > Key: WFLY-4324 > URL: https://issues.jboss.org/browse/WFLY-4324 > Project: WildFly > Issue Type: Bug > Environment: Java with 1.8 v and JBOS 7 > Reporter: ANKUSH NIKHAR > > Hi, > I am facing issue when I am trying to deploy web service on Jboss 7 and using jdk 1.8 version. Below are the sample log : > This issue does not impact the processing of my code execution. Is this just warning or will it harm in future. > I am migrating my project from jdk1.7 to 1.8. > When I try to deploy WS with jdk1.7, I didn't get such error. > 18:56:01,032 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015852: Could not index class sun/applet/AppletPanel.class at /D:/Test Eclipse/Migration Eclipse/Mig Workspace/CDLibrary/CDLibrary-test/content/InMemory.war/WEB-INF/lib/tools.jar: java.lang.IllegalStateException: Unknown tag! pos=1006 poolCount = 1018 > at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:606) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2] > at org.jboss.jandex.Indexer.index(Indexer.java:640) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2] > at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:100) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] > at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_31] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_31] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1915) JDBC_PING discovery fails when stale entries are found in the database

by Patrick Haas (JIRA)

[ https://issues.jboss.org/browse/JGRP-1915?page=com.atlassian.jira.plugin.... ] Patrick Haas commented on JGRP-1915: ------------------------------------ This issue can prevent cluster startup solely due to the value of the address GUID that's generated. If the 'stuck' database row has a sufficiently high GUID, no node will be able to start up. > JDBC_PING discovery fails when stale entries are found in the database > ---------------------------------------------------------------------- > > Key: JGRP-1915 > URL: https://issues.jboss.org/browse/JGRP-1915 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.1 > Reporter: Patrick Haas > Assignee: Bela Ban > > Node: "CHQ-PATRICKH-55008" > Database contains two rows.. other node is dead but was unable to remove the JDBC entry. > 1) JChannel.connect(...) > 2) JChannel.down(Event[CONNECT_WITH_STATE_TRANSFER_USE_FLUSH]) > 3) STATE_TRANSFER -> FRAG2 -> MFC -> UFC -> GMS > 4) GMS.down(...) calls out to joinWithStateTransfer -> joinInternal(...) > JDBC pulls the node list from the database table. > Ping Data: > - CHQ-PATRICKH-3895, name=CHQ-PATRICKH-3895, addr=10.1.130.228:55503, server > - CHQ-PATRICKH-55008, name=CHQ-PATRICKH-55008, addr=10.1.130.228:57489 > joinInternal is a never-terminating while loop: > - down: Event.FIND_INITIAL_MBRS_EVT > - inspect responses -- no valid join responses > - responses are NOT empty -> does not become singletonMember > - gets all coordinators (none) > - Sorts all nodes by GUID in a TreeSet > - Is first of all joiners? > - No, another joiner is listed first > ... repeat forever > When the process is restarted and a node ID < than the existing db entry is generated, it successfully takes over as owner. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1915) JDBC_PING discovery fails when stale entries are found in the database

by Patrick Haas (JIRA)

Patrick Haas created JGRP-1915: ---------------------------------- Summary: JDBC_PING discovery fails when stale entries are found in the database Key: JGRP-1915 URL: https://issues.jboss.org/browse/JGRP-1915 Project: JGroups Issue Type: Bug Affects Versions: 3.6.1 Reporter: Patrick Haas Assignee: Bela Ban Node: "CHQ-PATRICKH-55008" Database contains two rows.. other node is dead but was unable to remove the JDBC entry. 1) JChannel.connect(...) 2) JChannel.down(Event[CONNECT_WITH_STATE_TRANSFER_USE_FLUSH]) 3) STATE_TRANSFER -> FRAG2 -> MFC -> UFC -> GMS 4) GMS.down(...) calls out to joinWithStateTransfer -> joinInternal(...) JDBC pulls the node list from the database table. Ping Data: - CHQ-PATRICKH-3895, name=CHQ-PATRICKH-3895, addr=10.1.130.228:55503, server - CHQ-PATRICKH-55008, name=CHQ-PATRICKH-55008, addr=10.1.130.228:57489 joinInternal is a never-terminating while loop: - down: Event.FIND_INITIAL_MBRS_EVT - inspect responses -- no valid join responses - responses are NOT empty -> does not become singletonMember - gets all coordinators (none) - Sorts all nodes by GUID in a TreeSet - Is first of all joiners? - No, another joiner is listed first ... repeat forever When the process is restarted and a node ID < than the existing db entry is generated, it successfully takes over as owner. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-707) NullPointer when changing order of the rules

by Francesco Peloi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-707?page=com.atlassian.jira.plugin... ] Francesco Peloi edited comment on DROOLS-707 at 2/24/15 12:57 PM: ------------------------------------------------------------------ Hi [~mfusco], I found other 2 cases where I get not consistent behavior with variables and order of the rule lines. I created a pull request with a few cases in the 6.1.x branch, they weren't working on master where I was getting another weird exception (The import org.kie.api.definition.rule.Propagation cannot be resolved - maybe something has changed). If I remember correctly, the line that throws a NPE is exactly the same as the problem you fixed already in this ticket. was (Author: eweriuer): Hi [~mfusco], I found other 2 cases where I get strange behavior with variables and order of the rule lines. I created a pull request with a few cases in the 6.1.x branch, they weren't working on master where I was getting another weird exception (The import org.kie.api.definition.rule.Propagation cannot be resolved - maybe something has changed). If I remember correctly, the line that throws a NPE is exactly the same as the problem you fixed already in this ticket. > NullPointer when changing order of the rules > -------------------------------------------- > > Key: DROOLS-707 > URL: https://issues.jboss.org/browse/DROOLS-707 > Project: Drools > Issue Type: Bug > Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.0.Final, 6.0.1.Final, 6.1.0.Final, 6.2.0.CR4 > Reporter: Francesco Peloi > Assignee: Mario Fusco > Fix For: 6.2.0.Final > > > Hi there, > we are having some serious issues with some rules, they are throwing a NullPointerException and we don't understand why. I have tried to narrow down the problem to the smallest rule possible, now this rule doesn't really make much sense put like this but the real rule is more complex with more constraints. At the end the result is the same: a NPE. > I have tried it with many Drools versions from 5.x to latest 6.3.0-SNAPSHOT. > I tested this in isolation with the minimum amount of code possible, and attached it as well if someone wants to try it quickly. > Note that if line 2 of the when: > $a : Integer() > is moved as first line, the rule runs ok. > Please find the reproducer here: https://groups.google.com/forum/#!topic/drools-usage/-oNqu3l4cqE -- This message was sent by Atlassian JIRA (v6.3.11#6341)

8 years, 7 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2015