Re: Tomcat5 java.lang.OutOfMemoryError

2005-01-11 Thread Ryan Stewart
I posted a how-to on this just yesterday I think. Try the archives. It's 
typically a good idea to check there before you post.

-Original Message-
From: SARMIENTO Claudia COGA[EMAIL PROTECTED]
To: 'Tomcat Users List'tomcat-user@jakarta.apache.org
Date: Mon Jan 10 10:49:20 PST 2005
Subject: Tomcat5  java.lang.OutOfMemoryError

Hello all:
I have problems with memory in Tomcat, this happen when the servlet try to
forward the result jsp only if the result is too big (a set of rows in a
period date)
Th bean doesn't have problems, but the servlet yes, so i think i need to
change my configuration to set more memory at startup. (Actually is the
default)

I work in Tomcat 5.0.25 under W2000 with tomcat as a service, i read that i
have to re-install tomcat
(http://marc.theaimsgroup.com/?l=tomcat-userm=104331482014538w=2) the
notes is for tomcat 4, is the same for tomcat 5.0?

Thanks!
Claudia

PD:

This is the exactly error:

2005-01-10 11:26:42 StandardWrapperValve[invoker]: Servlet.service() para
servlet invoker lanzó excepción
java.lang.OutOfMemoryError


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Re: Out of Memory when compiling JSP (Struts app on Tomcat 4.1.27)

2005-01-08 Thread Ryan Stewart
If you're nervous about registry work, back up your registry. Then open regedit 
and find:
HKLM\SYSTEM\CurrentControlSet\Services\Apache Tomcat 4.1\Parameters

(You can choose a different control set as well, and for Tomcat 5 users, this 
is under ...\Services\Tomcat5\Parameters.)

You should see some Java startup options there already. They are named JVM 
Option Number x where x is a zero-based option count. The x *must* be 
incremented by one each time. If you skip a number, only the options before the 
skip will be loaded. e.g. If you set options 0, 1, 3, 4, and 5, then only 0 and 
1 will be loaded. The rest will be ignored. Also, you must set the JVM Option 
Count key to the total number of options you have set. This will be one more 
than your highest option number. Think of it as an array where the options are 
the elements and the option count is the array length. I would guess that's how 
it's implemented.

-Original Message-
From: David Johnson[EMAIL PROTECTED]
To: Tomcat Users Listtomcat-user@jakarta.apache.org
Date: Thu Jan 06 07:40:27 PST 2005
Subject: Re: Out of Memory when compiling JSP (Struts app on Tomcat 4.1.27)

Cool. Thanks

the question is how do I get all of these options working when tomcat
runs as a service...




On Thu, 6 Jan 2005 15:28:30 -, Dale, Matt [EMAIL PROTECTED] wrote:
 It could also be that the Permanent Generation has filled up, look up the 
 docs on how to increase that or start with -XX:MaxPermSize=128M
 
 -Original Message-
 From: SANTOS, DANIEL (SBCSI) [mailto:[EMAIL PROTECTED]
 Sent: 06 January 2005 14:57
 To: Tomcat Users List; [EMAIL PROTECTED]
 Subject: RE: Out of Memory when compiling JSP (Struts app on Tomcat
 4.1.27)
 
 Chachany,
 
 It sounds like it's using the default of -Xmx64m.  Probably the best way
 to troubleshoot out or memory errors is to see what is really happening
 with garbage collecting, the same way that you tune it.  If you can add
 these options, then the JVM will spit out all kinds of useful
 information:
 
 -XX:+PrintTenuringDistribution -XX:+PrintGCDetails -Xverbosegc
 
 But it sounds like the problem is that it's not getting the options.
 What you really need to figure out is exactly how the service is getting
 started.  For instance, if it's calling tomcat.exe then I don't believe
 that the JAVA_OPTS environment variable is ever looked at since that is
 in the startup.sh and startup.bat files (I'm not 100% certain about that
 however).
 
 Find out how it's starting.  Also, post the version of Java you are
 using (since the options I gave you above don't work on all versions, I
 think 1.4 and up or 1.3 and up).  But the -Xverbosegc works all the way
 back to 1.1 if I'm correct.
 
 Daniel
 
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: Thursday, January 06, 2005 8:25 AM
 To: tomcat-user@jakarta.apache.org
 Subject: Out of Memory when compiling JSP (Struts app on Tomcat 4.1.27)
 
 Hi all
 
 I'm working on an application currently that is experiencing some
 intermittent memory problems when installed onto our integration
 test server, but not on the development staff's local laptops.
 
 I have attempted to increase the maximum memory available to Tomcat by
 creating a global environment variable (because tomcat runs as a
 service)
 
 JAVA_OPTS=-Xmx512M
 
 Which doesnt seem to have made a difference. Is this the best way to
 increaqte the memory available to an application? Is my syntax wrong?
 Are there other options I can set that will help?
 
 The weird thing is that when I look at the memory usage of Tomcat.exe,
 the most memory it has used is 110,000
 
 there seems to be no pattern to the memory errors (as usual) and it
 happens a lot when compiling JSP files.
 
 The system memory seems high, but not horribly so. I see the following
 in Task Manager
 
 MEM Usage = 885,000 (varies)
 
 Commit Charge:
 Limit : 2,522,244
 Peak : 958,260
 
 Anyone?
 
 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]
 
 
 -
 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]



