E-WS: Can't Log into PIA after WebLogic 8.1 SP5 or SP6 Upgrade, ERROR: session cookie name (null) is either empty, or using a numeric first character> (Doc ID 647113.1)

Last updated on JUNE 27, 2013

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.44 to 8.48 [Release 8.4]
Information in this document applies to any platform.
***Checked for relevance on 27-Jun-2013***


Symptoms

After applying the WebLogic 8.1 SP5 or SP6, customers can't log into PIA.


Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.


You can get to the WebLogic Server Administration Console.

Exceptions similar to the following are written to the PIA_weblogic.log:

javax.naming.NoPermissionException: User <anonymous> does not have permission on weblogic.management.home to perform lookup operation.
javax.naming.NoPermissionException: User <anonymous> does not have permission on weblogic.management.home to perform lookup operation.
at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:365)
at weblogic.jndi.internal.ServerNamingNode.checkLookup(ServerNamingNode.java:329)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:153)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:188)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:196)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:196)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:256)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:363)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at psft.pt8.auth.WebLogicDiscovery.getServerProperties(WebLogicDiscovery.java:60)
at psft.pt8.auth.WebProfile.loadProfile(WebProfile.java:265)
at psft.pt8.auth.WebProfile.checkAndLoadProfile(WebProfile.java:80)
at psft.pt8.psp.service(psp.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at psft.pt8.psfilter.doFilter(psfilter.java:76)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6987)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
ERROR: session cookie name (null) is either empty, or using a numeric first character


You may see the following messages in WebLogic log:

####<Jun 14, 2006 3:23:10 PM MST> <Info> <HTTP> <jclpsoft03> <PIA> <ExecuteThread: '49' for queue: 'weblogic.kernel.Default'> <> <> <BEA-101047> <[ServletContext(id=16785420,name=PORTAL,context-path=)] ERROR: session cookie name (null) is either empty, or using a numeric first character>

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms