There is a new project at http://centaurus.sourceforge.net which adresses these
problems. Unfortunately the docs are only in german right now.
Michael
-Ursprungliche Nachricht-
Von: Michal Kwiatek [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 11. Mai 2004 09:42
An: [EMAIL PROTECTED]
And we switched from FreeTDS (which AFAIK is the predecessor of jTDS) to the MS
driver years ago because is had more functionality. We use it with heavy
statements and result sets and had never any problem with it ;-)
Michael
-Ursprungliche Nachricht-
Von: Tuncay Baskan
what I would do is to try a few things.
1. increase the ramp up time and see if that affects it. It could be
the load balancer is helping tomcat handle the load
My ramp up is sufficient.
2. build the latest JMeter and use the distribution graph I wrote to
look at the requests. the new
Hi Steve,
I am jumping into this discussion rather late and I am probably not going to
answer any of your questions. I just would like to add that I examined the
session persistence and listeners topic also very deep some weeks ago. After
all I found it not really practical because the servlet
Before calling session.invalidate() I now interrupt the thread which causes a database
rollback. Now my JMeter-Tests run fine.
As for stopping the thread before invalidating a session,
how will you
control that? You could perform this action as part of the general
logout page, but what
Hello,
I try to correctly reinitialize my sessions after a session deserialization. For this
I try to use the ServletContextListener and the HttpSessionActivationListener. I use
Tomcat 4.1.30.
From testing I saw that during a startup (with a serialized session available) the
I asked for your opinion because I wanted to know if anyone can imagine for what
purpose the sessionDidActivate event is useful if not for reinitilization work after
the session has become deserialized.
It it is for that purpose, then IMO there must be fully initialized context at that
point.
We can talk opinions all we want -- if it's a grey area in
the spec, and
your container (Tomcat, in this case) does things a certain way then
that's how it goes.
But if people would agree with me we could try to get a next spec more specific.
That's my intention.
Have you at least
Yoav, thanks for your understanding. I've just read the 2.4 spec regarding this and
cannot any big clarifications. Can you point me to the chapter where you found it.
I find this issue logged as bug #30344. It's exactly what I mean. But IMO this not
described in the spec, neither 2.3 nor 2.4.
But it's not explicit enough, and for that you should ask the Servlet
Expert Group (you can find a link for that on the JSR154 home page).
Yes, I sent them a comment.
Best regards
Michael
-
To unsubscribe, e-mail: [EMAIL
Daniel
Thanks for the setup. I was looking for a long time for a working combination of
binary, config files and install instruction.
I have manually installed the old JK connector a lot of times without any problems but
it never worked for me for JK2 with the install instruction that ships
Hello,
I have used the 'old' JK connector for a long time with Tomcat 4.0 and 4.1 and IIS. I
had never any problems with stability.
Very recently I figured out how to set up the JK2 connector (thanks Daniel).
Now I wonder if I should from now use JK2 instead. What are the pros and cons?
Best
Hello,
I wonder how I can activate logging for the JK2 ISAPI connector?
With the old JK there were the registry keys log_file and log_level. But they seem not
to work with JK2. I also tried logFile and logLevel.
Any ideas?
Michael
13 matches
Mail list logo