___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: web.xml servlet mappings, url pattern and CGI.PATH_INFO (tomcat 4.1.31)

2005-01-04 Thread Ryan Stewart
I don't know anything about ColdFusion, but if I understand you right, you're 
wanting to tack extra information onto a url beyond the file name and retrieve 
it somewhere for use, like so:
http://server/context/index.cfm/someParam

Then the page is actually index.cfm, and when it is run it will be able to see 
the someParam. Is this correct? If so, my first thought is a query string. 
Can you use one instead of the above?

Next, here's why what you're trying to do with the url-pattern won't work. The 
'*' in a url-pattern isn't actually a normal wildcard. There are only a couple 
of specific ways it can be used:
1) /* or /something/* or /.../* - This is path mapping. When a request is made, 
the longest matching pattern is used.
2) *.something - This is extension mapping. Anything with the extension you 
specify will be matched.

(For full rules on url-pattern matching, see the Servlet spec, chapter 11.)

I suppose you could map a pattern like /cfm/* to your own servlet, which would 
extract the file name from the path and request it from the cfm servlet and 
also do something with your extra information.

This early in the morning, I can't think of a good way to do what you want 
easily.

-Original Message-
From: Jack Eidsness[EMAIL PROTECTED]
To: Tomcat Users Listtomcat-user@jakarta.apache.org
Date: Mon Jan 03 13:09:01 PST 2005
Subject: web.xml servlet mappings, url pattern and CGI.PATH_INFO (tomcat 4.1.31)

I am new to the J2EE world, so hopefully I will not use terms incorrectly.

Due to circumstances beyond my control, coldfusion has been retrofitted 
into a J2EE web application and I have recently taken on the task of 
trying to make previously existing cfm code work as part of a tomcat 
installation.   I have found (so far) only one thing that doesn't work 
like it used to, and its a significant problem for me.

CGI apps can have a false path appended after the script name, which is 
written into the CGI.PATH_INFO variable, so that it can be available to 
scripts.  It would seem that tomcat is less flexible than apache httpd 
about when this information will be supplied.  At least, jakarta-tomcat 
4.1.31 doesn't want to play ball.  I have not yet experimented with 
version 5.x.

I have found a lot of discussion of this matter, but no conclusive 
answer as to what the workaround is, nor, as i fear, that there is no 
viable workaround.

By default, my coldfusion war file came with this in the web.xml:

   servlet-mapping id=macromedia_mapping_3
  servlet-nameCfmServlet/servlet-name
  url-pattern*.cfm/url-pattern
   /servlet-mapping

attempting to browse (via the coyote thingie) to
http://{server}/cfusion/htdocs/index.cfm
will bring up the right page, but
http://{server}/cfusion/htdocs/index.cfm/fake_path
this gets me a 404.

So far, I have only found one way to make tomcat give me the correct 
PATH_INFO -
If I do this:
   url-pattern/htdocs/index.cfm/*/url-pattern
then I will be able to run the right script and CGI.PATH_INFO is set to 
/fake_path.

Naturally, if you have more than a couple situations where you use 
PATH_INFO, this configuration becomes quickly unmanageable, and 
unreasonable.  (grep -iRl path_info . will only get me so far)

