Sharing HTTP session on multiple logins

If two users login into an application with same credentials and from different browsers can i use same http session to handle both the clients.
My objective is how many ever users login with same credentials we use same session to handle them.
I do not want to stop multiple login with same credentials.

Associate the data with the logged in user instead of the session then.

Similar Messages

Share http session across multiple EARs

I am curious to know the following:-
--> is it possible to share http session across multiple EARs running on same Weblogic application server.
i.e weblogic server/Jboss
--> is it possible to share http session across multiple EARs running on different Weblogic application server.
i.e weblogic server/Jboss
Please share the steps/way to acheive the same.

What are you trying to achieve / accomplish by splitting it up?
e.g. Clean Build in workshop will be faster for multiple EAR's , but unless you have all your application level libraries as shared libraries you might increase your runtime footprint. or you might want independent deploy/redeploy for your apps etc.
If however you need the session to be shared , that these aren't really independent web-applications and shouldn't be separate ear's. In most cases though you dont actually need the session as shared (e.g. a user's data is fetched from the database , you dont really need the session shared, you need a single shared sign on). So when you say is the session shared, what is the data that you need shared? should it be in the session in the first place?
And finally are these webapp's really independent (functionally ) or not?
Edited by: deepshet on Oct 13, 2009 2:09 PM

HTTP session sharing

Hi,
We have a need for session sharing among the different JVMs and have been trying the application cluster functionality with zero luck. Now we are thinking of looking into coherence because by reading the documentation we came to know this is something we could accomplish it. Since being a very new on this, have anyone done this and if you have can we get some information on how to do it. We will really appreciate your help on this.
Thanks,
Raj

To better understand the background of your root problem,
1) which Application Server product are you using?
2) the term "clustering" may mean different things to different App Server implementations. Does your reference to clustering also mean "Http Session Replication" has been specifically enabled, or that by simply clustering JVMs you expect this to happen automatically?
3) is access to the session needed by the same web app or different web apps in the JVMs?

Multiple Plugin HTTP Sessions

Hello everybody
We have developed a BSP that is displayed in a Portals using an iView. When the user navigate to this iView a Plugin HTTP Session appears in the R/3 system.
If the user navigate to another iView and after a while he/she returns to the BSP iView, a new Plugin HTTP Session apears in the R/3 system.
Is possible to avoid this? Can a user have a unique session?
Thank you in advanced.
Rubé

As much I understand this.
This is the default feature of BSP .You are using an I View ,you have plugin http session and one RFC connection in R3.
Now once you leave leave the BSP page ,Your plug in session shall be finished since it is no more using that BSP.
Once you come back to the same page ,I believe you get the new session for that BSP.
In my point of view ,My reply is No but you can check with developers if they can modify sessions mechanism ?
Thanks
Hope this helps you.
Amit

Using Voice Browsers, creates multiple HTTP Sessions

