[overlord-issues] [JBoss JIRA] (RTGOV-534) PicketLink linkage error when rtgov installed with switchyard in EAP 6.3
Gary Brown (JIRA)
issues at jboss.org
Wed Jul 23 09:37:30 EDT 2014
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)
More information about the overlord-issues
mailing list