[JBoss JIRA] (WFLY-4326) Enable JPA meterics, all metrics zero
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-4326?page=com.atlassian.jira.plugin.... ]
Scott Marlow closed WFLY-4326.
------------------------------
> 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
> Labels: jpa
>
> 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-4326) Enable JPA meterics, all metrics zero
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-4326?page=com.atlassian.jira.plugin.... ]
Scott Marlow commented on WFLY-4326:
------------------------------------
Try using the jboss-cli (.sh or .bat) tool to display the statistics (you should see "Query execution" "Max time" and other statistics).
{quote}
./jboss-cli.sh
connect
cd /deployment=npetest.ear/subsystem=jpa/jpa-hibernate=YourEar#JPADB
:read-resource(include-runtime=true,recursive=true)
{quote}
> 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
> Labels: jpa
>
> 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-4326) Enable JPA meterics, all metrics zero
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-4326?page=com.atlassian.jira.plugin.... ]
Scott Marlow resolved WFLY-4326.
--------------------------------
Resolution: Rejected
not a bug...
> 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
> Labels: jpa
>
> 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-3512) Removing a data-source that is used by a deployment breaks the deployment
by Ivo Studensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-3512?page=com.atlassian.jira.plugin.... ]
Ivo Studensky reassigned WFLY-3512:
-----------------------------------
Assignee: Ivo Studensky (was: Stefano Maestri)
Fix Version/s: 9.0.0.Beta1
Resolution: Done
> Removing a data-source that is used by a deployment breaks the deployment
> -------------------------------------------------------------------------
>
> Key: WFLY-3512
> URL: https://issues.jboss.org/browse/WFLY-3512
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 8.1.0.Final
> Reporter: Jeff Mesnil
> Assignee: Ivo Studensky
> Fix For: 9.0.0.Beta1
>
>
> Use case: a Web app which depends on a data-source resource configured in the datasources subsystem (and *not* in the deployment)
> I used the bmp quickstart and move the datasource-definition from the -ds.xml file to the standalone-full.xml configuration file.
> 1. Start the server
> {noformat}
> 11:31:38,279 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-9) WFLYJCA0001: Bound data source [java:jboss/datasources/BMTQuickstartDS]
> {noformat}
> 1. Deploy the web app
> {noformat}
> 11:32:33,664 INFO [org.jboss.as.server.deployment] (MSC service thread 1-16) WFLYSRV0027: Starting deployment of "wildfly-bmt.war" (runtime-name: "wildfly-bmt.war")
> ...
> 11:32:35,976 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0021: Registered web context: /wildfly-bmt
> 11:32:36,020 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "wildfly-bmt.war" (runtime-name : "wildfly-bmt.war")
> {noformat}
> 2. check the web app works
> 3. Remove the data-source from the CLI
> {noformat}
> [standalone@localhost:9990 /] /subsystem=datasources/data-source=bmt-quickstart:remove
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies:
> Service jboss.naming.context.java.jboss.datasources.BMTQuickstartDS was depended upon by service jboss.persistenceunit.\"wildfly-bmt.war#primary\".__FIRST_PHASE__",
> "rolled-back" => true
> }
> {noformat}
> => the operation failed.
> but the web context has been unregistered by the server:
> {noformat}
> 11:33:33,345 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0022: Unregistered web context: /wildfly-bmt
> 11:33:33,354 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 71) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'wildfly-bmt.war#primary'
> 11:33:33,355 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 71) HHH000227: Running hbm2ddl schema export
> 11:33:33,356 INFO [stdout] (ServerService Thread Pool -- 71) Hibernate: drop table BMT_KVPair if exists
> 11:33:33,358 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 71) HHH000230: Schema export complete
> 11:33:33,360 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0010: Stopping weld service for deployment wildfly-bmt.war
> 11:33:33,378 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 71) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'wildfly-bmt.war#primary'
> 11:33:33,379 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-11) WFLYJCA0010: Unbound data source [java:jboss/datasources/BMTQuickstartDS]
> 11:33:33,383 INFO [org.jboss.as.controller] (management-handler-thread - 1) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.naming.context.java.jboss.datasources.BMTQuickstartDS (missing) dependents: [service jboss.persistenceunit."wildfly-bmt.war#primary".__FIRST_PHASE__]
> {noformat}
> and the web app no longer works (it returns a 404 error).
> At this point, the data-source resource is still present but its corresponding JNDI binding is not. If I try to redeploy the web app it fails:
> {noformat}
> 11:35:48,736 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /Users/jmesnil/Developer/wildfly/dist/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ff/2df0dc4b7d9d1e04a88448deba520c2b714b8b/content
> 11:35:48,748 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment wildfly-bmt.war (runtime-name: wildfly-bmt.war) in 9ms
> 11:35:48,749 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "wildfly-bmt.war" (runtime-name: "wildfly-bmt.war")
> 11:35:48,775 INFO [org.jboss.as.jpa] (MSC service thread 1-6) WFLYJPA0002: Read persistence.xml for primary
> 11:35:48,786 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment wildfly-bmt.war (runtime-name: wildfly-bmt.war) in 36ms
> 11:35:48,787 INFO [org.jboss.as.server.deployment] (MSC service thread 1-16) WFLYSRV0027: Starting deployment of "wildfly-bmt.war" (runtime-name: "wildfly-bmt.war")
> 11:35:48,815 INFO [org.jboss.as.jpa] (MSC service thread 1-13) WFLYJPA0002: Read persistence.xml for primary
> 11:35:48,829 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("redeploy") failed - address: ([("deployment" => "wildfly-bmt.war")]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"wildfly-bmt.war#primary\".__FIRST_PHASE__ is missing [jboss.naming.context.java.jboss.datasources.BMTQuickstartDS]"]}
> 11:35:48,830 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0011: Redeploy of deployment "wildfly-bmt.war" was rolled back with the following failure message: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"wildfly-bmt.war#primary\".__FIRST_PHASE__ is missing [jboss.naming.context.java.jboss.datasources.BMTQuickstartDS]"]}
> 11:35:48,835 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) WFLYSRV0028: Stopped deployment wildfly-bmt.war (runtime-name: wildfly-bmt.war) in 4ms
> 11:35:48,836 INFO [org.jboss.as.controller] (management-handler-thread - 1) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.persistenceunit."wildfly-bmt.war#primary".__FIRST_PHASE__ (missing) dependents: [service jboss.deployment.unit."wildfly-bmt.war".POST_MODULE]
> 11:35:48,836 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /Users/jmesnil/Developer/wildfly/dist/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ff/2df0dc4b7d9d1e04a88448deba520c2b714b8b/content
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (JBWEB-309) Getting 505 status instead 413 for long query parameters string and connection shut down on client side
by Roman Nikolaienko (JIRA)
Roman Nikolaienko created JBWEB-309:
---------------------------------------
Summary: Getting 505 status instead 413 for long query parameters string and connection shut down on client side
Key: JBWEB-309
URL: https://issues.jboss.org/browse/JBWEB-309
Project: JBoss Web
Issue Type: Bug
Components: Tomcat
Affects Versions: JBossWeb-7.0.16.GA
Reporter: Roman Nikolaienko
Assignee: Remy Maucherat
Hello,
During investigation bug in our application, I've figured out that we send too long queries parameters string ( such as size of request headers > org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE) to Jboss.
There are strange things were:
1. Response status code = 505, instead 413 as per HTTP1.1 spec (http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html).
2. After client gets back 505, jboss destroys socket and client will get "java.net.SocketException: Connection reset" if tried to parse response or reuse connection in connection pool.
Here is Jboss DEBUG logs:
13:53:41,977 DEBUG [org.apache.coyote.http11.Http11Processor] (http-/0.0.0.0:10001-1) Error parsing HTTP request header: java.lang.IllegalArgumentException: Request header is too large
at org.apache.coyote.http11.InternalInputBuffer.fill(InternalInputBuffer.java:727) [jbossweb-7.0.16.Final-redhat-1.jar:]
at org.apache.coyote.http11.InternalInputBuffer.parseRequestLine(InternalInputBuffer.java:435) [jbossweb-7.0.16.Final-redhat-1.jar:]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:838) [jbossweb-7.0.16.Final-redhat-1.jar:]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679) [jbossweb-7.0.16.Final-redhat-1.jar:]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.16.Final-redhat-1.jar:]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
13:53:41,978 DEBUG [org.apache.coyote.http11.Http11Processor] (http-/0.0.0.0:10001-1) Error preparing request Unsupported HTTP version "null"
13:53:44,830 DEBUG [org.apache.catalina.session.ManagerBase] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Start expire sessions StandardManager at 1423173224830 sessioncount 0
13:53:44,830 DEBUG [org.apache.catalina.session.ManagerBase] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) End expire sessions StandardManager processingTime 0 expired sessions: 0
13:53:54,911 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) PeriodicRecovery: background thread Status <== SCANNING
13:53:54,911 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) PeriodicRecovery: background thread scanning
13:53:54,911 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) Periodic recovery first pass at Thu, 5 Feb 2015 13:53:54
13:53:54,911 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) AtomicActionRecoveryModule first pass
13:53:54,911 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery) processing /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction transactions
13:53:54,911 DEBUG [com.arjuna.ats.arjuna] (Periodic Recovery)
So it looks like 505 status is returned because protocol version was not parsed at all.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4326) Enable JPA meterics, all metrics zero
by Tim Mickelson (JIRA)
[ https://issues.jboss.org/browse/WFLY-4326?page=com.atlassian.jira.plugin.... ]
Tim Mickelson commented on WFLY-4326:
-------------------------------------
As you asked I put a part of the trace below. Since I'm using JNDI to look up the EntityManagerFactory in Spring, it should be the EE that is deploying it.
16:28:21,493 INFO [org.jboss.as.jpa.parse] (MSC service thread 1-1) JBAS011401: Read persistence.xml for JPADB
16:28:21,494 TRACE [org.jboss.as.jpa.parse] (MSC service thread 1-1) PersistenceUnitMetadataImpl(version=1.0) [
name: JPADB
jtaDataSource: java:/youconnect
nonJtaDataSource: null
transactionType: JTA
provider: org.hibernate.ejb.HibernatePersistence
classes[
]
packages[
]
mappingFiles[
]
jarFiles[
]
validation-mode: AUTO
shared-cache-mode: UNSPECIFIED
properties[
hibernate.transaction.manager_lookup_class: org.hibernate.transaction.JBossTransactionManagerLookup
jboss.entity.manager.jndi.name: java:app/JPADB
hibernate.temp.use_jdbc_metadata_defaults: false
hibernate.dialect: org.hibernate.dialect.PostgreSQLDialect
hibernate.jdbc.use_streams_for_binary: true
hibernate.show_sql: false
jboss.entity.manager.factory.jndi.name: java:app/JPADBFactory
hibernate.format_sql: true
]]
16:28:21,849 TRACE [org.jboss.as.jpa.entityManagerBind] (MSC service thread 1-1) binding the transaction scoped entity manager to jndi name 'JPADB'
16:28:21,850 TRACE [org.jboss.as.jpa.entityManagerFactoryBind] (MSC service thread 1-1) binding the entity manager factory to jndi name 'JPADBFactory'
> 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
> Labels: jpa
>
> 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] (WFCORE-466) Improve output of patch info command
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-466?page=com.atlassian.jira.plugin... ]
Alexey Loubyansky reassigned WFCORE-466:
----------------------------------------
Assignee: Alexey Loubyansky (was: Emanuel Muckenhuber)
> Improve output of patch info command
> ------------------------------------
>
> Key: WFCORE-466
> URL: https://issues.jboss.org/browse/WFCORE-466
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Patching
> Affects Versions: 1.0.0.Alpha1
> Reporter: Martin Simka
> Assignee: Alexey Loubyansky
>
> With connected CLI output of {{patch info}} command is:
> {noformat}
> [standalone@localhost:9999 /] patch info
> {
> "outcome" : "success",
> "result" : {
> "cumulative-patch-id" : "jboss-eap-6.2.3.CP",
> "patches" : [],
> "version" : "6.2.3.GA",
> "addon" : null,
> "layer" : {"base" : {
> "cumulative-patch-id" : "layer-base-jboss-eap-6.2.3.CP",
> "patches" : []
> }}
> }
> }
> {noformat}
> Some users are confused by two elements cumulative-patch-id and they are not sure which id they should use e.g. with rollback command.
> Output should be somehow improved but I don't have any suggestion.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 5 months
[JBoss JIRA] (WFLY-4326) Enable JPA meterics, all metrics zero
by Tim Mickelson (JIRA)
[ https://issues.jboss.org/browse/WFLY-4326?page=com.atlassian.jira.plugin.... ]
Tim Mickelson commented on WFLY-4326:
-------------------------------------
Scott, I'm really sorry, now I see the metrics for JPA, maybe it was slow picking up? Only note, but I don't think it is important is that I only see the two first "bars", i.e. "Sessions closed" and "Transactions Successful". e.g "Sessions Closed" has the closed number 6, and the bar is filled up to the number 6 and thats cool, but e.g. "Execution Count" is 102, but the bar is totally white and the same for all other bars. I'm guessing that it is a bug, but probably a smaller issue?
Question (if its ok to ask) on JBoss 7.1.1 the "Query execution" "Max time" also shows the actual query, is this possible in Wildfly?
> 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
> Labels: jpa
>
> 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 Tim Mickelson (JIRA)
[ https://issues.jboss.org/browse/WFLY-4323?page=com.atlassian.jira.plugin.... ]
Tim Mickelson commented on WFLY-4323:
-------------------------------------
Thanks Tom, I created WFLY-4326 and put a link to this issue. I will be following closely how these two issues progress, but I'm sticking with Wildfly, because I need Websocket and these issues are not blockers, only very annoying.
> 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