Losing HTTP Sessions

Hi All,
          We are having some trouble with HTTP sessions. Sometimes our browser will have a session cookie set but will be issued a new session cookie anyways. This seems to occur only one in every 10 attempts, and seems to occur more frequently on certain machines. When this occurs we lose all of the session data that we were previously using.
          Our environment is as follows:
          We have three load balanced Sun One Web Servers fronting 6 mananged 8.1 sp5 web logic instances. We've verified that multicast is working and that we've configured the plugin/application to have a unique cookie name already. We've also set the persistence type to 'replicated'
          Only clue that we have so far comes from our plug-in logs. It seems to be complaining about connection pooling:
          Mon Jan 22 16:04:39 2007 getPooledConn: No more connections in the pool for Host[XXX.XXX.XXX.XXX] Port[8003] SecurePort[8004]
          Mon Jan 22 16:04:39 2007 Connect returns -1, and error no set to 55, msg 'A connect operation on a socket is not complete.'
          Any ideas? Thanks in advance!
          Regards,
          Ray Siu

To the OP (jirey)
This issue is 8 months old without a resolution posted, were you able to get past this?
Thanks

Similar Messages

Sun One (Netscape) Plugin: Losing HTTP Session Problem

Hi All,
We are having some trouble with HTTP sessions. Sometimes our browser will have a session cookie set but will be issued a new session cookie anyways. This seems to occur only one in every 10 attempts, and seems to occur more frequently on certain machines. When this occurs we lose all of the session data that we were previously using.
Our environment is as follows:
We have three load balanced Sun One Web Servers fronting 6 mananged 8.1 sp5 web logic instances. We've verified that multicast is working and that we've configured the plugin/application to have a unique cookie name already. We've also set the persistence type to 'replicated'
Only clue that we have so far comes from our plug-in logs. It seems to be complaining about connection pooling:
Mon Jan 22 16:04:39 2007 getPooledConn: No more connections in the pool for Host[XXX.XXX.XXX.XXX] Port[8003] SecurePort[8004]
Mon Jan 22 16:04:39 2007 Connect returns -1, and error no set to 55, msg 'A connect operation on a socket is not complete.'
Any ideas? Thanks in advance!
Regards,
Ray Siu

Check if your web app has the same cookie name (weblogic.xml) as defined in the obj.conf.
Jin

Losing user session using the AutoLoginBacking portlet

I have a need to use a cookie based login within my portal. I am using the AutoLoginBacking
portlet that is located in the tutorial.portal samples. My portal contains a
Main Book with a page (that contains the AutoLoginBacking.portlet) and two nested
books within the Main Book (one book contains 1 page, the other book contains
4 pages in a "tabbed" fashion)
I have noticed that this AutoLoginBacking Login portlet appears to be losing the
session when I move to the book containing the 4 pages within my bea portal.
This nested book contains pageflow portlets. When I traverse to page 1 of this
book, the login session appears to work fine, but when I traverse to page 4, I
seem to loose the session.
The way I see this behavior occuring is I grab the user name and place it on the
page...only on page 1 does it appear, on page 4, it appears as null and my AutoLoginBacking
portlet reverts from Logout to Login
Could this be do to the fact that the login uses a backing file instead of it
being a PageFlow portlet like the LoginController? I've read some documentation
on the bea site: http://dev2dev.bea.com/products/wlworkshop81/articles/pg_flows.jsp
that states, "Forwarding/redirecting to a nested page flow, or raising any action
on it, causes nesting to occur. The original page flow is pushed onto the "nesting
stack" until the nested page flow raises a return action, using the return-action
attribute on @jpf:forward. "
Does anyone know how to resolve this issue?
Thanks for your help.

I have a need to use a cookie based login within my portal. I am using the AutoLoginBacking
portlet that is located in the tutorial.portal samples. My portal contains a
Main Book with a page (that contains the AutoLoginBacking.portlet) and two nested
books within the Main Book (one book contains 1 page, the other book contains
4 pages in a "tabbed" fashion)
I have noticed that this AutoLoginBacking Login portlet appears to be losing the
session when I move to the book containing the 4 pages within my bea portal.
This nested book contains pageflow portlets. When I traverse to page 1 of this
book, the login session appears to work fine, but when I traverse to page 4, I
seem to loose the session.
The way I see this behavior occuring is I grab the user name and place it on the
page...only on page 1 does it appear, on page 4, it appears as null and my AutoLoginBacking
portlet reverts from Logout to Login
Could this be do to the fact that the login uses a backing file instead of it
being a PageFlow portlet like the LoginController? I've read some documentation
on the bea site: http://dev2dev.bea.com/products/wlworkshop81/articles/pg_flows.jsp
that states, "Forwarding/redirecting to a nested page flow, or raising any action
on it, causes nesting to occur. The original page flow is pushed onto the "nesting
stack" until the nested page flow raises a return action, using the return-action
attribute on @jpf:forward. "
Does anyone know how to resolve this issue?
Thanks for your help.

How to close a HTTP session when a user closes the window

Hi,
I am having problems when closing the browser of a BW web report. After I closed the browser by going File->close, I ran SM04 and found out the Plugin HTTP session hangs at the server side.
How can we terminate the Plugin HTTP session at the server side when user closes the internet browser?
I did implement a logoff function at my web template and this was implimented on the Menu page, if user clicks on the logoff, the Plugin HTTP session is terminated at server side correctly.
If user navigates to the other pages from the main page... then the logoff function was not implimented in the other pages. So many of the users are closing the windows directly. Eevn if we impliment logoff in all the subpages, As you know, 50% of time user will close the report by closing the internet browser instead of clicking the logoff. That leaves lots of hanging Plugin HTTP sessions at our server side.
Regards,
Tony

Hi,
And also take a look on the Genral property of the web template. We solved this problem by changing only this property (no extra things).
<b>Property: Value</b>
Automatic Session Management: Active
With rgds,
Anil Kumar Sharma .P
Message was edited by: Anil Kumar Sharma

Bw web report plugin http session hangs at the server side

Hi,
I am having problems when closing the browser of a BW web report. After I closed the browser by going File->close, I ran SM04 and found out the Plugin HTTP session hangs at the server side.
How can we terminate the Plugin HTTP session at the server side when user closes the internet browser?
I did implement a logoff function at my web template, if user clicks on the logoff, the Plugin HTTP session is terminated at server side correctly. But As you know, 50% of time user will close the report by closing the internet browser instead of clicking the logoff. That leaves lots of hanging Plugin HTTP sessions at our server side.
By the way, we actived our BEX service at the SICF.
Thanks for help!
JA

Hi
If you want to avoid a blank page with logoff button, add opener=0
<a href="<SAP_BW_URL CMD='LOG_OFF' ~command='logoff'
>" onClick="javascript:window.close(opener=0);">Log off</a>
If you want to close the session via X, use this code:
create a sapscript function
function closeSession()
logoff()
window.unload=CloseSession()
However, the Plugin HTTP session isn't killed.
Regards

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
          >> >
          >> >
          >>
          >
          >

How to find the list of users loggin through HTTP session

Hi All,
we are using SRM 5.5 system with ITS. I am able to find the list of concurrent users from ABAP level using report "CCUEVAL" but how do I know the list of concurrent users logged in from HTTP session?.
could you please let us know the SAP note number or any report?
Thanks in advance,
Mohan Karri

Hi Uday,
thank you very much for your prompt response.
I need a report because by end of every month I would need the average peak http users list for the reporting month.
or tell me how to find " how many users logged in through HTTP session in a day?"
Thanks
Mohan

How to get HTTP session in Applcation Module IMPL file

Hi Guys,
Can any one tell me how to get HTTP session in Applcation Module IMPL file ?
thnks

You can, but that's not a best practice.
Re: How to reach HttpContext from model Project

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

Dynamic reloading in iWS 6.0 causes my http session to be lost

Hi,
I have a problem with dynamic reloading in iWS 6.0 Sp2 on Solaris 8. I have not set the reload-interval for the class-loader, in fact i haven't included anything related to the classloader in the web-apps.xml file.
The default behaviour is observed, the classes are reloaded every 30 seconds. So far, so good.
I have seen that if a change a class, iWS reloads the entire application, destroying all the servlets in it. This destroys my HTTP session.
The same behaviour is observed in a redeployment, and in a reloading of config files.
Is there any way of avoiding this?
Thanks.
By the way, could anyone describe the classloader architecture of iWS.
Juan

Scott,
Does the problem only occur on MSIE clients? Do this work properly on Communicator? If so, you may be running into a problem with how MSIE determines the maxage for a cookie.
The criteria that IE uses for creating a new session is the length of time that a session has been alive. For this reason, when a user tries to connect to a web application on the iWS webserver through IE, the time on the client server and on the webserver must be set correctly. Otherwise, the user could experience problems with session data getting lost or discarded by the client.
This problem does not occur on Netscape browsers, as Netscape browsers set the cookie using the client-side clock and the maxage sent by the server.
Refer to this technote and see if the helps:
http://knowledgebase.iplanet.com/ikb/kb/articles/4704.html

Https session lifetime

How can lifetime of a secure session be controlled in OC4J 9.0.3-9.0.4?
Is "session-timeout" parameter in web.xml valid or is the SSL session controlled by other parameters?
We are migrating to https an application that worked properly in http mode, and sessions expire now after just a few seconds. We can't find where to config https session timeout. OC4J documentation is very vague regarding to secure applications.
Thanks,
Modulab Team

Having the same problem for more than 1 week, couldn't find a solution. Session expires in a very short time in https. We're using standalone OC4J (9.0.3). Do I have to change it with AS now ? Isn't there any other solution, patch or something like that ?
Any kind of your help would be greatly appreciated since thousands of WEB users of our institution CAN NOT use all of our https WEB apps.
Regards,

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

