0 Replies Latest reply on Dec 7, 2007 5:18 PM by jdsignature

    class cast exception

    jdsignature

      Here is the issues:
      the problem occurred from the customized login module to authenticate the user:

      3:10:54,668 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing
      java.lang.ClassCastException: org.jboss.security.plugins.JaasSecurityManager
      at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.java:488)
      at com.choicepoint.cpgs.shields.ShieldFormAuthenticator.authenticate(ShieldFormAuthenticator.java:162)
      at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:416)
      at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
      at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
      at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
      at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
      at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
      at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
      at java.lang.Thread.run(Thread.java:595)


      Solutions to have JBoss fully JAVA EE Compliance: the JBoss container configurations must be modified as followings:
      jboss-services.xml



      <!-- The call by value mode. true if all lookups are unmarshalled using

      the caller's TCL, false if in VM lookups return the value by reference.

      -->

      true

      ...



      deploy/ear-deployer.xml



      <!-- EAR deployer, remove if you are not using ear deployments -->



      <!-- A flag indicating if ear deployments should have their own scoped

      class loader to isolate their classes from other deployments.

      -->

      true

      <!-- A flag indicating if the ear components should have in VM call

      optimization disabled.

      -->

      true





      deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xml



      <!-- Get the flag indicating if the normal Java2 parent first class

      loading model should be used over the servlet 2.3 web container first

      model.

      -->

      true

      true

      <!-- A flag indicating if the JBoss Loader should be used. This loader

      uses a unified class loader as the class loader rather than the tomcat

      specific class loader.

      -->

      true


      Can anybody provide any feedbacks on this topic, thanks