April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3791) Create an API to scroll events received on the topics

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3791?page=com.atlassian.jira.plugi... ] Massimiliano Dessi resolved DROOLS-3791. ---------------------------------------- Resolution: Done https://github.com/desmax74/openshift-hacep/commit/d57a8ca52b2aa6d266e484... > Create an API to scroll events received on the topics > ----------------------------------------------------- > > Key: DROOLS-3791 > URL: https://issues.jboss.org/browse/DROOLS-3791 > Project: Drools > Issue Type: Sub-task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3810) Enable a fast forward system to skip already processed events

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-3810: ------------------------------------------ Summary: Enable a fast forward system to skip already processed events Key: DROOLS-3810 URL: https://issues.jboss.org/browse/DROOLS-3810 Project: Drools Issue Type: Sub-task Environment: Using the identifier data of the last processed event on the Control topic , we need to skip the event on the topic from the head without procesing and start the work on the events only when the last rpocessed event is found on the events topic Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9477) Cannot create two hosts with unspecified default web module in Undertow

by Michal Petrov (Jira)

[ https://issues.jboss.org/browse/WFLY-9477?page=com.atlassian.jira.plugin.... ] Michal Petrov reassigned WFLY-9477: ----------------------------------- Assignee: Michal Petrov > Cannot create two hosts with unspecified default web module in Undertow > ----------------------------------------------------------------------- > > Key: WFLY-9477 > URL: https://issues.jboss.org/browse/WFLY-9477 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 11.0.0.Final > Reporter: Tomaž Cerar > Assignee: Michal Petrov > Priority: Minor > > As a user, I cannot create two hosts with unspecified default web module. Currently the default-web-module is checked only for uniqueness and by default there is defined ROOT.war, which by default doesn't exist. Current behavior is that in case of non existing module defined by default-web-module, when accessing the root context ('/'), the content defined as part of welcome-file handler is provided. > As a user I should not be forced to put random values to avoid duplicity check, when I don't want to have set default-web-module. As such the default-web-module should have undefined default which could be checked and avoided failures due duplicates as there are in reality none. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11343) Lock is not released when JTS is enabled and a timer is cancelled inside a transaction

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFLY-11343?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFLY-11343: ------------------------------------------------ Tomas Hofman <thofman(a)redhat.com> changed the Status of [bug 1648762|https://bugzilla.redhat.com/show_bug.cgi?id=1648762] from POST to MODIFIED > Lock is not released when JTS is enabled and a timer is cancelled inside a transaction > -------------------------------------------------------------------------------------- > > Key: WFLY-11343 > URL: https://issues.jboss.org/browse/WFLY-11343 > Project: WildFly > Issue Type: Bug > Components: EJB > Environment: EAP 6.4.18 > Reporter: Shaun Appleton > Assignee: Thomas Jenkinson > Priority: Major > Fix For: 15.0.0.Final > > > Description of problem: > Lock is held by EJB timer (TimerServiceImpl) and in case JTS transaction is cancelled the lock won't be released correctly . This code is the problem: > https://github.com/wildfly/wildfly/blob/78dee79dd0f49c6cbd2b8db5d8640980f... > Basically it holds the timer lock until the transaction completes, and then attempts to release it in afterCompletion. The problem is that when JTS is enabled afterCompletion will be called by a seperate thread, which can't call unlock as it is not the owner. > A simple fix could be to just change the lock to a semaphore, so that the other thread can release it. > Version-Release number of selected component (if applicable): > How reproducible: > Always > Steps to Reproduce: > 1. Start a JTA/JTS tx and call an EJB timer inside it > 2. Make the transaction timeout > 3. Capture a thread dump and see a thread like below (0a0818b80 is locked object) > --------------------------------------------------------------------------------------------------------- > "Incoming-2,RouterPoliciesClusterGroup,svc-3-comecimpolicy-59228 (, payload=52 bytes)" #661 prio=5 os_prio=0 tid=0x00007f5214c2d000 nid=0x1e67 waiting on condition [0x00007f520ac97000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00000000a0818b80> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Locked ownable synchronizers: > - <0x00000000ea1f4c48> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) > --------------------------------------------------------------------------------------------------------- > Actual results: > Lock being held forever > Expected results: > Lock getting released -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4239) WARN if system-property is already set and is being overridden

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFCORE-4239?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-4239: ------------------------------------------------- Tomas Hofman <thofman(a)redhat.com> changed the Status of [bug 1654454|https://bugzilla.redhat.com/show_bug.cgi?id=1654454] from POST to MODIFIED > WARN if system-property is already set and is being overridden > -------------------------------------------------------------- > > Key: WFCORE-4239 > URL: https://issues.jboss.org/browse/WFCORE-4239 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Reporter: Brad Maxwell > Assignee: Chao Wang > Priority: Major > Fix For: 8.0.0.Beta2, 8.0.0.Final > > > WARN if system-property is already set and is being overridden > If user sets a system property using the java opts or on the command line and the same system property is defined in the standalone.xml, then the standalone.xml value overrides that passed on the commandline/JAVA_OPTS, a warning would be useful as looking at the logs (and ps), it shows value1 passed on the command line and nothing indicating that the value was changed later. > JAVA_OPTS="$JAVA_OPTS -Dmy.system.property=value1" > {code} > <system-properties> > <property name="my.system.property" value="value2"/> > </system-properties> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-685) UI Automation - ServiceRole/Binding

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-685?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-685: --------------------------------- Sprint: Kiali Sprint #20 > UI Automation - ServiceRole/Binding > ----------------------------------- > > Key: SWSQE-685 > URL: https://issues.jboss.org/browse/SWSQE-685 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: automation > > Automate the validations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-685) UI Automation - ServiceRole/Binding

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-685?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan reassigned SWSQE-685: ------------------------------------ Assignee: Hayk Hovsepyan > UI Automation - ServiceRole/Binding > ----------------------------------- > > Key: SWSQE-685 > URL: https://issues.jboss.org/browse/SWSQE-685 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Automate the validations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-559) Added namespace filters in assert_all_items tests.

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-559?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-559: --------------------------------- Priority: Minor (was: Major) > Added namespace filters in assert_all_items tests. > -------------------------------------------------- > > Key: SWSQE-559 > URL: https://issues.jboss.org/browse/SWSQE-559 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Priority: Minor > Labels: automation > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-232) Deployment fails when Dependencies is empty in a jars manifest

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFLY-232?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-232: ---------------------------------------------- Tomas Hofman <thofman(a)redhat.com> changed the Status of [bug 1539985|https://bugzilla.redhat.com/show_bug.cgi?id=1539985] from POST to MODIFIED > Deployment fails when Dependencies is empty in a jars manifest > -------------------------------------------------------------- > > Key: WFLY-232 > URL: https://issues.jboss.org/browse/WFLY-232 > Project: WildFly > Issue Type: Enhancement > Reporter: Gábor Farkas > Assignee: Stuart Douglas > Priority: Major > Fix For: 8.0.0.Alpha1 > > Attachments: empty-manifest.ear > > > I have a WAR, which produces the following error on deployment: > Caused by: java.lang.IllegalArgumentException: Empty module specification > at org.jboss.modules.ModuleIdentifier.fromString(ModuleIdentifier.java:169) [jboss-modules.jar:1.1.1.GA] > at org.jboss.as.server.deployment.module.ManifestDependencyProcessor.deploy(ManifestDependencyProcessor.java:83) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > ... 5 more > I found that my WAR contains a jar in WEB-INF/lib that has empty dependencies defined in its manifest. More exactly it's "Dependencies: ", so the colon is followed by a space character before the new line characters. The ManifestDependencyProcessor parses this as one dependency, the name of which is the empty string. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2562) NullPointerException when removing configuration history

by RH Bugzilla Integration (Jira)

[ https://issues.jboss.org/browse/WFCORE-2562?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-2562: ------------------------------------------------- Tomas Hofman <thofman(a)redhat.com> changed the Status of [bug 1434141|https://bugzilla.redhat.com/show_bug.cgi?id=1434141] from POST to MODIFIED > NullPointerException when removing configuration history > -------------------------------------------------------- > > Key: WFCORE-2562 > URL: https://issues.jboss.org/browse/WFCORE-2562 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 2.1.0.Final > Reporter: Dennis Reed > Assignee: Ken Wills > Priority: Major > Fix For: 3.0.0.Beta12 > > > org.jboss.as.controller.persistence.ConfigurationFile#deleteRecursively is missing error checking. > If an I/O error occurs while listing the directory contents (file permission error/etc) it still tries to use the listing and gets a NullPointerException. > This method is used while removing old configuration history directories during boot, and the NullPointerException causes the EAP boot to abort. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2019