display problem on tomcat 4 when 'dir' attribute is used
hi; i have a simple JSP (written with JSF) which accepts a text input and outputs the input in a line below. also, i am using the 'dir' attribute with a rtl value. deploying this JSP on tomcat 5 and 4 yields 2 different results: on tomcat 4, the result of the outputed Text displays all the characters are in reverse. e.g: hello input is displyed as olleh in the output. on tomcat 5 there is no problem. its like the 'dir' attribute affects something in tomcat 4 and doesn't on tomcat 5. P.S my preffered output is what tomcat 5 produces. can anybody please explain these differences? thanks.
Re: DataSource and JNDI problem at Tomcat 4+Apache
On Thu, 2003-10-02 at 01:12, Peter Harrison wrote: On Thu, 02 Oct 2003 01:01, Tuna Vardar wrote: What can be the cause for the exception I mentioned above? Any comments? Sounds very similar to the issue I had when trying to move to 4.1.27. When I moved from 4.0.4 to 4.1.27 the exact same issue arose. If you put everything under a context it should be okay. I placed everything under a context in server.xml, but still same problem existed. Have you simply added the connector to an existing install, or did you try a new install with the connector? Also, the warp connector is actually old - isn't the Apache connector for 4.1.X the AJP connector? I added connector to an existing install. And finally I used JK 1.3 AJP connector. And now application works fine with Apache 1.3. Regards, Peter Thanks. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DataSource and JNDI problem at Tomcat 4+Apache
Hello, I got a datasource definition at server.xml and the web application gets connection to DB by getting datasource object from JNDI. I defined the Resource between GlobalNamingResources tags. And I defined ResourceLink from Context definition. This configuration works perfectly with Tomcat 4.1. I use MySQL 3.23 as a database server. But when application is plugged to Apache Web Server by using org.apache.catalina.connector.warp.WarpConnector connector, I got following exception: Cannot load JDBC driver class 'null' java.lang.NullPointerException It seems like Apache + Tomcat 4 configuration doesn't get the DataSource description and its parameters from server.xml. MySQL drivers are placed both in TOMCAT_HOME/common/lib and web application's WEB_INF/lib directory. What can be the cause for the exception I mentioned above? Any comments? Br, tuna - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DataSource and JNDI problem at Tomcat 4+Apache
On Thu, 02 Oct 2003 01:01, Tuna Vardar wrote: What can be the cause for the exception I mentioned above? Any comments? Sounds very similar to the issue I had when trying to move to 4.1.27. When I moved from 4.0.4 to 4.1.27 the exact same issue arose. If you put everything under a context it should be okay. Have you simply added the connector to an existing install, or did you try a new install with the connector? Also, the warp connector is actually old - isn't the Apache connector for 4.1.X the AJP connector? Regards, Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
problem using Tomcat 4 with JBoss 3.0.6
Hi all,
I've a problem using Tomcat 4 with JBoss 3.0.6, as I can't reach JBoss
Server with the same instructions that run from a standalone application. I
didn't configure Tomcat for JNDI, but I wrote everything inside the code,
follows the Exception I found and the related piece of code (the exception
occurs between the 2 log messages).
Thanks in advance for your help!
Stefano Moro
** Exception ***
NamingException in PushMessage: javax.naming.CommunicationException [Root
exception is java.rmi.ServerException: RemoteException occurred in server
thread; nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments; nested
exception is:
java.net.MalformedURLException: no protocol: Group/Apache]
Code
public PushMessage(String terminal, String message)
{
this.terminal = terminal;
this.message = message;
jndiProps = new java.util.Properties() ;
jndiProps.setProperty(java.naming.factory.initial,
org.jnp.interfaces.NamingContextFactory ) ;
jndiProps.setProperty(java.naming.factory.url.pkgs,
org.jboss.naming:org.jnp.interfaces ) ;
jndiProps.setProperty(java.naming.provider.url,jnp://localhost:1099);
}
[...]
Context context = null;
QueueConnectionFactory qcf = null;
try
{
context = new InitialContext(jndiProps);
LogSrv.logMessage( debug 1 *);
qcf = (QueueConnectionFactory) context.lookup(
QUEUE_CONNECTION_FACTORY_JNDI_NAME);
LogSrv.logMessage( debug 2 *);
}
catch (NamingException Ne)
{
LogSrv.logMessage(NamingException in PushMessage: + Ne.toString());
Ne.printStackTrace();
}
[...]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Problem with Tomcat 4.x and SSL
Hello Tomcat team, i will use Tomcat 4.x or Tomcat 5.x with J2SDK 1.2.2. I have download and installed JSSE 1.0.3 as installed extension by copying the tree JAR-Files into my %JAVA_HOME%\jre\lib\ext directory. I have done all the points of your how to ssl with tomcat of your site of http://jakarta.apache.org/tomcat/tomcat-4.0-doc/ssl-howto.html http://jakarta.apache.org/tomcat/tomcat-4.0-doc/ssl-howto.html I have done the changes of server.xml successfully and start tomcat successfully too. My problem is when i try to write on my browser (IE 5.5 SP2) https://localhost:8443/ https://localhost:8443 than the browser show Page not found. Otherwise when i write http://localhost http://localhost/ than comes the index-page of tomcat, that means the setup of tomcat was successfully. I don´t no what for configuring is failled and i hope for your help. Best regards Lazaros Zachariadis
RE: DTD problem starting tomcat 4
That helped. But that was the DOCTYPE since August. Why did it work before? Has something changed at Sun? --Dean On Thu, 9 Jan 2003, Turner, John wrote: I'm pretty sure it's you, not Tomcat. My web.xml is different: ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd; Note Sun Microsystems, Inc., not Sun Micro as it is in yours. Or is that an edit/typo? John -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: DTD problem starting tomcat 4
Not sure. I've never really paid any attention to it. John -Original Message- From: Dean Anderson [mailto:[EMAIL PROTECTED]] Sent: Friday, January 10, 2003 4:03 PM To: Tomcat Users List Subject: RE: DTD problem starting tomcat 4 That helped. But that was the DOCTYPE since August. Why did it work before? Has something changed at Sun? --Dean On Thu, 9 Jan 2003, Turner, John wrote: I'm pretty sure it's you, not Tomcat. My web.xml is different: ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd; Note Sun Microsystems, Inc., not Sun Micro as it is in yours. Or is that an edit/typo? John -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: DTD problem starting tomcat 4
That should not make any differences since Tomcat (aka the Digester) use local copy of the DTD. So even if the URL is wrong, internally, Tomcat uses the previous one and your app should still deploy. As why the URL change, I guess it is related when java.sun.com where re-designed :-( -- Jeanfrancois Turner, John wrote: Not sure. I've never really paid any attention to it. John -Original Message- From: Dean Anderson [mailto:[EMAIL PROTECTED]] Sent: Friday, January 10, 2003 4:03 PM To: Tomcat Users List Subject: RE: DTD problem starting tomcat 4 That helped. But that was the DOCTYPE since August. Why did it work before? Has something changed at Sun? --Dean On Thu, 9 Jan 2003, Turner, John wrote: I'm pretty sure it's you, not Tomcat. My web.xml is different: ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd; Note Sun Microsystems, Inc., not Sun Micro as it is in yours. Or is that an edit/typo? John -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DTD problem starting tomcat 4
Since about the 4th of January, I've been getting an Invalid PUBLIC ID error on the following web.xml file: This app has been working for quite a while, and hasn't been changed. Likewise, tomcat4 hasn't been changed. When I try the java.sun.com url, it works. Whats up? Also, I couldn't figure out how to make it load a local dtd file. It seems unwise to depend on remote links for critical services... (it seems unwise to use tomcat, if it will break without modification... I am somewhat alarmed.) ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Micro//DTD Web Application 2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd; web-app /web-app Tomcat was restarted several times in december, without complaints. vxml.av8.net_log.2003-01-04.txt:2003-01-04 19:40:13 Invalid PUBLIC ID: -//Sun Micro//DTD Web Application 2.3//EN vxml.av8.net_log.2003-01-09.txt:2003-01-09 19:50:26 Invalid PUBLIC ID: -//Sun Micro//DTD Web Application 2.3//EN vxml.av8.net_log.2003-01-09.txt:2003-01-09 19:55:57 Invalid PUBLIC ID: -//Sun Micro//DTD Web Application 2.3//EN vxml.av8.net_log.2003-01-09.txt:2003-01-09 20:39:17 Invalid PUBLIC ID: -//Sun Micro//DTD Web Application 2.3//EN -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: DTD problem starting tomcat 4
I'm pretty sure it's you, not Tomcat. My web.xml is different: ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd; Note Sun Microsystems, Inc., not Sun Micro as it is in yours. Or is that an edit/typo? John -Original Message- From: Dean Anderson [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 9:50 PM To: Tomcat Users List Subject: DTD problem starting tomcat 4 Since about the 4th of January, I've been getting an Invalid PUBLIC ID error on the following web.xml file: This app has been working for quite a while, and hasn't been changed. Likewise, tomcat4 hasn't been changed. When I try the java.sun.com url, it works. Whats up? Also, I couldn't figure out how to make it load a local dtd file. It seems unwise to depend on remote links for critical services... (it seems unwise to use tomcat, if it will break without modification... I am somewhat alarmed.) ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Micro//DTD Web Application 2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd; web-app /web-app Tomcat was restarted several times in december, without complaints. vxml.av8.net_log.2003-01-04.txt:2003-01-04 19:40:13 Invalid PUBLIC ID: -//Sun Micro//DTD Web Application 2.3//EN vxml.av8.net_log.2003-01-09.txt:2003-01-09 19:50:26 Invalid PUBLIC ID: -//Sun Micro//DTD Web Application 2.3//EN vxml.av8.net_log.2003-01-09.txt:2003-01-09 19:55:57 Invalid PUBLIC ID: -//Sun Micro//DTD Web Application 2.3//EN vxml.av8.net_log.2003-01-09.txt:2003-01-09 20:39:17 Invalid PUBLIC ID: -//Sun Micro//DTD Web Application 2.3//EN -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Problem with Tomcat 4
I have a installation of Apache/Tomcat which is working...sort of. I have everything configured according to the snippets I will post below. Here is the strangeness: I initially configured Tomcat as standalone and was able to pull up the servlet app perfectly well. Everything performed as expected. Now when I call the URL mapped to Tomcat, I get a blank, well-formed HTML page! That is 'HTMLBODY/BODY/HTML'. My pertinent configs are below. I setup the workers.properties as loadbalanced because I could only find a complete config in this form. --First, My httpd.conf stuff-- # Mod_jk configuration LoadModulejk_module libexec/mod_jk.so AddModule mod_jk.c JkWorkersFile /usr/local/apache/conf/workers.properties JkLogFile /usr/local/apache/logs/mod_jk.log JkLogLevelinfo JkLogStampFormat [%a %b %d %H:%M:%S %Y] JkMount /servlets/* loadbalancer JkMount /*.jsp loadbalancer --Next,my workers.properties-- # Using Single Tomcat Instance using AJPV13 # #workers.tomcat_home=/usr/local/tomcat #workers.java_home=/usr/local/jdk ps=/ worker.list=tomcat1, loadbalancer # Definition for Ajp13 worker (Ajp12 left to readers imagination) # worker.tomcat1.port=8009 worker.tomcat1.host=remotehost.wellinx.com worker.tomcat1.type=ajp13 # Specifies the load balance factor when used with a load balanced # worker # # Note: # - lbfactor must be 0 # - The lower the lbfactor the less work done by worker worker.tomcat1.lbfactor=100 # # Load Balancer worker # # # The loadbalancer (type lb) worker performs weighted round-robin # load balancing with sticky sessions. # Note: # If a worker dies, the load balancer will check its state #once in a while. Until then all work is redirected to peer #worker. worker.loadbalancer.type=lb worker.loadbalancer.balanced_workers=tomcat1 # # END workers.properties # --Finally, my server.xml stuff-- !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=10 maxProcessors=75 acceptCount=10 debug=0/ Context path=/servlets docBase=/usr/local/tomcat/webapps/servlets debug=0 reloadable=false Logger className=org.apache.catalina.logger.FileLogger prefix=wellinx- suffix = .log timestamp=true/ /Context Any ideas why I get a blank page? The logs show that the connection is being made from the apache server to the java server through port 8009. Debugging showed that the request was received and finished by Tomcat, but the response was the blank page. Thanks! Ben Ricker Web Security System Administrator Wellinx.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
performance problem with Tomcat 4 + ISAPI + IIS 5
We encounter a real problem of performances on our server. We were able to determinate that the problem comes from the ISAPI filter (neither the webapp nor the hardware nor the tomcat installation...). A more detailed description of the case is available ( with duke dollars ! ;) ) at : http://forum.java.sun.com/thread.jsp?forum=33thread=244516 Has someone had the same problem or got some info ? Regards. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Problem configurating tomcat 4 with IIS
Hello there! I'm following the steps in the document at http://members.ozemail.com.au/~lampante/howto/tomcat/iisnt/index.html to setup tomcat 4 on Windows 2000 with IIS as an nt service. when I try to execute the order jk_nt_service -s tomcat, I get the following error: StartService failed - Acesso Denegado (0x5) Acceso Denegado is Access Denied. Any ideas, please? thanks in advance, Alex - Do You Yahoo!? Yahoo! Messenger! Comunicación instantánea gratis con tu gente.
xalan.jar problem with tomcat 4 ...
Trying not to embarress myself a second time with a 'spelling mistake', I think I've checked everything this time *cross fingers* First, xalan.jar is installed with the xalan-j port, and I have build.properties set right for it: reilly2001# grep xalan build.properties xalan.jar=/usr/local/xalan-j2.1.0/bin/xalan.jar reilly2001# ls -lt /usr/local/xalan-j2.1.0/bin/xalan.jar -rw-r--r-- 1 root wheel 732330 Jan 14 00:29 /usr/local/xalan-j2.1.0/bin/xalan.jar Build goes through to building what I believe is the docs ... and then fails looking for: /usr/local/java_misc/jakarta-tomcat-4.0.1-src/webapps/tomcat-docs/build.xml:80: java.lang.NoClassDefFoundError: javax/xml/transform/Source Which, from what I can tell, is part of xalan.jar: reilly2001# find /usr/local/xalan-j2.1.0 -name Source* -print | grep transform /usr/local/xalan-j2.1.0/docs/apidocs/javax/xml/transform/class-use/Source.html /usr/local/xalan-j2.1.0/docs/apidocs/javax/xml/transform/class-use/SourceLocator.html /usr/local/xalan-j2.1.0/docs/apidocs/javax/xml/transform/SourceLocator.html /usr/local/xalan-j2.1.0/docs/apidocs/javax/xml/transform/Source.html /usr/local/xalan-j2.1.0/src/javax/xml/transform/SourceLocator.java /usr/local/xalan-j2.1.0/src/javax/xml/transform/Source.java But, I'm also getting: build-main: [style] DEPRECATED - xslp processor is deprecated. Use trax or xalan instead. at the top ... but I am using xalan, aren't I? -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Problem running tomcat 4 in apache 1.3.19
See http://marc.theaimsgroup.com/?l=tomcat-devm=99020542608948w=2 (the ant-dev mailinglist...). The Exception btw is caused by a bug... If you call the http://servername/examples/servlets/ you get the nullpointer exception, because it cannot find what the welcome page should be (eg index.html) and passes the null value. If you call http://servername/examples/servlets/index.html it works fine.. Have fun, Martin van den Bemt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 23, 2001 12:53 PM To: [EMAIL PROTECTED] Subject: Re:Problem running tomcat 4 in apache 1.3.19 Would you please tell me how to compile web_apps.so. I got error with pthread ... (serveral people had the same error but I could not find the solution on tomcat list) when i start apache. Someone suggested that module should be compiled with LD_LIBRARY_PATH properly set up, but I checked it and it still does not work. My machine: Linux Mandrake with kernel 2.4.1 IBMJdk1.3 gcc version: 2.95.3 Regards, Tomek /) Tomasz Sucharzewski (\ / )Unix/Sybase Administrator ( \ _( (__ Web-Application Development_) )_ (((\ \ /_ Electronic Data Processing Department _\ / /))) ( \_/ / ING Bank N.V. \ \_/ ) \ / \ / \_/ phone: (+48 22) 820-41-58 \_/ / / mobilephone: (+48 606) 666-015\ \ / / email: [EMAIL PROTECTED] \ \ Reply Separator Subject:Problem running tomcat 4 in apache 1.3.19 Author: [EMAIL PROTECTED] Date: 01-05-21 23:58 Hi, After a struggle to get tomcat 4 running on my systen (running on Linux with jdk 1.3.1), I tried to configure tomcat 4 to run with apache. After following (some) of the instructions in the server.xml and other sources I got the web_webapp.so actually compiled and running in apache ( which means : apache doesn't crash when I start it up..). I mounted the examples to be served by tomcat 4 and when I go there (say http://servername/examples/ I get a nice directory overview and I want to click on servlets. then I get a nice exception (without exception..) : java.lang.NullPointerException at javax.servlet.http.HttpUtils.getRequestURL(HttpUtils.java:338) at org.apache.catalina.connector.HttpResponseBase.toAbsolute(HttpResp onseBase.j ava:669) at org.apache.catalina.connector.HttpResponseBase.sendRedirect(HttpRe sponseBase .java:1072) at org.apache.catalina.connector.HttpResponseFacade.sendRedirect(Http ResponseFa cade.java:150) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultS ervlet.jav a:1084) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:519) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) snap a lot All this stuff is working great on the 8080 port, which is handled by tomcat itself. Can anybody enlighten me on what is going on or how to correctly configure (and compile) the connection to tomcat Note : the example of mounting _INFO_ to eg /tomcatinfo/ works... Thanx for the help.. Mvgr, Martin van den Bemt - ATTENTION: The information in this electronic mail message is private and confidential, and only intended for the addressee. Should you receive this message by mistake, you are hereby notified that any disclosure, reproduction, distribution or use of this message is strictly prohibited. Please inform the sender by reply transmission and delete the message without copying or opening it. Messages and attachments are scanned for all viruses known. If this message contains password-protected attachments, the files have NOT been scanned for viruses by the ING mail domain. Always scan attachments before opening them. -
Problem running tomcat 4 in apache 1.3.19
Hi, After a struggle to get tomcat 4 running on my systen (running on Linux with jdk 1.3.1), I tried to configure tomcat 4 to run with apache. After following (some) of the instructions in the server.xml and other sources I got the web_webapp.so actually compiled and running in apache ( which means : apache doesn't crash when I start it up..). I mounted the examples to be served by tomcat 4 and when I go there (say http://servername/examples/ I get a nice directory overview and I want to click on servlets. then I get a nice exception (without exception..) : java.lang.NullPointerException at javax.servlet.http.HttpUtils.getRequestURL(HttpUtils.java:338) at org.apache.catalina.connector.HttpResponseBase.toAbsolute(HttpResponseBase.j ava:669) at org.apache.catalina.connector.HttpResponseBase.sendRedirect(HttpResponseBase .java:1072) at org.apache.catalina.connector.HttpResponseFacade.sendRedirect(HttpResponseFa cade.java:150) at org.apache.catalina.servlets.DefaultServlet.serveResource(DefaultServlet.jav a:1084) at org.apache.catalina.servlets.DefaultServlet.doGet(DefaultServlet.java:519) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) snap a lot All this stuff is working great on the 8080 port, which is handled by tomcat itself. Can anybody enlighten me on what is going on or how to correctly configure (and compile) the connection to tomcat Note : the example of mounting _INFO_ to eg /tomcatinfo/ works... Thanx for the help.. Mvgr, Martin van den Bemt
