0 Replies Latest reply on Oct 3, 2011 2:40 AM by Bobby Harsono

    Jboss 6.0.0 SLF4J Security exception when deploying

    Bobby Harsono Newbie

      I had to deploy applications at work and i tried to deploy a file called "ReportService.WAR", then i deploy it using Jboss 6.0.0 and got this error

       

      Deployment "vfs:///apps/jboss/server/default/deploy/ReportServices.war" is in error due to the following reason(s): java.lang.SecurityException: class "org.apache.commons.logging.impl.SLF4JLog"'s signer information does not match signer 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.Final]
          at org
      .jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.checkComplete(ProfileControllerContext.java: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(AbstractTwoPhaseModificationAction.java:74) [:0.2.2]
          at org
      .jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.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_10]
          at java
      .util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_10]
          at java
      .util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_10]
          at java
      .util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_10]
          at java
      .util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) [:1.6.0_10]
          at java
      .util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) [:1.6.0_10]
          at java
      .util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_10]
          at java
      .util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_10]
          at java
      .lang.Thread.run(Thread.java:619) [:1.6.0_10]

       

       

       

      Now, i didn't do any coding activity so i didn't know anything inside the code..but i do check the file and find if it used slf4j 1.6.0 while in jboss lib used sl4j 1.5.11, assuming this was the key problem i tried replace the jar in lib with 1.6.0 and ended unsuccess..anybody know what is the problem and how to fix it?

       

      Thanks