Is there a way to make this work without naming every cfm file that 
might use PATH_INFO in the web.xml?

For anyone interested in helping, here are some things that I have tried 
that did not work (in each case, I have tried it as a replacement, 
breaking the normal way it works for possible experimental value, or as 
an additional servlet-mapping):

If I do this:
  url-pattern*.cfm/*/url-pattern
I get an error in the jakarta logs when the web.xml is read;

java.lang.IllegalArgumentException: Invalid url-pattern *.cfm/* in 
servlet mapping

I looked up the source code and it says you can't start a servlet 
mapping's url-pattern with *. and have a / in the pattern at once. :/

If I do this (nevermind that its not exactly what I want):
   url-pattern*.cfm*/url-pattern
Then the second * is not expanded as a wildcard. i.e. a file named 
index.cfm* (literal '*' character) could be processed as a cfm file.

If I do this
   url-pattern/*.cfm/*
I get a 404.

Thanks in advance for any time that any of you spend considering this issue,



___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Re: JSP compilation problem

2005-01-03 Thread Ryan Stewart
As QM mentioned, Tomcat 5.0 doesn't support Java 5.0 out of the box, so to 
speak. I believe there's a patch you need to make them play nicely. Tomcat 5.5, 
as he pointed out, is very tight with Java 5.0.

-Original Message-
From: Frank W. Zammetti[EMAIL PROTECTED]
To: Tomcat Users Listtomcat-user@jakarta.apache.org
Date: Sun Jan 02 11:46:49 PST 2005
Subject: Re: JSP compilation problem

Very interesting... Switching to JDK 1.4.2 solved the problem.  I didn't 
even do an uninstall/reinstall... I always install my SDK to c:\java, so 
all I did was rename it and copy the directory over from another PC, so 
any paths and registry settings should still be valid, there's just an 
older version in it's place.  I made sure to delete the Tomcat work 
folder for the app, started up Tomcat and tried it, everything worked 
fine... JSP class was generared, servlet compiled, and page came up, no 
problem.

So... Is there actually a problem using JDK 5.0 with Tomcat 5.0.29?  If 
so, what version of Tomcat is OK with 5.0? (assuming any are, which I DO 
assume).  Or is this just some sort of fluke situation?

In any case, my problem is solved, and that was the resolution.



___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: JSP compilation problem

2005-01-01 Thread Ryan Stewart
I answered you yesterday on this. There's generally no reason to post the same 
question two days in a row. Just wait and see if an answer shows up. Your 
problem is (still) that you have one or more errors in your JSP. If you can't 
figure out where the compiler output is, then go and compile the translated 
servlet manually.

-Original Message-
From: Frank W. Zammetti[EMAIL PROTECTED]
To: Tomcat Usertomcat-user@jakarta.apache.org
Date: Thu Dec 30 06:53:31 PST 2004
Subject: JSP compilation problem

Hello.  I'm using Tomcat 5.0.29.  Working from home today and trying to 
run a working application on my laptop, and I'm seeing an exception when 
trying to access the first JSP of the app.  Here's the on-screen display:
[...]
exception
org.apache.jasper.JasperException: Unable to compile class for JSP
[...]

___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Re: JSP compilation problem

2005-01-01 Thread Ryan Stewart
First, I apologize if I came of sounding rude before. As an infrequent visitor 
to this list, I wasn't aware that you are a frequent contributor. I also don't 
seem to have received the other reply you mention. My next thought is that you 
might have two versions of Java installed. If so, which version is Tomcat 
using? Are you sure you compiled the servlet with the same one?

-Original Message-
From: Frank W. Zammetti[EMAIL PROTECTED]
To: Tomcat Users Listtomcat-user@jakarta.apache.org
Date: Sat Jan 01 07:22:09 PST 2005
Subject: Re: JSP compilation problem

I did not post twice Ryan.  If two posts appeared, it is the same 
problem with the list processor that we've been seeing for weeks now.

I did post a reply however... I tried your suggestion and manually 
compiled.  I have NO classpath variable in the environment (I thought 
this might have been a classpath issue, and I guess it could still be, 
but I don't see how at this point).  I manually put servlet-api.jar, 
jsp-api.jar and jasper-runtime.jar in /tomcat/common/lib on the 
classpath and compiled, and it compiles cleanly.  So the problem would 
not appear to be a problem with the generated servlet.  Any other ideas?

Thank you!



___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: JSP compilation problem

2004-12-31 Thread Ryan Stewart
Quite simply, you have an error in your JSP that is preventing the translated 
servlet from compiling. If you don't know where to look for the compiler 
output, then just go and manually compile the servlet.

-Original Message-
From: Frank W. Zammetti[EMAIL PROTECTED]
To: Tomcat Usertomcat-user@jakarta.apache.org
Date: Thu Dec 30 06:53:31 PST 2004
Subject: JSP compilation problem

[...]
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented 
it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP
[...]
root cause
Compile failed; see the compiler error output for details.
[...]

___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: java.lang.NullPointerException in tomcat 5.5.4

2004-12-31 Thread Ryan Stewart
In your login.jsp you're calling the dispatch method of 
gnu.beanfactory.servlet.Dispatcher and most likely passing it null as an 
argument. I don't know anything about this beanfactory, so I can't say much 
more at the moment.

-Original Message-
From: ssk 2001[EMAIL PROTECTED]
To: tomcat-user@jakarta.apache.org
Date: Fri Dec 31 00:08:20 PST 2004
Subject: java.lang.NullPointerException in tomcat 5.5.4

 I installed tomcat 5.5.4 ,jdk1.5 and beanfactory 1.0.1. When run the 
 application it gave the error which is shown below , Pls can anyone help it 
 solve this..
HTTP STATUS ERROR 500
[...]
root cause 
java.lang.NullPointerException
[...]
gnu.beanfactory.servlet.Dispatcher.dispatch(Dispatcher.java:58) 
org.apache.jsp.login_jsp._jspService(org.apache.jsp.login_jsp:101)  [...]

___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Context not auto-reloading

2004-12-24 Thread Ryan Stewart
I have the following context file in conf\Catalina\localhost, but get no 
reloading on change of webapp contents. Can someone point out what I'm doing 
wrong?

Context docBase=C:\Projects\webStats\target
path=webStats
reloadable=true
backgroundProcessorDelay=2
/Context


___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)

2004-06-06 Thread Ryan Stewart
Ah, thanks! I'll have to go with option 2 as I'm pretty well tied to Tomcat 4 and I 
have to develop toward IE.

-Original Message-
From: Bill Barker[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Sat Jun 05 21:47:40 PDT 2004
Subject: Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)

This is a pretty well known bug in MSIE.  The short version is that that TC
4.1.x sends two redirects to get you to the login page, and MSIE gets
confused.  The options to get around this are:
1) Don't use MSIE.
2) Use the default SSL port (e.g. 443).
3) Use TC 5.0.x instead of TC 4.1.x.

Ryan Stewart [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
 I posted a question about this about a week ago, but haven't seen any
reply.

 I've set up Tomcat 4.1.30 for secure access via SSL. Unsecure port is
8080, secure port is 8081. I use Tomcat for J2EE application development,
and the problem is related to that. Using basic authentication, things work
fine. When I move from an unsecure to a secure area of my application, the
dialog box pops up and upon entering the correct user/password, I'm
redirected to the secure port. However, if I change to form based
authentication, when trying to send me to the login form, it sends me to the
unsecure port using https. In other words:
 https://localhost:8080/secureApp/login.jsp

 It should be sending me to 8081. Any clue why this would happen? Snippets
from my connectors in server.xml are below. If you need other info, just
ask.

 Connector className=org.apache.coyote.tomcat4.CoyoteConnector ...
 port=8080 ... redirectPort=8081 scheme=http secure=false ...
   Factory
 className=org.apache.catalina.net.DefaultServerSocketFactory/
 /Connector
 Connector className=org.apache.coyote.tomcat4.CoyoteConnector ...
 port=8009 ... redirectPort=8081 scheme=http secure=false ... 
   Factory
 className=org.apache.catalina.net.DefaultServerSocketFactory/
 /Connector
 Connector className=org.apache.catalina.connector.http.HttpConnector
 port=8081 ... scheme=https secure=true
   Factory className=org.apache.catalina.net.SSLServerSocketFactory
 clientAuth=false keystoreFile=.keystore protocol=TLS/
 /Connector


___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)

2004-06-05 Thread Ryan Stewart
No, you misunderstand. Port 8080 is the unsecure port, so trying to access it with 
https gives a cannot find server error. That's my problem. For some reason, the 
server is trying to redirect to an unsecure port using a secure protocol, which 
doesn't work.

-Original Message-
From: Ariel Valentin[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Sat Jun 05 19:01:31 PDT 2004
Subject: Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)

What is happening once you are logged in?
Does it continue to use the secure protocol on port 8080?
https://localhost:8080/

Mr. Ariel S. Valentin
mailto: [EMAIL PROTECTED]




From: Ryan Stewart [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)
Date: Fri, 4 Jun 2004 20:24:52 -0700 (PDT)

I posted a question about this about a week ago, but haven't seen any 
reply.

I've set up Tomcat 4.1.30 for secure access via SSL. Unsecure port is 8080, 
secure port is 8081. I use Tomcat for J2EE application development, and the 
problem is related to that. Using basic authentication, things work fine. 
When I move from an unsecure to a secure area of my application, the dialog 
box pops up and upon entering the correct user/password, I'm redirected to 
the secure port. However, if I change to form based authentication, when 
trying to send me to the login form, it sends me to the unsecure port using 
https. In other words:
https://localhost:8080/secureApp/login.jsp

It should be sending me to 8081. Any clue why this would happen? Snippets 
from my connectors in server.xml are below. If you need other info, just 
ask.

Connector className=org.apache.coyote.tomcat4.CoyoteConnector ...
port=8080 ... redirectPort=8081 scheme=http secure=false ...
   Factory
className=org.apache.catalina.net.DefaultServerSocketFactory/
/Connector
Connector className=org.apache.coyote.tomcat4.CoyoteConnector ...
port=8009 ... redirectPort=8081 scheme=http secure=false ... 
   Factory
className=org.apache.catalina.net.DefaultServerSocketFactory/
/Connector
Connector className=org.apache.catalina.connector.http.HttpConnector
port=8081 ... scheme=https secure=true
   Factory className=org.apache.catalina.net.SSLServerSocketFactory
clientAuth=false keystoreFile=.keystore protocol=TLS/
/Connector


___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)

2004-06-04 Thread Ryan Stewart
I posted a question about this about a week ago, but haven't seen any reply.

I've set up Tomcat 4.1.30 for secure access via SSL. Unsecure port is 8080, secure 
port is 8081. I use Tomcat for J2EE application development, and the problem is 
related to that. Using basic authentication, things work fine. When I move from an 
unsecure to a secure area of my application, the dialog box pops up and upon entering 
the correct user/password, I'm redirected to the secure port. However, if I change to 
form based authentication, when trying to send me to the login form, it sends me to 
the unsecure port using https. In other words: 
https://localhost:8080/secureApp/login.jsp 

It should be sending me to 8081. Any clue why this would happen? Snippets from my 
connectors in server.xml are below. If you need other info, just ask.

Connector className=org.apache.coyote.tomcat4.CoyoteConnector ...
port=8080 ... redirectPort=8081 scheme=http secure=false ...
  Factory
className=org.apache.catalina.net.DefaultServerSocketFactory/
/Connector
Connector className=org.apache.coyote.tomcat4.CoyoteConnector ...
port=8009 ... redirectPort=8081 scheme=http secure=false ... 
  Factory
className=org.apache.catalina.net.DefaultServerSocketFactory/
/Connector
Connector className=org.apache.catalina.connector.http.HttpConnector
port=8081 ... scheme=https secure=true
  Factory className=org.apache.catalina.net.SSLServerSocketFactory
clientAuth=false keystoreFile=.keystore protocol=TLS/
/Connector


___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: value for useBean class attribute invalid

2004-06-04 Thread Ryan Stewart
-Original Message-
From: Ben[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Fri Jun 04 18:59:40 PDT 2004
Subject: value for useBean class attribute invalid

Hi there,

I'm trying to set up a simple beans backed jsp application. I set up 
everything, the bean compiles, the context for the web app is set.
*snip*

package my.packages;

public class PrimitiveBean implements java.io.Serializable
{
   String content = PrimitiveBean says hi!;

   PrimitiveBean() {
   }

*snip*

One problem I see is that your constructor isn't public, therefore the bean can't be 
instantiated by any class outside the package it is in. If that's not the problem, I'd 
make doubly sure your WEB-INF folder is being picked up correctly.

___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Secure web.xml and WEB-INF

2004-05-31 Thread Ryan Stewart
-Original Message-
From: Bond, James Bond[EMAIL PROTECTED]
To: Tomcat Users List[EMAIL PROTECTED]
Date: Sun May 30 22:40:16 PDT 2004
Subject: Secure web.xml and WEB-INF

Hello. Please, give me some tips how to secure (deny for reading in
browser) access to web.xml and WEB-INF folder? Any suggestions are welcome:)
Thanks

WEB-INF is inaccessible to the client as per the Java Servlet Specification.

___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Secure web.xml and WEB-INF

2004-05-31 Thread Ryan Stewart
-Original Message-
From: Bond, James Bond[EMAIL PROTECTED]
To: Tomcat Users List[EMAIL PROTECTED]
Date: Sun May 30 22:40:16 PDT 2004
Subject: Secure web.xml and WEB-INF

Hello. Please, give me some tips how to secure (deny for reading in
browser) access to web.xml and WEB-INF folder? Any suggestions are welcome:)
Thanks

WEB-INF is inaccessible to the client as per the Java Servlet Specification.

___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Secure web.xml and WEB-INF

2004-05-31 Thread Ryan Stewart
-Original Message-
From: Bond, James Bond[EMAIL PROTECTED]
To: Tomcat Users List[EMAIL PROTECTED]
Date: Sun May 30 22:40:16 PDT 2004
Subject: Secure web.xml and WEB-INF

Hello. Please, give me some tips how to secure (deny for reading in
browser) access to web.xml and WEB-INF folder? Any suggestions are welcome:)
Thanks

WEB-INF is inaccessible to the client as per the Java Servlet Specification.

___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Tomcat 4.1.30 SSL redirect half working

2004-05-30 Thread Ryan Stewart
This is my first time using a mailing list, so hopefully I'm doing this right. I 
assume the same basic rules as usenet--text only, no attachments, bottom post, etc?

Okay, my problem: I've set up Tomcat 4.1.30 for secure access via SSL. Unsecure port 
is 8080, secure port is 8081. I use Tomcat for J2EE application development, and the 
problem is related to that. Using basic authentication, things work fine. When I move 
from an unsecure to a secure area of my application, the dialog box pops up and upon 
entering the correct user/password, I'm redirected to the secure port. However, if I 
change to form based authentication, when trying to send me to the form, it sends me 
to the unsecure port using https. In other words:
https://localhost:8080/secureApp/login.jsp

It should be sending me to 8081. Any clue why this would happen? My connectors in 
server.xml are below. If you need other info, just ask.

Connector className=org.apache.coyote.tomcat4.CoyoteConnector acceptCount=100 
bufferSize=2048 compression=off connectionLinger=-1 connectionTimeout=2 
connectionUploadTimeout=30 debug=0 disableUploadTimeout=true 
enableLookups=true maxKeepAliveRequests=100 maxProcessors=75 minProcessors=5 
port=8080 protocolHandlerClassName=org.apache.coyote.http11.Http11Protocol 
proxyPort=0 redirectPort=8081 scheme=http secure=false serverSocketTimeout=0 
tcpNoDelay=true tomcatAuthentication=true useBodyEncodingForURI=true 
useURIValidationHack=false
  Factory className=org.apache.catalina.net.DefaultServerSocketFactory/
/Connector
Connector className=org.apache.coyote.tomcat4.CoyoteConnector acceptCount=10 
bufferSize=2048 compression=off connectionLinger=-1 connectionTimeout=2 
connectionUploadTimeout=30 debug=0 disableUploadTimeout=false 
enableLookups=true maxKeepAliveRequests=100 maxProcessors=75 minProcessors=5 
port=8009 protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler 
proxyPort=0 redirectPort=8081 scheme=http secure=false serverSocketTimeout=0 
tcpNoDelay=true tomcatAuthentication=true useBodyEncodingForURI=true 
useURIValidationHack=false
  Factory className=org.apache.catalina.net.DefaultServerSocketFactory/
/Connector
Connector className=org.apache.catalina.connector.http.HttpConnector 
port=8081 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 
debug=0 scheme=https secure=true
Factory className=org.apache.catalina.net.SSLServerSocketFactory 
clientAuth=false keystoreFile=.keystore protocol=TLS/
/Connector

___
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]