To make the long and short of it. Nothing in my application(s) should LIVE over
a restart.
So serialization does NOT make sense for me at all. Users timeout after
inactivity too which otherwise might be a good reason for using it (maybe it
would be fine there as the timeout is pretty long).
H
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ray,
On 1/12/14, 8:45 AM, Ray Holme wrote:
> [S]erialization causes some problems in apache-tomcat-7.0.35
>
> I have several applications and run on fedora linux. I have used
> many releases of fedora and tomcat.
>
> My applications are characteri
Nice, I do that for many things, but not all of it. You are right, I probably
could do that.
Nice food for thought!
:=]
On Monday, January 13, 2014 11:31 AM, Daniel Mikusa
wrote:
On Jan 13, 2014, at 8:37 AM, Ray Holme wrote:
> OK, that makes perfect sense. We are NOT talking about SESS
Another option would be to read them from the db once, at system
startup, and then keep them static from there. You're still hitting
your db, but not on an ongoing basis.
On 1/13/2014 9:02 AM, Ray Holme wrote:
Oh, I missed one comment from Daniel before (embedded and I did not see on the
On Jan 13, 2014, at 9:02 AM, Ray Holme wrote:
> Oh, I missed one comment from Daniel before (embedded and I did not see on
> the first pass, sorry).
>
> No, you don't know the application so I would like to explain that some
> information kept in the "shared application" beans is very static,
I have (in the past) dealt with transient so OK, makes sense.
Not familiar with "putting in container" to shield from Apache serialization.
Will look for writeup. Thanks.
On Monday, January 13, 2014 10:12 AM, Johan Compagner
wrote:
>IS THERE A WAY TO STOP WARNINGS AND TELL TOMCAT NOT TO
>
>
> IS THERE A WAY TO STOP WARNINGS AND TELL TOMCAT NOT TO SERIALIZE A BEAN?
>
> Right now, I have stopped warnings but caused other problems.
>
>
just don't add those beans to a session or if you do add them make sure
that they are in containers and that those fields are transient
then those fie
On Jan 13, 2014, at 8:37 AM, Ray Holme wrote:
> OK, that makes perfect sense. We are NOT talking about SESSION objects (where
> I am defining session as login to logout of a USER as I mentioned before,
> perhaps you are defining this as "while tomcat is up" - I can see either
> def.). These ty
Oh, I missed one comment from Daniel before (embedded and I did not see on the
first pass, sorry).
No, you don't know the application so I would like to explain that some
information kept in the "shared application" beans is very static, needs to be
loaded from the DB and is used everywhere by
OK, that makes perfect sense. We are NOT talking about SESSION objects (where I
am defining session as login to logout of a USER as I mentioned before, perhaps
you are defining this as "while tomcat is up" - I can see either def.). These
type beans are all fine, but I would actually never want t
On Jan 12, 2014, at 8:45 AM, Ray Holme wrote:
I haven't been following this thread, but I wanted to clarify a couple comments
here just to make sure someone reading this in the future doesn't get the wrong
ideas.
> serialization causes some problems in apache-tomcat-7.0.35
No. What causes pr
erialization causes some problems in apache-tomcat-7.0.35
I have several applications and run on fedora linux. I have used many releases
of fedora and tomcat.
My applications are characterized by
a) all use a DB (firebird)
b) all use both jsp and java servlets
c) all use transient java
12 matches
Mail list logo
