SOLVED - Re: Desperate: Tomcat 5.5. j_security_check

2006-12-22 Thread Gregor Schneider
Hi guys, first of all: Thanks to all of you for your help! We got it (JDBC-REALM) working now, however, it was a long way. The resolution in short words: We installed a vanilla JDK 1.5 from SUN plus a vanilla Tomcat 5.5 from Apache, same error occured, empty string in the query for j_username

Re: Desperate: Tomcat 5.5. j_security_check

2006-12-22 Thread Mark Thomas
Gregor Schneider wrote: > now i've tried to set up a memory-realm, and i'm getting the following > error for a change: > > DEBUG http-8080-Processor4 > org.apache.catalina.authenticator.FormAuthenticator > - Authenticating username 'tomcat' > DEBUG http-8080-Processor4 > org.apache.catalina.authen

Re: Desperate: Tomcat 5.5. j_security_check

2006-12-22 Thread mylene
Hi Gregor, Shouldn't you add a clueuser to your tomcat-users.xml? Mylene On 12/22/06, Gregor Schneider <[EMAIL PROTECTED]> wrote: god, what a bloody crap, i'm about to dump this whole tomcat into the bin and jump out of the window now i've tried to set up a memory-realm, and i'm getting t

Re: Desperate: Tomcat 5.5. j_security_check

2006-12-22 Thread Gregor Schneider
god, what a bloody crap, i'm about to dump this whole tomcat into the bin and jump out of the window now i've tried to set up a memory-realm, and i'm getting the following error for a change: DEBUG http-8080-Processor4 org.apache.catalina.authenticator.FormAuthenticator - Authenticating user

RE: Desperate: Tomcat 5.5. j_security_check

2006-12-21 Thread Caldarale, Charles R
> From: Martin Gainty [mailto:[EMAIL PROTECTED] > Subject: Re: Desperate: Tomcat 5.5. j_security_check > > http://developers.sun.com/sunstudio/articles/options.html > yes I would recompile with -xtarget=generic to stay 32bit generic or > to specifically target 64 bit recompil

Re: Desperate: Tomcat 5.5. j_security_check

2006-12-21 Thread Martin Gainty
age - From: "Gregor Schneider" <[EMAIL PROTECTED]> To: Sent: Thursday, December 21, 2006 3:28 PM Subject: Desperate: Tomcat 5.5. j_security_check > Hi list, > > we're really, really deperate here. > > We have developed a web-app on Debian Edge with Tom

RE: Desperate: Tomcat 5.5. j_security_check

2006-12-21 Thread Caldarale, Charles R
> From: Gregor Schneider [mailto:[EMAIL PROTECTED] > Subject: Desperate: Tomcat 5.5. j_security_check > > This whole setup worked on Debian Sarge with a single processor on a > 32bit-machine, but it does not work on Debian Edge Dual CPU Dual Core > Opteron 64bit. No,

Re: Desperate: Tomcat 5.5. j_security_check

2006-12-21 Thread Gregor Schneider
oliver, sorry, j_user_name was just a typo in my post. sure, the parameter is j_username, and as you can see in the logs, it's read properly from the form by j_security_check. f.y.i., this is the form, which actually is working on our dev-machine but not in our production-environment:

Re: Desperate: Tomcat 5.5. j_security_check

2006-12-21 Thread olivier nouguier
j_username should give you something better ;-) On 12/21/06, Gregor Schneider <[EMAIL PROTECTED]> wrote: Hi list, we're really, really deperate here. We have developed a web-app on Debian Edge with Tomcat 5.5.17 using Form-based Authentication with a JDBC-realm. Database is a MySQL 4.1.11

Desperate: Tomcat 5.5. j_security_check

2006-12-21 Thread Gregor Schneider
Hi list, we're really, really deperate here. We have developed a web-app on Debian Edge with Tomcat 5.5.17 using Form-based Authentication with a JDBC-realm. Database is a MySQL 4.1.11 However, when we try to authenticate, the content passed from j_security_check -> mysql-driver -> MySQL alway