August 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1159) ConnectionListener leaked if TSR throws IllegalStateException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1159?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1159: ------------------------------------------------ Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1088470|https://bugzilla.redhat.com/show_bug.cgi?id=1088470] from VERIFIED to CLOSED > ConnectionListener leaked if TSR throws IllegalStateException > ------------------------------------------------------------- > > Key: JBJCA-1159 > URL: https://issues.jboss.org/browse/JBJCA-1159 > Project: IronJacamar > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 1.0.24.Final, 1.1.4.Final > Environment: AS7 EAP6.1 > Reporter: Koen Janssens > Assignee: Jesper Pedersen > Priority: Blocker > Fix For: 1.0.25.Final, 1.1.5.Final, 1.2.0.Beta1 > > > When a connection is retrieved from the MCP, ironjacamar will register it to ongoing JTA transaction. However, if the ongoing TX is not 'active' anymore the connection is lost. > The code of AbstractPool demonstrates the problem. The call to getLock will throw an exception if the current TX is not active anymore and the cl is not returned to the pool. > This issue can be reproduced on AS7 by using any EJB that requires a tx and does something with a DB connection. Put a breakpoint in the code below after retrieving the connectionlistener, and then wait for the transaction to timeout. Once that's done, continue the thread. The connection is not release (can be seen in JMX) > We have noticed this problem regularly during our performance tests. > {code} > ConnectionListener cl = mcp.getConnection(subject, cri); > if (trace) > log.tracef("Got connection from pool tracked by transaction=%s tx=%s", cl, trackByTransaction); > TransactionSynchronizationRegistry tsr = getTransactionSynchronizationRegistry(); > Lock lock = getLock(); > try > { > lock.lockInterruptibly(); > } > catch (InterruptedException ie) > { > Thread.interrupted(); > throw new ResourceException(bundle.unableObtainLock(), ie); > } > {code} > It seems this issue was introduced by changes done for https://issues.jboss.org/browse/JBJCA-572 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1161) NPE in SemaphoreArrayListManagedConnectionPool

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1161?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1161: ------------------------------------------------ Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1088470|https://bugzilla.redhat.com/show_bug.cgi?id=1088470] from VERIFIED to CLOSED > NPE in SemaphoreArrayListManagedConnectionPool > ---------------------------------------------- > > Key: JBJCA-1161 > URL: https://issues.jboss.org/browse/JBJCA-1161 > Project: IronJacamar > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 1.0.25.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Blocker > Fix For: 1.0.26.Final > > > {noformat} > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.doDestroy(SemaphoreArrayListManagedConnectionPool.java:866) > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:312) > at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:404) > {noformat} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3189) Error validating jboss-ejb3.xml.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3189?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3189: ----------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1119805|https://bugzilla.redhat.com/show_bug.cgi?id=1119805] from VERIFIED to CLOSED > Error validating jboss-ejb3.xml. > -------------------------------- > > Key: WFLY-3189 > URL: https://issues.jboss.org/browse/WFLY-3189 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.Final > Environment: WildFly 8.0.0.Final > Reporter: shinzey shinzey > Assignee: David Lloyd > > I'm trying to configure code completion for jboss-ejb3.xml with schema, but fail to do that due to the following validation error: > {noformat} > src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' to a(n) 'type definition' component. [33] > src-resolve: Cannot resolve the name 'javaee:jboss-ejb-jarType' to a(n) 'type definition' component. [35] > src-resolve: Cannot resolve the name 'javaee:jboss-enterprise-beansType' to a(n) 'type definition' component. [37] > src-resolve: Cannot resolve the name 'javaee:assembly-descriptor-entry' to a(n) 'element declaration' component. [35] > src-resolve: Cannot resolve the name 'javaee:jboss-assembly-descriptor-bean-entryType' to a(n) 'type definition' component. [39] > {noformat} > The jboss-ejb3.xml is quite simple: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <jboss:ejb-jar version="3.1" impl-version="2.0" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:jboss="http://www.jboss.com/xml/ns/javaee" > xmlns:s="urn:security:1.1" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd > http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd"> > <assembly-descriptor> > <s:security> > <ejb-name>*</ejb-name> > <s:security-domain>testsd</s:security-domain> > </s:security> > </assembly-descriptor> > </jboss:ejb-jar> > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBEE-148) Unbounded ELEvaluator cache can cause OOMEs

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBEE-148?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on JBEE-148: ---------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1088423|https://bugzilla.redhat.com/show_bug.cgi?id=1088423] from VERIFIED to CLOSED > Unbounded ELEvaluator cache can cause OOMEs > ------------------------------------------- > > Key: JBEE-148 > URL: https://issues.jboss.org/browse/JBEE-148 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jboss-jstl-api > Affects Versions: jboss-jstl-api_1.2_spec-1.0.5.Final, jboss-jstl-api_1.2_spec-1.1.0.Final > Reporter: Aaron Ogburn > Assignee: Tomaz Cerar > Fix For: jboss-jstl-api_1.2_spec-1.1.1.Final, jboss-jstl-api_1.2_spec-1.0.6.Final > > Attachments: diff.out > > > Unbounded jstl ELEvaluator cache can cause OOMEs. > Related community issue: > https://issues.apache.org/bugzilla/show_bug.cgi?id=31789 > This was fixed in 1.0 and 1.1 but never got added to 1.2 so we missed this here too. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3541) RemoteDomainConnectionService should not shut down the provided executor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3541?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3541: ----------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1112215|https://bugzilla.redhat.com/show_bug.cgi?id=1112215] from VERIFIED to CLOSED > RemoteDomainConnectionService should not shut down the provided executor > ------------------------------------------------------------------------ > > Key: WFLY-3541 > URL: https://issues.jboss.org/browse/WFLY-3541 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 9.0.0.Beta1 > > > The WFLY-3225 fix changed RemoteDomainConnectionService from creating its own executor to accepting an external one via its constructor. But its stop() code was not modified to remove the call to shutdown the executor. As a result the service is shutting down an injected executor prematurely, leading to issues like https://bugzilla.redhat.com/show_bug.cgi?id=1112215. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3199) Remove external BOM from jboss-as-parent

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3199?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3199: ----------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1082820|https://bugzilla.redhat.com/show_bug.cgi?id=1082820] from VERIFIED to CLOSED > Remove external BOM from jboss-as-parent > ---------------------------------------- > > Key: WFLY-3199 > URL: https://issues.jboss.org/browse/WFLY-3199 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Gier > Assignee: Paul Gier > Priority: Minor > Fix For: 8.1.0.CR1, 8.1.0.Final > > > The jboss-as-parent pom currently depends on an external BOM (apacheds-parent) to get some dependency versions. This means that it's not obvious which version is used for some dependencies. And it's possible that a version could be unintentionally upgraded. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-826) Fix for SECURITY-640 breaks "Continuation Required" logic of the NegotiationAuthenticator and SPNEGOLoginModule

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-826?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-826: -------------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1097803|https://bugzilla.redhat.com/show_bug.cgi?id=1097803] from VERIFIED to CLOSED > Fix for SECURITY-640 breaks "Continuation Required" logic of the NegotiationAuthenticator and SPNEGOLoginModule > --------------------------------------------------------------------------------------------------------------- > > Key: SECURITY-826 > URL: https://issues.jboss.org/browse/SECURITY-826 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_1_Final > > > The fix for SECURITY-640 breaks "Continuation Required" logic of the NegotiationAuthenticator and SPNEGOLoginModule. The "Continuation Required" logic is not triggered by all clients. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-4705) differences between registered and described operations for messaging resources in domain mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-4705?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-4705: ---------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1097770|https://bugzilla.redhat.com/show_bug.cgi?id=1097770] from VERIFIED to CLOSED > differences between registered and described operations for messaging resources in domain mode > ---------------------------------------------------------------------------------------------- > > Key: AS7-4705 > URL: https://issues.jboss.org/browse/AS7-4705 > Project: Application Server 7 > Issue Type: Bug > Components: Console, JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 7.1.2.Final (EAP) > > > The console does not give the same list of operation names for a messaging jms-topic resource when AS7 runs in standalone mode or domain mode. > In standalone mode: > {noformat} > [standalone@localhost:9999 /] /subsystem=messaging/hornetq-server=default/jms-topic=testT/:read-operation-names > { > "outcome" => "success", > "result" => [ > "add", > "add-jndi", > "count-messages-for-subscription", > "drop-all-subscriptions", > "drop-durable-subscription", > "list-all-subscriptions", > "list-all-subscriptions-as-json", > "list-durable-subscriptions", > "list-durable-subscriptions-as-json", > "list-messages-for-subscription", > "list-messages-for-subscription-as-json", > "list-non-durable-subscriptions", > "list-non-durable-subscriptions-as-json", > "read-attribute", > "read-children-names", > "read-children-resources", > "read-children-types", > "read-operation-description", > "read-operation-names", > "read-resource", > "read-resource-description", > "remove", > "remove-messages", > "undefine-attribute", > "whoami", > "write-attribute" > ] > } > {noformat} > In domain mode: > {noformat} > [domain@localhost:9999 /] /host=master/server=server-one/subsystem=messaging/hornetq-server=default/jms-topic=testT/:read-operation-names > { > "outcome" => "success", > "result" => [ > "count-messages-for-subscription", > "list-all-subscriptions", > "list-all-subscriptions-as-json", > "list-durable-subscriptions", > "list-durable-subscriptions-as-json", > "list-messages-for-subscription", > "list-messages-for-subscription-as-json", > "list-non-durable-subscriptions", > "list-non-durable-subscriptions-as-json", > "read-attribute", > "read-children-names", > "read-children-resources", > "read-children-types", > "read-operation-description", > "read-operation-names", > "read-resource", > "read-resource-description" > ] > } > {noformat} > I was expecting to have access to the same list of operations names using this address in domain mode than in standalone mode but some are missing (eg drop-all-subscriptions). > However it is possible to perform the operation even when it is not displayed in the operation names: > {noformat} > [domain@localhost:9999 /] /host=master/server=server-one/subsystem=messaging/hornetq-server=default/jms-topic=testT/:read-operation-description(name="drop-all-subscriptions") > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014753: There is no operation drop-all-subscriptions registered at address [ > (\"subsystem\" => \"messaging\"), > (\"hornetq-server\" => \"default\"), > (\"jms-topic\" => \"testT\") > ]", > "rolled-back" => true > } > [domain@localhost:9999 /] /host=master/server=server-one/subsystem=messaging/hornetq-server=default/jms-topic=testT/:drop-all-subscriptions() > { > "outcome" => "success", > "result" => undefined > } > {noformat} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2511) NPE in QueueReadAttributeHandler if QueueControl does not exist

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2511?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2511: ----------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1095294|https://bugzilla.redhat.com/show_bug.cgi?id=1095294] from VERIFIED to CLOSED > NPE in QueueReadAttributeHandler if QueueControl does not exist > --------------------------------------------------------------- > > Key: WFLY-2511 > URL: https://issues.jboss.org/browse/WFLY-2511 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS > Affects Versions: 8.0.0.Beta1 > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Fix For: 8.0.0.CR1 > > > I noticed this in a testsuite server log for EAP, but looking at WF code the same thing could happen there. Basically QueueReadAttributeHandler assumes a QueueControl exists and throws an NPE if that assumption is wrong: > 19:14:25,402 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) JBAS014612: Operation ("read-attribute") failed - address: ([ > ("subsystem" => "messaging"), > ("hornetq-server" => "default"), > ("queue" => "39742e8e-32e7-481d-905a-580fd6b67476") > ]): java.lang.NullPointerException > at org.jboss.as.messaging.QueueReadAttributeHandler.executeRuntimeStep(QueueReadAttributeHandler.java:115) > at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:96) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:607) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:485) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:282) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:277) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:231) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:137) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:173) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:105) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:125) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:121) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_25] > at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_25] > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:121) [jboss-as-controller-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283) [jboss-as-protocol-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504) [jboss-as-protocol-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final-redhat-1.jar:2.1.1.Final-redhat-1] > IIRC this kind of thing has been fixed elsewhere??? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3359) Transferring an operation attachments to slaves may lead to an OOM

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3359?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3359: ----------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1108952|https://bugzilla.redhat.com/show_bug.cgi?id=1108952] from VERIFIED to CLOSED > Transferring an operation attachments to slaves may lead to an OOM > ------------------------------------------------------------------ > > Key: WFLY-3359 > URL: https://issues.jboss.org/browse/WFLY-3359 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Emanuel Muckenhuber > Assignee: Emanuel Muckenhuber > Fix For: 9.0.0.Beta1 > > > Transferring an operation attachment to a slave may lead to an OutOfMemoryError. > {code} > 19:44:47,794 ERROR [stderr] (domain-mgmt-handler-thread - 13) Exception in thread "domain-mgmt-handler-thread - 13" java.lang.OutOfMemoryError: Java heap space > 19:44:47,795 ERROR [stderr] (domain-mgmt-handler-thread - 13) at java.util.Arrays.copyOf(Arrays.java:2271) > 19:44:47,795 ERROR [stderr] (domain-mgmt-handler-thread - 13) at java.io.ByteArrayOutputStream.toByteArray(ByteArrayOutputStream.java:178) > 19:44:47,795 ERROR [stderr] (domain-mgmt-handler-thread - 13) at org.jboss.as.controller.remote.TransactionalProtocolClientImpl$ReadAttachmentInputStreamRequestHandler$1.execute(TransactionalProtocolClientImpl.java:277) > 19:44:47,796 ERROR [stderr] (domain-mgmt-handler-thread - 13) at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283) > 19:44:47,796 ERROR [stderr] (domain-mgmt-handler-thread - 13) at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504) > 19:44:47,797 ERROR [stderr] (domain-mgmt-handler-thread - 13) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > 19:44:47,797 ERROR [stderr] (domain-mgmt-handler-thread - 13) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > 19:44:47,797 ERROR [stderr] (domain-mgmt-handler-thread - 13) at java.lang.Thread.run(Thread.java:724) > 19:44:47,798 ERROR [stderr] (domain-mgmt-handler-thread - 13) at org.jboss.threads.JBossThread.run(JBossThread.java:122) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 3 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 August 2014