How to suppress implicit conversions when spliiting up the query string into parameters

2006-06-29 Thread KHZ (SAW) 
Hi world.
 
We’ve severe problems if a URL contains an umlaut. For URL usage we encode
strings using UTF-8, i.e. “ü” (which would be ü in HTML) can be viewed
as “%c3%bc”. Getting the request parameter I’ld expect the same string. But
we see 2 characters. Obviously it’s interpreted as ISO8859-1 and so we see
“ü”. It’s obviously p.i.t.ar. to convert such a thing directly to “ü”.
 
As a workaround we split the query string ourselves (Java) and store it in a
hash map. Using these data we can apply the decoding using UTF-8. There it
works good. But the application is big. So we want to remove the real
problem.
 
I assume that it’s some setting in some XML file. How can we suppress such
implicit conversions?
 
If my assumption is wrong that Tomcat splits up the query string then please
give me a hint which tool is responsible for that.
 
Best regards,Karl-Heinz.

AW: Error while connecting to MySQL database

2006-06-29 Thread KHZ (SAW) 
Hi Navaneeth.

Check whether you've an XML file according to your web app in the
conf/Catalina/ directory.

When removing the elder web app this file is also removed.

Regards,Karl-Heinz.


-Ursprüngliche Nachricht-
Von: Gordon Smith [mailto:[EMAIL PROTECTED] 
Gesendet: Donnerstag, 29. Juni 2006 15:51
An: 'Tomcat Users List'
Betreff: RE: Error while connecting to MySQL database

If Class.forName throws a null pointer exception, chances are it can't find
the driver because you have a Tomcat configuration problem or other
classpath-related problem relating to driver setup.  Please check out the
documentation on tomcat.apache.org for the details for your version of
Tomcat.

As an aside, please consult the MySQL documentation about setting a root
password and disabling unneeded accounts in the database.  You are leaving a
gaping security hole in your app by not establishing a root db pwd.  

Once you put a root pwd in place, there's no reason to share it in this
forum as long as you can connect by using that pwd from the MySQL client.

Hope this helps.

Cheers,
Gordon Smith

-Original Message-
From: navaneethan loganathan [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 28, 2006 7:57 PM
To: users@tomcat.apache.org
Subject: Error while connecting to MySQL database

Hi,

I am facing a problem with my Apache-Tomcat-MySQL installation.MyEnvironment
is as follows:
Redhat ES4(2.6.9-5.EL), Apache-Tomcat-5.5.15, MySQL 4.1.12, Java version
1.5.0_06, Apache-Tomcat connector ajp13,
mysql-connector-java-3.2.0-alpha-bin.jar.

After installation and configuration I am unable to connect to the database
through the application and getting the following exception in
catalina.outlog file.

java.lang.NullPointerException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)

However, I am able to browse my site perfectly with
http://localhost/index.jsp (the connector also configured perfectly, so that
I do not need to specify the port number in URL).
 I put the mysql-connector-java-3.2.0-alpha-bin.jar file in
$CATALINA_HOME/common/lib and also specified in CLASSPATH.

I am able to login to MySQL through command and access the database without
any problem.

My db.properties is as under:

# MySQL database access properties
db.driver = org.gjt.mm.mysql.Driver
db.url = jdbc:mysql://localhost:3306/testdb
db.user = root
db.pwd =
Any clue will be very much helpfull.Thanks in advance.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AW: How to suppress implicit conversions when spliiting up the query string into parameters

2006-06-30 Thread KHZ (SAW) 
Thanks a lot, Hassan.
 
Now we’ve decoded things in the split up components. So knowing how to
suppress is obsolete.
 
It has to be set in server.xml.
 
Regards,   Karl-Heinz.
 
 
  _  

Von: KHZ (SAW) [mailto:[EMAIL PROTECTED] 
Gesendet: Donnerstag, 29. Juni 2006 14:35
An: 'users@tomcat.apache.org'
Betreff: How to suppress implicit conversions when spliiting up the query
string into parameters
 
Hi world.
 
We’ve severe problems if a URL contains an umlaut. For URL usage we encode
strings using UTF-8, i.e. “ü” (which would be ü in HTML) can be viewed
as “%c3%bc”. Getting the request parameter I’ld expect the same string. But
we see 2 characters. Obviously it’s interpreted as ISO8859-1 and so we see
“ü”. It’s obviously p.i.t.ar. to convert such a thing directly to “ü”.
 
As a workaround we split the query string ourselves (Java) and store it in a
hash map. Using these data we can apply the decoding using UTF-8. There it
works good. But the application is big. So we want to remove the real
problem.
 
I assume that it’s some setting in some XML file. How can we suppress such
implicit conversions?
 
If my assumption is wrong that Tomcat splits up the query string then please
give me a hint which tool is responsible for that.
 
Best regards,Karl-Heinz.

Is it possible to configure Tomcat in a way that it uses different CPUs for different parallel requests?

2006-07-04 Thread KHZ (SAW) 
Hi world.
 
Are there Tomcat settings for achieving such a behaviour?
 
Regards,   Karl-Heinz.