[JBoss JIRA] (WFLY-4326) Enable JPA meterics, all metrics zero
by Tim Mickelson (JIRA)
Tim Mickelson created WFLY-4326:
-----------------------------------
Summary: Enable JPA meterics, all metrics zero
Key: WFLY-4326
URL: https://issues.jboss.org/browse/WFLY-4326
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 8.2.0.Final
Environment: Windows 7, Ubuntu 14.04, CentOS, JDK1.7
Reporter: Tim Mickelson
Assignee: Scott Marlow
Enable JPA on any ear deployd on server and no metrics are presented. The datasource is JTA enabled and the same deployments (ears) deployd on JBoss 7.1.1 result in non zero metrics when JPA is enabled per ear on JBoss 7.1.1.
Note: I have a very similar issue with the transaction metrics WFLY-4323
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4323) Transaction metrics all zero
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-4323?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on WFLY-4323:
-------------------------------------
Hi Tim, I think your issue is likely to be similar, but in a different component and code path. I would raise a new issue and link it to this. Use the JPA component and hopefully [~smarlow] will pick it up.
> Transaction metrics all zero
> ----------------------------
>
> Key: WFLY-4323
> URL: https://issues.jboss.org/browse/WFLY-4323
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 8.2.0.Final
> Environment: Linux, JDK 1.7, Spring 4, Hibernate
> Reporter: Tim Mickelson
> Assignee: Michael Musgrove
>
> Hello, I have enabled the transactions metrics in standalone.xml on my Wildfly 8.2.0 as below but the transactions metrics are always zero, even though I have many projects deployed using transactions. Probably something trivial is missing, could some one tell me what is wrong? I'm using the Spring Framework 4.1.2 and Hibernate as installed in the Wildfly modules.
> I started this as a question on the forum but got no answer. Please note that the exact same configuration on the same server gives Transaction statistics with the same deployments on JBoss 7.1.1
>
> Thanks for any help, Tim Mickelson
>
>
> <subsystem xmlns="urn:jboss:domain:transactions:2.0">
> <core-environment>
> <process-id>
> <uuid/>
> </process-id>
> </core-environment>
> <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>
> <coordinator-environment default-timeout="300" statistics-enabled="true"/>
> </subsystem>
>
>
> The datasource is configured as (with jta true):
>
> <datasource jta="true" jndi-name="java:/youconnect" pool-name="youconnect_Pool" enabled="true" use-java-context="true" use-ccm="true">
> <connection-url>jdbc:postgresql://127.0.0.1:5432/youconnect</connection-url>
> <driver-class>org.postgresql.Driver</driver-class>
> <driver>ps</driver>
> <pool>
> <min-pool-size>10</min-pool-size>
> <max-pool-size>30</max-pool-size>
> <prefill>true</prefill>
> <flush-strategy>IdleConnections</flush-strategy>
> </pool>
> <security>
> <user-name>yyyy</user-name>
> <password>xxxxx</password>
> </security>
> </datasource>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4320) add->activate->remove->add->activate fails for Resource Adapter
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-4320?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on WFLY-4320:
-------------------------------------
I have no idea of the conditions under which the INFO is returned, but maybe we can just say after a :remove you have to call /:reload? Did it work for you on amq? I was using the activemq community rar.
> add->activate->remove->add->activate fails for Resource Adapter
> ----------------------------------------------------------------
>
> Key: WFLY-4320
> URL: https://issues.jboss.org/browse/WFLY-4320
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 8.2.0.Final
> Reporter: Johnathon Lee
> Assignee: Stefano Maestri
>
> add->activate->remove->add->activate fails for Resource Adapter
> [1]
> [jolee@jolee540 jboss-eap-6.3.x]$ bin/jboss-cli.sh --connect
> [standalone@localhost:9999 /] deploy /home/jolee/amq.rar
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=amq:add(archive=amq.rar,transaction-support=XATransaction)
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=amq:activate
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=amq:remove
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=amq:add(archive=amq.rar,transaction-support=XATransaction)
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=amq:activate
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014749: Operation handler failed: Service jboss.ra.deployment.amq is already registered",
> "rolled-back" => true
> }
> TRACE from failure
> 15:15:53,732 TRACE [org.jboss.as.connector.logging] (management-handler-thread - 10) ConnectorServices: getDeploymentServiceName(amq,<resource-adapter><archive>amq.rar</archive><transaction-support>XATransaction</transaction-support></resource-adapter>) -> service jboss.ra.deployment.amq
> 15:15:53,733 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 10) JBAS014612: Operation ("activate") failed - address: ([
> ("subsystem" => "resource-adapters"),
> ("resource-adapter" => "amq")
> ]): org.jboss.msc.service.DuplicateServiceException: Service jboss.ra.deployment.amq is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:236) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:742) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:243) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2433) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:243) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2433) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:345) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.as.connector.util.RaServicesFactory.createDeploymentService(RaServicesFactory.java:104)
> at org.jboss.as.connector.subsystems.resourceadapters.RaOperationUtil.activate(RaOperationUtil.java:320)
> at org.jboss.as.connector.subsystems.resourceadapters.RaActivate$1.execute(RaActivate.java:57)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:611) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:489) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:290) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:285) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1132) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:251) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:152) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:203) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:132) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:149) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_45]
> at javax.security.auth.Subject.doAs(Subject.java:396) [rt.jar:1.6.0_45]
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:149) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:298) [jboss-as-protocol-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:537) [jboss-as-protocol-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final-redhat-1.jar:2.1.1.Final-redhat-1]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4320) add->activate->remove->add->activate fails for Resource Adapter
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/WFLY-4320?page=com.atlassian.jira.plugin.... ]
Johnathon Lee commented on WFLY-4320:
-------------------------------------
That's frustrating. I had multiple iterations and was not presented with the :reload-required output.
The intention of the JIRA was to address the dynamic addition and removal of a resource adapter. Thus allowing for the same resource adapter to be removed and then re-added with a different configuration and no :reload in the process.
> add->activate->remove->add->activate fails for Resource Adapter
> ----------------------------------------------------------------
>
> Key: WFLY-4320
> URL: https://issues.jboss.org/browse/WFLY-4320
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 8.2.0.Final
> Reporter: Johnathon Lee
> Assignee: Stefano Maestri
>
> add->activate->remove->add->activate fails for Resource Adapter
> [1]
> [jolee@jolee540 jboss-eap-6.3.x]$ bin/jboss-cli.sh --connect
> [standalone@localhost:9999 /] deploy /home/jolee/amq.rar
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=amq:add(archive=amq.rar,transaction-support=XATransaction)
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=amq:activate
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=amq:remove
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=amq:add(archive=amq.rar,transaction-support=XATransaction)
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=amq:activate
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014749: Operation handler failed: Service jboss.ra.deployment.amq is already registered",
> "rolled-back" => true
> }
> TRACE from failure
> 15:15:53,732 TRACE [org.jboss.as.connector.logging] (management-handler-thread - 10) ConnectorServices: getDeploymentServiceName(amq,<resource-adapter><archive>amq.rar</archive><transaction-support>XATransaction</transaction-support></resource-adapter>) -> service jboss.ra.deployment.amq
> 15:15:53,733 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 10) JBAS014612: Operation ("activate") failed - address: ([
> ("subsystem" => "resource-adapters"),
> ("resource-adapter" => "amq")
> ]): org.jboss.msc.service.DuplicateServiceException: Service jboss.ra.deployment.amq is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:236) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:742) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:243) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2433) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:243) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2433) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:345) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.as.connector.util.RaServicesFactory.createDeploymentService(RaServicesFactory.java:104)
> at org.jboss.as.connector.subsystems.resourceadapters.RaOperationUtil.activate(RaOperationUtil.java:320)
> at org.jboss.as.connector.subsystems.resourceadapters.RaActivate$1.execute(RaActivate.java:57)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:611) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:489) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:290) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:285) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1132) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:251) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:152) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:203) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:132) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:149) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_45]
> at javax.security.auth.Subject.doAs(Subject.java:396) [rt.jar:1.6.0_45]
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:149) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:298) [jboss-as-protocol-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:537) [jboss-as-protocol-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final-redhat-1.jar:2.1.1.Final-redhat-1]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4323) Transaction metrics all zero
by Tim Mickelson (JIRA)
[ https://issues.jboss.org/browse/WFLY-4323?page=com.atlassian.jira.plugin.... ]
Tim Mickelson edited comment on WFLY-4323 at 2/6/15 9:35 AM:
-------------------------------------------------------------
Ok, when I enable the JPA metrics I actually have the same problem as for the transactions, in the manager all metrics are zero. I have made no special configurations, it's practically out of the box from download and I'm running 3 different servers all with the same issue. One on windows 7 (my development env), one on Ubunt (test env) and one on CentOS (production env).
Also for the JPA metrics all works like a charm on JBoss 7.1.1 in all environments.
I'm guessing that the issue is extremly simular as for the transaction metrics. Please let me konow if this is a different issue and I should open another issue for this?
was (Author: tim_mickelson):
Ok, when I enable the JPA metrics I actually have the same problem as for the transactions, in the manager all metrics are zero. I have made no special configurations, it's practically out of the box from download and I'm running 3 different servers all with the same issue. One on windows 7 (my development env), one on Ubunt (test env) and one on CentOS (production env).
Also for the JPA metrics all works like a charm on JBoss 7.1.1 in all environments.
I'm guessing that the issue is extremly simular as for the transaction metrics.
> Transaction metrics all zero
> ----------------------------
>
> Key: WFLY-4323
> URL: https://issues.jboss.org/browse/WFLY-4323
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 8.2.0.Final
> Environment: Linux, JDK 1.7, Spring 4, Hibernate
> Reporter: Tim Mickelson
> Assignee: Michael Musgrove
>
> Hello, I have enabled the transactions metrics in standalone.xml on my Wildfly 8.2.0 as below but the transactions metrics are always zero, even though I have many projects deployed using transactions. Probably something trivial is missing, could some one tell me what is wrong? I'm using the Spring Framework 4.1.2 and Hibernate as installed in the Wildfly modules.
> I started this as a question on the forum but got no answer. Please note that the exact same configuration on the same server gives Transaction statistics with the same deployments on JBoss 7.1.1
>
> Thanks for any help, Tim Mickelson
>
>
> <subsystem xmlns="urn:jboss:domain:transactions:2.0">
> <core-environment>
> <process-id>
> <uuid/>
> </process-id>
> </core-environment>
> <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>
> <coordinator-environment default-timeout="300" statistics-enabled="true"/>
> </subsystem>
>
>
> The datasource is configured as (with jta true):
>
> <datasource jta="true" jndi-name="java:/youconnect" pool-name="youconnect_Pool" enabled="true" use-java-context="true" use-ccm="true">
> <connection-url>jdbc:postgresql://127.0.0.1:5432/youconnect</connection-url>
> <driver-class>org.postgresql.Driver</driver-class>
> <driver>ps</driver>
> <pool>
> <min-pool-size>10</min-pool-size>
> <max-pool-size>30</max-pool-size>
> <prefill>true</prefill>
> <flush-strategy>IdleConnections</flush-strategy>
> </pool>
> <security>
> <user-name>yyyy</user-name>
> <password>xxxxx</password>
> </security>
> </datasource>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4323) Transaction metrics all zero
by Tim Mickelson (JIRA)
[ https://issues.jboss.org/browse/WFLY-4323?page=com.atlassian.jira.plugin.... ]
Tim Mickelson commented on WFLY-4323:
-------------------------------------
Ok, when I enable the JPA metrics I actually have the same problem as for the transactions, in the manager all metrics are zero. I have made no special configurations, it's practically out of the box from download and I'm running 3 different servers all with the same issue. One on windows 7 (my development env), one on Ubunt (test env) and one on CentOS (production env).
Also for the JPA metrics all works like a charm on JBoss 7.1.1 in all environments.
I'm guessing that the issue is extremly simular as for the transaction metrics.
> Transaction metrics all zero
> ----------------------------
>
> Key: WFLY-4323
> URL: https://issues.jboss.org/browse/WFLY-4323
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 8.2.0.Final
> Environment: Linux, JDK 1.7, Spring 4, Hibernate
> Reporter: Tim Mickelson
> Assignee: Michael Musgrove
>
> Hello, I have enabled the transactions metrics in standalone.xml on my Wildfly 8.2.0 as below but the transactions metrics are always zero, even though I have many projects deployed using transactions. Probably something trivial is missing, could some one tell me what is wrong? I'm using the Spring Framework 4.1.2 and Hibernate as installed in the Wildfly modules.
> I started this as a question on the forum but got no answer. Please note that the exact same configuration on the same server gives Transaction statistics with the same deployments on JBoss 7.1.1
>
> Thanks for any help, Tim Mickelson
>
>
> <subsystem xmlns="urn:jboss:domain:transactions:2.0">
> <core-environment>
> <process-id>
> <uuid/>
> </process-id>
> </core-environment>
> <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>
> <coordinator-environment default-timeout="300" statistics-enabled="true"/>
> </subsystem>
>
>
> The datasource is configured as (with jta true):
>
> <datasource jta="true" jndi-name="java:/youconnect" pool-name="youconnect_Pool" enabled="true" use-java-context="true" use-ccm="true">
> <connection-url>jdbc:postgresql://127.0.0.1:5432/youconnect</connection-url>
> <driver-class>org.postgresql.Driver</driver-class>
> <driver>ps</driver>
> <pool>
> <min-pool-size>10</min-pool-size>
> <max-pool-size>30</max-pool-size>
> <prefill>true</prefill>
> <flush-strategy>IdleConnections</flush-strategy>
> </pool>
> <security>
> <user-name>yyyy</user-name>
> <password>xxxxx</password>
> </security>
> </datasource>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4320) add->activate->remove->add->activate fails for Resource Adapter
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-4320?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on WFLY-4320:
-------------------------------------
Hi,
{code}
[standalone@localhost:9990 /] /subsystem=resource-adapters/resource-adapter=amq:remove
INFO [org.jboss.as.cli.CommandContext] {
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
{code}
The strange thing is that is not always printed out. But even when its not:
{code}
[standalone@localhost:9990 /] /subsystem=resource-adapters/resource-adapter=amq:add(archive=activemq-rar-5.11.0.rar,transaction-support=XATransaction)
INFO [org.jboss.as.cli.CommandContext] {"outcome" => "success"}
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=resource-adapters/resource-adapter=amq:activate
INFO [org.jboss.as.cli.CommandContext] {"outcome" => "success"}
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=resource-adapters/resource-adapter=amq:remove
INFO [org.jboss.as.cli.CommandContext] {"outcome" => "success"}
{"outcome" => "success"}
[standalone@localhost:9990 /] /:reload
INFO [org.jboss.as.cli.CommandContext] {
"outcome" => "success",
"result" => undefined
}
{
"outcome" => "success",
"result" => undefined
}
[standalone@localhost:9990 /] /subsystem=resource-adapters/resource-adapter=amq:add(archive=activemq-rar-5.11.0.rar,transaction-support=XATransaction)
INFO [org.jboss.as.cli.CommandContext] {"outcome" => "success"}
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=resource-adapters/resource-adapter=amq:activate
INFO [org.jboss.as.cli.CommandContext] {"outcome" => "success"}
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=resource-adapters/resource-adapter=amq:remove
INFO [org.jboss.as.cli.CommandContext] {"outcome" => "success"}
{"outcome" => "success"}
{code}
> add->activate->remove->add->activate fails for Resource Adapter
> ----------------------------------------------------------------
>
> Key: WFLY-4320
> URL: https://issues.jboss.org/browse/WFLY-4320
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 8.2.0.Final
> Reporter: Johnathon Lee
> Assignee: Stefano Maestri
>
> add->activate->remove->add->activate fails for Resource Adapter
> [1]
> [jolee@jolee540 jboss-eap-6.3.x]$ bin/jboss-cli.sh --connect
> [standalone@localhost:9999 /] deploy /home/jolee/amq.rar
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=amq:add(archive=amq.rar,transaction-support=XATransaction)
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=amq:activate
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=amq:remove
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=amq:add(archive=amq.rar,transaction-support=XATransaction)
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=amq:activate
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014749: Operation handler failed: Service jboss.ra.deployment.amq is already registered",
> "rolled-back" => true
> }
> TRACE from failure
> 15:15:53,732 TRACE [org.jboss.as.connector.logging] (management-handler-thread - 10) ConnectorServices: getDeploymentServiceName(amq,<resource-adapter><archive>amq.rar</archive><transaction-support>XATransaction</transaction-support></resource-adapter>) -> service jboss.ra.deployment.amq
> 15:15:53,733 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 10) JBAS014612: Operation ("activate") failed - address: ([
> ("subsystem" => "resource-adapters"),
> ("resource-adapter" => "amq")
> ]): org.jboss.msc.service.DuplicateServiceException: Service jboss.ra.deployment.amq is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:236) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:742) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:243) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2433) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:243) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2433) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:345) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.as.connector.util.RaServicesFactory.createDeploymentService(RaServicesFactory.java:104)
> at org.jboss.as.connector.subsystems.resourceadapters.RaOperationUtil.activate(RaOperationUtil.java:320)
> at org.jboss.as.connector.subsystems.resourceadapters.RaActivate$1.execute(RaActivate.java:57)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:611) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:489) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:290) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:285) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1132) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:251) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:152) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:203) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:132) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:149) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_45]
> at javax.security.auth.Subject.doAs(Subject.java:396) [rt.jar:1.6.0_45]
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:149) [jboss-as-controller-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:298) [jboss-as-protocol-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:537) [jboss-as-protocol-7.4.3.Final-redhat-SNAPSHOT.jar:7.4.3.Final-redhat-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final-redhat-1.jar:2.1.1.Final-redhat-1]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4323) Transaction metrics all zero
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/WFLY-4323?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on WFLY-4323:
----------------------------------------
We deprecated enable-statistics in favour of statistics-enabled (see commit f6c2527). Using either name will update the new attribute in the model but TransactionSubsystemAdd#performCoordinatorEnvBoottime is asking the model for the old deprecated attribute which in the model is now undefined.
The fix is for TransactionSubsystemAdd to ask for the new attribute, ie TransactionSubsystemRootResourceDefinition.STATISTICS_ENABLED
> Transaction metrics all zero
> ----------------------------
>
> Key: WFLY-4323
> URL: https://issues.jboss.org/browse/WFLY-4323
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 8.2.0.Final
> Environment: Linux, JDK 1.7, Spring 4, Hibernate
> Reporter: Tim Mickelson
> Assignee: Michael Musgrove
>
> Hello, I have enabled the transactions metrics in standalone.xml on my Wildfly 8.2.0 as below but the transactions metrics are always zero, even though I have many projects deployed using transactions. Probably something trivial is missing, could some one tell me what is wrong? I'm using the Spring Framework 4.1.2 and Hibernate as installed in the Wildfly modules.
> I started this as a question on the forum but got no answer. Please note that the exact same configuration on the same server gives Transaction statistics with the same deployments on JBoss 7.1.1
>
> Thanks for any help, Tim Mickelson
>
>
> <subsystem xmlns="urn:jboss:domain:transactions:2.0">
> <core-environment>
> <process-id>
> <uuid/>
> </process-id>
> </core-environment>
> <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>
> <coordinator-environment default-timeout="300" statistics-enabled="true"/>
> </subsystem>
>
>
> The datasource is configured as (with jta true):
>
> <datasource jta="true" jndi-name="java:/youconnect" pool-name="youconnect_Pool" enabled="true" use-java-context="true" use-ccm="true">
> <connection-url>jdbc:postgresql://127.0.0.1:5432/youconnect</connection-url>
> <driver-class>org.postgresql.Driver</driver-class>
> <driver>ps</driver>
> <pool>
> <min-pool-size>10</min-pool-size>
> <max-pool-size>30</max-pool-size>
> <prefill>true</prefill>
> <flush-strategy>IdleConnections</flush-strategy>
> </pool>
> <security>
> <user-name>yyyy</user-name>
> <password>xxxxx</password>
> </security>
> </datasource>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months