I am using the default voicebrowser.aef script.
I do a Create URL Document step followed by a Voice Browser step.
The VXML developer is telling me the different HTTP sessions are getting created for the 2 steps and it is extremely critical that the same HTTP session is used throughtout the call.
Does anyone have any insight on this or know of a way I set it to use the same session thourghout?
Ive attached screen shots of my script...
This is the log excerpt from the VXML log...
DEBUG [2011-04-21 08:57:16,950] [http-8080-1] [CallController] [] - : ~~~HTTPSession ID: 86DD667F1ED8C42D8430D4DE8D38ED9A
DEBUG [2011-04-21 08:57:16,952] [http-8080-1] [CallController] [] - : ~~~HTTPSession Creation Time: 1303394236902
DEBUG [2011-04-21 08:57:16,952] [http-8080-1] [CallController] [] - : ~~~HTTPSession Last Accessed: 1303394236902
DEBUG [2011-04-21 08:57:16,953] [http-8080-1] [CallController] [] - : ****** PARAMETERS : *********
DEBUG [2011-04-21 08:57:16,953] [http-8080-1] [CallController] [] - :       txtDNIS = 7079
DEBUG [2011-04-21 08:57:16,953] [http-8080-1] [CallController] [] - :       txtANI = 6516864319
DEBUG [2011-04-21 08:57:16,955] [http-8080-1] [CallController] [] - :       UserInput =
DEBUG [2011-04-21 08:57:16,955] [http-8080-1] [CallController] [] - :       FromState = 0
DEBUG [2011-04-21 08:57:16,955] [http-8080-1] [CallController] [] - :       txtCTIID = 1234567890
DEBUG [2011-04-21 08:57:16,955] [http-8080-1] [CallController] [] - :       txtLineNbr = 1
DEBUG [2011-04-21 08:57:18,044] [http-8080-2] [CallController] [] - : ~~~HTTPSession ID: B64DDD4D99F4A4A490B35DC5BA817928
DEBUG [2011-04-21 08:57:18,044] [http-8080-2] [CallController] [] - : ~~~HTTPSession Creation Time: 1303394238044
DEBUG [2011-04-21 08:57:18,044] [http-8080-2] [CallController] [] - : ~~~HTTPSession Last Accessed: 1303394238044
DEBUG [2011-04-21 08:57:18,044] [http-8080-2] [CallController] [] - : ****** PARAMETERS : *********
DEBUG [2011-04-21 08:57:18,044] [http-8080-2] [CallController] [] - :       TimeOutCount = 0
DEBUG [2011-04-21 08:57:18,044] [http-8080-2] [CallController] [] - :       FromState = 1
DEBUG [2011-04-21 08:57:18,045] [http-8080-2] [CallController] [] - :       BadCount = 0

As much I understand this.
This is the default feature of BSP .You are using an I View ,you have plugin http session and one RFC connection in R3.
Now once you leave leave the BSP page ,Your plug in session shall be finished since it is no more using that BSP.
Once you come back to the same page ,I believe you get the new session for that BSP.
In my point of view ,My reply is No but you can check with developers if they can modify sessions mechanism ?
Thanks
Hope this helps you.
Amit

Multiple Login in ATG on multiple server instances.

Hi,
I'm facing a issue with multiple logins in my web application. The scenario is explained below:
1. I login from one browser (IE) and add an item to cart. Then I navigate to cart page. I logout.
2. I login from another browser (Chrome) and add another item to cart. Now I have two items in my cart. I'm still logged in.
3. I login to IE again and it throws error saying ConcurrentUpadteException.
This is very obvious.
1. In first step the profile's order is picked up from repository and updates it version to '2' (suppose). This change is there still in the cache and not persisted in the DB. I logout. The order will get persisted only after 5 minutes, due to cache configuration.
2. Next in step 2 we get the same order from the repository and makes its version number to '2' also. I'm still logged in.
3. Now in step 3 when the order is again picked up from repository and updates the order version to '2'. Hence the ConcurrentUpdateException.
This is happening because I have multiple sever instances and the request can be handled by any of the server instance. Had there been only one server instance it would have only one cache, and order will be picked up from the same cache every time.
If I can invalidate the sessions across all the server instances I can resolve this issue. The problem is how can I do this. Is this possible by a making changes in the program or by changing any configuration.
Please give me suggestions on how to take it up from here.

Not sure what is the real issue you are facing. For resolving the concurrentUpdateException in order, ATG is suggesting some steps to follow while updating the order.
Check the below solution, you need to have a support id to access this article.
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1362812.1
Regarding your second question, for invalidating the cache for multiple instances, ATG provides different Caching Modes, you may check the documentation.
http://docs.oracle.com/cd/E23095_01/Platform.93/RepositoryGuide/html/s1003cachingmodes01.html
Cheers
R

Fatal bug with shared JDBC Session Persistence

