-
1. Re: Problem: SecurityAssociationValve Failed to determine s
starksm64 Aug 3, 2005 11:46 AM (in response to tu_gupta)Your not using a final release of jboss I would assume.
-
2. Re: Problem: SecurityAssociationValve Failed to determine s
tu_gupta Aug 3, 2005 6:53 PM (in response to tu_gupta)hi,
Thanx for such a quick response.
I hava tried deployment on JBoss 4.0.0 and JBoss 4.0.1sp1. Both are giving me the same error.
Regards
Tushar Gupta -
3. Re: Problem: SecurityAssociationValve Failed to determine s
andrepgs Mar 17, 2006 2:06 PM (in response to tu_gupta)I have the same problem ... but I use only Tomcat 5.5.9 to publish my projects.
You found a solution to this question?
tks,
André -
4. Re: Problem: SecurityAssociationValve Failed to determine s
andrepgs Mar 20, 2006 8:06 PM (in response to tu_gupta)I found the solution at:
http://wiki.apache.org/tomcat/Tomcat/Howto
in section:
"How can I access members of a custom Realm or Principal?"
[]'s
Andre Pastore -
5. Re: Problem: SecurityAssociationValve Failed to determine s
whitingjr Jan 4, 2012 1:38 PM (in response to starksm64)Hi Scott,
This error is still happening in AS7.1 Beta1 and will be present in the Final version coming out soon.
The reason I raise this is because the valve is throwing an NullPointerException. That occurs for every request which does not have a principle associated with the session. The NPE is being caugth by the catch block and the message is being logged at debug level.
There are two things I raise as a concern.
a) The affect to performance. The situation is the server throws an exception regardless of the application code for all requests in the given situation.
b) The second is the debug message is in my (humble) opinion using the wrong logging method. Shouldn't the valve rather be logging the message using the debug method rather than debugf ? *
* debugf being the method to use when passing the message format to the logger object.
Do you think these two issues are worthy of a JIRA and a patch ?
Regards,
Jeremy
-
7. Re: Problem: SecurityAssociationValve Failed to determine s
whitingjr Jan 5, 2012 5:01 AM (in response to jfclere)Hi Jean-Frederic,
Thank you for the suggestion but it isn't necessary relevant to the code that is being discussed. Though I did not provide enough information in my previous post. Additional details from me will explain why.
The code being discussed in this thread is not application code created by users. It is JBoss AS system code. The Valve that is throwing the NPE is
org.jboss.as.web.security.SecurityContextAssociationValve
on line 129
The application I am deploying and testing has no requirements for manipulating the session or the security principle. The resurection of this thread is to highlight the system code could do with patching to prevent it throwing an exception on every web request.
Regards,
Jeremy
-
8. Re: Problem: SecurityAssociationValve Failed to determine s
whitingjr Jan 5, 2012 4:47 AM (in response to jfclere)Hello Jean-Frederic,
The information you provided will help me with creating a patch. Though the objective of the patch will be to detect null pointers rather than change the behaviour of the valve.
Many thanks,
Jeremy
-
9. Re: Problem: SecurityAssociationValve Failed to determine s
jfclere Jan 6, 2012 4:05 AM (in response to whitingjr)Please create a JIRA that looks like a bug.
-
10. Re: Problem: SecurityAssociationValve Failed to determine s
whitingjr Jan 6, 2012 5:10 AM (in response to jfclere)Hi,
Ok I will create a couple of JIRAs, one for the logging method and the second for null pointer handling.
Regards,
Jeremy
-
11. Re: Problem: SecurityAssociationValve Failed to determine s
whitingjr Jan 12, 2012 6:01 AM (in response to whitingjr)