ble to
specify the binding host IP in Tomcat 3.2?
Thanks
--
Chris Janicki
781-662-9424
Industrious Activities, Inc.
http://www.ia-inc.com
Is it possible your "Classname" is not unique?... there might be a name
conflict with another class of the same name (in some other package).
>> Original Message <<
On 5/26/01, 5:14:20 AM, Kris Gonzalez <[EMAIL PROTECTED]> wrote
regarding Problem with importing
Are you using Java 1.3? If so, downgrade to the last 1.2.2.5 (or the
latest 1.2). Java 1.3 has some very serious, and unfortunately very
intermittent thread problems.
Chris
>> Original Message <<
On 5/30/01, 6:12:27 AM, "Heijns, P.J.B." <[EMAIL PROTECTED]>
This works for me:
String[] args = { "-start" };
org.apache.tomcat.startup.Tomcat.main(args);
>> Original Message <<
On 5/30/01, 11:57:59 AM, Joseph Variamparambil
<[EMAIL PROTECTED]> wrote regarding Starting tomcat
from a Java Class:
> hell
Are you using Java 1.3? If so downgrade to 1.2.2.5 or later. Java 1.3
has intermittent synchronization problems.
>> Original Message <<
On 5/31/01, 5:06:00 PM, Joe Howes <[EMAIL PROTECTED]> wrote regarding Tomcat
tanks all by itself:
> I've found a couple of
I'm using Tomcat 3.1 for some JSP development work, without Apache.
Starting up Tomcat is conflicting with other software (an unrelated
Apache/JSP engine) running on the same machine, so I want to disable the
server on port 8007. It's mostly just an annoyance, but I also don't want
to steal t
to
> edit your server.xml file to change 8007 to something else (8081
perhaps?).
> If you do really want to remove it, either remove or comment out the
lines
> in the server.xml file for the connector with the handler of
> Ajp12ConnectionHandler. It should look something like:
&g
I've been running Tomcat 3.1 on Solaris with JRE 1.3 and its been fine so
far. However it has a very light load, and there is a serious new bug in
1.3 that may break things if you have lots of busy threads. See:
http://developer.java.sun.com/developer/bugParade/bugs/4293268.html
PS: I'd a
Suggestion: I've had some confusing problems when using packages in 3.1,
so you might want to jar up any packaged classes (even if it is just one)
into a jar and use the WEB-INF/lib directory as Matt suggested.
Chris
>> Original Message <<
On 2/1/01, 9:24:40 AM
I think the checksum error comes from certain 'tar' versions which cannot
properly handle very long file names. By ignoring the errors you may be
ok, or you may have some loss with the longer file names. Try a
different implementation of tar. (Solaris 'tar' works.)
Chris
>>
I've discovered (after some frustration) than certain variable names used
in an HTML form won't be passed to my bean via the "jsp:setProperty" tag.
For example, using "page" as a name doesn't work. I *can* explicitly
set it via:
myBean.setPage(request.getProperty("page"));
But this
Try this:
Today's date is: <%=(new java.util.Date()).toString()%>
>> Original Message <<
On 2/3/01, 11:38:20 AM, [EMAIL PROTECTED] wrote regarding current date in a
web page:
> Can any body help me?
> my problem is that i dont know, using jsp, how to pres
I think port 8007 is used for connection to Apache. Are you trying to
use it as a regular web service port?
Original Message dated 2/3/01, 6:58:01 PM
Author: Nael Mohammad <[EMAIL PROTECTED]>
Re: Handler Thread Problem:
Community,
I'm getting the following error message when a request com
I've been told that Tomcat listens on port 8007 (the Apache connector)
for instructions to shutdown. Have you disabled the Apache connector
service (in ~/conf/web.xml?)
>> Original Message <<
On 2/4/01, 8:16:57 AM, Loïc Courtois <[EMAIL PROTECTED]> wrote
regar
The phrase "Compiled Code" in your stack trace indicates that your java
bytecode has been compiled by the JIT or Hotspot, so it has no reference
to line numbers anymore. You can prevent your code from being natively
compiled by setting an environment variable: JAVA_COMPILER=NONE Then,
java w
Check out this bug before you commit to 1.3 for production: 4293268 (on
Sun's Java Bug Parade)
It's a rare bug on slow apps, but a killer if your JVM is heavily loaded.
>> Original Message <<
On 1/25/01, 3:02:50 PM, "Michael G. Anderson" <[EMAIL PROTECTED]> wrot
lag? I did setenv and set for this variable.
> Didn't help. Is there a reference that describes these features where I
> could look this up?
> java -version
> java version "1.2.2"
> Classic VM (build Linux_JDK_1.2.2_FCS, native threads, sunwjit)
> ^ Could this b
Just a guess... I've had several problems where the compiled page screws
up when it hits quotes. Try changing the double quotes (") to single
('), or none at all.
Also be sure to declare your variables: <%!int jspID;%> or whatever, so it
is in scope.
Chris
>> Original Messag
It really sounds like a browser problem. There's not much you can do to
the JSP other than to try changing the redirection to/from a
relative/absolute URL (if possible) to see if that makes a difference
with your browser. The next obvious suggestion is to verify the problem
on a different br
It looks like your app is hung at the Class.forName() method, which will
reference a class loader. I seem to remember that there are some very
special caveats about using a class loader from within a JSP... you
somehow don't get access to the same classpath or scope for some reason,
maybe sec
Check out bug# 4293268 on Sun's Java bug parade. It described a 1.3
threading bug that involves lost locks. I've had similar deadlock
problem on a different app (not Tomcat) that went away when I downgraded
to Java 1.2.2.5. It is an rare problem that most occurs when a system is
under load.
Are you using Java 1.3 by any chance?
>> Original Message <<
On 2/8/01, 8:46:56 AM, Mark Richards <[EMAIL PROTECTED]> wrote
regarding RE: Connection refused under hight load:
> AFAIK, this limit doesn't apply for TCP/IP connections, only netbios
> connections.
13:15 AM, "Markus Ebersberger"
<[EMAIL PROTECTED]> wrote regarding RE: Connection refused
under hight load:
> > -Original Message-
> > From: Chris Janicki [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, February 08, 2001 3:32 PM
> > To: [EMAIL PROTECTED]
&
I'm currently using Forte 2.0 for a big JSP project. The color-coded
editor is a god-send (although I had to simplify the colors schemes to be
comfortable... a simple black=Java and blue=html is fine with me). The
ability to compile the JSP file within the IDE (press F9) saves a lot of
time
Another bonus of Forte is that it is bundled with the Tomcat JSP
compiler/engine, so there are no new quirks to learn if that is also your
deployment environment.
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<&l
I don't have time to test this, but I think the problem is not in the
stack trace, but the previous line. Try replacing it with:
<%= exception.getMessage() %>
I think the <%= %> expects a String or native.
FYI: A good way to learn/debug JSP is to look at the "*.java" file
created by the serv
Wouldn't that be the value of the request's "Content-length"?
>> Original Message <<
On 2/12/01, 10:39:27 AM, "sun" <[EMAIL PROTECTED]> wrote regarding
HttpUtil:
> hi, there,
> I use HttpUtil to get post data, but always get error: short read.
> what is wrong?
12:14:52 PM, "sun" <[EMAIL PROTECTED]> wrote regarding Re:
HttpUtil:
> yes, I tried that, got same error, "short read",
> in terms of docs, it means posted inputstream is invalid, but I am not
sure
> about that.
> -Original Message-
> From: Chris J
'rmiregistry' runs on port 1099 by default. You can specify another port
by supplying it as the argument ('rmiregistry [port] &'). The biggest
difference between Windows and Unix (Linux), is that Unix only lets
'root' use ports below 1024.
An even better option for many apps is to run the re
We've been having a most frustrating time debugging JSP code that for all
purposes has been perfectly good, except our parameter names are getting
stepped on by Tomcat. We used to have parameters named "page",
"pageSize", and "field". None of these would be sent to our bean, yet
they *would*
Yes Mr. GRUMPY-ASS, I did check the archives, and the Faq-o-matic, and
Sun. I only found references to the JSP implicit variables, of which
"pageSize" and "field" are NOT.
Does anyone in a more amiable mood have insight on this?
>> Original Message <<
On 2/12
Your browser has to accept cookies in order for sessions to work...
verify your browser setup.
>> Original Message <<
On 2/12/01, 10:52:21 AM, janis <[EMAIL PROTECTED]> wrote regarding Can't get work
in 4.0/b1:
> Hello!
> I am running Tomcat4.0/b1 on Linux R
String paraname = request.getParameter("checkboxName"); // 'request' is a
built-in JSP object
>> Original Message <<
On 2/13/01, 12:21:40 PM, "sun" <[EMAIL PROTECTED]> wrote regarding Re:
HttpUtil:
> but how to get parameter value passed from previous page, 5
I think this is the right direction... you need to declare your variable,
not just instantiate it.
<%! NewsBean currentNewsBean; %> // note the !
This *declaration* will allow this variable to be "in scope" when you break
out of <%script-mode%> and back into HTML mode with <%=expressi
34 matches
Mail list logo
