Sebastian,
On windows we had an issue where sessions were being switched - i.e. client
sessions were sent to the wrong clients allowing people to see each others
information. Needless to say what havoc that this caused. I searched this mail list
and found someone who had a similar problem and had logged the problem with
Allaire/Macromedia. They acknowledged it as a bug but never supplied an answer. I
resurrected the problem on this list and sure enough I received a bunch of e-mail from
people who were experiencing the same thing but assumed it was their application, not
JRun that was the culprit. After a big uproar on this list, Macromedia responded with
a patch. We applied the patch, but the problem still occured. Our solution was to go
with another Java server. I have to say that none are
easier to use than JRun, but I am afraid we just don't have faith in JRun. I really
liked it - easy to use and administer (EJB was a little more cumbersome, but I think
that the ejipt solution was more stop-gap than anything).
Sebastian Millies <[EMAIL PROTECTED]> wrote: Hello,
in February, Ben Groeneveld posted a question about losing
session attributes:
http://www.mail-archive.com/[email protected]/msg05805.html
Has this question been answered?
I seem to run into a similar problem: JRun 3.1 build 26414 under
RedHat 7.2 seems to create unexpected new sessions. The problem
is easily reproducible. It happens every time when I request a new JSP
page, but not when I forward to the same JSP I'm already on (I'm using Struts).
I log the session ID to the event-log, and see a new session is created,
causing me to lose previously stored session attributes.
It's not a time-out issue. The web.xml file sets the session timeout to 30 minutes.
It doesn't seem to be a permission problem: Setting directory permissions
to 777 and running JRun as root makes no difference. I've checked
my Browser settings (IE 6) to accept all Cookies. Choice of JVM (Sun, Blackdown
or IBM) also has no influence.
It's not a concurrency or load issue, either: I'm talking one single user, one single
browser session.
The strange thing is, this ONLY happens in the JRun/Linux combination
- the same web application works just fine in Tomcat 3.2.4 on the same
Red Hat box, and in JRun3.1 under NT 4.0 SP6 (although that's JRun build 16777).
I guess that means the application itself is guilt-free, although I've not been able
to
create a scaled-down example to send to the people at Macromedia.
I'm considering switching to Tomcat for production use. This problem diminishes
my faith in the JRun server - recalling that there have been issues with session
tracking before.
As it is, I'm flummoxed, and would be grateful for any assistance.
Best,
Sebastian
--------------------------------------------------------------------------
Sebastian Millies, IDS Scheer AG
Postfach 10 15 34, 66015 Saarbr�cken
Zimmer 2.34, email: [EMAIL PROTECTED]
fon +49-681-210-3221, fax +49-681-210-1311
______________________________________________________________________
This list and all House of Fusion resources hosted by CFHosting.com. The place for
dependable ColdFusion Hosting.
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
