Thank you Tanya and Douglas for your suggestions.
I am not quite sure that this error depends on the session id.
I’ve changed the gx_appConfig.xml session id value, but it didn’t help.
Maybe the problem exist at the interface of ApplinX → Mainframe.
I give you a detailed description of case:
I have an application with a JSP generated pages. On one of them I have a search form.
I select some options on it and submit it. In next step I should see a page with a counter, which counts records.
On a web browser I only see the screenlocker page, nothing else.
On ApplinX Administrator (in session view) I see the window with the record counter.
After more then a minute, in the same time when the record counter shows the results (in session view),
the search form page is reloading and the “User already attached error” appears.
In server log I have this:
2011-01-13 14:51:39,394 [W00005_Request_Handler] WARN > WebDev:E9CF9C8B64CB54003FBD7DDEE23A7B40: Wait Host Quiet failed
2011-01-13 14:51:39,394 [W00005_Request_Handler] WARN > WebDev:E9CF9C8B64CB54003FBD7DDEE23A7B40: Wait condition timed out
2011-01-13 14:52:06,413 [W00008_Request_Handler] WARN > GXUser$UserAlreadyAttachedException: User E9CF9C8B64CB54003FBD7DDEE23A7B40 is already attached
The most interesting thing is that when I’ve adjusted the ‘Wait condition timeout’ parameter in host activity of my application, from default 60000 ms to 120000 ms, the "User already attached error’ didn’t appear.
Regards,
Maciej
#Mainframe-Integration#webMethods#ApplinX