[JBoss JIRA] (RTGOV-329) Consider refactoring/cleanup of ActivtyServerLogger
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-329?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-329:
-----------------------------
Fix Version/s: (was: 2.1.0.Final)
> Consider refactoring/cleanup of ActivtyServerLogger
> ---------------------------------------------------
>
> Key: RTGOV-329
> URL: https://issues.jboss.org/browse/RTGOV-329
> Project: RTGov (Run Time Governance)
> Issue Type: Quality Risk
> Components: Activity Collector
> Affects Versions: 1.0.0.Final
> Reporter: Jiri Pechanec
> Assignee: Gary Brown
> Attachments: Performance.java
>
>
> 1) I consider the code to be overcomplicated - are we really getting any performance boost with reusing the ArrayList of events? I found on the web that clear() might be even slower than new allocation
> 2) There is unsynced access to fields _sequenceNumber and _failuresSinceLastSuccess
> 3) I am not sure if it is wise to mix synchronization on Java level - _timer in BatchedActivityUnitLogger - and Java EE level - method synchornization on @Singleton
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 9 months
[JBoss JIRA] (RTGOV-329) Consider refactoring/cleanup of ActivtyServerLogger
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-329?page=com.atlassian.jira.plugin.... ]
Gary Brown reopened RTGOV-329:
------------------------------
> Consider refactoring/cleanup of ActivtyServerLogger
> ---------------------------------------------------
>
> Key: RTGOV-329
> URL: https://issues.jboss.org/browse/RTGOV-329
> Project: RTGov (Run Time Governance)
> Issue Type: Quality Risk
> Components: Activity Collector
> Affects Versions: 1.0.0.Final
> Reporter: Jiri Pechanec
> Assignee: Gary Brown
> Fix For: 2.1.0.Final
>
> Attachments: Performance.java
>
>
> 1) I consider the code to be overcomplicated - are we really getting any performance boost with reusing the ArrayList of events? I found on the web that clear() might be even slower than new allocation
> 2) There is unsynced access to fields _sequenceNumber and _failuresSinceLastSuccess
> 3) I am not sure if it is wise to mix synchronization on Java level - _timer in BatchedActivityUnitLogger - and Java EE level - method synchornization on @Singleton
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 9 months
[JBoss JIRA] (RTGOV-585) Fuse: Sending {"amount":400, "customer":"Fred"} results in Unrecognized field "amount"
by Andrej Vano (JIRA)
Andrej Vano created RTGOV-585:
---------------------------------
Summary: Fuse: Sending {"amount":400,"customer":"Fred"} results in Unrecognized field "amount"
Key: RTGOV-585
URL: https://issues.jboss.org/browse/RTGOV-585
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Andrej Vano
Assignee: Gary Brown
Fix For: 2.0.0.Final
Based on the documentation I'm sending the request {"amount":400,"customer":"Fred"} but the response is:
Unrecognized field "amount" (Class org.overlord.rtgov.quickstarts.demos.ordermgmt.model.Order), not marked as ignorable
at [Source: java.io.ByteArrayInputStream@822005f; line: 1, column: 14] (through reference chain: org.overlord.rtgov.quickstarts.demos.ordermgmt.model.Order["amount"])
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 9 months
[JBoss JIRA] (RTGOV-564) Discriminate between Service Responsetime and component Responsetime in Kibana dashboard
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-564?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-564.
------------------------------
Resolution: Done
Thanks for the example dashboard Ivan.
After further consideration I realised that basing the decision on the contents of the gateway field is only relevant for switchyard (and other services that report this information) however other systems may not have a gateway but still be 'public'.
Therefore implemented a new boolean field on the RPCActivityType called 'internal' to indicate this fact. I've updated the default dashboard to use this information - and the filter can be disabled to show all services.
> Discriminate between Service Responsetime and component Responsetime in Kibana dashboard
> ------------------------------------------------------------------------------------------
>
> Key: RTGOV-564
> URL: https://issues.jboss.org/browse/RTGOV-564
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Components: User Interface
> Affects Versions: 2.0.0.Final
> Reporter: ivan mckinley
> Assignee: Gary Brown
> Fix For: 2.0.0.Final
>
> Attachments: RTGOV Gateways-1411930853701.json
>
>
> Kibana ui
> The current kibana dashboard shows the response times for all component response times. It was observed that this is not optimal and clear to end-users. Endusers would initially be most interested in the response times on the promoted interface “soap binding” for example. Independent to the switchyard world, this would mean only displaying the response time for the entire serviceTX (and ignoring the components response times) or as its know the activityUnit
> Proposal,
> that the landing kibana dashboard shows the response times for the entire serviceTX in a dedicated table and the response times for the components in another.
> View the response of components could be another widget. i would not suggest another dashboard as this would mean users could not drill down into a service’s components
> Example, in the default dashboard, the table LIST OF SERVICES TABLE.
> This table displays the service tx response time but also the component response time. to the end user this not exactly clear
> {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService
> {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService/FundsService
> {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService/InventoryService
> {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService/LogisticsService
> howto,
> Perhaps a flag will be required on the response time object to discriminate component response time and service tx response times
>
>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 9 months
[JBoss JIRA] (RTGOV-564) Discriminate between Service Responsetime and component Responsetime in Kibana dashboard
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-564?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-564:
-----------------------------
Git Pull Request: https://github.com/Governance/rtgov/pull/213
> Discriminate between Service Responsetime and component Responsetime in Kibana dashboard
> ------------------------------------------------------------------------------------------
>
> Key: RTGOV-564
> URL: https://issues.jboss.org/browse/RTGOV-564
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Components: User Interface
> Affects Versions: 2.0.0.Final
> Reporter: ivan mckinley
> Assignee: Gary Brown
> Fix For: 2.0.0.Final
>
> Attachments: RTGOV Gateways-1411930853701.json
>
>
> Kibana ui
> The current kibana dashboard shows the response times for all component response times. It was observed that this is not optimal and clear to end-users. Endusers would initially be most interested in the response times on the promoted interface “soap binding” for example. Independent to the switchyard world, this would mean only displaying the response time for the entire serviceTX (and ignoring the components response times) or as its know the activityUnit
> Proposal,
> that the landing kibana dashboard shows the response times for the entire serviceTX in a dedicated table and the response times for the components in another.
> View the response of components could be another widget. i would not suggest another dashboard as this would mean users could not drill down into a service’s components
> Example, in the default dashboard, the table LIST OF SERVICES TABLE.
> This table displays the service tx response time but also the component response time. to the end user this not exactly clear
> {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService
> {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService/FundsService
> {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService/InventoryService
> {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService/LogisticsService
> howto,
> Perhaps a flag will be required on the response time object to discriminate component response time and service tx response times
>
>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 9 months
[JBoss JIRA] (SRAMP-577) s-ramp-demos-webapp-multimodule-web WAR fails to deploy in EAP
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-577?page=com.atlassian.jira.plugin.... ]
Brett Meyer resolved SRAMP-577.
-------------------------------
Resolution: Done
> s-ramp-demos-webapp-multimodule-web WAR fails to deploy in EAP
> --------------------------------------------------------------
>
> Key: SRAMP-577
> URL: https://issues.jboss.org/browse/SRAMP-577
> Project: S-RAMP
> Issue Type: Bug
> Reporter: Eric Wittmann
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> {code}
> 10:00:17,293 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war" (runtime-name: "s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war")
> 10:00:17,576 INFO [org.jboss.web] (ServerService Thread Pool -- 145) JBAS018210: Register web context: /s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT
> 10:00:17,617 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT]] (ServerService Thread Pool -- 145) JBWEB000287: Exception sending context initialized event to listener instance of class org.jboss.resteasy.plugins.server.servlet.ResteasyBootstr
> ap: java.lang.RuntimeException: Unable to find a public constructor for class org.jboss.resteasy.core.AsynchronousDispatcher
> at org.jboss.resteasy.plugins.server.resourcefactory.POJOResourceFactory.registered(POJOResourceFactory.java:35) [resteasy-jaxrs-2.3.8.Final-redhat-3.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:120) [resteasy-jaxrs-2.3.8.Final-redhat-3.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:106) [resteasy-jaxrs-2.3.8.Final-redhat-3.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:83) [resteasy-jaxrs-2.3.8.Final-redhat-3.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addPerRequestResource(ResourceMethodRegistry.java:72) [resteasy-jaxrs-2.3.8.Final-redhat-3.jar:]
> at org.jboss.resteasy.spi.ResteasyDeployment.registration(ResteasyDeployment.java:375) [resteasy-jaxrs-2.3.8.Final-redhat-3.jar:]
> at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:233) [resteasy-jaxrs-2.3.8.Final-redhat-3.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap.contextInitialized(ResteasyBootstrap.java:28) [resteasy-jaxrs-2.3.8.Final-redhat-3.jar:]
> at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:161) [jboss-as-web-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:59) [jboss-as-web-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:94) [jboss-as-web-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_40]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_40]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> 10:00:17,634 ERROR [org.apache.catalina.core] (ServerService Thread Pool -- 145) JBWEB001103: Error detected during context /s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT start, will stop it
> 10:00:17,668 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 145) MSC000001: Failed to start service jboss.web.deployment.default-host."/s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT": org.jboss.msc.service.StartException in service jboss.web.deployment.default-host."/s-ramp-demos-webapp-multimodu
> le-web-0.6.0-SNAPSHOT": org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:97)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_40]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_40]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:166)
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:59)
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:94)
> ... 6 more
> 10:00:17,687 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.web.deployment.default-host.\"/s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT\"" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host.\"/s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT\": org.jboss.msc.service.StartException in anonymous
> service: JBAS018040: Failed to start context
> Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context"}}
> 10:00:17,727 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war (runtime-name: s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war) in 39ms
> 10:00:17,731 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".component."org.apache.catalina.servlets.DefaultServlet".START (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".component."org.apache.jasper.servlet.JspServlet".START (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".component."org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher".START (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".component."org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap".START (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.web.deployment.default-host."/s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT" (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.web.deployment.default-host."/s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT".realm (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> JBAS014777: Services which failed to start: service jboss.web.deployment.default-host."/s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 9 months
[JBoss JIRA] (SRAMP-576) Demo not working: s-ramp-demos-mvn-integration
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-576?page=com.atlassian.jira.plugin.... ]
Brett Meyer resolved SRAMP-576.
-------------------------------
Resolution: Done
> Demo not working: s-ramp-demos-mvn-integration
> ----------------------------------------------
>
> Key: SRAMP-576
> URL: https://issues.jboss.org/browse/SRAMP-576
> Project: S-RAMP
> Issue Type: Feature Request
> Reporter: Eric Wittmann
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> Testing for the 0.6.0 community release. The s-ramp-demos-mvn-integration demo appears to no longer work. The first half of it works fine (adding the artifact to s-ramp via maven). However the second half fails with:
> {code}
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building S-RAMP Demos: Maven Integration - App 0.6.0-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> Downloading: http://repository.jboss.org/nexus/content/groups/developer/org/overlord/s...
> Downloading: http://maven.repository.redhat.com/techpreview/all/org/overlord/sramp/dem...
> Downloading: http://repo.fusesource.com/nexus/content/groups/public/org/overlord/sramp...
> Downloading: sramp://localhost:8080/s-ramp-server/org/overlord/sramp/demos/s-ramp-demos-mvn-integration-artifacts/0.6.0-SNAPSHOT/maven-metadata.xml
> Downloaded: sramp://localhost:8080/s-ramp-server/org/overlord/sramp/demos/s-ramp-demos-mvn-integration-artifacts/0.6.0-SNAPSHOT/maven-metadata.xml (2 KB at 0.7KB/sec)
> Downloading: sramp://localhost:8080/s-ramp-server/org/overlord/sramp/demos/s-ramp-demos-mvn-integration-artifacts/0.6.0-SNAPSHOT/s-ramp-demos-mvn-integration-artifacts-0.6.0-SNAPSHOT.pom
> [WARNING] The POM for org.overlord.sramp.demos:s-ramp-demos-mvn-integration-artifacts:jar:0.6.0-SNAPSHOT is missing, no dependency information available
> Downloading: sramp://localhost:8080/s-ramp-server/org/overlord/sramp/demos/s-ramp-demos-mvn-integration-artifacts/0.6.0-SNAPSHOT/s-ramp-demos-mvn-integration-artifacts-0.6.0-SNAPSHOT.jar
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 9 months
[JBoss JIRA] (SRAMP-577) s-ramp-demos-webapp-multimodule-web WAR fails to deploy in EAP
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-577?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-577:
-----------------------------------
That's what I get for using RE. I'll probably just convert this to plain-old REST
> s-ramp-demos-webapp-multimodule-web WAR fails to deploy in EAP
> --------------------------------------------------------------
>
> Key: SRAMP-577
> URL: https://issues.jboss.org/browse/SRAMP-577
> Project: S-RAMP
> Issue Type: Bug
> Reporter: Eric Wittmann
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> {code}
> 10:00:17,293 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war" (runtime-name: "s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war")
> 10:00:17,576 INFO [org.jboss.web] (ServerService Thread Pool -- 145) JBAS018210: Register web context: /s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT
> 10:00:17,617 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT]] (ServerService Thread Pool -- 145) JBWEB000287: Exception sending context initialized event to listener instance of class org.jboss.resteasy.plugins.server.servlet.ResteasyBootstr
> ap: java.lang.RuntimeException: Unable to find a public constructor for class org.jboss.resteasy.core.AsynchronousDispatcher
> at org.jboss.resteasy.plugins.server.resourcefactory.POJOResourceFactory.registered(POJOResourceFactory.java:35) [resteasy-jaxrs-2.3.8.Final-redhat-3.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:120) [resteasy-jaxrs-2.3.8.Final-redhat-3.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:106) [resteasy-jaxrs-2.3.8.Final-redhat-3.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:83) [resteasy-jaxrs-2.3.8.Final-redhat-3.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addPerRequestResource(ResourceMethodRegistry.java:72) [resteasy-jaxrs-2.3.8.Final-redhat-3.jar:]
> at org.jboss.resteasy.spi.ResteasyDeployment.registration(ResteasyDeployment.java:375) [resteasy-jaxrs-2.3.8.Final-redhat-3.jar:]
> at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:233) [resteasy-jaxrs-2.3.8.Final-redhat-3.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap.contextInitialized(ResteasyBootstrap.java:28) [resteasy-jaxrs-2.3.8.Final-redhat-3.jar:]
> at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:161) [jboss-as-web-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:59) [jboss-as-web-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:94) [jboss-as-web-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_40]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_40]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> 10:00:17,634 ERROR [org.apache.catalina.core] (ServerService Thread Pool -- 145) JBWEB001103: Error detected during context /s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT start, will stop it
> 10:00:17,668 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 145) MSC000001: Failed to start service jboss.web.deployment.default-host."/s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT": org.jboss.msc.service.StartException in service jboss.web.deployment.default-host."/s-ramp-demos-webapp-multimodu
> le-web-0.6.0-SNAPSHOT": org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:97)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_40]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_40]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:166)
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:59)
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:94)
> ... 6 more
> 10:00:17,687 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.web.deployment.default-host.\"/s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT\"" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host.\"/s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT\": org.jboss.msc.service.StartException in anonymous
> service: JBAS018040: Failed to start context
> Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context"}}
> 10:00:17,727 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war (runtime-name: s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war) in 39ms
> 10:00:17,731 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".component."org.apache.catalina.servlets.DefaultServlet".START (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".component."org.apache.jasper.servlet.JspServlet".START (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".component."org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher".START (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".component."org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap".START (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.web.deployment.default-host."/s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT" (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> service jboss.web.deployment.default-host."/s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT".realm (missing) dependents: [service jboss.deployment.unit."s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT.war".deploymentCompleteService]
> JBAS014777: Services which failed to start: service jboss.web.deployment.default-host."/s-ramp-demos-webapp-multimodule-web-0.6.0-SNAPSHOT"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 9 months