[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:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1095294|https://bugzilla.redhat.com/show_bug.cgi?id=1095294] from MODIFIED to ON_QA
> 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)
9 years, 10 months
[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:
-----------------------------------------------
Emanuel Muckenhuber <emuckenh(a)redhat.com> changed the Status of [bug 1108952|https://bugzilla.redhat.com/show_bug.cgi?id=1108952] from MODIFIED to ON_QA
> 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.Alpha1
>
>
> 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)
9 years, 10 months
[JBoss JIRA] (WFLY-3569) DB2 jdbc driver and XA datasource
by Philippe Van Der Gucht (JIRA)
Philippe Van Der Gucht created WFLY-3569:
--------------------------------------------
Summary: DB2 jdbc driver and XA datasource
Key: WFLY-3569
URL: https://issues.jboss.org/browse/WFLY-3569
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 8.1.0.Final
Reporter: Philippe Van Der Gucht
Assignee: Jason Greene
Our type 4 JDBC compliant driver has trouble when writing to two different xa-datasources.
A write has been issued to the datasources but not committed (2 phase). Then, before the commit, a read is done from one of the datasources and this happens:
{noformat}
2014-06-30 15:53:59,837 WARN [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (default task-2) IJ000305: Connection error occured: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@1de1a1e[state=NORMAL managed connection=org.jboss.jca.adapters.jdbc.xa.XAManagedConnection@187619 connection handles=0 lastUse=1404136358809 trackByTx=true pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@1d0f8a mcp=SemaphoreArrayListManagedConnectionPool@b559c4[pool=ourDS] xaResource=XAResourceWrapperImpl@1e747c0[xaResource=org.jboss.jca.adapters.jdbc.xa.XAManagedConnection(a)187619 pad=false overrideRmValue=null productName=IDS/UNIX64 productVersion=IFX11700 jndiName=java:/ourDS] txSync=null]: com.ibm.db2.jcc.am.XaException: [jcc][t4][10401][12066][4.13.127] XA exception: XAER_NOTA ERRORCODE=-4228, SQLSTATE=null
at com.ibm.db2.jcc.am.id.c(id.java:454)
at com.ibm.db2.jcc.am.id.c(id.java:478)
at com.ibm.db2.jcc.t4.bc.a(bc.java:2094)
at com.ibm.db2.jcc.t4.bc.a(bc.java:2333)
at com.ibm.db2.jcc.t4.bc.start(bc.java:1934)
at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.start(XAManagedConnection.java:259)
at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.start(XAResourceWrapperImpl.java:203)
{noformat}
datasource configuration:
{code:xml}
<xa-datasource jndi-name="java:/ourDS" pool-name="ourDS" enabled="true">
<xa-datasource-property name="ServerName">127.0.0.1</xa-datasource-property>
<xa-datasource-property name="PortNumber">9033</xa-datasource-property>
<xa-datasource-property name="DatabaseName">ours</xa-datasource-property>
<xa-datasource-property name="DriverType">4</xa-datasource-property>
<xa-datasource-class>com.ibm.db2.jcc.DB2XADataSource</xa-datasource-class>
<driver>com.informix</driver>
<security>
<user-name>user</user-name>
<password>password</password>
</security>
</xa-datasource>
{code:xml}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months