June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2410) Wrong resource and operation descriptions for Elytron filesystem-realm in management model and XSD

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2410?page=com.atlassian.jira.plugi... ] Chao Wang reassigned WFCORE-2410: --------------------------------- Assignee: Chao Wang (was: Darran Lofthouse) > Wrong resource and operation descriptions for Elytron filesystem-realm in management model and XSD > -------------------------------------------------------------------------------------------------- > > Key: WFCORE-2410 > URL: https://issues.jboss.org/browse/WFCORE-2410 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta7 > Reporter: Ondrej Lukas > Assignee: Chao Wang > Labels: user_experience > > There are some wrong or insufficient resource and operation description for Elytron filesystem-realm in CLI: > * attribute {{levels}} for filesystem-realm - description says "The number of levels of directory hashing to apply.", but created directory structure does not use any hashing. Example how it works: when levels is set to 3 then for user admin following directory structure and file a/d/m/admin.xml is used. Description of levels should be fixed. This should be also fixed in XSD. > * description of {{digest}} password encryption/hash mechanisms in {{set-password}} operation for identity of filesystem-realm says "A password using a salted digest." which is wrong. It seems it is copy-pasted from {{salted-simple-digest}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8932) Misleading error message when datasource is disabled

by Martin Stefanko (JIRA)

