0 Replies Latest reply on Aug 8, 2012 12:42 PM by ejroberts

    Servlet deployed in JBoss 7.1.1 causing an IllegalStateException: JBAS018053: No security context found

    ejroberts
    ejroberts Aug 8, 2012 12:42 PM

      I have deployed the Netty HTTP Tunnel Servlet and supporting config as prescribed by the HornetQ documentation to my standalone JBoss (7.1.1.Final) installation. The send and receive of messages works fine,

      but whenever the send of a message is issued, the following exception is thrown

       

      2012-08-08 16:12:00,147 ERROR [org.apache.catalina.connector.CoyoteAdapter](http-executor-threads - 1) An exception or error occurred in the container during the request processing: java.lang.IllegalStateException: JBAS018053: No security context found
    at org.jboss.as.web.security.SecurityActions$6.run(SecurityActions.java:136)
    at org.jboss.as.web.security.SecurityActions$6.run(SecurityActions.java:130)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.jboss.as.web.security.SecurityActions.popRunAsIdentity(SecurityActions.java:130)
    at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:155)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
    at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:518)
    at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
    at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:801)
    at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
    at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:821)
    at java.lang.Thread.run(Thread.java:662)
    at org.jboss.threads.JBossThread.run(JBossThread.java:122)

       

      The error appears to be coming from JBoss Web. The JMS communication actually succeeds.

       

      Other Servlets have been deployed to the JBoss server without such errors. What is it that determines the chain of valves for a given Servlet as it appears this chain is different ?

       

      I already asked on the HornetQ forum to see if this is specific to the way the JMS stuff is working, but after debugging the exception found that it is happening before the Servlet service method is called (https://community.jboss.org/message/752593#752593)