We are attempting to launch a three-tier site with two clusters, one at the
          web layer (JSP/servlet/images) and a separate cluster at the app server
          layer (EJBs). We are running WebLogic server 4.5.1 Service Pack 8 on Solaris
          2.7. In production we use Solaris JDK 1.2.1.04, and in development we use
          JavaSoft JDK 1.2.2. We are able to duplicate this problem with both JDKs. We
          are using the WebLogic kona/oracle driver for session persistence because
          the Oracle JDBC driver would not work for this purpose - we are using the
          Oracle OCI driver for our EJB persistence in a separate pool in the app
          server cluster.
          We attempted to configure our web cluster to work with in-memory session
          replication. We found the performance of the WebLogic proxy to be abysmal -
          causing a 5x to 10x performance degredation over shared JDBC persistence. We
          were running the proxy on WebLogic, which we were advised would be slow. Its
          performance is beyond slow, it is completely unusable and should NEVER be a
          recommended or even supported configuration. We do not wish to purchase
          separate licenses for iPlanet, refuse to run IIS in a production setting,
          and cannot use Apache until WebLogic 5.1, so we are stuck with shared JDBC
          persistence until we can upgrade to 5.1.
          Using JDBC session persistence with a shared persistent store amongst all
          the clustered web servers results in our users getting brand-new sessions
          populated with data from OTHER USERS' SESSIONS. This is very easy to
          replicate using the provided test JSP and java class. This behavior results
          in new users coming to the site and finding themselves logged in as other
          users.
          The test.jsp file simply accesses the session, prints out some information,
          and then adds a few values to the session. The JSP prints out the value of
          session.isNew(), the session's ID, and the number of values in the session
          space. If you hit this jsp with a new browser window, the session should be
          new, and the number of values should be zero.
          The test Java class hits a URL with this test.jsp file repeatedly, and
          checks to make sure that the session is empty. It keeps a counter of the
          number of hits which resulted in non-empty sessions and the total number of
          hits. Because this java class does not maintain cookie data of any kind and
          merely opens new HTTP connections, it should always receive a brand-new,
          non-empty session.
          When we set the JDBC session persistence property
          weblogic.httpd.session.persistentStoreShared=true and run the test, we see
          periodically see the test.jsp file receiving a brand-new (session.isNew() =
          true), yet non-empty (session.getValueNames().length != 0) session. This is
          extremely bad behavior and makes the shared JDBC session persistence setting
          worthless. We were able to duplicate this behavior with both a single server
          and multiple servers in a cluster.
          If we set weblogic.httpd.session.persistentStoreShared=false, then this test
          works fine. This also means that we cannot cluster web servers.
          To run the test, simply start a WebLogic instance using the provided
          properties file, put the jsp in the document-root somewhere, and then run
          SessionTest.java, providing the URL of the test JSP as the only command-line
          argument. You will need to modify the properties file to have the proper
          database settings and document-root. The java class will display a running
          tally of the number of hits, and the number of hits that result in
          non-empty, illegal sessions, with a total at the end.
          So, we are now in a position where we are completely unable to launch our
          site in a clustered, no-single-point-of-failure configuration. Obviously,
          clustering was one of the main reasons to choose WebLogic, and we are
          extremely distressed that we are unable to get this configuration to work.
          Any help would be appreciated.
          [web.standalone.properties]
          [SessionTest.java]
          [test.jsp]


