2015-11-04 20:20 GMT+03:00 Linux Support :
> Hi again,
>
> configured the TC service to run as a non privileged user. In my
> understanding we cannot use a privileged port to bind TC to. Is there a way
> i can use port 80 for TC in the case of using a non root user ?
http://tomcat.apache.org/ ->
If you're running on a UNIX variant, use JSVC. The source is included in
the tomcat download in bin/commons-daemon/native.tar.gz.
On 11/4/2015 10:20 AM, Linux Support wrote:
Hi again,
configured the TC service to run as a non privileged user. In my
understanding we cannot use a privileged port
2014-02-25 16:55 GMT+04:00 Ja kub :
> Hi
>
> Do you know if in Tomcat is something similar to jboss port-offset ?
>
> -Djboss.socket.binding.port-offset=100
>
> It would be convinient for starting several tomcats on the same operating
> system. No need to change ports in server.xml
Tomcat configur
On 5/14/2013 5:27 AM, Mark Thomas wrote:
On 14/05/2013 04:34, Chirag Dewan wrote:
You need to destroy the connector to close the port.
Mark,
That seems to work. :)
Now the port is free. But is it the right approach?
You had a problem you couldn't solve. Someone with an @apache.org e-mai
On 14/05/2013 04:34, Chirag Dewan wrote:
>
>
>> You need to destroy the connector to close the port.
>
> Mark,
>
> That seems to work. :)
>
> Now the port is free. But is it the right approach?
You had a problem you couldn't solve. Someone with an @apache.org e-mail
address (i.e. an Apache co
ent: Tuesday, 14 May 2013 2:41 AM
Subject: Re: Port still busy after removing connector in Embedded Tomcat 7.0.30
On 13/05/2013 16:34, Chirag Dewan wrote:
> Hi,
>
> I am embedding Apache Tomcat 7.0.30 in my application. I am using the Tomcat
> class,and my application requires dynam
> From: Caldarale, Charles R
> Subject: RE: Port still busy after removing connector in Embedded Tomcat
> 7.0.30
> > How long are you waiting? Can you give us the specifics of your
> > connector configuration? I wonder if the connector is remaining open
> > for
On 13/05/2013 16:34, Chirag Dewan wrote:
> Hi,
>
> I am embedding Apache Tomcat 7.0.30 in my application. I am using the Tomcat
> class,and my application requires dynamic addition and removal of
> connectors(HTTP).
>
> Now while removing the connectors,the application gets undeployed but the
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: Port still busy after removing connector in Embedded Tomcat
> 7.0.30
> > If I am calling the removeConnector, shouldn't it cleanup the
> > context and the free the port?
> In theory,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 5/13/13 1:03 PM, Chirag Dewan wrote:
>> If the context was removed, but the Connector was still there,
>> should you not get a 404 Not Found, rather than a timeout ?
>
>
> If I am calling the removeConnector, shouldn't it cleanup the
>
Monday, 13 May 2013 10:13 PM
Subject: Re: Port still busy after removing connector in Embedded Tomcat 7.0.30
Chirag Dewan wrote:
>> How do you observe that the connector is still bound to the port?
>
> Yes. I used netstat to observe that. Plus when I try to add another context
&
hristopher Schultz
To: Tomcat Users List
Sent: Monday, 13 May 2013 9:47 PM
Subject: Re: Port still busy after removing connector in Embedded Tomcat 7.0.30
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 5/13/13 11:34 AM, Chirag Dewan wrote:
I am embedding Apache Tomcat 7.
see my java process listening on port 1090 and 8080.
I really dont understand what wrong I might be doing.
Thanks
From: Christopher Schultz
To: Tomcat Users List
Sent: Monday, 13 May 2013 9:47 PM
Subject: Re: Port still busy after removing connector in Emb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 5/13/13 11:34 AM, Chirag Dewan wrote:
> I am embedding Apache Tomcat 7.0.30 in my application. I am using
> the Tomcat class,and my application requires dynamic addition and
> removal of connectors(HTTP).
>
> Now while removing the conn
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vanky,
On 3/25/2009 9:09 AM, Venky Vasant wrote:
I am sure this is very simple question but i could not find a proper
information
Where do i find the official information about what port range can be
used for tomcat s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vanky,
On 3/25/2009 9:09 AM, Venky Vasant wrote:
> I am sure this is very simple question but i could not find a proper
> information
>
> Where do i find the official information about what port range can be
> used for tomcat server port and HTTP con
Venky Vasant wrote:
I am sure this is very simple question but i could not find a proper information
Where do i find the official information about what port range can be used for
tomcat server port and HTTP connector port for all windows servers.
Regards
Venkat
You can use any po
netstat -a
from a Command window, will show you all the ports in use on any Windows
server.
-Original Message-
From: Venky Vasant [mailto:venkat...@yahoo.com]
Sent: 25 March 2009 13:10
To: users@tomcat.apache.org
Subject: Port range
I am sure this is very simple question but i could no
kjwchu wrote:
I have an application which is running on jakarta-tomcat-4.1.31. Now I want
to move this application in apache-tomcat-6.0.16. I wonder if anyone has
this experience or any thoughts about what areas I would need to make
changes and so on. Thanks!
The war should just work. You wi
go through the web.xml file in the web-inf floder
you have to include details in and
On Sat, Jul 12, 2008 at 8:56 PM, kjwchu <[EMAIL PROTECTED]> wrote:
>
> I have an application which is running on jakarta-tomcat-4.1.31. Now I want
> to move this application in apache-tomcat-6.0.16. I wonder if
use mok_jk
Melanie Pfefer wrote:
> Hello
>
> a servlet is running on port 9000 while apache in
> running on port 80.
>
> Is there a way to change this behavior so that users
> who type
> http://server1/OpenObject?doc=ERW
>
> will receive the same content of
> http://server1:9000/OpenObject?doc=ER
use mok_jk
Melanie Pfefer wrote:
Hello
a servlet is running on port 9000 while apache in
running on port 80.
Is there a way to change this behavior so that users
who type
http://server1/OpenObject?doc=ERW
will receive the same content of
http://server1:9000/OpenObject?doc=ERW but the URL
doe
Much simpler than what I said... no idea why I didn't think of it. Simplicity
is key :)
-Original Message-
From: Peter Crowther [mailto:[EMAIL PROTECTED]
Sent: quinta-feira, 31 de Janeiro de 2008 15:46
To: 'Tomcat Users List'
Subject: RE: port
> From: Tony Chamberl
y 2008 17:07
> To: Tomcat Users List
> Subject: Re: port
>
> I can't figure out the iptable commands to do it.
>
> On Thu, Jan 31, 2008 at 9:45 AM, Peter Crowther
> <[EMAIL PROTECTED]>
> wrote:
>
> > > From: Tony Chamberlain [mailto:[EMAIL PROTECTED]
&g
I can't figure out the iptable commands to do it.
On Thu, Jan 31, 2008 at 9:45 AM, Peter Crowther <[EMAIL PROTECTED]>
wrote:
> > From: Tony Chamberlain [mailto:[EMAIL PROTECTED]
> > We had tomcat running on port 8080 (which is default).
> > Since some people block that port we moved it to the
> >
> From: Tony Chamberlain [mailto:[EMAIL PROTECTED]
> We had tomcat running on port 8080 (which is default).
> Since some people block that port we moved it to the
> http port 80. Now some places that are expecting it on 8080
> can't find it anymore.
>
> Anyway to have it run on both? Maybe forwar
Hi,
You can have an apache HTTPd redirecting it to port 8080 of Tomcat.
Additionaly, if you're on Linux, you can do port forwarding with IPTables
-Original Message-
From: Tony Chamberlain [mailto:[EMAIL PROTECTED]
Sent: quinta-feira, 31 de Janeiro de 2008 15:18
To: users@tomcat.apache.or
When you don't give your browser get a port number, it assumes port 80
which is the registered, well known port for web traffic as defined by
the IANA. Production websites all listen on port 80 which is why you
never have to put it in your URLs to Google for example. The entire
list of these
when you go on normal websites, you are using port 80.
look for 8080 in your server.xml and change it to 80
bye
On Nov 20, 2007 3:14 PM, jdpl <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> how come when I'm accessing a page on my local apache, i always have to put
> in the port number, e.g:
>
> http://l
> From: lightbulb432 [mailto:[EMAIL PROTECTED]
> Subject: RE: Port-based virtual hosting
>
> If you somehow have multiple contexts (within the same Host
> or Service, or within different ones in your Tomcat instance)
> that point to the same WAR file or docBase, are there mul
The question's more of a general one to help me understand some elements in
server.xml. Maybe I'll start with this question first, though:
If you somehow have multiple contexts (within the same Host or Service, or
within different ones in your Tomcat instance) that point to the same WAR
file or d
> From: lightbulb432 [mailto:[EMAIL PROTECTED]
> Subject: Port-based virtual hosting
>
> Is there any functional difference between the two
> options - if they're both even possible? Which would
> you go with?
>
> - 1 Service element with 5 HTTP connectors (each on a
> different port) and one E
I can't do that because, well, you know how this business is. I will
just run on port 80.
Caldarale, Charles R wrote:
From: Dave Sailer [mailto:[EMAIL PROTECTED]
Subject: Re: port problem
more detail: we have a customer 404 error page with...
:http://www.blahblah.net/mypage.html&qu
> From: Dave Sailer [mailto:[EMAIL PROTECTED]
> Subject: Re: port problem
>
> more detail: we have a customer 404 error page with...
>
> :http://www.blahblah.net/mypage.html"; width="100%"
> height="105" scrolling="no" f
more detail: we have a customer 404 error page with...
:http://www.blahblah.net/mypage.html"; width="100%"
height="105" scrolling="no" frameborder="0">
The build script replaces http://www.blahblah.net with
http://test.blahblah.net and my hosts file maps test.blahblah.net to
127.0.0.1, this
Dave Sailer wrote:
I'm running tomcat 5.5 and sniffing out problems with a somewhat complex
web site. After deploying the war into the running tomcat, I go to the
home page and get some exceptions. Looking at the sniffer output, most
of the requests are to localhost:8080, but some are to just l
t to IbmX509???
Please advise!
Thanks!
jeff
-Original Message-
From: Mike Sabroff [mailto:[EMAIL PROTECTED]
Sent: Friday, February 03, 2006 11:43 AM
To: Tomcat Users List
Subject: Re: Port 8443 won't become active (UNCLASSIFIED)
JAVA_HOME/jre/lib/security/java.security:ssl.K
mcat Users List
Subject: Re: Port 8443 won't become active (UNCLASSIFIED)
JAVA_HOME/jre/lib/security/java.security:ssl.KeyManagerFactory.algorithm=Sun
X509
JAVA_HOME/jre/lib/deploy.jar - found in here
JAVA_HOME/jre/lib/jsse.jar - and here
This is the default for a normal sun installation.
W
riday, February 03, 2006 11:24 AM
To: 'Tomcat Users List'
Subject: RE: Port 8443 won't become active
OK, so it isn't the java version. I've ensured JAVA_HOME is correct and
that the PATH is pointing to the right version. All the jars are running
through 1.4.2.
I'm
going through the whole cert process of a root &
intermediate certificate but that didn't do anything either.
Jeff
-Original Message-
From: Samara, Fadi N Mr ACSIM/ASPEX [mailto:[EMAIL PROTECTED]
Sent: Friday, February 03, 2006 11:33 AM
To: 'Tomcat Users List'
Subject: RE
Classification: UNCLASSIFIED
Caveats: NONE
Have you generated key pairs yet ?
-Original Message-
From: Jeffery G. Summers [mailto:[EMAIL PROTECTED]
Sent: Friday, February 03, 2006 11:24 AM
To: 'Tomcat Users List'
Subject: RE: Port 8443 won't become active
OK, so it
MAIL PROTECTED]
Sent: Thursday, February 02, 2006 1:53 PM
To: 'Tomcat Users List'
Subject: RE: Port 8443 won't become active
When we contracted our upgrades the consultant installed version 1.4.2 but
when I just ran "java -version" the box tells me that 1.3.1 is the
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Subject: Re: Port 8443 won't become active
>
> when I had this problem it was caused by the presence of a
> file named "tcnative-1.dll" in the ~/Tomcat 5.5/bin
> directory. When I removed that .dll file,
Hi Jeff,
when I had this problem it was caused by the presence of a file named
"tcnative-1.dll" in the ~/Tomcat 5.5/bin directory. When I removed that .dll
file, everything worked as described in the Tomcat documentation for SSL.
--Tony C.
-- Original message
to try it does
anyone have a "Quickie Guide" I could use?
Thanks!
Jeff
-Original Message-
From: Peter Crowther [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 02, 2006 12:28 PM
To: Tomcat Users List
Subject: RE: Port 8443 won't become active
> From: Jeffery G. Summers
ginal Message-
From: Peter Crowther [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 02, 2006 12:28 PM
To: Tomcat Users List
Subject: RE: Port 8443 won't become active
> From: Jeffery G. Summers [mailto:[EMAIL PROTECTED]
> Our webserver is an IBM P615C AIX 5.2 box.
Whose JVM
Yes, I can almost recite it by rote ;-).
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 02, 2006 12:24 PM
To: Tomcat Users List
Subject: RE: Port 8443 won't become active
> From: Jeffery G. Summers [mailto:[EMAIL PROTECTED]
&
> From: Jeffery G. Summers [mailto:[EMAIL PROTECTED]
> Our webserver is an IBM P615C AIX 5.2 box.
Whose JVM and what version?
- Peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTE
> From: Jeffery G. Summers [mailto:[EMAIL PROTECTED]
> Subject: Port 8443 won't become active
>
> Our webserver is an IBM P615C AIX 5.2 box. I have attempted
> the following to enable port 8443:
>
> 1) keytool -genkey -alias tomcat -keyalg RSA
> 2) Edited server.xml and uncommented the port
49 matches
Mail list logo
