the old HTTP1.1 connector now, to see if I still get the below
exception...
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 8:56 AM
To: Tomcat Users List
Subject: Re: 4.1.17 Problems - Possibly Coyote Connector?
This is bug
I reverted back to the legacy HTTP1.1 connector (the one that is added to port 8083 by
default) and I can not produce the below exception
Definately coyote related
-Original Message-
From: Luc Foisy
Sent: Thursday, December 19, 2002 9:40 AM
To: Tomcat Users List; [EMAIL
I'd like to restate that this error continues to occur and the server will
eventually run out of memory
I am going to test the old HTTP1.1 connector now, to see if I still get the
below exception...
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent
Good to know, thank you!!
John
-Original Message-
From: Luc Foisy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 9:47 AM
To: Tomcat Users List
Subject: RE: 4.1.17 Problems - Possibly Coyote Connector?
I reverted back to the legacy HTTP1.1 connector (the one
on production server AGAIN! I don't need the clients ripping me a new umm below
orafice again! :)
Anyways, using the legacy HTTP1.1 connector I have not been able to reproduce the
socketException after multiple people pounding on it for the last 10 minutes. That
makes me happy...
I also wish I could
I have a connector problem as well, just a bit different. I am using a
version of the JK connector that I used to use with tomcat 3.2.4 and had no
problems. After switching to Tomcat 4.1.16 and above, I have been having
problems serving pages. It seems to be related to the timeout attribute
Hello,
Did not work for me. I still get the blank pages. Mine are servlet
related, not JSP related.
Fabio.
Torsten Fohrer wrote:
This is bug in 4.1.17 which will fixed in Tomcat 4.1.18,
i attach the compiled classes that fixe it.
update the tomcat-coyote and it should work...
--
Fabio
a beta).
You should check for other factors which could cause memory consumption
(like having too many active sessions), and report if you find a part of
Tomcat causing the problem.
Anyways, using the legacy HTTP1.1 connector I have not been able to reproduce the socketException after multiple
Fabio Mengue wrote:
Hello,
Did not work for me. I still get the blank pages. Mine are servlet
related, not JSP related.
The bug can affect servlets which use a Writer. The same patch should
fix it.
Remy
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
for??? I have no idea what goes on
behind the scenes and really I am not caring much, I just want something that works.
Whatever it might not be, the memory use jump happens everytime i get that exception,
so whatever it is, is close by.
Anyways, using the legacy HTTP1.1 connector I have not been
whatever it is, is close by.
Anyways, using the legacy HTTP1.1 connector I have not been
able to reproduce the socketException after multiple people
pounding on it for the last 10 minutes. That makes me happy...
The legacy HTTP/1.1 connector is bad in many ways (I know, because I
Remy Maucherat wrote:
Fabio Mengue wrote:
Hello,
Did not work for me. I still get the blank pages. Mine are servlet
related, not JSP related.
The bug can affect servlets which use a Writer. The same patch should
fix it.
I'm sorry... But it didn't.
What can I do to help figure this out
Please try this steps.
1. hang on catalina.out, access.log
2. request the page with the browser = something changes in logs?
3. add some System.out.println() at beginning and end of the servlet
4. request the page again with the browser = output of the System.out.println
ok?
On Thursday
Buy more memory. It's cheap. Is this supposed to be a server or a
workstation? :)
- Original Message -
From: Torsten Fohrer [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Thursday, December 19, 2002 11:27 AM
Subject: Re: 4.1.17 Problems - Possibly Coyote Connector
] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 5:56 AM
To: Tomcat Users List
Subject: Re: 4.1.17 Problems - Possibly Coyote Connector?
This is bug in 4.1.17 which will fixed in Tomcat 4.1.18,
i attach the compiled classes that fixe it.
update the tomcat-coyote and it should work
-Original Message-
From: Dodd Gatsos [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 12:59 PM
To: Tomcat Users List
Subject: Re: 4.1.17 Problems - Possibly Coyote Connector?
Buy more memory. It's cheap. Is this supposed to be a server or a
workstation
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 12:28 PM
To: Tomcat Users List
Subject: Re: 4.1.17 Problems - Possibly Coyote Connector?
what does this servlet/page do?
Actually I can do it with any jsp in the context
. One
thing that I know for sure is that my application is being called and is
returning from Do Get properly. I do not have this problem with 4.1.12. We
rolled our dev environment back to 4.1.12 and everything is working fine
now. I suspect, but am not sure that the problem is in the connector. Can
: 4.1.17 Problems - Possibly Coyote Connector?
I have been trying out 4.1.17 in my development environment
and it is giving
me much grief. When I first start the server everything works
fine, but
after hitting my webapp a few times (say 10 to 20 times) it
starts returning
blank pages. I
To: Tomcat Users List
Subject: RE: 4.1.17 Problems - Possibly Coyote Connector?
if you could, can you gander at the message thread with the subject Tomcat
4.1.x and SocketException
and see if this is perhaps a related issue?
-Original Message-
From: Matt Small [mailto:[EMAIL PROTECTED
exactly what is happening to me. 4.1.12 works, 4.1.17 gives
me the problem. One thing to note is that my application does not use JSP so
must be a catalina or coyote issue. Are you using the stock Coyote/HTTP 1.1
connector or are you using one of the JK connectors?
I have not seen any sort
.
This looks like exactly what is happening to me. 4.1.12
works, 4.1.17 gives
me the problem. One thing to note is that my application does
not use JSP so
must be a catalina or coyote issue. Are you using the stock
Coyote/HTTP 1.1
connector or are you using one of the JK connectors?
I am using
.
This looks like exactly what is happening to me. 4.1.12
works, 4.1.17 gives
me the problem. One thing to note is that my application does
not use JSP so
must be a catalina or coyote issue. Are you using the stock
Coyote/HTTP 1.1
connector or are you using one of the JK connectors?
I am using
Hi,
Do you know where I can download the latest connector for IIS (5.0) with Tomcat 4.1.12?
Also, we're experiencing a problem that hang Tomcat when the current connection
reached around 256 connections. Should we upgrade to Tomcat 4.1.17?
Thanks,
Tuan
--
To unsubscribe, e-mail: mailto
to it's global configuration
since it can't make a match.
John
-Original Message-
From: Daryl Lee [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 13, 2002 7:44 AM
To: Tomcat User List
Subject: Apache connector-localhost only
I cannot get my Apache-Tomcat mod_jk connector to work
, December 14, 2002 10:49 AM
To: Tomcat Users List
Subject: Connector
Hello.
Is the following true for Tomcat 4.1?
mod_jk2 ajp1.3/ajp1.4 CoyoteConnector+JkCoyoteHandler Current
developpements. Enabled by default in 4.1; works in 4.0. mod_jk2
supports in-process JVM and load
This isn't the place for design or feature suggestions. You want the
tomcat-dev list, not tomcat-user.
John
-Original Message-
From: Sven Köhler [mailto:[EMAIL PROTECTED]]
Sent: Sunday, December 15, 2002 3:27 PM
To: [EMAIL PROTECTED]
Subject: [BUG] AJP connector with specific
Hi!
using TomCat 4.1.12 i created a new AJP connector listening on port 8009
and IP-adress 127.0.0.1 and delted the old Connector that was listening
on 0.0.0.0:8009 (BTW: why i can't i simply change it? why must i create
a new Connector to enter an IP?)
After restarting Tomcat, Tomcat
Hello.
Is the following true for Tomcat 4.1?
mod_jk2 ajp1.3/ajp1.4 CoyoteConnector+JkCoyoteHandler Current
developpements. Enabled by default in 4.1; works in 4.0. mod_jk2
supports in-process JVM and load balancing. See Coyote JK 2
http://192.168.1.3:8080/tomcat-docs/config/jk2.html
Hi Noel!
Yes, we use the root for dav and filtering, since unique and clear
identities/url-identifiers are very important to us.
In your conf-snipplet it seems that you bind the tomcat connector by
mime-type and then redefine the the mime-type in the 'dav' location to
avoid being captured
I cannot get my Apache-Tomcat mod_jk connector to work for anything other
than localhost. Apache 2.0.43, Tomcat 4.1.12, Linux (Redhat 8.0). Trying
to run http://localhost/examples/HelloWorldExample works, but if
localhost is replaced with either an IP address or a valid hostname, the
error_log
-
From: Daryl Lee [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 13, 2002 7:44 AM
To: Tomcat User List
Subject: Apache connector-localhost only
I cannot get my Apache-Tomcat mod_jk connector to work for anything other
than localhost. Apache 2.0.43, Tomcat 4.1.12, Linux (Redhat 8.0
I have ports 80 and 8080 both open. In particular, when I hit the host
from inside the firewall, but from another host, the connector fails.
Thus, http://localhost/... works, but http://tigger/... fails.
On Fri, Dec 13, 2002 at 09:15:39AM -0500, Denise Mangano wrote:
Daryl,
Just out
example.
The Location solution resolves that conflict, although, I seem to recall
having to ensure that the module order was correct when I first installed
mod_dav. If you look at the LoadModule/AddModule ordering in your
httpd.conf file, you want to put mod_dav after the connector, which means
Hi!
using TomCat 4.1.12 i created a new AJP connector listening on port 8009
and IP-adress 127.0.0.1 and delted the old Connector that was listening
on 0.0.0.0:8009 (BTW: why i can't i simply change it? why must i create
a new Connector to enter an IP?)
After restarting Tomcat, Tomcat
Hi,
I'm having two services/websites set up on my Tomcat. One on port 80 another on 81
(the sites are the same except that the port 80 is the one that is used the most).
Within the last year the website at port 80 has stopped twice! When accessing the
website that stopped from client browsers
Dear tomcat wizards.
I can't get mod_dav to work since the jk connector routes all http
method calls for *.xml pages to tomcat. Any solution I can think of
requires a modification of the connectors in tomcat.
Before I proceed, I need help to decide what the best solution is:
Alt 1: Allow
be to define a DNS
entry and virtual host, e.g., dav.domain.tld.
--- Noel
-Original Message-
From: Jonas Bosson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 12, 2002 10:56
To: [EMAIL PROTECTED]
Subject: Apache+mod_dav+connector dilemma
Dear tomcat wizards.
I can't get mod_dav
Connector.
*
* Symptoms:
*
* When using the coyote connector with this example, all output from
the second invocation
* of the examples/servlet/SessionExample is not returned to the client.
Any attempt to read the
* BufferReader derived from the InputStream returns null.
*
* This program works
I'm a Tomcat newbie--I'm trying to set this up for one of my users. I
Googled and searched the list archives, but haven't found the answer.
I'm running jakarta-tomcat-4.1.12, apache_1.3.26, and
jakarta-tomcat-connectors-4.1.12 (installed from source) under Solaris
2.6.
I followed the directions
We are using Tomcat to serve pages that can take a long time to
generate, (in excess of 1 minute). To prevent the browser from retrying
to resend the request, we are committing the request using flushBuffer()
immediately after setting the response headers. However, it appears that
the
hi,
I would like to connect Apache 2.0.43 with Tomcat 4.1 by using the JK2
connector, I have try to build the src found at the adress :
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0.2/src/jakarta-tomcat-connectors-jk2-2.0.2-src.tar.gz
Here you can find my
I asked once before and was assured I could replace the HP-provided Tomcat
3.3.1 with a newer version. I have Tomcat 4.1.12-LE (with Java 1.4.0)
working fine standalone and although I thought I wasn't going to have to do
this part, it looks like I've been elected to try to convince Tomcat to
Wendy Smoak writes:
I asked once before and was assured I could replace the HP-provided Tomcat
3.3.1 with a newer version. I have Tomcat 4.1.12-LE (with Java 1.4.0)
working fine standalone and although I thought I wasn't going to have to do
this part, it looks like I've been elected to try to
Actually, I've got one box where I have mod_jk.so (the 1.1.0 version that
comes with 3.3.1) talking very nicely to the Jk2 CoyoteConnector running in
4.1.13. The nice thing about mod_jk at the moment is that you can
mix-and-match native and Java versions freely.
Wendy Smoak [EMAIL PROTECTED]
s:[EMAIL PROTECTED]...
Hi
I am a newbie and having problems with mysql connector. I
download the mysql-connector-java-2.0.14-bin.jar and put
the file in the C:\j2sdk1.4.0_02\jre\lib\ext as the readme
file instructed. But when I tried to run a jsp file with
content:
%@ page language=java import=
: Cookies translation problem on isapi connector using IIS5 +
TOMCA T 4.0.1
Dear all,
Look like that when I use IIS with AJP3 and TomCat 4.0.1 with the
isapi_redirect.dll cookies can become HTTP translated and/or truncated.
This ugly HTTP translation occurs during request communication between
-exampl
es-howto.html
Jason
-Original Message-
From: Evelin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 26, 2002 12:49 AM
To: [EMAIL PROTECTED]
Subject: mysql connector problems
Hi
I am a newbie and having problems with mysql connector. I
download the mysql-connector-java-2.0.14
Hello group.
I'm not able to configure Apache + SSL with Tomcat to make available to servlets the
SSL data, such like are returned by request.getRemoteUser() function (always return
NULL).
Apache runs correctly with HTTPS, but Tomcat no.
Any idea?
]
-
Hello, have u uncommented the ssl connector in server.xml? what version of
tc? what version of apache? what platform? os? have u configured mod_ssl and
JkMount in httpd.conf? many variables that can break ssl
Hi
I am a newbie and having problems with mysql connector. I
download the mysql-connector-java-2.0.14-bin.jar and put
the file in the C:\j2sdk1.4.0_02\jre\lib\ext as the readme
file instructed. But when I tried to run a jsp file with
content:
%@ page language=java import=java.sql
Hi
I am a newbie and having problems with mysql connector. I
download the mysql-connector-java-2.0.14-bin.jar and put
the file in the C:\j2sdk1.4.0_02\jre\lib\ext as the readme
file instructed. But when I tried to run a jsp file with
content:
%@ page language=java import=java.sql
cookies are used. I think that this
is a side-effect of the HTTP/1.1 extended cookie definition.
So for example MY_KEY_VALUE=815 on TomCat working alone becomes
MY%5fKEY%5fVALUE%3d815 on IIS + Tomcat. WHY ?
I believe, that the connector architecture between IIS and Tomcat is the
cause
Hi,
I am trying to configure two tomcat servers on a single win2k host with two
nic with 4 ip addresses.
A 4.0.6 server configured on IP 192.168.1.1 and 192.168.2.1 on port 80 and
443 with no AJP connector activated.
A 4.1.12 server configured on IP 192.168.1.2 and 192.168.2.2 on port 8080
Is there any particular good reason to change HTTP port from 8080 to 80
and the SSL connector port from 8443 to 443?
They causing problems for me. Some people are suggesting that we should
change the ports.
I changed the HTTP Connector port from 8080 to 80
Then I uncommented the SSL Connector
PM
To: Tomcat Users List
Subject: HTTP and SSL Connector port problems
Is there any particular good reason to change HTTP port from
8080 to 80
and the SSL connector port from 8443 to 443?
They causing problems for me. Some people are suggesting that
we should change the ports
Sorry little typo below
pot=port number
-Original Message-
From: Ralph Einfeldt
Sent: Wednesday, November 20, 2002 12:11 PM
To: Tomcat Users List; [EMAIL PROTECTED]
Subject: RE: HTTP and SSL Connector port problems
The reason that this is recommende is that you otherwise
have
both. IE will behave the same, so run Apache or Tomcat on 80/443 and
don't forget to the the redirect ports in either the http1/1 connector
and/or the Ajp-Connector.
Mech
P.S. Don't use Tomat 4.1.12 with SSL, upgrade to 4.1.14. Minor? ssl
warning bug:
http://nagoya.apache.org/bugzilla/show_bug.cgi
' [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Wednesday, November 20, 2002 3:33 AM
Subject: RE: HTTP and SSL Connector port problems
Another good reason to change to 80/443 is the following issue:
http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg73342.html
http://nagoya.apache.org
Also, everyone has different mileages. Just soemone did not able
to figure out, that does not mean it's a bug.
Pae
Mech
P.S. Don't use Tomat 4.1.12 with SSL, upgrade to 4.1.14. Minor? ssl
warning bug:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14164
--
To unsubscribe, e-mail:
Users List
Subject: HTTP and SSL Connector port problems
Is there any particular good reason to change HTTP port from
8080 to 80
and the SSL connector port from 8443 to 443?
They causing problems for me. Some people are suggesting that
we should change the ports.
But how come
Connector port problems
Another good reason to change to 80/443 is the following issue:
http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg73342.html
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13861
If you use a security-constraint confidential to force ssl you might
:
Subject: Re: HTTP and SSL Connector port problems
Did I miss something that I should I have changed in some other files or
place?
All I did was to change the ports number in server.xml
On 20 Nov 2002 at 7:33, Pae Choi wrote
To: Tomcat Users List
Cc:
Subject: Re: HTTP and SSL Connector port problems
Did I miss something that I should I have changed in some other files or
place?
All I did was to change the ports number in server.xml
On 20 Nov 2002
before
-Original Message-
From: Peter Lee [mailto:[EMAIL PROTECTED]]
Sent: Wed 11/20/2002 2:12 PM
To: Tomcat Users List
Cc:
Subject: Re: HTTP and SSL Connector port problems
Did I miss something that I should I have
DK 1.4.1 on Solaris.
Could be please give me a tip which kind of connector we should use.
There are already 3 (!) kind of connectors:
- mod_jk
- mod_jk2
- mod_webapp
Which will work and which will you recommend with the above mentioned
version/configuration in mind?
The documenation seems to be
I changed the HTTP Connector port from 8080 to 80
Then I uncommented the SSL Connector section and changed the
SSL port from 8443 to 433
These are supposed to be well-known ports. But how come after I
made the changes, Tomcat just refused to
start? I am on the Win2000 platform.
!-- Define
Those ports you mentioned are privileged ports, I think you can only use
them if you have ROOT rights (UNIX) or admin rights (Windoze NT/2000), if
you don't have root rights I don´t think Tomcat can bind to a privileged
port. Do you start Tomcat as ROOT?
Mvh
KR
--
To unsubscribe, e-mail:
]'
Subject: Which Apache Connector works and which is recommend
for Tomcat
4. 1.12?
Hi Folks,
we want to use Apache and Tomcat as tandem you recommend.
We currently use Apache 1.3.27 and Tomcat 4.1.12 and JDK
1.4.1 on Solaris.
Could be please give me a tip which kind of connector
Connector className=org.apache.coyote.tomcat4.CoyoteConnector
port=8004 minProcessors=5 maxProcessors=75
enableLookups=true redirectPort=8443
acceptCount=10 debug=0 connectionTimeout=2
useURIValidationHack=false
Connector className=org.apache.coyote.tomcat4.CoyoteConnector
port=8004 minProcessors=5 maxProcessors=75
enableLookups=true redirectPort=8443
acceptCount=10 debug=0 connectionTimeout=2
useURIValidationHack=false
are in the same case :_)
- Original Message -
From: Brandon Cruz [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Tuesday, November 19, 2002 5:29 PM
Subject: RE: Coyote Connector won't listen on port 8004, only 8009 (Tomcat
4.1.12)
Connector className
]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Tuesday, November 19, 2002 5:29 PM
Subject: RE: Coyote Connector won't listen on port 8004, only 8009
(Tomcat
4.1.12)
Connector className=org.apache.coyote.tomcat4.CoyoteConnector
port=8004 minProcessors=5 maxProcessors=75
This is a known issue, which was fixed, maybe in 4.1.14. The connector wasn't using
the port value in server.xml, for some fairly complicated reasons. (eventually it
should get that value from jk2.properties, the same file that mod_jk2 will be reading,
but the architecture to support
. The result: tomcat was
being started up with the B configuration.
Perhaps you are in the same case :_)
- Original Message -
From: Brandon Cruz [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Tuesday, November 19, 2002 5:29 PM
Subject: RE: Coyote Connector won't
...
-Original Message-
From: Jeff Tulley [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 19, 2002 12:08 PM
To: [EMAIL PROTECTED]
Subject: Re: Coyote Connector won't listen on port 8004, only
8009(Tomcat 4.1.12)
Yeah, maybe that is the real problem. The problem I discussed in my last
email had more
On 19 Nov 2002, at 11:16, Kristján Rúnarsson wrote:
Yes, I did start Tomcat as the administrator, so I have all the rights.
Those ports you mentioned are privileged ports, I think you can only use
them if you have ROOT rights (UNIX) or admin rights (Windoze NT/2000), if
you don't have root
Hi All,
Can someone enlighten me on the difference between the coyote connector and
the Catalina httpconnector. Which one of the two is the recommended connector with
Tomcat 4.0.4. I am using tomcat primarily for file uploads and downloads.
Regards,
Joseph
--
To unsubscribe, e-mail
Hi all,
Runnin' Tomcat 4.0.2 and Apache 1.3.26 on SOLARIS 8 in Production.
I'd like to get /webapp-info/ secured by login/password - even BASIC -
when asked by
http://my.sever.com/webapp-info/
Any help welcome.
Jean-Luc B :O)
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For
Hi Everyone,
I am trying to get the source files to build the mod_jk connector for Apache2.0.43. I
tried downloading from the main jakarta site at
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.0/src/ and
I get a corrput file. Does anyone have a mirror site
Connector className=org.apache.coyote.tomcat4.CoyoteConnector
port=8004 minProcessors=5 maxProcessors=75
enableLookups=true redirectPort=8443
acceptCount=10 debug=0 connectionTimeout=2
useURIValidationHack=false
Hi Folks,
we want to use Apache and Tomcat as tandem you recommend.
We currently use Apache 1.3.27 and Tomcat 4.1.12 and JDK 1.4.1 on Solaris.
Could be please give me a tip which kind of connector we should use.
There are already 3 (!) kind of connectors:
- mod_jk
- mod_jk2
ce files to build the mod_jk connector for
Apache2.0.43. I tried downloading from the main jakarta site at
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.0
/src/ and I get a corrput file. Does anyone have a mirror site or a copy of
the source tar than I can use to get the
was wondering if the connector
architecture of tomcat allowed (without too much trouble) to use another
protocol.
But it's true that using http is not a big problem and I'll probably end
up doing that.
yves
Milt Epstein wrote:
On Thu, 14 Nov 2002, Yves Duhem wrote:
Hi,
I would like to use servlets
Hi all,
Runnin' Tomcat 4.0.2 and Apache 1.3.26 on SOLARIS 8 in Production.
I'd like to get /webapp-info/ secured by login/password - even BASIC -
when asked by
http://my.sever.com/webapp-info/
Any help welcome.
Jean-Luc B :O)
--
To unsubscribe, e-mail:
: Yves Duhem [mailto:yves.duhem;cryptolog.com]
Sent: Friday, November 15, 2002 4:03 AM
To: Tomcat Users List
Subject: Re: non Http connector
Thanks for your answer,
in fact I don't want to use http at all and I was wondering if it was
possible with tomcat.
I already have my own protocol
John,
Maybe you can clear this up for me.. I get the hint from several
different messages that the CoyoteConnector handles both JK and JK2.
Looking at the server.xml it appears that, based on the comments in
that file
!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 --
Connector
JK is known as ajp13. JK2 is known as, I believe, ajp14. The precursor
to JK was JServ, and that is known as ajp12.
The Coyote Connector (org.apache.coyote.tomcat4.CoyoteConnector) can speak
JK and JK2. The Ajp13Connector (org.apache.ajp.tomcat4.Ajp13Connector) only
speaks JK
Hello,
I've written a resource adapter for an EIS compliant
with the J2EE Connector Architecture. I've done some
preliminatry testing using Sun's J2ee Server Reference
Implementation. I would like to move my test
application to a straight stand alone Tomcat
installation. I've read all
On Fri, 15 Nov 2002, Jason Rizer wrote:
Date: Fri, 15 Nov 2002 11:01:46 -0800 (PST)
From: Jason Rizer [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: Tomcat support for Java Connector Architecture?
Hello,
I've written
No. Tomcat standalone is not a J2EE server, and
only supports
servlet/jsp.
I suspected as much. Thanks for the quick
confirmation.
-Jason (who is back to Sun's RI server and all its
foibles)
__
Do you Yahoo!?
Yahoo! Web Hosting - Let the
peculiar
requirement.
-Original Message-
From: Yves Duhem [mailto:yves.duhem;cryptolog.com]
Sent: Friday, 15 November 2002 10:03 p.m.
To: Tomcat Users List
Subject: Re: non Http connector
Thanks for your answer,
in fact I don't want to use http at all and I was wondering if it was
possible
with SSL.)
I would like to know if a connector behaving like this exists somewhere,
or if i'll have to modify one of the existing connectors (and in that
case is there any developer documentation about the connector framework?).
Thanks
yves
--
To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe
(no headers).
(and all this would be used with SSL.)
I would like to know if a connector behaving like this exists somewhere,
or if i'll have to modify one of the existing connectors (and in that
case is there any developer documentation about the connector framework?).
Are you saying that you
He could also implement the Remote interface and set up RMI communication on
a different port than what the HTTP connector runs on - which gives you
quite a bit of the protocol set up for free. Any HTTP servlet which
implements this interface can also act as a RMI server. IMHO one of the
biggest
On Thu, 14 Nov 2002, Randy Secrist wrote:
He could also implement the Remote interface and set up RMI
communication on a different port than what the HTTP connector runs
on - which gives you quite a bit of the protocol set up for free.
Any HTTP servlet which implements this interface can also
and
http://localhost:8080 just fine.
However when I test the connector by browsing to http://localhost/examples I get a
404 error.
The apache error.log says
File does not exist: /var/www/html/examples
On inspection of the cataline.out file I see:
Nov 6, 2002 2:40:07 PM
the garbage colletion), but the
answer never comes to my browser. I mean, I get a blank page with some
tags, but not the answer I expected.
Then, on tomcat-4.1.14/conf/server.xml, I altered
Connector className=org.apache.coyote.tomcat4.CoyoteConnector
...
To
Connector className
Hi there,
I'm using tomcat 4.1.12 and I found something strange : I'm trying to change
the default port for Coyote/JK2 AJP 1.3 Connector, to be able to run
multiple instances of Tomcat.
So I edit the server.xml and modified port=8009 to port=8109 for
instance :
!-- Define a Coyote/JK2 AJP
Pernoud [mailto:apernoud;sopragroup.com]
Sent: 04 November 2002 14:14
To: [EMAIL PROTECTED]
Subject: Coyote/JK2 AJP 1.3 Connector stays on 8009 ? Possible bug ?
Hi there,
I'm using tomcat 4.1.12 and I found something strange : I'm
trying to change
the default port for Coyote/JK2 AJP 1.3
901 - 1000 of 1439 matches
Mail list logo
