ibm mq - Same Application deployed in two different websphere 8 profiles share session? -


I have an application war, I have created two profiles of AppSrv01, AppSrv02 on websphere 8.0.0.0.

MQ connectivity in my application, J. 2ee application on Stropes 1.1.

I have deployed war on both servers AppSrv01 Reference B as A reference A and APRV 02.

I have session listeners in my application which will take care of the total available sessions.

The scenario is given below ....

Login to the URL localhost: 9082 / A, go to some page in it.

Going and logging on the localhost URL: 9082 / b, go to some page in the other tab of the same browser.

The URL is going on Local Host: 9082 / A, clicking on some links or URLs from the current page.

When it comes to remote debug from the server for session listener ... it shows the stack given below

  daemon thread [webcontenter: 10] ( Suspension (breakpoint at the line 24 in the session's Controller Listener) Session session information author (HTPsEvenEvent) line: 24WeapSpaceObserver) .sessionCreated (ISession) line: 111 sessions EventDispatcher.session created (Eastion) line: 98 session manager. Securitization (string, int, boolean) line: 268 session manager. Generation Session (ServalCounter, Service Service, Session Affinity Contains, Boolean) Row: 640 WsSessionContext (Session-Link). , Boolean, Boolean) line: 485 WsSessionContext (sessioncontext) .getIHttp session (HTTPProvativeArchiveIt, HTTPServicesIpence, Boolean) line: 419SRITQVSTContact. Get Session (Boolean, Webpages) Line: 104 SRRSServeletRoyest.Jetation (Boolean) line: 2099 SRTServletRequest.getSession () line: 2083 RequestProcessor.processLocale (HttpServletRequest, HttpServletResponse) Line: 631 RequestProcessor.process (HttpServletRequest, HttpServletResponse) Line: 230 ActionServlet .process (HttpServletRequest, HttpServletResponse) Row: 1482 ActionServlet.doPost (HttpServletRequest, HttpServletResponse) Line: 525 ActionServlet (HttpServlet). Service (HTTPVERTETUREST, HTTPSvET Response) Line: 59T (ServletRapest, ServletWrapper) Service (ServletRequest, ServletResponse, WebAppServletInvocationEvent) line: 1147 ServletWrapperImpl (ServletWrapper) .handleRequest (ServletRequest, ServletResponse, WebAppDispatcherContext) Row: 722 ServletWrapperImpl (ServletWrapper) .handleRequest (ServletRequest, ServletResponse) line: 449 ServletWrapperImpl.handleRequest (ServletRequest, ServletResponse) line : 178 WebAppFilterManagerImpl (WebAppFilterManager) .invokeFilters (ServletRequest, ServletResponse, IServletContext, RequestProcessor, EnumSet & lt; CollaboratorInvocationEnum & gt;) Line: 1020 CacheServletWrapper.handleRequest (ServletRequest, Circlet Response) Line: 87WS WebConnantire (Webcontractor) Indal Requests (Iceview, ErosSpens) Line: 883 WSWeb Container Handle Request (Irivest, IrsSpace) Line: 1659 W.C. RD (Virtual Connection) Line: 195 HTTP Inbound Link Hidden Deletion () Line: 452 HTTP Inbound Link Featured New Reset () Line: 511 HttpInboundLink.processRequest () Row: 305 HttpInboundLink.ready (VirtualConnection) Line: 276 NewConnectionInitialReadCallback.sendToDiscriminators ( Virtual Connection, TCPReadRequestContext, Boolean) Row: 214 NewConnectionInitialReadCallback.complete (Virtual Connection, TCPReadRequestContext) Row: 113 AioReadCompletionListener.futureCompleted (IAbstractAsyncFuture, Object) line: 165 AsyncFuture (AbstractAsyncFuture) .invokeCallback line: 217 AsyncFuture (AsyncChannelFuture) .fireComple TionActions () Row: 161 AsyncFuture.completed (long) line: 138 ResultHandler.complete (AsyncFuture, int, int) line: 204 ResultHandler Roinnint Processing LOOP (Boolean) Line: 775 Results Handler $ 2. RAN () Row: 905 Threadpool $ Worker Stop () line: 1648   

This is creating another session example. It needs to be understood why it is making another example.

When you open tabs in IE, in the same session, then you have only one cookie JSESSIONID per domain .

When you go to localhost: 9082 / a - you have JSESSIONID as SESSIONID is -a .

When you go to localhost: 9082 / b> - you have JSESSIONID like SESSIONID-B .

So when you access the app on AppSrv01, then JSESSIONID goes to AppSrv01 Session-B . Appserver does not know about this session ID, so it thinks a new user and makes a session.

Try to open an IE- & gt; File - & gt; You will not face the above problem when access to the new session and application on APSRV 02.

If you have some IEWATCH or Fidler, then you will be able to see from JSESSIONID clients / browsers.

Comments

Popular posts from this blog

Pass DB Connection parameters to a Kettle a.k.a PDI table Input step dynamically from Excel -

multithreading - PhantomJS-Node in a for Loop -

c++ - MATLAB .m file to .mex file using Matlab Compiler -