cancel
Showing results for 
Search instead for 
Did you mean: 

BaseLoginException in the appserver

Former Member
0 Kudos

Hi,

I am using SAP Web AS 6.40 sneak preview version.

When I am trying to call the application from the remote client and when I am looking up for the EJB in the context I am getting the following error on the server(from the logviewer)

Message ID : 0007E947722B006400000001000012A40003F5F1A1740FF6

Severity : Error

Location : com.sap.engine.services.security

Source Name : com.sap.engine.services.security

Thread : SAPEngine_Application_Thread[impl:3]_10

Message : Exception com.sap.engine.services.security.exceptions.BaseLoginException: Error in some of the login modules.

at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:102)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:123)

at com.sap.engine.services.servlets_jsp.server.runtime.context.SessionServletContext.doLogin(SessionServletContext.java:547)

at com.sap.engine.services.servlets_jsp.server.runtime.context.SessionServletContext.checkUser(SessionServletContext.java:267)

at com.sap.engine.services.servlets_jsp.server.runtime.context.ApplicationContext.checkMap(ApplicationContext.java:400)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.checkRequest(HttpHandlerImpl.java:64)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:655)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:221)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:146)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)

at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)

Caused by: java.lang.OutOfMemoryError

Any ideas?

Thanks

Kavitha

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello Kavitha,

Please open the Config Tool (.../j2ee/configtool/configtool.bat) and navigate to 'cluster-data'-> 'instance_ID<#####>'-> 'server_ID<#######>'

With 'server_ID<#######>' highlighted, on the right side under 'General' tab you should see 'Java settings'. Try increasing the 'Max heap size (in MB)' setting to ensure that you are not running out of heap memory. In the 'Java parameters' section, look for a parameter named '-XX:MaxPermSize'. If this parameter does not exist, add the following line:

-XX:MaxPermSize=128m

If MaxPermSize exists, but is a smaller value, please try increasing it to 128m. The -XX:MaxPermSize parameter controls the class loading memory area. Typically out of memory is triggered by either a lack of Heap memory (Max heap size) or a lack of class loading memory (-XX:MaxPermSize).

If the problem continues, please add the following parameters to the 'Java parameters' area:

-verbose:gc

-XX:+PrintGCDetails

-XX:+PrintGCTimeStamps

Please duplicate the problem and review the Standard Output which should either be in

.../J2E/JC00/work/std_server0.out

or

.../J2E/JC00/j2ee/cluster/server/log/console_logs/output.log

In one of these log files, you'll find the garbage collection output with will show you memory usage information of the Perm and Heap memory areas. Look near the end of this trace for the memory information at the time of the OutofMemory error. This should tell you in which area you are exceeding the memory limits.

If neither memory area is reaching its limit, you could be running out of client threads, which can also trigger the OutofMemory error.

Regards,

Nathan