[
https://issues.jboss.org/browse/AS7-2416?page=com.atlassian.jira.plugin.s...
]
Rostislav Svoboda commented on AS7-2416:
----------------------------------------
I met the same problem with domain, just running domain.sh without any apps deployment.
{code}
[Server:server-two] 16:56:22,637 INFO [org.jboss.as.naming] (Controller Boot Thread)
JBAS011800: Activating Naming Subsystem
[Server:server-two] 16:56:22,685 INFO [org.jboss.as.naming] (MSC service thread 1-4)
JBAS011802: Starting Naming Service
[Server:server-two] 16:56:22,859 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service
thread 1-3) Starting remote JMX connector
[Server:server-two] 16:56:23,035 WARN [org.jboss.modules] (MSC service thread 1-1) Failed
to define class org.jboss.jca.core.spi.transaction.xa.XATerminator in Module
"org.jboss.ironjacamar.api:main" from local module loader @9c0ec97 (roots:
/home/rsvoboda/TESTING/6.0.0.DR5/jboss-eap-6.0.0.Alpha2/modules):
java.lang.SecurityException: class
"org.jboss.jca.core.spi.transaction.xa.XATerminator"'s signer information
does not match signer information of other classes in the same package
[Server:server-two] at java.lang.ClassLoader.checkCerts(ClassLoader.java:807)
[:1.6.0_22]
[Server:server-two] at java.lang.ClassLoader.preDefineClass(ClassLoader.java:488)
[:1.6.0_22]
[Server:server-two] at java.lang.ClassLoader.defineClassCond(ClassLoader.java:626)
[:1.6.0_22]
[Server:server-two] at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
[:1.6.0_22]
[Server:server-two] at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) [:1.6.0_22]
[Server:server-two] at
org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:395)
[jboss-modules.jar:1.0.3.GA]
[Server:server-two] at
org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261)
[jboss-modules.jar:1.0.3.GA]
[Server:server-two] at
org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76)
[jboss-modules.jar:1.0.3.GA]
[Server:server-two] at org.jboss.modules.Module.loadModuleClass(Module.java:590)
[jboss-modules.jar:1.0.3.GA]
[Server:server-two] at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:183)
[jboss-modules.jar:1.0.3.GA]
[Server:server-two] at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:361)
[jboss-modules.jar:1.0.3.GA]
[Server:server-two] at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:333)
[jboss-modules.jar:1.0.3.GA]
[Server:server-two] at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:310)
[jboss-modules.jar:1.0.3.GA]
[Server:server-two] at
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:103)
[jboss-modules.jar:1.0.3.GA]
[Server:server-two] at
org.jboss.as.connector.transactionintegration.TransactionIntegrationService.start(TransactionIntegrationService.java:73)
[jboss-as-connector-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
[Server:server-two] at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[jboss-msc-1.0.1.GA-redhat-0-todo.jar:1.0.1.GA]
[Server:server-two] at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[jboss-msc-1.0.1.GA-redhat-0-todo.jar:1.0.1.GA]
[Server:server-two] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_22]
[Server:server-two] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_22]
[Server:server-two] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]
[Server:server-two]
[Server:server-two] 16:56:23,037 ERROR [org.jboss.msc.service.fail] (MSC service thread
1-1) MSC00001: Failed to start service jboss.connector.transactionintegration:
org.jboss.msc.service.StartException in service jboss.connector.transactionintegration:
Failed to start service
[Server:server-two] at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780)
[jboss-msc-1.0.1.GA-redhat-0-todo.jar:1.0.1.GA]
[Server:server-two] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_22]
[Server:server-two] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_22]
[Server:server-two] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]
[Server:server-two] Caused by: java.lang.SecurityException: class
"org.jboss.jca.core.spi.transaction.xa.XATerminator"'s signer information
does not match signer information of other classes in the same package
...
{code}
Problem when deploying multiple jars which depend on a signed module
--------------------------------------------------------------------
Key: AS7-2416
URL:
https://issues.jboss.org/browse/AS7-2416
Project: Application Server 7
Issue Type: Bug
Components: Deployment, Modules
Affects Versions: 7.1.0.Alpha1
Reporter: Paul Gier
Assignee: Thomas Diesler
Fix For: 7.1.0.CR1
Attachments: deployment-error.txt, deployments.zip,
jbossws-cxf-server-4.0.0.Beta6.jar
There seems to be a problem with parallel loading a signed module when multiple
deployments depend on the module.
The error message says that multiple jars are loading the same package with different
signatures, even though the package is only in one jar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira