Session getting timeout

we have an application in CF5. after we migrating the IE6 to IE8, we are getting intermittent error that session is getting timeout due to the cookie is getting expired automatically or not saving in the users pc. do the people are aware of this issue. before upgrading to IE6 it was working fine. how we can avoid this or what are the alternatives.

Browser choice is in the hands of the visitor. There's little you can do about that.
It may be necessary to adapt your code to cope with new browsers. How did you set sessions using cfapplication, cfcookie and so on?

Similar Messages

Bean in Session getting inaccessible after x minutes

Hi,
we are currently devloping iViews (JspDynPapes) for EP6 SP2.
We have several iViews which put bean in the iPortalComponentSession and the HttpSession.
We have the following problem:
An iView stores information in a bean and put it into session to be displayed in a table on a JSP. Now,
if the user waits for x minutes (more than 15!) and he triggers an server side event of the ivew, the iView tries to get the bean back from session. But, if the user has done nothing for a certain period, the bean can not be accessed in that session. This raises an NullPointerException. The bean seems to be disappeared or invalid.
Do beans stored in a session get invalid or deleted after a certin period? Can this period be customized?
Thanks for your help,
Maik

Hi Maik,
not the beans stored in the session become invalid but the session itself! For session timeout settings see Anyway to Setting Portal Timeout
In addition, see http://java.sun.com/products/servlet/2.3/javadoc/javax/servlet/http/HttpSession.html#setMaxInactiveInterval(int) (which overrides the servlet-container settings for this specific session).
Hope it helps
Detlev

RDS 2012 - Session Collection Timeout vs Group Policy Timeout

Which policy applies?
The RD Session Collection timeout or the group policy?
My Remote desktop servers are in an OU at a top level with all of my other servers, so I have a administrative timeout group policy which is extremely strict to keep our administrators off server consoles. But for the RD farms I would like to have a less
strict policy so that users only get disconnected overnight and not if they go out to lunch (as an example)
I know one way to do this is to write individual group policies, but that removes the ease of control by configuring each session collection timeout via the Session Collection.

Hi Robin,
Thank you for posting in Windows Server Forum.
You can configure timeout and reconnection settings on a per user basis by using the Remote Desktop Services Extension to the Local Users and Groups snap-in or to the Active Directory Users and Computers snap-in.
Timeout and reconnection settings configured by using Remote Desktop Session Host Configuration will take precedence over timeout and reconnection settings that have been configured for a specific user account.
More information (for reference)
Configure Timeout and Reconnection Settings for Remote Desktop Services Sessions
http://technet.microsoft.com/en-us/library/cc754272.aspx
Hope it helps!
Thanks.
Dharmesh Solanki

User Session gets invalidated automatically

Hi,
          The user session gets invalidated automatically ,this happens irregularly but has been seen many times.
          Any ideas?


          Akshay <[email protected]> wrote:
          >Hi,
          >The user session gets invalidated automatically ,this happens irregularly
          >but has been seen many times.
          >Any ideas?
          hi,
          1. Check whether u have mistakenly called the session.invalidate() method if
          u are using HTTPSession
          2. Check the App.server Session Timeout
          3. If you are using Cookies check whether the cookies MaximumAge is expried before
          the
          complition of your process / transcation.
          regards,
          Elango
          Elango TR
          Sip Technologies & Exports Ltd. Elnet Software City,Chennai
          http://www.siptech.co.in
          [email protected]

How can I set a Session bean timeout

Hello !
How can I set a Session bean to time out eg. 48 hours ?
Thanks
Uiloq Slettemark

For stateful session beans you can use the timeout attribute in the orion-ejb-jar e.g.
<session-deployment timeout=1800 ..>
this is specified in seconds and Default Value: 30 (minutes)
regards
Debu

JSP session getting destroyed when second user logs in

Hi,
I am facing a session related problem in a small login program in jsp. I am using three jsp pages, login.jsp (user logs in), page1.jsp (creates a session and stores username) and page2.jsp (accesses session).
Login.jsp:
No jsp actually. Just a simple html form.
Page1.jsp:
String name=request.getParameter("Name");
session=request.getSession(true);
session.setAttribute("Name",name);
Page2.jsp:
session=request.getSession(false);
if(session.isNew())
System.out.println("new session created");
String name=session.getAttribute("Name").toString();
As expected, it works like session getting set at page1 and used at page2. It works good if users log in one by one. The problem arises when 2 (or more users with different logins) try to access the page at same time. When a new user logs in, the previous user session gets destroyed (session.isNew() becomes true and session Id changes).
Is it the way I am using sessions (missing something), or there is some setting in tomcat server to specify maximum number of logins (sessions that can be handled).
Regards
Kamal

Hi,
Thanks for reply, but I guess the problem is not clear. Let me explain..
A user logs in, he reaches first page (page1.jsp), here session is getting set. Then user goes to page2.jsp where application retrieves the information from session and uses it. It works all well.
When two (or more) user logs in.. First user logs in, he reaches page 1, session is set. But then another user logs in (different id) and a session is set for him as well. Now the problem here is that session for first user gets destroyed at this point, which is unexpected (two sessions should not conflict, on different machines).
Additionally, the problem does not happen necessarily at second login. eg. sometimes 4 users log in and when fifth one logs in, fourth gets logged out (session gets destroyed).
I am not able to figure out, whether the problem is in code (given in first post) or there is some tomcat setting responsible for this behavior.
Regards
Kamal

New Session getting created(!)

          Hi All,
          I am facing a wierd behavior. I have an application with a
          login page(jsp). User submits his authentication details,
          is authenticated in a servlet, and some of his information is
          put in the session. Later he gets "redirected" to another
          jsp(just like any other app).
          This is working fine most of the times. But randomly it is
          so happening that the jsp being redirected to does not get the
          values put in the session.
          Some more debugging showed that from login jsp to servlet, same
          session continued till the very last step(just before
          redirection). Just after
          response.sendRedirect(response.encodeRedirectURL(url));
          a new session gets created(!!). Any pointers?
          Please note I am testing all this out in a browser which is
          accepting cookies.


Urgent!!
          We have the same problem on WLS5.1.
          Any suggestions would be fine
          Regards
          Osman
          "Bijay Kumar" <[email protected]> schrieb im Newsbeitrag
          news:3d0ed20f$[email protected]..
          >
          > Hi All,
          > I am facing a wierd behavior. I have an application with a
          > login page(jsp). User submits his authentication details,
          > is authenticated in a servlet, and some of his information is
          > put in the session. Later he gets "redirected" to another
          > jsp(just like any other app).
          >
          > This is working fine most of the times. But randomly it is
          > so happening that the jsp being redirected to does not get the
          > values put in the session.
          >
          > Some more debugging showed that from login jsp to servlet, same
          > session continued till the very last step(just before
          > redirection). Just after
          > response.sendRedirect(response.encodeRedirectURL(url));
          > a new session gets created(!!). Any pointers?
          >
          > Please note I am testing all this out in a browser which is
          > accepting cookies.
          >

CF11 : cflogin doesn't "stuck" after session/login timeout

Hi,
Since migrating from CFMX7 to CF11 we are experiencing some weird failure with cflogin (using session or cookie storage).
Basically when we log-in on the application after a session/client timeout the first login doesn't last for longer than the login submit request.
The second login however is OK
I made a very simple application.cfc/index.cfm with short timeouts to check this:
<cfcomponent
output="false"
hint="I define the application settings and event handlers.">
        
        <cfset this.name = hash( getCurrentTemplatePath() ) />
        <cfset this.applicationTimeout = createTimeSpan( 0, 0, 10, 0 ) />
        <cfset this.sessionTimeout = createTimeSpan( 0, 0, 0, 10 ) />
        
        <cfset THIS.SessionManagement = true />
        <cfset THIS.ClientManagement = true />
        <cfset THIS.SetClientCookies = true />
        <cfset THIS.loginStorage = "Session" />
        <cfset THIS.clientStorage = "sidys" />
        
        <cfsetting showdebugoutput="false" />
        <cffunction
                name="OnRequestStart"
                access="public"
                returntype="boolean"
                output="true"
                hint="Fires at first part of page processing.">
                
                <cfargument
                name="TargetPage"
                type="string"
                required="true"
                />
                <cfset SetLocale("fr_FR") />
                <cfif IsDefined("Form.logout") or IsDefined("URL.logout")>
                        <cflogout />
                </cfif>
                <cflogin idletimeout="20">
                        <cfdump var="#Session#">
                        <cfinclude template="form.inc" />
<cfif not isDefined("cflogin") or (cflogin.name IS "" OR cflogin.password IS "")>
        <cfoutput>
                <form method="post">
                <b>login :</b>
                <input type="text" name="j_username" size="24" class="champ" />
                <b>passwordnbsp;:</b>
                <input type="password" name="j_password" size="15" class="champ" />
                <input type="submit" value="Login" class="button" name="submit" />
                </form>
        </cfoutput>
        <cfabort>
<cfelse>
        <cflock timeout="10" scope="Session" type="exclusive">
                <cfloginuser name="#cflogin.name#" Password="#cflogin.password#" roles="role">
                <cfset Session.id=cflogin.name />
        </cflock>
</cfif>
                </cflogin>
                <cfdump var="#Session#">
                <cfif GetAuthUser() NEQ "">
                        <cfoutput>
                                <form method="Post">
                                <input type="submit" Name="Logout" value="Logout">
                                </form>
                        </cfoutput>
                </cfif>
                 <cfreturn true />
        </cffunction>
</cfcomponent>

I created a directory and copied your code to it. The exception was that I set THIS.ClientManagement to false and commented out the lines <cfset THIS.clientStorage = "sidys" /> and <cfinclude template="form.inc" />.
The code worked as expected. The files I used in the test are shown below.
index.cfm
We are in index.cfm<br>
<cfdump var="#session#">
Application.cfc
<cfcomponent>

<cfset this.name = hash(getCurrentTemplatePath()) />
<cfset this.applicationTimeout = createTimeSpan( 1, 0, 0, 0 ) />
<cfset this.sessionTimeout = createTimeSpan( 0, 0, 0, 10 ) />

<cfset THIS.SessionManagement = true />
<cfset THIS.ClientManagement = false />
<cfset THIS.SetClientCookies = true />
<cfset THIS.loginStorage = "Session" />


<cfsetting showdebugoutput="false" />
<cffunction
                name="OnRequestStart"
                access="public"
                returntype="boolean"
                output="true"
                hint="Fires at first part of page processing.">
                
                <cfargument
                name="TargetPage"
                type="string"
                required="true"
                />
                <cfset SetLocale("fr_FR") />
                <cfif IsDefined("Form.logout") or IsDefined("URL.logout")>
                        <cflogout />
                </cfif>
                   <cflogin idletimeout="10">
                  
                   <cfif isDefined("cflogin.name") AND cflogin.name IS NOT "" AND cflogin.password IS NOT "">
                         
                         <cfloginuser name="#cflogin.name#" Password="#cflogin.password#" roles="role">
                         <cfset Session.id=cflogin.name />
                  <cfelseif getAuthUser() IS "">
                          
                          <cfinclude template="loginForm.cfm">
                          <cfabort>
                 </cfif>
                </cflogin>
        <cfif getAuthUser() NEQ "">
            <cfinclude template="logoutForm.cfm">
            
        </cfif>
    <cfreturn true />
    </cffunction>
</cfcomponent>
loginform.cfm
<div>
<form method="post">
<b>login :</b>
<input type="text" name="j_username" size="24" class="champ" />
<b>password :</b>
<input type="password" name="j_password" size="15" class="champ" />
<input type="submit" value="Login" class="button" name="submit" />
</form>
</div>
logoutform.cfm
<div>
<form method="Post">
<input type="submit" Name="Logout" value="Logout">
</form>
</div>
You will observe that, like you, I set the session and cflogin timeout to a low test value, 10 seconds. When I first opened the URL to index.cfm in the browser, the login form was duly displayed. I entered a name and password and submitted the form.
I got the index.cfm page again. That time it had the logout button and a dump of the session scope. The dump contained an id (my username), confirming that login was still active. When I re-requested index.cfm, repeatedly in the browser, within around 4 or 5 seconds, its contents remained unchanged. I then waited for about 15 to 20 seconds, for the login and session to time out.
I then repeated the procedure of logging in and re-requesting index.cfm every 4 or 5 seconds. I got the same result: its contents remained unchanged. That is the expected behaviour of cflogin and session.

How to prevent session getting killed

Hi All,
I am trying to execute a procedure which contains a long running query .
The query takes so much time to execute that the session gets killed .
Can anybody please let me know what should I do to prevent my session being killed/
Is there any parameter to be set to do so?
Many thanks in advance.

try to avoid posting 2 questions for the same subject
Can I alter the default profile

I am trying to upload a podcast rss and I am getting timeouts

I am attepting to upload an rss podcast but I am getting timeouts. Does anyone know how to correct this?

It depends on whether your server is failing to respond, or whether the problem lies with the iTunes Store's submission process. Try subscribing manually to your feed from the 'Advanced' menu and see how it behaves: if it fails to load there, or is very slow to do so, then you should look at your server. If it's OK, then the problem may lie with the Store and all you can really do is wait for a bit then try again.

Inactive Sessions Getting Automatically Generated in Database

I am facing a strange problem of getting huge number of inactive sessions getting generated th the database server which leads to it's connection closure.
The Error reads as "Failed to check out an Application due to connection failure of Application Module."
This happens each time I execute the following code:
String amDefName = "amendprgo.model.CSDInvFRCAmendPrgoServices";
String configName = "CSDInvFRCAmendPrgoServicesLocal";
ApplicationModule app1 = Configuration.createRootApplicationModule(amDefName,configName) ;
String voInstanceName="prgoHdrRO";
ViewObject prgoHdrROVO =app1.createViewObjectFromQueryStmt(voInstanceName,"select * from INV_PRGO_HDR");
prgoHdrROVO.setWhereClause("PRGO_ID="+tempRow.getAttribute("PrgoId")+" and DEPOT_CD = '0' and ITEM_CAT = 'I3' ");
prgoHdrROVO.executeQuery();
if(prgoHdrROVO.getEstimatedRowCount()>0){
return true;
I know there is a process of creating connection and View Object in Model part in JDeveloper, but I want to know why this problem happens.

ApplicationModule app1 = Configuration.createRootApplicationModule(amDefName,configName) ;is your problem as it causes at least one (sometimes more) connections to open. As you don't free the resource after using it the connection remains open even if you can't access it anymore.
You should call Configuration.releaseApplicationModule(...), with the application module you created before returning.
On the other side you shoulnd not even call createRootApplicationModule in the first place (as it causes trouble if you don't deeply know what the framework do with a root application module).
Can you tell us the use case which make you call createRootApplicationModule()? We might find a better solution.
Timo
Edited by: Timo Hahn on 19.05.2011 13:45
PS: something to read http://blogs.oracle.com/jdevotnharvest/entry/when_to_use_createrootapplicationmodule_in_oracle_adf and http://radio-weblogs.com/0118231/2009/08/20.html#a959

Why do I get timeout when deploying SQL Server data source in Weblogic Admin Console?

Hi all
I'm attempting connectivity between WLS 10.3.6.0 and SQL Server 2008R. I've downloaded sqljdbc4.jar and added to the end of the Weblogic Classpath in commEnv.cmd. Then I set up a data source in Admin Console and pressed the Test Data Source button - success. But when I tick the box to deploy to AdminServer it hangs for ages and I get timeout exception.
Any ideas?
Many thanks
James

Make sure the web server settings between the QA and the Production servers are also compatible.
I suspect your suspecion about permissions is the closest to the answer. But this is a little out of my depth of expertise.
Realize that ColdFusion default behavior is to NOT generate and actual swf FILE. Rather what it does is generate the swf content in memory and directly deliver it to the client. But if the web server is configured to look for an actual file system file you may have a clash going on

Editing session gets canceled

I am starting an editing session programmatically, so clicking outside of the cell being edited does not stop the session.
But even when I have resizableColumns="false" sortableColumns="false" if I move a mouse with a left button down over a column separator the session gets canceled.
How can I get rid of this effect?
Thanks

Well, funny enough, but that's exactly what I want: clicking anywhere outside of the grid does not end the editing session.
Tell me then please, what would the proper way of achieving such effect be?
Thanks

Systemd/user: tmux sessions get killed when stopping systemd session

Following the wiki guide on systemd/user, I am now starting my X sessions using systemd unit files for my user.
My problem: when I quit X or exit the systemd session (for example through $ systemctl --user exit), my tmux sessions get killed along with it. Note, I do not start tmux with unit files, but simply through invoking “tmux” in a virtual terminal. I have also tried detaching the tmux session before quitting the systemd session, but to no avail.
How can I make my tmux sessions survive X closing?

That is beacuse tmux becomes a child process of the systemd --user session. So it gets caught up in the cgroup and everything. What I have done is I start a system service of tmux as my user (I have creatively come up with the name "[email protected]"). Here is what I've got, that has been working for me:
% cat /etc/systemd/system/[email protected]
[Unit]
Description=Start detached tmux session
After=multi-user.target
Before=shutdown.target
[Service]
Type=forking
User=%I
WorkingDirectory=%h
ExecStart=/usr/bin/tmux new-session -d -s %u
ExecStop=/usr/bin/tmux kill-session -t %u
Restart=always
[Install]
WantedBy=multi-user.target
Last edited by WonderWoofy (2013-04-27 22:35:27)

Unable to read AsynchronousSocketChannel after getting timeout exception

i am trying to read some data on the server using a AsynchronousSocketChannel .
I have this scenario :
1- Call channel.read : this will print "Received"
2- Call channel.read : this should fail due to timeout exception.
3- Call channel.read : I am sending data in this case but I got the exception "Reading not allowed due to timeout or cancellation"
Below is the source code
My environment is :
OS : Windows 7
JDK :
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
package com.qmic.asynchronous;
import java.io.InputStream;
import java.io.PrintWriter;
import java.net.InetAddress;
import java.net.InetSocketAddress;
import java.net.Socket;
import java.nio.ByteBuffer;
import java.nio.channels.AsynchronousChannelGroup;
import java.nio.channels.AsynchronousServerSocketChannel;
import java.nio.channels.AsynchronousSocketChannel;
import java.nio.channels.CompletionHandler;
import java.util.concurrent.ConcurrentLinkedQueue;
import java.util.concurrent.ExecutorService;
import java.util.concurrent.Executors;
import java.util.concurrent.Future;
import java.util.concurrent.TimeUnit;
public class NIOChannel {
     public static void main(String[] args) {
          try{
               MyAsynchronousTcpServer server = new MyAsynchronousTcpServer();
               Thread serverThread = new Thread(server);
               serverThread.start();
               Socket socket = new Socket(InetAddress.getByName("127.0.0.1"), 9001, InetAddress.getByName("127.0.0.1"), 9003);
               socket.setSoTimeout(30000);
               socket.setKeepAlive(true);
               if (socket.isConnected()){
                    PrintWriter dos = new PrintWriter(socket.getOutputStream());
                    InputStream input = socket.getInputStream();
                    byte[] buffer = new byte[1024];
                    // Data of the first call
                    dos.print("ABCDEFGH");
                    dos.flush();
                    byte[] data = new byte[50];
                    socket.getInputStream().read(data);
                    // Print the result from server, written in handler of first read operation.
                    System.out.println("Result is:" + new String(data));
                    if (data.length > 0){
                         Thread.sleep(10000); // Wait for 10 Seconds so the second read on the server will fail.
                    // Data of the third call
                    dos.print("ABCDEFGH");
                    dos.flush();
          }catch(Exception ex){
               ex.printStackTrace();
     class MyAsynchronousTcpServer implements Runnable{
          final int SERVER_PORT = 9001;
          final String SERVER_IP = "127.0.0.1";
          private int THREAD_POOL_SIZE = 10;
          private int DEFAULT_THREAD_POOL_SIZE = 2;
          ConcurrentLinkedQueue<ListenHandler> handlers = new ConcurrentLinkedQueue<ListenHandler>();
          boolean shutDown = false;
          public void run(){
               //create asynchronous server-socket channel bound to the default group
               try {
                    // Create the ChannelGroup(thread pool).
                    ExecutorService executorService = Executors.newFixedThreadPool(THREAD_POOL_SIZE);
                    AsynchronousChannelGroup group = AsynchronousChannelGroup.withCachedThreadPool(executorService, DEFAULT_THREAD_POOL_SIZE);
                    AsynchronousServerSocketChannel asynchronousServerSocketChannel =
                         AsynchronousServerSocketChannel.open(group);
                    if (asynchronousServerSocketChannel.isOpen())
                         //bind to local address
                         asynchronousServerSocketChannel.bind(new InetSocketAddress(SERVER_IP, SERVER_PORT));
                         while(!shutDown){
                              Future<AsynchronousSocketChannel> asynchronousSocketChannelFuture =asynchronousServerSocketChannel.accept();
                              final AsynchronousSocketChannel channel = asynchronousSocketChannelFuture.get(); // Timeout can be specified in the get() function, thread is blocked here
                              System.out.println("New channel created successfully");
                              // First call, should print Result of call 1 is : 10 (size of ABCDEFGH)
                              ByteBuffer buffer1 = ByteBuffer.allocateDirect(250);
                              channel.read(buffer1, 5, TimeUnit.SECONDS, null, new CompletionHandler<Integer, Object>() {
                                   @Override
                                   public void completed(Integer result, Object attachment) {
                                        System.out.println("Result of call 1 is :" + result);
                                        ByteBuffer response = ByteBuffer.wrap("Received".getBytes());
                                        channel.write(response);
                                   @Override
                                   public void failed(Throwable exc, Object attachment) {
                                        exc.printStackTrace();
                              Thread.sleep(3000);
                              // Second read, should print error InterruptedByTimeoutException
                              ByteBuffer buffer2 = ByteBuffer.allocateDirect(250);
                              channel.read(buffer2, 5, TimeUnit.SECONDS, null, new CompletionHandler<Integer, Object>() {
                                   @Override
                                   public void completed(Integer result, Object attachment) {
                                        System.out.println("Result of call 2 is :" + result);
                                   @Override
                                   public void failed(Throwable exc, Object attachment) {
                                        exc.printStackTrace();
                              Thread.sleep(9000);
                              // Second read operation was failed, no try to read again . AN EXCEPTION IS THROWN HERE : Reading not allowed due to timeout or cancellation
                              ByteBuffer buffer3 = ByteBuffer.allocateDirect(250);
                              channel.read(buffer3, 5, TimeUnit.SECONDS, null, new CompletionHandler<Integer, Object>() {
                                   @Override
                                   public void completed(Integer result, Object attachment) {
                                        System.out.println("Result of call 3 is :" + result);
                                   @Override
                                   public void failed(Throwable exc, Object attachment) {
                                        exc.printStackTrace();
                    else
                         System.out.println("The asynchronous server-socket channel cannot be opened!");
               catch (Exception ex)
                    ex.printStackTrace();
                    System.err.println(ex);
     }

I'm having the same "Unable to read the SIM card" issue. My phone is less than two months old, the unable to read SIM card issue started about a week after I purchased the phone. That was followed by a host of erratic, sporadic issues to the phone becomes unusable and the only way to temporarily fix it is to remove the battery for a few seconds. I've gone through the factory reset with Verizon reps where I purchased the phone from as well as with a Verizon online Chat representative. In a nutshell, I got a ticket to send the phone back to Samsung in Plano, Texas to get the phone fixed, I am going to do that today because this problem is ridiculous.

Session getting timeout

Similar Messages

Maybe you are looking for