I hope this is not too far fetched, but we are expieriencing a similar
          problem with jms (messages are mixed up between queues). This happens only
          if we are using message persistence in an oracle db (everything works ok
          when we are not using persistent messages). Could it be that there is a
          serious bug in the jdbc code/oracle driver code or connection handling
          (regarding multi threading)? This would explain that, whenever you use
          persistence with oracle databases, messages/sessions (or other) are mixed
          up.
          - Falk
          "Grant Kushida" <[email protected]> wrote in message
          news:[email protected]...
          > We are attempting to launch a three-tier site with two clusters, one at
          the
          > web layer (JSP/servlet/images) and a separate cluster at the app server
          > layer (EJBs). We are running WebLogic server 4.5.1 Service Pack 8 on
          Solaris
          > 2.7. In production we use Solaris JDK 1.2.1.04, and in development we use
          > JavaSoft JDK 1.2.2. We are able to duplicate this problem with both JDKs.
          We
          > are using the WebLogic kona/oracle driver for session persistence because
          > the Oracle JDBC driver would not work for this purpose - we are using the
          > Oracle OCI driver for our EJB persistence in a separate pool in the app
          > server cluster.
          >
          > We attempted to configure our web cluster to work with in-memory session
          > replication. We found the performance of the WebLogic proxy to be
          abysmal -
          > causing a 5x to 10x performance degredation over shared JDBC persistence.
          We
          > were running the proxy on WebLogic, which we were advised would be slow.
          Its
          > performance is beyond slow, it is completely unusable and should NEVER be
          a
          > recommended or even supported configuration. We do not wish to purchase
          > separate licenses for iPlanet, refuse to run IIS in a production setting,
          > and cannot use Apache until WebLogic 5.1, so we are stuck with shared JDBC
          > persistence until we can upgrade to 5.1.
          >
          > Using JDBC session persistence with a shared persistent store amongst all
          > the clustered web servers results in our users getting brand-new sessions
          > populated with data from OTHER USERS' SESSIONS. This is very easy to
          > replicate using the provided test JSP and java class. This behavior
          results
          > in new users coming to the site and finding themselves logged in as other
          > users.
          >
          > The test.jsp file simply accesses the session, prints out some
          information,
          > and then adds a few values to the session. The JSP prints out the value of
          > session.isNew(), the session's ID, and the number of values in the session
          > space. If you hit this jsp with a new browser window, the session should
          be
          > new, and the number of values should be zero.
          >
          > The test Java class hits a URL with this test.jsp file repeatedly, and
          > checks to make sure that the session is empty. It keeps a counter of the
          > number of hits which resulted in non-empty sessions and the total number
          of
          > hits. Because this java class does not maintain cookie data of any kind
          and
          > merely opens new HTTP connections, it should always receive a brand-new,
          > non-empty session.
          >
          > When we set the JDBC session persistence property
          > weblogic.httpd.session.persistentStoreShared=true and run the test, we see
          > periodically see the test.jsp file receiving a brand-new (session.isNew()
          =
          > true), yet non-empty (session.getValueNames().length != 0) session. This
          is
          > extremely bad behavior and makes the shared JDBC session persistence
          setting
          > worthless. We were able to duplicate this behavior with both a single
          server
          > and multiple servers in a cluster.
          >
          > If we set weblogic.httpd.session.persistentStoreShared=false, then this
          test
          > works fine. This also means that we cannot cluster web servers.
          >
          > To run the test, simply start a WebLogic instance using the provided
          > properties file, put the jsp in the document-root somewhere, and then run
          > SessionTest.java, providing the URL of the test JSP as the only
          command-line
          > argument. You will need to modify the properties file to have the proper
          > database settings and document-root. The java class will display a running
          > tally of the number of hits, and the number of hits that result in
          > non-empty, illegal sessions, with a total at the end.
          >
          > So, we are now in a position where we are completely unable to launch our
          > site in a clustered, no-single-point-of-failure configuration. Obviously,
          > clustering was one of the main reasons to choose WebLogic, and we are
          > extremely distressed that we are unable to get this configuration to work.
          > Any help would be appreciated.
          >
          >
          >
          >

How to share a session across multiple jws?

Hi!
I have this problem.
I'm looking for a way to have shared sessions, available across multiple JWS with WLW 8.1
I try to get a session with this code:
WebServiceContext wsContext = WebServiceContext.currentContext(); WebServiceSession session = (WebServiceSession)wsContext.getSession();
but it throws COntextNotFoundException....
I added the session descriptor in weblogic.xml to set the param CookiesEnabled to true, because I read that using this code works but requires that the client support cookies to keep the HttpSession object around.
But it's not works!
How can I get to HTTP session from a JWS?
And....it's possible to share a session accross multiple JWS?
Thanks a lot!

You may be interested (& probably discouraged at the end) in this discussion http://forum.java.sun.com/thread.jspa?threadID=619170
cheers,
ram.

Using a single iTunes library with multiple logins.

I've setup my iMac to have multiple logins for everyone in my family. I'd like everyone to use the same iTunes library, though, so that all purchases and playlists can be seen and used by everyone. I have it so that everyone has the same files, but not the same library. That is, the playlists don't come through on the other logins, and purchases made from one login don't translate to another.
I'm not trying to rip anyone off, I just want my whole family to have the same library.
Is this possible?

