[jboss-jira] [JBoss JIRA] Reopened: (JBAS-8921) JBoss 6.0.0 Neo - No valid security context for the caller identity
Jason Greene (JIRA)
jira-events at lists.jboss.org
Thu Apr 21 14:27:00 EDT 2011
[ https://issues.jboss.org/browse/JBAS-8921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Greene reopened JBAS-8921:
--------------------------------
Due to feedback from the community, I have split the AS7 and AS6 projects and reopened all unscheduled AS6 issues that are a year or less old. This will make it easier community members to find and work on them.
Future releases beyond 6.1 can be done provided a community member steps up to coordinate them.
> JBoss 6.0.0 Neo - No valid security context for the caller identity
> -------------------------------------------------------------------
>
> Key: JBAS-8921
> URL: https://issues.jboss.org/browse/JBAS-8921
> Project: Legacy JBoss Application Server 6
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB
> Affects Versions: 6.0.0.CR1
> Environment: Red Hat Enterprise Linux Server release 5.5 (Tikanga)
> Reporter: Daniel Jipa
> Assignee: Carlo de Wolf
> Labels: jboss
> Fix For: No Release
>
>
> java.lang.IllegalStateException: No valid security context for the caller identity: java.lang.IllegalStateException: No valid security context for the
> caller identity
> at org.jboss.ejb3.EJBContextImpl.getCallerPrincipal(EJBContextImpl.java:142) [:1.6.3]
> at com.asf.security.server.SecurityWrapper.getLoggedUser(SecurityWrapper.java:32) [:2.0-dev 03/01/2011 17:44]
>
> This happens apparently for no reason after running fine for certain period of time and is thrown for every call after that. After re-login the problem disappears. I've read the bug was resolved in jboss 5.0.0
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list