Skip to Content
1
Jan 17, 2011 at 09:32 PM

MII Logon Error

610 Views

Hi,

We are on NW CE 7.1 EHP1 and MII 12.1 SP 7 build 47.

There are 300 plus users, some regular webservice calls to MII.

Recently, we encountered with situation where MII did not allow any users to login to application, it displayed an error saying "Logon limit exceeded. Please try again later" Since none of us were able to enter the application finally we were forced to re-start NW which eventually fixed the issue.

Then I checked for settings in AS Java Config tool -->Instance >Services >Security and found following properties set,

1) LoginModuleClassLoaders = blank nothing specified

2) LogonURL = /j_security_check

3) MaxUsersCount = 100000

4) ServiceStartupLockAttemptsInterval = 1000

5) ServiceStartupLockTimeLimit = 1800000

6) SessionExpirationPeriod = 100000000

7) SynchPermissionsWithDatabase = true

8) VerifyLoginModulesOnDeploy = true

9) WriteSuccessfulLogonStatistics = false

10) forceCreateAllUserEntries = false

11) sessions_size = 200

With such large User Count of 1,000,000 set I don't think it was something to do with User count.

When MII came back up I found below error in NW logs

Message: Can not create shm web object. Possible out of shm free slots. Check the shared memory configuration

Date: 2011-01-14

Time: 22:02:08:831

Category: com.sap.engine.session.runtime.http.HttpRuntimeSessionModel

Location: com.sap.engine.session.runtime.http.HttpRuntimeSessionModel

Application: sap.com/xappsxmiiear

Thread: Thread[HTTP Worker [@1175508341],5,Dedicated_Application_Thread]

Data Source: j2ee\cluster\server0\log\defaultTrace_00.trc

Arguments:

DSR Transaction: 38216e70205c11e09fdf001cc4eaf0be

Message Code: com.sap.ASJ.ses.rt0001

Session: 1200

Transaction:

User: est_tuber_t218

Time Zone: 0-600

CSN Component: BC-JAS-COR-SES

DC Component: kernel.sda

Correlation ID: 1428850000000003

DSR Root Context ID: 38216E70205C11E09FDF001CC4EAF0BE

DSR Connection: 38216e70205c11e09fdf001cc4eaf0be

DSR Counter: 0

Host: gpiptcxm01

System: PR1

Instance: J00

Node: server0

Log ID: 001CC4EAF0BE250C0000000800000B2C

I am afraid we might face this issue again in future. so any suggestions/recommendations will be of great help.

Regards,

Adarsh