, Ivano Luberti wrote:
Hi, as stated in the subject, we had a correctly behaving tomcat
8.5 behind a reverse proxy implemented with Apache.
After upgrading to Tomcat 9 every request is seen by tomcat as
coming from localhost.
Apache and Tomcat are running on the same machine and reverse proxy
every request is seen by tomcat as
coming from localhost.
Apache and Tomcat are running on the same machine and reverse proxy
is implemented forwarding the request to localhost.
To say it all, before the upgrade requests arrived to tomcat via ip
v4 and after upgrade via ip v6
I have seen in
localhost.
Apache and Tomcat are running on the same machine and reverse proxy
is implemented forwarding the request to localhost.
To say it all, before the upgrade requests arrived to tomcat via ip
v4 and after upgrade via ip v6
I have seen in the doc that there is a filter in tomcat to deal
On 06/11/2024 21:17, Ivano Luberti wrote:
Hi, as stated in the subject, we had a correctly behaving tomcat 8.5
behind a reverse proxy implemented with Apache.
After upgrading to Tomcat 9 every request is seen by tomcat as coming
from localhost.
Apache and Tomcat are running on the same
Hi, as stated in the subject, we had a correctly behaving tomcat 8.5
behind a reverse proxy implemented with Apache.
After upgrading to Tomcat 9 every request is seen by tomcat as coming
from localhost.
Apache and Tomcat are running on the same machine and reverse proxy is
implemented
Alan,
On 8/1/24 05:00, Alan Masters wrote:
I have configured apache-tomcat-9.0.91 to run as localhost:8080 on
Windows 11.
Once I have executed the startup.bat, and open localhost:8080 and get:
If you're seeing this, you've successfully installed Tomcat.
Congratulation
Hi Alan,
On 01.08.24 11:00, Alan Masters wrote:
I have configured apache-tomcat-9.0.91 to run as localhost:8080 on
Windows 11.
Once I have executed the startup.bat, and open localhost:8080 and get:
If you're seeing this, you've successfully installed Tomcat.
Congratulation
I have configured apache-tomcat-9.0.91 to run as localhost:8080 on
Windows 11.
Once I have executed the startup.bat, and open localhost:8080 and get:
If you're seeing this, you've successfully installed Tomcat.
Congratulations
However frequently when closing down with shutdo
our logging.properties file:
> >
> > 1catalina.org.apache.juli.AsyncFileHandler.rotatable = false
> >
> > 2localhost.org.apache.juli.FileHandler.rotatable = false
> >
> > [...]
> > I'm not sure why this works as expected with the catalina log files, but
> not localhost.
&g
t; I'm not sure why this works as expected with the catalina log files, but
not localhost.
Note that "2localhost" setting has a typo:
s/FileHandler/AsyncFileHandler/
Best regards,
Konstantin Kolinko
-
To unsubscribe,
I hope someone can help me with a Tomcat (10.1.x) logging configuration
question.
I'm perplexed trying to figure out the logging configuration for the
localhost log. I'm using an external logrotate utility to handle log
rotation. This is working well for other Tomcat logs such as ca
On 9/8/23 8:34 AM, Ivano Luberti wrote:
I had similar problem with mod_security installed on servers and apache
used as proxy.
mod_security intercept the request and if considers it suspicious
generate a 403 error
Found it.
It's in the AWS WAF. A rule called
"AWS#AWSManagedRulesCommonRuleS
a
Amazon AWS) doesn't like the word "localhost."
If I enter it in a text field, through the UI, it won't save the
record, and if I feed it into our web services, it comes back with a
403:Forbidden.
My primary hypothesis is that the 403 is coming from an AWS firewall
ru
Yesterday, I discovered that our Tomcat-based webapp (running on a
Amazon AWS) doesn't like the word "localhost."
If I enter it in a text field, through the UI, it won't save the record,
and if I feed it into our web services, it comes back with a 403:Forbidden.
My primar
> Mark
>
>
>>
>> On Tue, Mar 31, 2020 at 1:20 PM Mark Thomas wrote:
>>
>>> On 31/03/2020 11:20, Aditya Kumar wrote:
>>>> Tomcat 9.0.30 on Windows Server 2012 / Java 1.8
>>>>
>>>> I've noticed on a freshly insta
. Basically,
> it's magic. :)
>
> The nice thing on *NIX is that even though there is a hand-wavy
> device supporting NIO for Java, it doesn't consume pairs of ports
> (which are a limited resource; see our recent discussion on the
> limits of TCP port numbers).
>
> -chri
>>> On 31.03.2020 14:20, Mark Thomas wrote:
>>>> On 31/03/2020 11:20, Aditya Kumar wrote:
>>>>> Tomcat 9.0.30 on Windows Server 2012 / Java 1.8
>>>>>
>>>>> I've noticed on a freshly installed version of tomcat 9,
>>
upon startup
there
are several connections to and from localhost on different ports
For example on my tomcat server there are 4 connections to and from
localhost (output from netstat)
TCP 0.0.0.0:8080 0.0.0.0:0
LISTENING 3972
TCP 127.0.0.1:55618 127.0.0.1:55619
ESTABL
Java 1.8
>>>>
>>>> I've noticed on a freshly installed version of tomcat 9,
>>>> upon startup there are several connections to and from
>>>> localhost on different ports
>>>>
>>>> For example on my tomcat server ther
at 9.0.30 on Windows Server 2012 / Java 1.8
>>>
>>> I've noticed on a freshly installed version of tomcat 9, upon startup
>> there
>>> are several connections to and from localhost on different ports
>>>
>>> For example on my tomcat server there are
.0.30 on Windows Server 2012 / Java 1.8
> > >
> > > I've noticed on a freshly installed version of tomcat 9, upon
> > > startup there
> > > are several connections to and from localhost on different ports
> > >
> > > For example on my to
9, upon startup
>>> there
>>> are several connections to and from localhost on different ports
>>>
>>> For example on my tomcat server there are 4 connections to and from
>>> localhost (output from netstat)
>>>
>>> TCP 0.0.0.0:8080
On Tue, Mar 31, 2020 at 1:20 PM Mark Thomas wrote:
> On 31/03/2020 11:20, Aditya Kumar wrote:
> > Tomcat 9.0.30 on Windows Server 2012 / Java 1.8
> >
> > I've noticed on a freshly installed version of tomcat 9, upon startup
> there
> > are several connections to
On 31.03.2020 14:20, Mark Thomas wrote:
On 31/03/2020 11:20, Aditya Kumar wrote:
Tomcat 9.0.30 on Windows Server 2012 / Java 1.8
I've noticed on a freshly installed version of tomcat 9, upon startup there
are several connections to and from localhost on different ports
For example
On 31/03/2020 11:20, Aditya Kumar wrote:
> Tomcat 9.0.30 on Windows Server 2012 / Java 1.8
>
> I've noticed on a freshly installed version of tomcat 9, upon startup there
> are several connections to and from localhost on different ports
>
> For example on my to
Kumar:
> Tomcat 9.0.30 on Windows Server 2012 / Java 1.8
>
> I've noticed on a freshly installed version of tomcat 9, upon startup
> there
> are several connections to and from localhost on different ports
>
> For example on my tomcat server there are 4 connections to
Tomcat 9.0.30 on Windows Server 2012 / Java 1.8
I've noticed on a freshly installed version of tomcat 9, upon startup there
are several connections to and from localhost on different ports
For example on my tomcat server there are 4 connections to and from
localhost (output from netstat)
w.
>
> [ERROR] Failed to execute goal
> com.atlassian.maven.plugins:amps-dispatcher-maven-plugin:8.0.2:run
> (default-cli) on project newplugin05: Cannot start container
> [org.codehaus.cargo.container.tomcat.Tomcat8xInstalledLocalContainer@6abca7a6]:
> Deployable [http://localh
-
From: Mark Thomas
Sent: Thursday, February 13, 2020 5:07 PM
To: users@tomcat.apache.org
Subject: Re: Error: Cannot start container
[org.codehaus.cargo.container.tomcat.Tomcat8xInstalledLocalContainer@6abca7a6]:
Deployable [http://localhost:2990/cargocpc/index.html] failed to finish
er.tomcat.Tomcat8xInstalledLocalContainer@6abca7a6]:
> Deployable [http://localhost:2990/cargocpc/index.html] failed to finish
> deploying within the timeout period [60]. The Deployable state is thus
> unknown. -> [Help 1]
>
> Thank in advance for your help.
>
> Best Re
@6abca7a6]:
Deployable [http://localhost:2990/cargocpc/index.html] failed to finish
deploying within the timeout period [60]. The Deployable state is thus
unknown. -> [Help 1]
Thank in advance for your help.
Best Regards,
Prasanna Mahapure
This e-mail and any files transmitted with it
I got slightly confused with the error message "command" because where I
come from we use different terminology.
Element
Description
http://localhost:8080 The
web server to process the request
/manager/text
The name and location of serve
t;
> > On Sat, 21 Dec 2019, 19:46 Mark Thomas, wrote:
> >
> >> On 21/12/2019 19:27, Zahid Rahman wrote:
> >>> I am on
> >>> http://tomcat.apache.org/tomcat-8.5-doc/manager-howto.html
> >>> Tomcat Web Application Manager This sam
ttp://tomcat.apache.org/tomcat-8.5-doc/manager-howto.html
>>> Tomcat Web Application Manager This same page is produced by
>>> http://localhost:8080/manager/html
>>> http://localhost:8080/manager/ but
>>> http://localhost:8080/manager/text produces
>
ote:
> > I am on http://tomcat.apache.org/tomcat-8.5-doc/manager-howto.html
> > Tomcat Web Application Manager
> > This same page is produced by
> > http://localhost:8080/manager/html
> > http://localhost:8080/manager/
> > but http://localhost:8080/manager/text
>
On 21/12/2019 19:27, Zahid Rahman wrote:
> I am on http://tomcat.apache.org/tomcat-8.5-doc/manager-howto.html
> Tomcat Web Application Manager
> This same page is produced by
> http://localhost:8080/manager/html
> http://localhost:8080/manager/
> but http://localhost:8080/manag
I am on http://tomcat.apache.org/tomcat-8.5-doc/manager-howto.html
Tomcat Web Application Manager
This same page is produced by
http://localhost:8080/manager/html
http://localhost:8080/manager/
but http://localhost:8080/manager/text
produces
FAIL - Unknown command [/text]
I thought that was a
n, it
> > searches the Tools.jar for annotations purpose.
> > 3. As we all know, JDK 11 has stopped shipping / bundling JRE which
> > contains the tools.jar,
> > Tomcat server reports an error which is following :--
> >
> > *ERROR localhost-st
our web application, it
> searches the Tools.jar for annotations purpose.
> 3. As we all know, JDK 11 has stopped shipping / bundling JRE which
> contains the tools.jar,
> Tomcat server reports an error which is following :--
>
> *ERROR localhost-startStop-1 org.apache.catalina.star
:--
*ERROR localhost-startStop-1 org.apache.catalina.startup.ContextConfig -
Unable to process Jar [jar:file:/ C:/JDK11/lib/tools.jar!/] for annotations*
java.nio.file.NoSuchFileException: C:\JDK11\lib\tools.jar
at
java.base/sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:85
be written unless you
start Tomcat as ROOT.
* Test the installation by:
** Starting Tomcat with startup.sh
** Pointing my browser at http://localhost:8080/.
** I see the Tomcat home page no problem
== Step 2: Configuring the Tomcat Manager Apps ==
* Edit the file /Library/Tomcat/conf/tomcat-users.xm
> From: Hassan Schroeder [mailto:hassan.schroe...@gmail.com]
> Subject: Re: Getting the Manager app running on localhost.. Please help
> FYI, I'm on MacOS (Sierra 10.12.6). I just now
> 1) installed apache-tomcat-8.5.32
> 2) added these two lines to tomcat-users.xml
>
&g
added these two lines to tomcat-users.xml
3) started tomcat (`bin/catalina.sh run`)
4) open browser to http://localhost:8080/manager/html
5) supplied above credentials
6) uploaded a war file which deployed correctly
I'm not sure why you created a context file, but it seems ext
orget to change
>> the passwords noted as "" with something "interesting".
>
> Yes. As I mentioned in the first email of this thread, I have a file
> [CATALINA_HOME]/conf/tomcat-users.xml with the following content:
>
>
>
>
>roles=&quo
> manager.xml file, ie:
>
> * Server Status: works
> * Manager: opens page but deploying war causes ‘This site can’t be
> reached’
> * Host Manager: ‘403 Access Denied’
>
> And by “132.0.0.0.”, I actually meant “127.0.0.1”. When I try that from
> ‘localhost:8080’, al
thread, I have a file
[CATALINA_HOME]/conf/tomcat-users.xml with the following content:
>By default, it can only run on localhost, and it's configured to listen to
>127.0.0.1 via the valve. If you uncomment the user role part and change the
>password, y
have you enabled all user roles with passwords?
in CATALINA_HOME/conf/tomcat-users.xml file? Also, don't forget to change
the passwords noted as "" with something "interesting".
By default, it can only run on localhost, and it's configured to listen to
127.0.0.1 v
ge but deploying war causes ‘This site can’t be reached’
* Host Manager: ‘403 Access Denied’
And by “132.0.0.0.”, I actually meant “127.0.0.1”. When I try that from
‘localhost:8080’, all buttons result in ‘403 Access Denied’. But when I access
the buttons from “127.0.0.1:8080”, I get the same behav
I have been trying to get my local Tomcat installation to allow me to deploy
apps from the local machine and nothing I do seems to help.
At the moment, I have a file [CATALINA_HOME]/conf/tomcat-users.xml with the
following content:
When I go to http://localhost:8080/ and click
mote address usually returns a non loop back ip
> address, even if the url was to localhost.
I read the issue the other way around - that the loopback address could
be spoofed.
Anyway...
Olaf has made a number of valid points. I await the answers to those
with interest.
Mark
>
> On F
I think this means, no remote http access, but allow admins remote desktop
access. Once in a local desktop sessions, allow the http access since the
request comes from local host
This issue is get remote address usually returns a non loop back ip
address, even if the url was to localhost
On
On 27/02/18 08:29, Vasantharaju Trichy wrote:
> Tomcat version 7.0.82 | Windows
>
>
>
> We have a requirement such that admins(tomcat users) need to login remotely
> to the machine where Tomcat is hosted and access tomcat webapp to perform
> certain action or see certain pages . These pages or a
valve.html#Remote_Address_Filter?
But: nevertheless request.getRemoteAddr(); can not be spoofed! That is
the origin of the request - that will be your data you need to check for
localhost. If you'd need to identify non-admin-requests from remote and
get the "real" ip, this may be mo
On 27.02.2018 09:29, Vasantharaju Trichy wrote:
Tomcat version 7.0.82 | Windows
We have a requirement such that admins(tomcat users) need to login remotely
to the machine where Tomcat is hosted and access tomcat webapp to perform
certain action or see certain pages . These pages or actions a
Tomcat version 7.0.82 | Windows
We have a requirement such that admins(tomcat users) need to login remotely
to the machine where Tomcat is hosted and access tomcat webapp to perform
certain action or see certain pages . These pages or actions are not
permitted if users login remotely
Initiall
t;
>>> 30-Nov-2016 08:32:21.197 SEVERE [Catalina-startStop-2]
>>> org.apache.catalina.core.ContainerBase.stopInternal A child
>container
>>> failed during stop
>>>
>>> java.util.concurrent.ExecutionException:
>>> org.apache.cata
Tomcat
>>
>> 30-Nov-2016 08:32:21.197 SEVERE [Catalina-startStop-2]
>> org.apache.catalina.core.ContainerBase.stopInternal A child container
>> failed during stop
>>
>> java.util.concurrent.ExecutionException:
>> org.apache.catalina.LifecycleException: Failed to st
gt; java.util.concurrent.ExecutionException:
> org.apache.catalina.LifecycleException: Failed to stop component
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]]
>
> at java.util.concurrent.FutureTask.report(Unknown Source)
>
> at java.util.conc
:
org.apache.catalina.LifecycleException: Failed to stop component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[]]
at java.util.concurrent.FutureTask.report(Unknown Source)
at java.util.concurrent.FutureTask.get(Unknown Source)
at
NG\)" :PREROUTING
> ACCEPT [10:1392] -A PREROUTING -p tcp -m tcp --dport 443 -j
> REDIRECT --to-ports 8443 :FORWARD ACCEPT [0:0] -A FORWARD -p tcp -m
> tcp --dport 443 -j ACCEPT -A FORWARD -j LOG
>
> $ telnet localhost 8443 Trying 127.0.0.1... Connected to
> localhost. Esca
t 443 -j ACCEPT
- -A FORWARD -j LOG
$ telnet localhost 8443
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
^C
Connection closed by foreign host.
(connects)
cschultz@europa:~$ telnet localhost 443
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Con
On 22.07.2016 05:28, chandra sekhar wrote:
Actually, i didn't configure the Apex ORDS yet with DB.As i told you in
previous mail chain i just extracted and trying to see the apche tomcat
home page first before going to configure Apex ORDS.
a) If you are using Internet Explorer, go into the "ext
16 11:29 PM
> To: Mekkelsen Madden, Steve
> >
> Cc: Tomcat Users List >
> Subject: Re: Tomcat starts but home page cannot open with url
> http://localhost:8080
>
> Actually, i didn't configure the Apex ORDS yet with DB.As i told you in
> previous mail chain i just extra
m: chandra sekhar [mailto:chandra.c...@gmail.com]
Sent: Thursday, July 21, 2016 11:29 PM
To: Mekkelsen Madden, Steve
Cc: Tomcat Users List
Subject: Re: Tomcat starts but home page cannot open with url
http://localhost:8080
Actually, i didn't configure the Apex ORDS yet with DB.As i told you in
gt;
>> From: chandra sekhar [mailto:chandra.c...@gmail.com]
>> Sent: Thursday, July 21, 2016 11:06 PM
>> To: Mekkelsen Madden, Steve
>> Cc: Tomcat Users List
>> Subject: Re: Tomcat starts but home page cannot open with url
>> http://localhost:8080
>>
>&
11:06 PM
> To: Mekkelsen Madden, Steve
> Cc: Tomcat Users List
> Subject: Re: Tomcat starts but home page cannot open with url
> http://localhost:8080
>
> Hi Steve,
>
> Please find the below details.
>
> 1.The port 8080 is available.But,need to check if the
: Mekkelsen Madden, Steve
Cc: Tomcat Users List
Subject: Re: Tomcat starts but home page cannot open with url
http://localhost:8080
Hi Steve,
Please find the below details.
1.The port 8080 is available.But,need to check if there is a firewall issue
like port or IP block.
netstat -tlnp |grep java
art
> with the logs, they will provide more details than you think.
>
> -Original Message-
> From: chandra sekhar [mailto:chandra.c...@gmail.com]
> Sent: Thursday, July 21, 2016 9:30 PM
> To: Tomcat Users List
> Subject: Re: Tomcat starts but home page cannot open with
ect: Re: Tomcat starts but home page cannot open with url
http://localhost:8080
Hi,
Please find the below info.
Platform ? --> Linux x86_64 bit
Where did you get that Tomcat from ? --> just tar backup of Production If
Windows, the zip version or the installer ?--> Linux x86_64 bit
Chandra,
On 7/21/2016 6:30 PM, chandra sekhar wrote:
> Hi,
>
> Please find the below info.
>
> Platform ? --> Linux x86_64 bit
> Where did you get that Tomcat from ? --> just tar backup of Production
> If Windows, the zip version or the installer ?--> Linux x86_64 bit
> apache-tomcat-7.0.55
>
Hi,
Please find the below info.
Platform ? --> Linux x86_64 bit
Where did you get that Tomcat from ? --> just tar backup of Production
If Windows, the zip version or the installer ?--> Linux x86_64 bit
apache-tomcat-7.0.55
And how you are trying to "get home page",--> Extracted the tar backup
On 21.07.2016 21:51, chandra sekhar wrote:
Hi All,
Can anybody,please help me or give me advice why i am not getting home page
of tomcat after extraction or installation of apache-tomcat-7.0.55.
Appreciated your help.
Maybe, if you provide some more information.
Platform ?
Where did you get t
Hi All,
Can anybody,please help me or give me advice why i am not getting home page
of tomcat after extraction or installation of apache-tomcat-7.0.55.
Appreciated your help.
Thanks,
Chandra
rporationMac OS X10.9.5x86_64 I
> have a web application(mytomcat-helloworld) in below directory
> /Library/Tomcat/apache-tomcat-8.0.28/webapps/ Server.xml is also
> out of box. unpackWARs="true" autoDeploy="true">
>
> I can access my application at bel
-tomcat-8.0.28/webapps/
Server.xml is also out of box.
I can access my application at below url:-
http://localhost:8080/mytomcat-helloworld/
Everything is fine till here.
I have now created a context xml in path
/Library/Tomcat/apache-tomcat-8.0.28/conf/Catalina/localhost/test.xml
as
I was hoping
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dan,
On 9/19/14 3:44 PM, Daniel Mikusa wrote:
> On Fri, Sep 19, 2014 at 3:33 PM, Miguel Pereira
> wrote:
>
>> Ahhh, thanks Dan,
>>
>> Unfortunately these are 3rd party apps what we receive as a WAR.
>> I am not sure that unzipping them and rezipp
On Fri, Sep 19, 2014 at 3:33 PM, Miguel Pereira
wrote:
> Ahhh, thanks Dan,
>
> Unfortunately these are 3rd party apps what we receive as a WAR. I am not
> sure that unzipping them and rezipping them is ideal nor maintainable. The
> main reason is that the context fragments remain after the apps a
Ahhh, thanks Dan,
Unfortunately these are 3rd party apps what we receive as a WAR. I am not
sure that unzipping them and rezipping them is ideal nor maintainable. The
main reason is that the context fragments remain after the apps are
undeployed which throw non fatal errors on subsequent tomcat re
On Fri, Sep 19, 2014 at 1:32 PM, Miguel Pereira
wrote:
> Thank you very much Dan,
>
> I looked at the links and noticed I am running tomcat 7 locally and 6 on
> our DEV environment.
> I also noticed that copyXML is present in the documentation for tomcat 7
> and defaults to false.
> Finally
> "
>
Thank you very much Dan,
I looked at the links and noticed I am running tomcat 7 locally and 6 on
our DEV environment.
I also noticed that copyXML is present in the documentation for tomcat 7
and defaults to false.
Finally
"
In an individual file at /META-INF/context.xml inside the application
fil
On Fri, Sep 19, 2014 at 12:28 PM, Miguel Pereira
wrote:
> Hey all,
>
> I was wondering where I could get some more information about these xml
> files. On one system they are created every time I deploy a web application
> and on another they are not.. I would prefer that tomcat does not create
>
Hey all,
I was wondering where I could get some more information about these xml
files. On one system they are created every time I deploy a web application
and on another they are not.. I would prefer that tomcat does not create
them. Anyone want to point me in the right direction?
Thank you,
Mi
nny Bhargava wrote:
>
>> Hi All,
>>
>> I tried to run tomcat 4.1.18 with ssl connection. I followed the
>> instructions in 'ssl configuration HOW-TO'.I changed the server.xml file
>> and mentioned the ssl port as 8443 which is the default.
>> I tried both t
On 8/28/2014 12:55 PM, Sunny Bhargava wrote:
Hi All,
I tried to run tomcat 4.1.18 with ssl connection. I followed the
instructions in 'ssl configuration HOW-TO'.I changed the server.xml file
and mentioned the ssl port as 8443 which is the default.
I tried both the links https://loca
Hi All,
I tried to run tomcat 4.1.18 with ssl connection. I followed the
instructions in 'ssl configuration HOW-TO'.I changed the server.xml file
and mentioned the ssl port as 8443 which is the default.
I tried both the links https://localhost:8443 and http://localhost:8443 but
the pag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Frank,
On 3/20/14, 1:03 PM, Frank Lugalla wrote:
> INFO: Initializing ProtocolHandler ["http-bio-8443"] Mar 20, 2014
> 11:54:02 AM org.apache.tomcat.util.net.jsse.JSSESocketFactory
> getStore SEVERE: Failed to load keystore type JKS with path
> C:/A
Hi Guys
Below are my log,my Tomcatv7 wont start.i tried to unstall and
reinstall the server but with no avail.any idea on this please?Tomcat just
says "Server Tomcat v7.0 Server at localhost failed to start." And gives the
b
ific?
You do use Eclipse? NetBeans? Puppet? Tivoli?
- -chris
> -Original Message- From: Christopher Schultz
> [mailto:ch...@christopherschultz.net] Sent: Monday, March 03, 2014
> 10:25 AM To: Tomcat Users List Subject: Re: Could not publish
> server configuration for Tomcat
Server at
localhost.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Frank,
On 3/3/14, 10:58 AM, Frank Lugalla wrote:
> Hi Guys Just started using Tomcat v7..deployed my application
> and I am getting this error when I try to run; Could not publish
> server configuration f
Server at
> localhost. Multiple Contexts have a path of "/etm".
>
> Has anyone got this type of error before?
This sounds like a deployment-specific problem. How are you deploying
to Tomcat?
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.o
Hi Guys
Just started using Tomcat v7..deployed my application and I am
getting this error when I try to run;
Could not publish server configuration for Tomcat v7.0 Server at localhost.
Multiple Contexts have a path of "/etm".
Has anyone got this type of error before?
nty wrote:
>
>
>
> > Date: Fri, 14 Feb 2014 14:19:04 -0800
> > Subject: Re: Eclipse: Server Tomcat v7.0 Server at localhost failed to
> start.
> > From: davek1...@gmail.com
> > To: users@tomcat.apache.org
> >
> > OK I added servlet-api.jar a
> Date: Fri, 14 Feb 2014 14:19:04 -0800
> Subject: Re: Eclipse: Server Tomcat v7.0 Server at localhost failed to start.
> From: davek1...@gmail.com
> To: users@tomcat.apache.org
>
> OK I added servlet-api.jar and jsp-api.jar to the
> Launch Configuration | Classpat
OK I added servlet-api.jar and jsp-api.jar to the
Launch Configuration | Classpath | Bootstrap Entries
and get the following error report:
HTTP Status 500 - java.lang.NoClassDefFoundError: javax/el/ELResolver
HTTP Status 500 - java.lang.NoClassDefFoundError: javax/el/ELResolver
2014-02-14 18:13 GMT+04:00 JB MORLA :
> Maybe you added a .jar file to the build path and there is a conflict with
> the jars already present in Eclipse and Tomcat.
> My solution was to remove the jars.
+1.
> On Thu, Feb 13, 2014 at 10:27 PM, Dave Kennedy wrote:
>
>> Env:
>> Windows 7
>> Java: j
r.DigesterFactory.(DigesterFactory.java:59)
> ... 14 more
>
> Feb 13, 2014 1:17:22 PM org.apache.catalina.core.ContainerBase
> startInternal
> SEVERE: A child container failed during start
> java.util.concurrent.ExecutionException:
> org.apache.catalina.LifecycleException: Faile
13, 2014 1:17:22 PM org.apache.catalina.core.ContainerBase startInternal
SEVERE: A child container failed during start
java.util.concurrent.ExecutionException:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHos
O [main]
> org.apache.catalina.core.StandardService.startInternal Starting service
> Catalina
> 06-Feb-2014 14:50:35.349 INFO [main]
> org.apache.catalina.core.StandardEngine.startInternal Starting Servlet
> Engine: Apache Tomcat/8.0.1
> 06-Feb-2014 14:50:35.375 INFO [localhost-startStop-1]
> org.apache.cata
na
06-Feb-2014 14:50:35.349 INFO [main]
org.apache.catalina.core.StandardEngine.startInternal Starting Servlet
Engine: Apache Tomcat/8.0.1
06-Feb-2014 14:50:35.375 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web
application directory C:\Program F
below message,
>
> FAIL - Application at context path /myapp could not be started
>
> FAIL - Encountered exception org.apache.catalina.LifecycleException:
> Failed to start component
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/myapp]]
>
> In catalina
1 - 100 of 652 matches
Mail list logo
