Recycle AppServer Kicks Out User

Hello,

When I perform a Recycle of our AppServer for some reason a particular user always gets a message that his session is offline and sometimes it will reconnect and other times it will kick him out completely. I am usually in Epicor during this same time and I do not receive any messages whatsoever that there is anything wrong with my Epicor session and I’ve never heard anyone else complain about getting disconnected though not everyone reports it like they should. :face_with_raised_eyebrow:

It doesn’t happen often but the reason I occasionally perform the Recycle is because our AppServer has gotten a spike in Memory Usage (from our usual base amount) and people are starting to complain about processes in Epicor being extremely slow. Is it possible that this one user’s session could be connected in some way to whatever is causing the AppServer Process Memory to spike and that’s why he experiences this disconnect of his session when I Recycle the AppServer? That’s the only thing I can think of that could cause this. This user does do a lot with Customizations in Epicor.

I guess most importantly can anyone help me figure out what is causing the spike in our AppServer Memory so that I can prevent it from happening and stop having to Recycle our AppServer when it gets too high?

Thanks for any thoughts,
-Heather

Anything special about that user?

They don’t happen to be the one that setup the Task Agent, with their userID, do they?

They are a Security Manager but No they did not setup the Task Agent.

From everything I’ve read (the online help and on here), it looked like the only concern with cycling the App Pool, was for processes, which might not complete within some predetermined timeout.

Does this user have a tweaked sysconfig file?

Perhaps tracing is turned on for that user

1 Like

What happens if you test the following:

  1. Have that user exit E10
  2. Have that user launch E10, but not to open any programs/forms
  3. Recycle the App Pool.

Does that user still see the message, with no open forms or processes running?

Do the same above but with step 2b added
2b. Exit the System monitor

1 Like

Does the user have Allow Session Impersonation enabled in user account maintenance?

1 Like

I like where Calvin is going here. How about a different binding? https? Windows?

2 Likes

I was going to mention the binding. But isn’t that the same for all users connecting to the same App?

I could see if you have two apps (we have one with Windows, and another with Windows User Channel). But then the user would only see it if you cycled the App they’re connected through

1 Like

@ckrusen AWESOME troubleshooting idea!!! I wish I would have thought about that! I will give this a try and let you know! Thank you Calvin!

@jeromy, they do not have Allow Session Impersonation on, it is unchecked.

I agree @Mark_Wonsil! I’ll try some more testing with the Recycle and this user and update this thread.

I have a SSO AppServer setup that I could have them connect to and try Recycling that to see what happens too.

The part about exiting system monitor was in case their configuration (the Normal, Priority and Duration settings) got smurfed.

1 Like

https binding is very resilient and we rarely see disconnects.

You can have as many bindings as appServers. Most SSO people have one for SSO and another for basic username/password just in case SSO goes down. It’s a long shot but if his binding was not https and others are then this would make sense. Unlikely but possible.

1 Like

I totally Smurf where you are going with that!

image

I wasn’t sure if “smurfed” was used outside my field of electrical engineering.

It’s more polite than fubar’d :slight_smile:
image

1 Like

I think we have our images reversed… :laughing:

Yes, definitely more polite! I actually never thought of using that but will from now on! That’s SMURFtastic! LOL :blue_heart: