blocks|key|141527|text|<session-config>
++++<session-timeout>-1</session-timeout>
</session-config>|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|141528|您可以在会话永不过期的情况下使用"-1“。因为您不知道线程完成所需的时间。|unstyled|141529|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>&lt;session-config&gt;
 &lt;session-timeout&gt;-1&lt;/session-timeout&gt;
&lt;/session-config&gt;
</code></pre>

You can use "-1" where the session never expires. Since you do not know how much time it will take for the thread to complete.

blocks|key|141581|text|通过javascript定期(比如每60秒一次)向服务器发送AJAX+Http请求，以维护与服务器的会话，直到文件上传完成。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141582|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Send AJAX Http Requests to the server periodically (say once for every 60 seconds) through javascript to maintain session with the server until the file upload gets completed.

blocks|key|359508|text|Hacky的方式：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|359509|当需要较大的up-/download时，可以通过编程方式增加会话超时。|359510|session.setMaxInactiveInterval(TWO_HOURS_IN_SECONDS)|code-block|syntax|javascript|359511|当该过程结束时，您可以将超时设置回其默认值。|359512|但是..。当您使用Java，并且up-/download不需要花费完整的一个小时时，更好的方法是异步运行任务(例如通过JMS+)。|359513|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Hacky way:

You could increase the session timeout programmatically when a large up-/download is expected.

<pre><code>session.setMaxInactiveInterval(TWO_HOURS_IN_SECONDS)
</code></pre>

When the process ends, you could set the timeout back to its default.

But.. when you are on Java EE, and the up-/download doesn't take a complete hour, the better way was to run the tasks asynchronous (via JMS e.g.).

blocks|key|359363|text|<session-config>
++++++++<session-timeout>-1</session-timeout>
</session-config>|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|359364|在上面的代码"60"+stands+for+the+minutes.中，会话将在60+minutes.之后过期，所以如果您想要更多时间。例如，描述您的会话永远不会过期的-1。|unstyled|offset|length|style|CODE|359365|entityMap^0|0|6|S|14|B|2C|2|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|N|8|@$G|O|H|P|I|J]|$G|Q|H|R|I|J]|$G|S|H|T|I|J]]|9|@]|A|$]]|$1|K|3|-4|5|F|7|U|8|@]|9|@]|A|$]]]|L|$]]

<pre><code>&lt;session-config&gt;
 &lt;session-timeout&gt;-1&lt;/session-timeout&gt;
&lt;/session-config&gt;
</code></pre>

In the above code <code>"60" stands for the minutes.</code> The session will expired after <code>60 minutes.</code> So if you want to more time. For Example <code>-1</code> that is described your session never expires.

blocks|key|141718|text|你可以看到许多选项作为你的问题的答案，但是你可以在会话永远不会过期的地方使用"-1“。因为您不知道线程完成所需的时间。例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141719|+++<session-config>
++++++++<session-timeout>-1</session-timeout>
++++</session-config>|code-block|syntax|javascript|141720|或者，如果您不希望因为某些原因而发生超时：|141721|<session-config>
++++<session-timeout>0</session-timeout>
</session-config>|141722|另一种选择是将数字增加到1000，等等，bla，bla，bla。|141723|但是如果你真的想停止，并且你认为你的应用程序没有必要强制用户注销，那么只需添加一个注销按钮，用户将决定何时退出。|141724|这是你可以做什么来解决这个问题，如果你不需要强制登出，并在您正在加载的文件，这可能需要时间的服务器和您的计算机速度和大小的文件。|141725|
+++|141726|只需评论它或删除它，就是这样！谭塔兰，谭谈！|141727|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|14|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

You can see many options as answer for your question, however you can use "-1" where the session never expires. Since you do not know how much time it will take for the thread to complete. E.g.:

<pre><code> &lt;session-config&gt;
 &lt;session-timeout&gt;-1&lt;/session-timeout&gt;
 &lt;/session-config&gt;
</code></pre>

Or if you don't want a timeout happening for some purpose:

<pre><code>&lt;session-config&gt;
 &lt;session-timeout&gt;0&lt;/session-timeout&gt;
&lt;/session-config&gt;
</code></pre>

Another option could be increase the number to 1000, etc, etc, bla, bla, bla.

But if you really want to stop and you consider that is unnecessary for your application to force the user to logout, just add a logout button and the user will decide when to leave.