padrepablo wrote:
Thanks much, but I've done that. That method shares FILES but not the LIBRARY
Then you missed a step or two.
The steps above share the entire iTunes library (media, artwork, playlists, library file, Genius files, everything).
In the Music/iTunes folder on everyone's login is a file called iTunes Library.itl.
Yes, and holding Option and selecting Choose library allows you to select which iTunes library you want to use.
THAT is the file I want to share, but I can't seem to move it.
The steps above will do exactly what you want.
All users will use the exact same iTunes library.
You need to hold Option and select Choose library (notice is says, "Library").
Once you copy your /Music/iTunes/ folder to /Users/Shared/ folder, everyone can delete /Username/iTunes/ folder.

In-memory replication of http session is not working in BEA7 cluster

          Hi everyone,
          I have 3 managed servers in Bea7.0 SP4 in a cluster. The client requests are sent
          through apache web server. I have given cluster address as URL in httpd.conf of
          apache server which sends the client requests for dynamic pages such as JSPs and
          servlets to the weblogic cluster.
          Load balancing is working fine. I ensured this from the log files of all the 3
          servers. All the 3 servers are getting different client requests and thus load
          balancing is working.
          Now, I wanted to achieve Fail-over. I do not think that i should use proxy plug-in
          for this. I feel the cluster itself will handle fail-over provided i make the
          http session as memory replicated.
          I updated the weblogic.xml with the following entry :
          <session-descriptor>
          <param-name>PersistentStoreType</param-name>
          <param-value>replicated</param-value>
          </session-param>
          </session-descriptor>
          I guess this is sufficient to make the http session as cluster aware.
          But when I shutdown server1, the user connected to server1 will be kicked out
          of the session and come to login page through server2 or server3 which are running
          fine.
          Could anyone help me to achieve http session as cluster aware. Does it indicate
          that I have to go for WLS proxy – HttpClusterServlet to achieve fail over for
          http session ?
          BTW, for your info, i am using setAttribute() and getAttribute() while manipulating
          the session.
          thanks in advance.


          Hi Ryan,
          Thanks for ur valuable input.
          I can see failover working.
          But, I can not continue with the same session in my application.
          I printed session Ids before and after failover, I found both are different.
          I guess session replication is a responsibility of weblogic/apache plugin.
          If not please let me know which all settings I should do to make failover working?
          Thanks again.
          Plad
          "ryan upton" <ryanjupton at learningvoyage dot com> wrote:
          >Plad,
          >
          >Are you trying to gracefully shut down the server? If you are then the
          >problem that you say you can't identify is simply the server's default
          >behavior which is to wait for all non-replicated sessions to be dropped
          >or
          >timed out before killing the process. Try forcing the shutdown: kill
          >-9 the
          >PID or CTRL-C if you started the server from the command line. You can
          >also
          >check the ``Ignore Sessions During Shutdown" checkbox under the server's
          >control tab in the admin console, this should allow you to shut down
          >gracefully without waiting for session timeout. BTW your sequence is
          >off
          >in #5 below, the replication doesn't occur upon failure, the replication
          >has
          >already happened once you created the session object on the first server,
          >I
          >think maybe you're confusing replication with failover.
          >
          >~RU
          >
          >"Plad" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Hi,
          >> I have 2 managed servers in a cluster.
          >>
          >> 1. I have got a DNS name configured which maps to these 2 managed server's
          >IP
          >> addresses.
          >> 2. I can browse my site using this DNS name.
          >> In HTTPD.conf I have :
          >>
          >> ServerName dev.a.b.net
          >>
          >> <IfModule mod_weblogic.c>
          >> WebLogicCluster 10.1.38.232:7023,10.1.34.51:7023
          >> MatchExpression *.*
          >> </IfModule>
          >>
          >> LoadModule weblogic_module modules/mod_wl_20.so
          >>
          >> 3. I have adeded session descriptor in weblogic.xml , also enabled
          >proxy
          >plugin
          >> in weblogic console.
          >>
          >> 4. I tested accessing my application using DNS url after shutting down
          >alternatively
          >> each manaed server. I can access application.
          >>
          >> 5. Now, problem comes when I access a managed server1 , keeping server2
          >down.
          >> I am able to access my application.
          >> Now, I start the server2.
          >> (Here I am supposing that replication should occur)
          >> Then I am shutting down server1.
          >> But, this time the server log shows me following:
          >>
          >>
          >> 9:58:51 AM GMT+05:30 NOTICE Web application(s) chlist still have
          >non-replicated
          >> sessions after 2 minutes of initiating SUSPEND. Waiting for non-replicated
          >sessions
          >> to finish.
          >> 10:00:51 AM GMT+05:30 NOTICE Web application(s) chlist still have
          >non-replicated
          >> sessions after 4 minutes of initiating SUSPEND. Waiting for non-replicated
          >sessions
          >> to finish.
          >>
          >> I am unable to make out where the problem is?
          >> Can it be a problem of Liecense? Is there any specialcluster liecense
          >for
          >weblogic8?
          >>
          >> Hoping to get replies.
          >> Thanx.
          >> Plad
          >>
          >> "ryan upton" <ryanjupton at learningvoyage dot com> wrote:
          >> >See my reply to your first post, but I've also added a few comments
          >here.
          >> >
          >> >"jyothi" <[email protected]> wrote in message
          >> >news:[email protected]...
          >> >>
          >> >> I guess someone from bea support team only can answer both your
          >question
          >> >and mine.
          >> >> As per my knowledge, we do not need to do any setup at Apache
          >side
          >> >regarding
          >> >> cluster other than mentioning cluster address as URL while
          >contacting
          >> >WLS
          >> >> from apache.
          >> >>
          >> >> I hope someone from Bea, will help us. I do not think that we
          >> >go for
          >> >WLS
          >> >> proxy plug-in using HttpClusterServlet for making session replication.
          >> > I
          >> >strongly
          >> >> feel that the cluster itself be able to manage the fail-over of
          >> >http
          >> >sessions
          >> >> provided we put the entry "PersistentStoreType" in weblogic.xml
          >> >regarding
          >> >> the session replication.
          >> >>
          >> >
          >> >The cluster does handle the management of Sessions. The clustered
          >> >applications still create the Session objects and the cluster manages
          >> >them
          >> >as per your deployment descriptor settings (replicated, JDBC, File)
          >however
          >> >the proxy has to be aware of which server the client has an affinity
          >> >for
          >> >(only with replicated sessions) and it does that by reading a cookie
          >> >passed
          >> >back from the server that handled the initial request and created
          >the
          >> >primary session object. The proxy has a list of both the primary
          >and
          >> >secondary server locations from this cookie that it can use to failover
          >> >the
          >> >request if the primary server fails. Clusters _DO NOT_ failover nor
          >> >do they
          >> >load balance, that's the job of your proxy, whether you're using the
          >> >HTTPClusterServlet, WLS Plug-in or a more sophisticated hardware load
          >> >balancer like Big IPs F5
          >> >
          >> >> jyothi
          >> >>
          >> >
          >> >~RU
          >> >
          >> >
          >>
          >
          >

