[JBoss JIRA] (RTGOV-536) Login does not work in EAP 4.3 for Kibana UI
by Jiri Pechanec (JIRA)
Jiri Pechanec created RTGOV-536:
-----------------------------------
Summary: Login does not work in EAP 4.3 for Kibana UI
Key: RTGOV-536
URL: https://issues.jboss.org/browse/RTGOV-536
Project: RTGov (Run Time Governance)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: User Interface
Reporter: Jiri Pechanec
Assignee: Gary Brown
Priority: Critical
When the RTGov is installed to EAP 4.3 it is not possible to log in into Kibana UI. The probalem is that web.xml is configured to use FORM-based auth using files
* login.html
* loginerror.html
but the aforementioned fles are nowhere to be found in the war file
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RTGOV-531) RTGov is not properly installed on EAP 6.3
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/RTGOV-531?page=com.atlassian.jira.plugin.... ]
Eric Wittmann closed RTGOV-531.
-------------------------------
> RTGov is not properly installed on EAP 6.3
> ------------------------------------------
>
> Key: RTGOV-531
> URL: https://issues.jboss.org/browse/RTGOV-531
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 2.0.0.Final
> Reporter: Jiri Pechanec
> Assignee: Eric Wittmann
> Priority: Blocker
>
> When a user installs the RTGov into EAP 6.3 it will modify standalone*.xml with elements that contain namespaces like
> {code:xml}
> <ns0:subsystem xmlns:ns0="urn:jboss:domain:overlord-configuration:1.0">
> <configurations xmlns="urn:jboss:domain:overlord-configuration:1.0">
> <ns2:configuration xmlns:ns2="urn:jboss:domain:overlord-configuration:1.0" xmlns="urn:jboss:domain:1.6" xmlns:ns1="urn:jboss:domain:overlord-configuration:1.0" name="overlord">
> <properties xmlns="urn:jboss:domain:overlord-configuration:1.0">
> <ns4:property xmlns:ns4="urn:jboss:domain:overlord-configuration:1.0" xmlns="urn:jboss:domain:1.6" xmlns:ns3="urn:jboss:domain:overlord-configuration:1.0" name="overlord.port" value="8080"/ >
> <ns5:property xmlns:ns5="urn:jboss:domain:overlord-configuration:1.0" xmlns="urn:jboss:domain:1.6" xmlns:ns3="urn:jboss:domain:overlord-configuration:1.0" name="overlord.baseUrl" value="htt p://localhost:${overlord.port}"/>
> {code}
> when the server is started it modifies the content of the config file into
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:overlord-configuration:1.0">
> <configurations>
> <configuration/>
> <configuration/>
> <configuration/>
> </configurations>
> {code}
> which prevents EAP from starting second time
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RTGOV-531) RTGov is not properly installed on EAP 6.3
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/RTGOV-531?page=com.atlassian.jira.plugin.... ]
Eric Wittmann resolved RTGOV-531.
---------------------------------
Resolution: Done
This was simply a bug in the subsystem parsing (marshaling) code. All fixed now, thanks for finding this [~jpechanec].
> RTGov is not properly installed on EAP 6.3
> ------------------------------------------
>
> Key: RTGOV-531
> URL: https://issues.jboss.org/browse/RTGOV-531
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 2.0.0.Final
> Reporter: Jiri Pechanec
> Assignee: Eric Wittmann
> Priority: Blocker
>
> When a user installs the RTGov into EAP 6.3 it will modify standalone*.xml with elements that contain namespaces like
> {code:xml}
> <ns0:subsystem xmlns:ns0="urn:jboss:domain:overlord-configuration:1.0">
> <configurations xmlns="urn:jboss:domain:overlord-configuration:1.0">
> <ns2:configuration xmlns:ns2="urn:jboss:domain:overlord-configuration:1.0" xmlns="urn:jboss:domain:1.6" xmlns:ns1="urn:jboss:domain:overlord-configuration:1.0" name="overlord">
> <properties xmlns="urn:jboss:domain:overlord-configuration:1.0">
> <ns4:property xmlns:ns4="urn:jboss:domain:overlord-configuration:1.0" xmlns="urn:jboss:domain:1.6" xmlns:ns3="urn:jboss:domain:overlord-configuration:1.0" name="overlord.port" value="8080"/ >
> <ns5:property xmlns:ns5="urn:jboss:domain:overlord-configuration:1.0" xmlns="urn:jboss:domain:1.6" xmlns:ns3="urn:jboss:domain:overlord-configuration:1.0" name="overlord.baseUrl" value="htt p://localhost:${overlord.port}"/>
> {code}
> when the server is started it modifies the content of the config file into
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:overlord-configuration:1.0">
> <configurations>
> <configuration/>
> <configuration/>
> <configuration/>
> </configurations>
> {code}
> which prevents EAP from starting second time
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RTGOV-531) RTGov is not properly installed on EAP 6.3
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/RTGOV-531?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated RTGOV-531:
--------------------------------
Git Pull Request: https://github.com/Governance/overlord-commons/pull/92
> RTGov is not properly installed on EAP 6.3
> ------------------------------------------
>
> Key: RTGOV-531
> URL: https://issues.jboss.org/browse/RTGOV-531
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 2.0.0.Final
> Reporter: Jiri Pechanec
> Assignee: Eric Wittmann
> Priority: Blocker
>
> When a user installs the RTGov into EAP 6.3 it will modify standalone*.xml with elements that contain namespaces like
> {code:xml}
> <ns0:subsystem xmlns:ns0="urn:jboss:domain:overlord-configuration:1.0">
> <configurations xmlns="urn:jboss:domain:overlord-configuration:1.0">
> <ns2:configuration xmlns:ns2="urn:jboss:domain:overlord-configuration:1.0" xmlns="urn:jboss:domain:1.6" xmlns:ns1="urn:jboss:domain:overlord-configuration:1.0" name="overlord">
> <properties xmlns="urn:jboss:domain:overlord-configuration:1.0">
> <ns4:property xmlns:ns4="urn:jboss:domain:overlord-configuration:1.0" xmlns="urn:jboss:domain:1.6" xmlns:ns3="urn:jboss:domain:overlord-configuration:1.0" name="overlord.port" value="8080"/ >
> <ns5:property xmlns:ns5="urn:jboss:domain:overlord-configuration:1.0" xmlns="urn:jboss:domain:1.6" xmlns:ns3="urn:jboss:domain:overlord-configuration:1.0" name="overlord.baseUrl" value="htt p://localhost:${overlord.port}"/>
> {code}
> when the server is started it modifies the content of the config file into
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:overlord-configuration:1.0">
> <configurations>
> <configuration/>
> <configuration/>
> <configuration/>
> </configurations>
> {code}
> which prevents EAP from starting second time
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RTGOV-531) RTGov is not properly installed on EAP 6.3
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/RTGOV-531?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on RTGOV-531:
-------------------------------------
I can reproduce this by making any change in the JBoss Admin UI, which presumably results in the standalone.xml file being marshaled to file. My guess is that the overlord extension(s) need to do *something* in response to this event. I will investigate.
> RTGov is not properly installed on EAP 6.3
> ------------------------------------------
>
> Key: RTGOV-531
> URL: https://issues.jboss.org/browse/RTGOV-531
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 2.0.0.Final
> Reporter: Jiri Pechanec
> Assignee: Eric Wittmann
> Priority: Blocker
>
> When a user installs the RTGov into EAP 6.3 it will modify standalone*.xml with elements that contain namespaces like
> {code:xml}
> <ns0:subsystem xmlns:ns0="urn:jboss:domain:overlord-configuration:1.0">
> <configurations xmlns="urn:jboss:domain:overlord-configuration:1.0">
> <ns2:configuration xmlns:ns2="urn:jboss:domain:overlord-configuration:1.0" xmlns="urn:jboss:domain:1.6" xmlns:ns1="urn:jboss:domain:overlord-configuration:1.0" name="overlord">
> <properties xmlns="urn:jboss:domain:overlord-configuration:1.0">
> <ns4:property xmlns:ns4="urn:jboss:domain:overlord-configuration:1.0" xmlns="urn:jboss:domain:1.6" xmlns:ns3="urn:jboss:domain:overlord-configuration:1.0" name="overlord.port" value="8080"/ >
> <ns5:property xmlns:ns5="urn:jboss:domain:overlord-configuration:1.0" xmlns="urn:jboss:domain:1.6" xmlns:ns3="urn:jboss:domain:overlord-configuration:1.0" name="overlord.baseUrl" value="htt p://localhost:${overlord.port}"/>
> {code}
> when the server is started it modifies the content of the config file into
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:overlord-configuration:1.0">
> <configurations>
> <configuration/>
> <configuration/>
> <configuration/>
> </configurations>
> {code}
> which prevents EAP from starting second time
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RTGOV-534) PicketLink linkage error when rtgov installed with switchyard in EAP 6.3
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-534?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-534:
-----------------------------
Git Pull Request: https://github.com/Governance/rtgov/pull/164
> PicketLink linkage error when rtgov installed with switchyard in EAP 6.3
> ------------------------------------------------------------------------
>
> Key: RTGOV-534
> URL: https://issues.jboss.org/browse/RTGOV-534
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Gary Brown
> Assignee: Gary Brown
> Priority: Blocker
> Fix For: 2.0.0.Final
>
>
> When rtgov is installed with swyd in EAP 6.3, the following exception occurs on startup:
> {noformat}
> 09:54:00,117 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/rtgov-ui]] (ServerService Thread Pool -- 76) JBWEB000284: Exception starting filter AuthenticationFilter: java.lang.LinkageError: loader constraint violation: when resolving method "org.picketlink.identity.federation.web.util.ConfigurationUtil.getConfiguration(Ljava/io/InputStreamLorg/picketlink/config/federation/PicketLinkType;" the class loader (instance of org/jboss/modules/ModuleClassLoader) of the current class, org/picketlink/identity/federation/web/filters/SamlSPFilter, and the class loader (instance of org/jboss/modules/ModuleClassLoader) for resolved class, org/picketlink/identity/federation/web/util/ConfigurationUtil, have different Class objects for the type org/picketlink/config/federation/PicketLinkType used in the signature
> at org.picketlink.identity.federation.web.filters.SamlSPFilter.init(SamlSPFilter.java:391) [overlord-commons-auth-2.0.3-SNAPSHOT.jar:2.0.3-SNAPSHOT]
> at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:416) [jbossweb-7.4.2.Final-redhat-1.jar:7.4.2.Final-redhat-1]
> at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3225) [jbossweb-7.4.2.Final-redhat-1.jar:7.4.2.Final-redhat-1]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3791) [jbossweb-7.4.2.Final-redhat-1.jar:7.4.2.Final-redhat-1]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:154) [jboss-as-web-7.4.0.Final-redhat-11.jar:7.4.0.Final-redhat-11]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:58) [jboss-as-web-7.4.0.Final-redhat-11.jar:7.4.0.Final-redhat-11]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:91) [jboss-as-web-7.4.0.Final-redhat-11.jar:7.4.0.Final-redhat-11]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_25]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_25]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_25]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RTGOV-534) PicketLink linkage error when rtgov installed with switchyard in EAP 6.3
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-534?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-534.
------------------------------
Resolution: Done
> PicketLink linkage error when rtgov installed with switchyard in EAP 6.3
> ------------------------------------------------------------------------
>
> Key: RTGOV-534
> URL: https://issues.jboss.org/browse/RTGOV-534
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Gary Brown
> Assignee: Gary Brown
> Priority: Blocker
> Fix For: 2.0.0.Final
>
>
> When rtgov is installed with swyd in EAP 6.3, the following exception occurs on startup:
> {noformat}
> 09:54:00,117 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/rtgov-ui]] (ServerService Thread Pool -- 76) JBWEB000284: Exception starting filter AuthenticationFilter: java.lang.LinkageError: loader constraint violation: when resolving method "org.picketlink.identity.federation.web.util.ConfigurationUtil.getConfiguration(Ljava/io/InputStreamLorg/picketlink/config/federation/PicketLinkType;" the class loader (instance of org/jboss/modules/ModuleClassLoader) of the current class, org/picketlink/identity/federation/web/filters/SamlSPFilter, and the class loader (instance of org/jboss/modules/ModuleClassLoader) for resolved class, org/picketlink/identity/federation/web/util/ConfigurationUtil, have different Class objects for the type org/picketlink/config/federation/PicketLinkType used in the signature
> at org.picketlink.identity.federation.web.filters.SamlSPFilter.init(SamlSPFilter.java:391) [overlord-commons-auth-2.0.3-SNAPSHOT.jar:2.0.3-SNAPSHOT]
> at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:416) [jbossweb-7.4.2.Final-redhat-1.jar:7.4.2.Final-redhat-1]
> at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3225) [jbossweb-7.4.2.Final-redhat-1.jar:7.4.2.Final-redhat-1]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3791) [jbossweb-7.4.2.Final-redhat-1.jar:7.4.2.Final-redhat-1]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:154) [jboss-as-web-7.4.0.Final-redhat-11.jar:7.4.0.Final-redhat-11]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:58) [jboss-as-web-7.4.0.Final-redhat-11.jar:7.4.0.Final-redhat-11]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:91) [jboss-as-web-7.4.0.Final-redhat-11.jar:7.4.0.Final-redhat-11]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_25]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_25]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_25]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RTGOV-535) SLA monitor integration test failing
by Gary Brown (JIRA)
Gary Brown created RTGOV-535:
--------------------------------
Summary: SLA monitor integration test failing
Key: RTGOV-535
URL: https://issues.jboss.org/browse/RTGOV-535
Project: RTGov (Run Time Governance)
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.Final
Test indicates that it receives 6 situations but expecting 3.
{noformat}
org.overlord.rtgov.tests.platforms.jbossas.slamonitor.JBossASSLAMonitorTest.testActivityEventsProcessed: java.lang.AssertionError: Expecting 3 (sla situations) processed events, but got: 6
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RTGOV-531) RTGov is not properly installed on EAP 6.3
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/RTGOV-531?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated RTGOV-531:
--------------------------------
Issue Type: Bug (was: Feature Request)
> RTGov is not properly installed on EAP 6.3
> ------------------------------------------
>
> Key: RTGOV-531
> URL: https://issues.jboss.org/browse/RTGOV-531
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 2.0.0.Final
> Reporter: Jiri Pechanec
> Assignee: Eric Wittmann
> Priority: Blocker
>
> When a user installs the RTGov into EAP 6.3 it will modify standalone*.xml with elements that contain namespaces like
> {code:xml}
> <ns0:subsystem xmlns:ns0="urn:jboss:domain:overlord-configuration:1.0">
> <configurations xmlns="urn:jboss:domain:overlord-configuration:1.0">
> <ns2:configuration xmlns:ns2="urn:jboss:domain:overlord-configuration:1.0" xmlns="urn:jboss:domain:1.6" xmlns:ns1="urn:jboss:domain:overlord-configuration:1.0" name="overlord">
> <properties xmlns="urn:jboss:domain:overlord-configuration:1.0">
> <ns4:property xmlns:ns4="urn:jboss:domain:overlord-configuration:1.0" xmlns="urn:jboss:domain:1.6" xmlns:ns3="urn:jboss:domain:overlord-configuration:1.0" name="overlord.port" value="8080"/ >
> <ns5:property xmlns:ns5="urn:jboss:domain:overlord-configuration:1.0" xmlns="urn:jboss:domain:1.6" xmlns:ns3="urn:jboss:domain:overlord-configuration:1.0" name="overlord.baseUrl" value="htt p://localhost:${overlord.port}"/>
> {code}
> when the server is started it modifies the content of the config file into
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:overlord-configuration:1.0">
> <configurations>
> <configuration/>
> <configuration/>
> <configuration/>
> </configurations>
> {code}
> which prevents EAP from starting second time
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RTGOV-534) PicketLink linkage error when rtgov installed with switchyard in EAP 6.3
by Gary Brown (JIRA)
Gary Brown created RTGOV-534:
--------------------------------
Summary: PicketLink linkage error when rtgov installed with switchyard in EAP 6.3
Key: RTGOV-534
URL: https://issues.jboss.org/browse/RTGOV-534
Project: RTGov (Run Time Governance)
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Gary Brown
Assignee: Gary Brown
Priority: Blocker
Fix For: 2.0.0.Final
When rtgov is installed with swyd in EAP 6.3, the following exception occurs on startup:
{noformat}
09:54:00,117 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/rtgov-ui]] (ServerService Thread Pool -- 76) JBWEB000284: Exception starting filter AuthenticationFilter: java.lang.LinkageError: loader constraint violation: when resolving method "org.picketlink.identity.federation.web.util.ConfigurationUtil.getConfiguration(Ljava/io/InputStreamLorg/picketlink/config/federation/PicketLinkType;" the class loader (instance of org/jboss/modules/ModuleClassLoader) of the current class, org/picketlink/identity/federation/web/filters/SamlSPFilter, and the class loader (instance of org/jboss/modules/ModuleClassLoader) for resolved class, org/picketlink/identity/federation/web/util/ConfigurationUtil, have different Class objects for the type org/picketlink/config/federation/PicketLinkType used in the signature
at org.picketlink.identity.federation.web.filters.SamlSPFilter.init(SamlSPFilter.java:391) [overlord-commons-auth-2.0.3-SNAPSHOT.jar:2.0.3-SNAPSHOT]
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:416) [jbossweb-7.4.2.Final-redhat-1.jar:7.4.2.Final-redhat-1]
at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3225) [jbossweb-7.4.2.Final-redhat-1.jar:7.4.2.Final-redhat-1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3791) [jbossweb-7.4.2.Final-redhat-1.jar:7.4.2.Final-redhat-1]
at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:154) [jboss-as-web-7.4.0.Final-redhat-11.jar:7.4.0.Final-redhat-11]
at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:58) [jboss-as-web-7.4.0.Final-redhat-11.jar:7.4.0.Final-redhat-11]
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:91) [jboss-as-web-7.4.0.Final-redhat-11.jar:7.4.0.Final-redhat-11]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_25]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_25]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_25]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months