How can I flag HTTP session attributes to not be replicated ?

          WLS 5.1 SP8 - In memory replication of a stateful servlet. Is
          there any way to flag data that has been, or is being, loaded into
          a HTTP session so as to not be replicated ? It's a long story,
          but we have some data loaded into a hashtable, more specifically
          a Properties object, stored in our session. With the hastable
          already loaded into the HTTP session, weblogic does not detect
          when we add values to the table, and therefore does not replicate
          the changes. Which is ok since WLS is working as designed. To
          get around this we load the hashtable back into the session everytime
          we add a value to the hashtable. Yup, I know that's ugly. Anyway,
          what I'm trying to find out if is there is an attribute that we
          can set to indicate, to not replicate this data or that data.
          Something along the lines of a attribute on a per hastable value
          basis. For example, I load value A into my hashtable, then I
          need to put my hashtable into the session to get it replicated.
          Next I load value B into the hastable, and again to get it replicated
          I have to load the entire hashtable back into the session. The
          problem here is that the entire table gets replciated. Does anyone
          know if I can set an attribute on value A, when I'm adding value
          B, so as to not replicate value A when I reload the table ? Of
          course all goal is to not store so much data in the session, but
          I'm trying to find a work around until that is completed.
          Thanks,
          David


          Where can I find documentation on the details of how Weblogic decides what will
          be replicated in the HTTPSession object (for example, it only replicates attributes
          which are set or updated using "setAttribute()"?
          Prasad Peddada <[email protected]> wrote:
          >Robert,
          >
          > It is true that we replicate only when you call setAttribute in case
          >of servlets.
          >
          >In case of EJB it is slightly different. EJB sends diff's across the
          >wire. It doesn't
          >replicate the entire state with every request.
          >
          >-- Prasad
          >
          >Chris Palmer wrote:
          >
          >> I think Viresh was referring to modifying part of one attribute causing
          >the whole
          >> of that attribute (i.e. the hashtable) to be replicated.
          >>
          >> Is it actually true though that the behaviour would be different in
          >a stateful
          >> session EJB? I had assumed that the WHOLE ejb state would be replicated
          >each time
          >> (i.e. after each invocation), without even the benefit of having a
          >mechanism such
          >> as setAttribute() to flag the attributes that had changed...
          >>
          >> Chris
          >>
          >> Robert Patrick wrote:
          >>
          >> ? Huh? Since when does it always replicate the entire HttpSession?
          > We were
          >> ? told that it uses a hook in the setAttribute() call to determine
          >which
          >> ? attributes have changed and only replicates those attributes. I
          >know this to
          >> ? be the case because if I retrieve a previously stored attribute from
          >the
          >> ? HttpSession and modify it, my changes do not get replicated unless
          >I call
          >> ? setAttribute again...
          >> ?
          >> ? Robert
          >> ?
          >> ? Viresh Garg wrote:
          >> ?
          >> ? ? Servlet sessions don't work on diffs, so no matter what you do,
          >entire
          >> ? ? Hashtable will be replicated. If you want the optimization for
          >only
          >> ? ? replicating the diff ( the stuff that has changed between 2 updates)
          >,
          >> ? ? consider using stateful session bean and having hashtable part
          >of
          >> ? ? conversational state of stateful session bean.
          >> ? ?
          >> ? ? The solution that you suggested on your own for your problem is
          >not ugly
          >> ? ? as the same solution is used by many customers that I know of.
          >This is
          >> ? ? particularly a problem for people that use Java Beans and use the
          >set
          >> ? ? Property directive of Java Bean in JSP. There also in our auto
          >generated
          >> ? ? code, we put the JavaBean back in HTTP Session, when a setter is
          >called to
          >> ? ? enforce replication.
          >> ? ?
          >> ? ? Keep in mind that whatever we do for replication, we want to support
          >it
          >> ? ? using ONLY standard servlet API and we don't want to introduce
          >any WLS
          >> ? ? specific API to achieve this, and so putting value back in session
          >is the
          >> ? ? only way.
          >> ? ?
          >> ? ? Viresh Garg
          >> ? ? Principal Developer Relations Engineer
          >> ? ? BEA Systems
          >> ? ?
          >> ? ? Dave Javu wrote:
          >> ? ?
          >> ? ? ? WLS 5.1 SP8 - In memory replication of a stateful servlet.
          >Is
          >> ? ? ? there any way to flag data that has been, or is being, loaded
          >into
          >> ? ? ? a HTTP session so as to not be replicated ? It's a long story,
          >> ? ? ? but we have some data loaded into a hashtable, more specifically
          >> ? ? ? a Properties object, stored in our session. With the hastable
          >> ? ? ? already loaded into the HTTP session, weblogic does not detect
          >> ? ? ? when we add values to the table, and therefore does not replicate
          >> ? ? ? the changes. Which is ok since WLS is working as designed.
          >To
          >> ? ? ? get around this we load the hashtable back into the session everytime
          >> ? ? ? we add a value to the hashtable. Yup, I know that's ugly.
          >Anyway,
          >> ? ? ? what I'm trying to find out if is there is an attribute that
          >we
          >> ? ? ? can set to indicate, to not replicate this data or that data.
          >> ? ? ? Something along the lines of a attribute on a per hastable value
          >> ? ? ? basis. For example, I load value A into my hashtable, then
          >I
          >> ? ? ? need to put my hashtable into the session to get it replicated.
          >> ? ? ? Next I load value B into the hastable, and again to get it replicated
          >> ? ? ? I have to load the entire hashtable back into the session. The
          >> ? ? ? problem here is that the entire table gets replciated. Does
          >anyone
          >> ? ? ? know if I can set an attribute on value A, when I'm adding value
          >> ? ? ? B, so as to not replicate value A when I reload the table ?
          >Of
          >> ? ? ? course all goal is to not store so much data in the session,
          >but
          >> ? ? ? I'm trying to find a work around until that is completed.
          >> ? ? ? Thanks,
          >> ? ? ? David
          >

What are the steps to setup an HTTP Session replication clustering in oc4j9

what are the steps to setup an HTTP Session replication clustering in oc4j9.0.5

Are you sure you have the correct version number for OC4J? Is this a standalone OC4J instance, if it then the steps involved are different from the full stack. Please check the Higher Availibility guide in the documentation on OTN.
Deepak

How to do http session stickiness based on URL patterns?

Is there a feature within the WL plugin for Apache that would allow me to emulate the "jvmroute" session stickiness behaviour as provided by Tomcat and its plugin. I would like to have the control to tie requests from http clients to particular WLS servers in a cluster depending on the URL. For example http://foo.com/web01 requests would be forwarded to an appsererver app01 and so on. For all other requests (e.g http://foo.com/web), the WL plugin would do its normal load balancing ignoring the stickiness. From my understanding the WLS inbuilt http session stickiness is based on JSessionIDs which are exchanged using cookies - which is something i cannot use in my case since i want the stickiness based on URL patterns.
I am using WLS 10.0 with Apache 2.2.4 on Linux.
Thanks
Ramdas

Session is not replicated across all the servers in the Cluster.
Apache knows which server to go using the JSession ID.
There is a concept of primary and secondary, secondary is selected based on the replication groups there are configured in the cluster.
you can configure the cluster so that /web01 requests go to different cluster, and /web requests go to different cluster.
but you can get all the funtiionalities from the single cluster.
Do you have any java caching that you are not able to replicate across the cluster ?(I know this can be done too).
let me know what you are actually trying to solve by doing the behavior you explained.

Losing HTTP Sessions

Similar Messages

Maybe you are looking for