Multiple logins on one account...

Is there any way to have multiple login/passwords connect to the same account in the Room Console?
Is the login/password tied to a particular account URL? Or can I setup two accounts to access the same account URL?
thanks
-sandy

hi Nigel,
We have multiple developers working on a project and the Room Console is a great asset in debugging. Right now we are just sharing one login, which isn't ideal, but isn't the end of the world either.
I think the best solution is probably to build out the Local Server so that it has a RoomConsole. (And can be instantiated from AS3 for unit tests.)
What is the workflow that you guys use for development? Do you use the LocalServer or do you use a server? Or do you have some internal tools that you haven't shared yet?
-sandy

Define HTTP Session Attribute in a Custom Authenticator

Hello everyone I developed sucessefully a Custom Authenticator for WLS10 that interacts with a web service.
But now I need to provide an object to the web applications with the some user information.
I was wondering defining the object in the HTTP Session but I dont know how to do it via de LoginModule of the custom authenticator.
Can anyone provide me some tips?
thanks in advance.

What kind of user information do you need to pass on to the webapplication ? username can be retrieved by request.getRemoteUser() (after successful login).
May be you need to clarify little bit more on what you want to achieve.
-Utpal

How to prevent multiple logins by using HttpBindingListener

Hi,
Can anyone tell me how do i actually use session to prevent multiple login from different machine? From my understanding, i need to use HttpBindingListener to valueBound and valueUnbound when user tries to login, but i encounter a problem is my session is always overwritten since i use setAttribute() method in servlet.
For instance i use username(aaa & bbb) to login in two different machine, my login is always overwritten if i use username bbb to login after username aaa. i know it is because setAttribute() method overwrite existing session data, so i would like to know what other method should i use to achieve what i want, tks.

