0 Replies Latest reply on Apr 26, 2011 7:06 AM by sjunejo

    jBoss 6 signer information mismatched

    sjunejo

      Hi Guys,

       

      I come across another problem while deploying my web application on jBoss 6 Final release. When I am deploying my 'war' it throws many exception and in the end it prints out following exception;

       

      DEPLOYMENTS IN ERROR:

        Deployment "vfs:///C:/jboss-6.0.0.Final/server/default/deploy/BrowserWeb.war" is in error due to the following reason(s): java.l

      ang.SecurityException: class "org.apache.xalan.xsltc.dom.DOMImpl$TypedNamespaceIterator"'s signer information does not match signe

      r information of other classes in the same package

       

       

              at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1370) [:2.2.0.GA]

              at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1316) [:2.2.0.GA]

              at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:968) [:2.2.0.GA]

              at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:82) [:6.0.0.F

      inal]

              at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.checkComplete(ProfileControllerContext.ja

      va:138) [:0.2.2]

              at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:246) [:0.2.2]

              at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.2.2]

              at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57) [:0.2.2]

              at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAct

      ion.java:74) [:0.2.2]

              at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationActi

      on.java:95) [:0.2.2]

              at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2]

              at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2]

       

       

              at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2]

              at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2]

              at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.2.2]

              at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2]

              at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2]

              at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_18]

              at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_18]

              at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_18]

              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:

      1.6.0_18]

              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)

      [:1.6.0_18]

              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) [:1.6.0_

      18]

              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_18]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_18]

              at java.lang.Thread.run(Thread.java:619) [:1.6.0_18]

       

       

      10:59:10,007 INFO  [service] Restored bootstrap log handlers

       

      Does any one else come across this issue? Let me know if you need more information.

       

      Thanks

       

      --

       

      SJunejo