Martin Stefanko created WFLY-8932: ------------------------------------- Summary: Misleading error message when datasource is disabled Key: WFLY-8932 URL: https://issues.jboss.org/browse/WFLY-8932 Project: WildFly Issue Type: Bug Affects Versions: 11.0.0.Alpha1 Reporter: Martin Stefanko Assignee: Martin Stefanko Priority: Minor test-connection-in-pool fails on a disabled datasource with: {code:java} JBAS010442: failed to match pool. Check JndiName: java:jboss/datasources/MyExampleDS" {code} {code:java} [standalone@localhost:9999 /] /subsystem=datasources/data-source=MyExampleDS:add(jndi-name=java:jboss/datasources/MyExampleDS, connection-url=\"jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE\", driver-name=h2, user-name=sa, password=sa, max-pool-size=10) {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=datasources/data-source=MyExampleDS:test-connection-in-pool() { "outcome" => "failed", "failure-description" => "JBAS010440: failed to invoke operation: JBAS010442: failed to match pool. Check JndiName: java:jboss/datasources/MyExampleDS", "rolled-back" => true } {code} The error message should rather convey that an operation was attempted on a disabled datasource. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2955) Hang in ExpressionSupportSmokeTestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2955?page=com.atlassian.jira.plugi... ] Brian Stansberry closed WFCORE-2955. ------------------------------------ Resolution: Rejected I misread the test log. This didn't hang; the test job just timed out. The thread dump is just the snapshot of where the test was when the test job aborted. > Hang in ExpressionSupportSmokeTestCase > -------------------------------------- > > Key: WFCORE-2955 > URL: https://issues.jboss.org/browse/WFCORE-2955 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Attachments: WFCORE-2955-threaddump.txt > > > Hang: > https://github.com/wildfly/wildfly-core/pull/2494 > https://ci.wildfly.org/viewLog.html?buildId=63669&buildTypeId=WildFlyCore... > I'll attach the thread dump. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2955) Hang in ExpressionSupportSmokeTestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2955?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2955: ------------------------------------------ Here's the DC code that's waiting for the latch: {code} final CountDownLatch latch = new CountDownLatch(1); final IOExceptionHolder exceptionHolder = new IOExceptionHolder(); boolean accepted = responseContext.executeAsync(new ManagementRequestContext.AsyncTask<Void>() { @Override public void execute(final ManagementRequestContext<Void> context) throws Exception { FlushableDataOutput output = null; try { MGMT_OP_LOGGER.tracef("Transmitting response for %d", context.getOperationId()); output = responseContext.writeMessage(response); output.write(ModelControllerProtocol.PARAM_RESPONSE); result.writeExternal(output); output.writeByte(ManagementProtocol.RESPONSE_END); output.close(); } catch (IOException e) { exceptionHolder.exception = e; } finally { StreamUtils.safeClose(output); latch.countDown(); } } }, false); {code} But the thread dump doesn't show any DC thread executing that AsyncTask. > Hang in ExpressionSupportSmokeTestCase > -------------------------------------- > > Key: WFCORE-2955 > URL: https://issues.jboss.org/browse/WFCORE-2955 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Attachments: WFCORE-2955-threaddump.txt > > > Hang: > https://github.com/wildfly/wildfly-core/pull/2494 > https://ci.wildfly.org/viewLog.html?buildId=63669&buildTypeId=WildFlyCore... > I'll attach the thread dump. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2955) Hang in ExpressionSupportSmokeTestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2955?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2955: ------------------------------------------ Test driver client is executing a read-resource, so that's pretty basic: {code} at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:57) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75) at org.jboss.as.controller.client.helpers.domain.impl.DomainClientImpl.execute(DomainClientImpl.java:82) at org.jboss.as.test.integration.domain.management.util.DomainTestUtils.executeForResult(DomainTestUtils.java:152) at org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.readResource(ExpressionSupportSmokeTestCase.java:634) {code} DC is trying to respond: {code} "management-handler-thread - 1" #111 prio=5 os_prio=0 tid=0xbdd86800 nid=0x3267 runnable [0xbf4fe000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0xe5d24950> (a java.util.concurrent.CountDownLatch$Sync) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304) at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$CompletedCallback.sendResponse(ModelControllerClientOperationHandler.java:320) - locked <0xe5ce2df8> (a org.jboss.as.controller.remote.ModelControllerClientOperationHandler$CompletedCallback) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:233) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:137) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:161) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) {code} > Hang in ExpressionSupportSmokeTestCase > -------------------------------------- > > Key: WFCORE-2955 > URL: https://issues.jboss.org/browse/WFCORE-2955 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Attachments: WFCORE-2955-threaddump.txt > > > Hang: > https://github.com/wildfly/wildfly-core/pull/2494 > https://ci.wildfly.org/viewLog.html?buildId=63669&buildTypeId=WildFlyCore... > I'll attach the thread dump. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2955) Hang in ExpressionSupportSmokeTestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2955?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2955: ------------------------------------- Attachment: WFCORE-2955-threaddump.txt > Hang in ExpressionSupportSmokeTestCase > -------------------------------------- > > Key: WFCORE-2955 > URL: https://issues.jboss.org/browse/WFCORE-2955 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Attachments: WFCORE-2955-threaddump.txt > > > Hang: > https://github.com/wildfly/wildfly-core/pull/2494 > https://ci.wildfly.org/viewLog.html?buildId=63669&buildTypeId=WildFlyCore... > I'll attach the thread dump. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2955) Hang in ExpressionSupportSmokeTestCase

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-2955: ---------------------------------------- Summary: Hang in ExpressionSupportSmokeTestCase Key: WFCORE-2955 URL: https://issues.jboss.org/browse/WFCORE-2955 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Hang: https://github.com/wildfly/wildfly-core/pull/2494 https://ci.wildfly.org/viewLog.html?buildId=63669&buildTypeId=WildFlyCore... I'll attach the thread dump. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2160) Incorrect JBOSS_HOME warning in vault.sh

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2160?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-2160: ------------------------------------------------- Radovan STANCEL <rstancel(a)redhat.com> changed the Status of [bug 1410924|https://bugzilla.redhat.com/show_bug.cgi?id=1410924] from ASSIGNED to NEW > Incorrect JBOSS_HOME warning in vault.sh > ---------------------------------------- > > Key: WFCORE-2160 > URL: https://issues.jboss.org/browse/WFCORE-2160 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 3.0.0.Alpha16 > Reporter: Dennis Reed > Assignee: Romain Pelisse > Priority: Minor > Fix For: 3.0.0.Alpha23 > > > vault.sh has an incorrect check to make sure JBOSS_HOME is set correctly. > SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd` > if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then > The check will always fail because of the incorrect "/..", which should be removed. > The incorrect value is only used for printing the "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur." log, and appears to have been around since at least EAP 6.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8929) Race condition if timers overlap due to long running execution and short schedules if database persistence is used

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8929?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-8929: -------------------------------------- Looking at server1.log this is what is happening (starting at around 2017-06-13 20:01:42,000, the relevant threads are 4 and 5, 4 is about to finish running a task, 5 is about to attempt to run the new one): [5] calls Timer.setState(ACTIVE) - internal timer state is active, DB state is still IN_TIMEOUT as the timer has not been persisted yet [4] attempts to run the timer, sees that the state is ACTIVE so calls shouldRun(). ShouldRun fails as the DB state is still IN_TIMEOUT [4] calculates a new timeout, but does not update the DB [5] changes the DB state to ACTIVE Which is how this gets out of sync. The solution looks to be fairly simple, and basically involves moving the lock up to the beginning of the method after the debug statements. Can you try https://github.com/wildfly/wildfly/compare/master...stuartwdouglas:WFLY-8... against your test case? I think this should fix it. > Race condition if timers overlap due to long running execution and short schedules if database persistence is used > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-8929 > URL: https://issues.jboss.org/browse/WFLY-8929 > Project: WildFly > Issue Type: Bug > Components: EJB > Environment: Configure DB persistence for timers as file-persistence will not have a persistence check for shouldRun to lock the timer execution. > Reporter: Wolf-Dieter Fink > Assignee: Stuart Douglas > Attachments: server-extract.log, server1.log > > > If timers (here calendar timer) are running longer than scheduled, or the schedule/processing get stuck do to thread or cpu bottleneck, it is possible that the updates for persistence overlap. > The issue seems that the task(1) try to finish the timer and task(2) is about to start but see the concurrency. > The DB is updated with the 'old' next timeout, but the internal Timer instance will be updated with the next possible schedule due to a race condition between the two threads updating the object. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-155) Add JSON and XML formatters

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-155?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-155: --------------------------------- Fix Version/s: 2.1.0.Alpha2 > Add JSON and XML formatters > --------------------------- > > Key: LOGMGR-155 > URL: https://issues.jboss.org/browse/LOGMGR-155 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: James Perkins > Assignee: James Perkins > Fix For: 2.1.0.Alpha2 > > > Add formatters which can format log messages in JSON and XML. These could be useful for log aggregators. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

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 June 2017