Hi,
This is the logic for session :
Connect to db for verification, once verified, system return a UserBean and this UserBean will be set in ClientSecurityEngine
When this particular user has been successfully verified, a new session will be created
if(success)
    session = request.getSession();
    User user;
    synchronized(session)
    user = (User) session.getAttribute("user");
    if(user == null)
       user = new User(ClientSecurityEngine.getInstance().getUserBean().getUsername());
       session.setAttribute("user", user);
/* User class */
public class User implements HttpSessionBindingListener {
    private static Map<String, HttpSession> logins = Collections.synchronizedMap(new HashMap<String, HttpSession>());
    private String username;
    public User(String username) {
        this.username = username;
    public String getUsername() {
        return username;
    @Override
    public void valueBound(HttpSessionBindingEvent event) {
        if (logins.containsKey(getUsername())) {
            HttpSession session = logins.remove(getUsername());
            if (session != null) {
                session.invalidate();
            logins.put(getUsername(), event.getSession());
        } else {
            logins.put(getUsername(), event.getSession());
    @Override
    public void valueUnbound(HttpSessionBindingEvent event) {
        logins.remove(getUsername());
}Edited by: EJP on 21/07/2011 14:22: added {noformat}{noformat} tags so we can actually read your code. Please use them.

Multiple Logins - Same Browser Cookie Problems??

Is there any Issues in which a User uses Tabs to Login (LDAP Authentication)?
I have only a Cookie Name in the Cookie Attributes in Authentication Setup.
I had multiple browsers opened and signed on an application. A :tx- row lock contention was evident..
INSERT INTO WWV_FLOW_DATA ( FLOW_INSTANCE, ITEM_ID, ITEM_VALUE ) VALUES ( :B4 , :B3 , :B2 ||':'||:B1 ||':0:0')
Can someone explain what happened here, and does multiple logins have to be prevented?
Should I add a Cookie Path and Domain to prevent this?
Thanks,
Mike

Mike,
I need a more detailed scenario to follow. I'm not even sure you are saying that something did not work properly.
FYI, cookies have no presence in session state.
Scott

Model session not in sync with Http Session

Hi All,
I have an application developed in JDev 11.1.1.4 and we are not using ADF Security for login.
The problem occurring is randomly some of the LOV on my home page are getting null (having no data). These LOVs are populated using the values passed as bind parameter from the login values (basically HTTP session values at web layer). So i added a method in all the task flow to set the session value at the model layer (default method) . Also on each call to the Am Impl call i am setting the value in the HTTP session and then invoking the method, but some how what happens is the Model level session value is not in sync with HTTP session and the list gets empty.
Any inputs what i can do to get out of this prblm ?
thnk

In this case you need to overwrite the activateState/passivateState method of your am and store/reads the values from the xml structure you get as parameters to this methods.
For more detailed information check the docs http://download.oracle.com/docs/cd/E12839_01/web.1111/b31974/bcstatemgmt.htm#sm0495
By the way, this is nothing you need to open an SR on as it's working as designed.
Timo

Sharing HTTP session on multiple logins

Similar Messages

Maybe you are looking for