gzilla/show_bug.cgi?id=22716
NotSerializableException not caught by PersistentManager
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RE
gzilla/show_bug.cgi?id=24368
Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager
thread
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RE
gzilla/show_bug.cgi?id=24368
Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager
thread
[EMAIL PROTECTED] changed:
What|Removed |Added
Se
gzilla/show_bug.cgi?id=24368
Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager
thread
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RE
gzilla/show_bug.cgi?id=24368
Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager
thread
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity
gzilla/show_bug.cgi?id=24368
Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager
thread
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RE
gzilla/show_bug.cgi?id=24368
Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager
thread
[EMAIL PROTECTED] changed:
What|Removed |Added
Stat
gzilla/show_bug.cgi?id=24368
Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager
thread
--- Additional Comments From [EMAIL PROTECTED] 2003-11-10 21:05 ---
Regarding the proposed fixes, I would argue that it would be helpful to include
a log statement
gzilla/show_bug.cgi?id=24368
Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager
thread
--- Additional Comments From [EMAIL PROTECTED] 2003-11-10 19:51 ---
With TC 5, there's no possible way the background thread can die like this. All
it will do
gzilla/show_bug.cgi?id=24368
Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager
thread
--- Additional Comments From [EMAIL PROTECTED] 2003-11-10 19:46 ---
Created an attachment (id=9033)
Patch for TC5 to fix th
gzilla/show_bug.cgi?id=24368
Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager
thread
--- Additional Comments From [EMAIL PROTECTED] 2003-11-10 19:46 ---
Created an attachment (id=9032)
Patch for TC4 to fix th
gzilla/show_bug.cgi?id=24368
Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager
thread
--- Additional Comments From [EMAIL PROTECTED] 2003-11-09 20:21 ---
Present in TC4 and TC5. I have submitted patches to tomcat-dev. BTW, the code
is not shared as the
gzilla/show_bug.cgi?id=24368
Unhandled Exception in PersistentManagerBase.processExpires() kills PersistentManager
thread
Summary: Unhandled Exception in
PersistentManagerBase.processExpires() kills
PersistentManager thread
Product: To
gzilla/show_bug.cgi?id=22716
NotSerializableException not caught by PersistentManager
Summary: NotSerializableException not caught by PersistentManager
Product: Tomcat 4
Version: 4.1.24
Platform: All
OS/Version: All
Status: NEW
Se
Clere, Jean-Frederic wrote:
Hi,
I am trying to use the PersistentManager. But it seems it is not working:
- maxActiveSessions=0:
No session are possible. (That is not what says the server.xml ).
- saveOnRestart=true:
A part creating the file it seems it is doing nothing.
Has someone already
Hi,
I am trying to use the PersistentManager. But it seems it is not working:
- maxActiveSessions=0:
No session are possible. (That is not what says the server.xml ).
- saveOnRestart=true:
A part creating the file it seems it is doing nothing.
Has someone already use it?
I need a more
gzilla/show_bug.cgi?id=5799
PersistentManager overwrites session every 60 seconds
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RE
gzilla/show_bug.cgi?id=5799
PersistentManager overwrites session every 60 seconds
Summary: PersistentManager overwrites session every 60 seconds
Product: Tomcat 4
Version: 4.0.1 Final
Platform: PC
OS/Version: Windows NT/2K
Statu
Bip Thelin typed the following on 02:35 PM 4/5/2001 -0700
>This is a minor change so you can specify the store to use within server.xml.
Thanks Bip, I've applied these patches. I also added a check in PersistentManager's
start() method to check whether Store is null, since this is the default if
If you get this email twice please ignore. Our emailserver experienced problems
yesterday
so I never think my email was delivered.
..bip
-
This is a minor change so you can specify the store to use within server.xml.
Here's how you can change the Store use from server.xml:
This is a minor change so you can specify the store to use within server.xml.
Here's how you can change the Store use from server.xml:
I'll hope to have a first cut of the JDBCStore soon.
..bip
[ PersistentManager.java ]
The following patches shouldn't affect default useage of Catalina. To try
them out, add the following to the server.xml section for the webapp
you want to use PersistentManager for:
Store
Added setManager() and getManager() methods to give the Store
a reference to the Man
22 matches
Mail list logo