Here is what you can do to solve the problem if you do not need to force to logout, and in you are loading files that could take time base on server and your computer speed and the size of the file.

<pre><code>&lt;!-- sets the default session timeout to 60 minutes. --&gt;
 &lt;!-- &lt;session-config&gt;
 &lt;session-timeout&gt;60&lt;/session-timeout&gt;
 &lt;/session-config&gt; --&gt;
</code></pre>

Just comment it or deleted that's it! Tan tararantan, tan tan!

blocks|key|359561|text|对于此问题，您可以通过两种方式声明时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|359562|1)要么给你太长的时间，让你的文件读取在这段时间之间完成。|359563|<session-config>
++++<session-timeout>+1000+</session-timeout>
</session-config>|code-block|syntax|javascript|359564|2)声明一个永远不会过期的时间。|359565|<session-config>
++++<session-timeout>-1</session-timeout>
</session-config>|359566|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

you can declare time in two ways for this problem..

1) either give too long time that your file reading is complete in between that time.

<pre><code>&lt;session-config&gt;
 &lt;session-timeout&gt; 1000 &lt;/session-timeout&gt;
&lt;/session-config&gt;
</code></pre>

2)declare time which is never expires your session.

<pre><code>&lt;session-config&gt;
 &lt;session-timeout&gt;-1&lt;/session-timeout&gt;
&lt;/session-config&gt;
</code></pre>

blocks|key|359643|text|我推荐的另一个选择是创建一个单独的应用程序，它是无状态的，可以接收大文件。在主应用程序上，打开一个新窗口或iframe，它将接受文件并通过该窗口发送文件，然后在使用Javascript开始上传后隐藏该窗口或iframe。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|359644|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Another option I would recommend is to create a separate application that is stateless that would take the large file. On your main app open a new window or iframe that will accept the file and send it through that window then hide the window or iframe once the upload has started using Javascript.

blocks|key|141561|text|如果您不希望因为某些原因而发生超时：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141562|<session-config>
++++<session-timeout>0</session-timeout>
</session-config>|code-block|syntax|javascript|141563|应该完全不会导致超时，->无限|141564|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

If you don't want a timeout happening for some purpose:

<pre><code>&lt;session-config&gt;
 &lt;session-timeout&gt;0&lt;/session-timeout&gt;
&lt;/session-config&gt;
</code></pre>

Should result in no timeout at all -> infinite

blocks|key|359690|text|你应该考虑将大文件分成块，并依靠多线程功能一次处理多个文件，或者使用TimerTask让整个过程作为后台任务运行，并编写另一个查询来了解它的状态，如果你可以知道一个文件或记录的处理时间，浏览器会显示一个进度条。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|359691|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You should consider splitting the large file to chunks and rely on multi threading capabilities to process more than one file at a time 
OR 
let the whole process run as a background task using TimerTask and write another query to know the status of it form the browser including a progress bar can be shown if you can know the process time of a file or record.

blocks|key|141610|text|通常，当请求处理发生时，会话不会过期。我认为有一个LB或其他什么东西，它读取整个文件，然后调用web容器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141611|这可能会导致延迟，从而导致会话过期。|141612|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Usually the session will not expire when request processing is happening. I think there is an LB or something in between which reads the entire file and then invokes the web container.

This might be causing a delay which is leading to expiry of the session.

I am trying to understand the real purpose of session configuration in Web.xml for session timeout.

<pre><code>&lt;!-- Session Configuration --&gt;
&lt;session-config&gt;
 &lt;session-timeout&gt;60&lt;/session-timeout&gt;
&lt;/session-config&gt;
</code></pre>

Now let me tell you about my question.

My application is importing/uploading a .txt file, which is bound to take more than 1 hour, since there are millions of records to be imported.
But the session times out after 1 hour though my application is still importing that .txt file which is in progress.
Such an application should not timeout as the application is doing some task in the background.

Session TimeOut in web.xml

服务器

容器

Java

我正在尝试理解在Web.xml中为会话超时配置会话的真正目的。<session-config> <session-timeout>60</session-timeout></session-config>现在让我告诉你我的问题。我的应用程序正在导入/上传一个.txt文件，由于有数百万条记录要导入，这势必要花费1小时以上的时间

问web.xml中的会话TimeOut
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问web.xml中的会话TimeOutEN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问web.xml中的会话TimeOut
EN