I am currently in the middle of an upgrade from Apache (2.2)/Tomcat
(5.5.16) to Apache (2.2)/Tomcat (6.0.24). The JVM is being upgraded from
1.5.0_09-b01 to 1.6.0_22-b22. The new host servers will be RedHat 6.2.
I would like to use the default application installation paths used by the
RPMs. H
> From: Jay Mann [mailto:jmand...@hotmail.com]
> Subject: Any examples of using the Web Services support (JSR 109)
> Are there any examples of using the Web Services support (JSR 109)?
The Tomcat doc for JSR-109 is rather terse:
http://tomcat.apache.org/tomcat-7.0-doc/extras.html#Web_Services_su
> From: Zoran Avtarovski [mailto:zo...@sparecreative.com]
> Subject: Re: Help in diagnosing server unresponsiveness
In addition to Igor's excellent advice, try the following.
> 3. Used memory has only gone back down to 4GB and is holding at this level
Take a heap dump and find out what's consum
Hi,
Are there any examples of using the Web Services support (JSR 109)? We
have a some web services we deploy to weblogic but i'd like to debug
them locally using tomcat since weblogic is overkill for my laptop.
These webservices use jax-ws annotations and just have normal servlet
definition
Thanks Igor,
I just stumbled upon that same document. I think you may be on to
something here.
I have a feeling that the GC may not be configured well.
Z.
On 6/02/13 2:15 PM, "Igor Cicimov" wrote:
>On Wed, Feb 6, 2013 at 1:15 PM, Zoran Avtarovski
>wrote:
>
>> Here's some updated observation
On Wed, Feb 6, 2013 at 1:15 PM, Zoran Avtarovski wrote:
> Here's some updated observations after a not quite incident (CPU and
> memory spiked but the app is still running):
>
> 1. Yesterday we had a 90% CPU spike at a time where there was absolutely
> no server traffic. Verified through both the
Here's some updated observations after a not quite incident (CPU and
memory spiked but the app is still running):
1. Yesterday we had a 90% CPU spike at a time where there was absolutely
no server traffic. Verified through both the HTTP logs and the mod_jk
logs. The CPU spiked and recovered back t
Chris,
On Sun, Feb 3, 2013 at 12:39 PM, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Howard,
>
>
> If your requirements allow for users to have to re-authenticate when
> you have a failover-event, then I highly recommend that you use
> sticky-sessions /withou
Thanks Pid! I will try this.
On Tue, Feb 5, 2013 at 12:17 AM, Pid wrote:
> On 05/02/2013 02:25, Zippy Zeppoli wrote:
> > Hello,
> > I have a tomcat 7 cluster which I want to do rolling deployments.
> > I am using FarmDeployer. I am wondering, what is the default behavior of
> > FarmDeployer, doe
Yes, it will have to be dynamically detected somehow. A real chore.
On Tue, Feb 5, 2013 at 2:48 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Pid,
>
> On 2/5/13 3:17 AM, Pid wrote:
> > On 05/02/2013 02:25, Zippy Zeppoli wrot
On Tue, Feb 5, 2013 at 6:10 PM, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Chris,
>
> On 2/2/13 11:47 AM, chris derham wrote:
>>> In the Java world, most people would only call it a consider it
>>> a "cluster" if the app servers actually know about each othe
Chris,
On Tue, Feb 5, 2013 at 5:58 PM, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Howard,
>
> On 2/1/13 9:57 PM, Howard W. Smith, Jr. wrote:
>> On Fri, Feb 1, 2013 at 2:20 PM, Christopher Schultz
>> wrote:
>>>
>>> If you want to improve performance even mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 2/2/13 11:47 AM, chris derham wrote:
>> In the Java world, most people would only call it a consider it
>> a "cluster" if the app servers actually know about each other --
>> for instance, if you are using session replication. IMO session
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Howard,
On 2/1/13 9:57 PM, Howard W. Smith, Jr. wrote:
> On Fri, Feb 1, 2013 at 2:20 PM, Christopher Schultz
> wrote:
>>
>> If you want to improve performance even more, ditch EJB
>> altogether.
>
> Wow, that hurt. ditch EJB altogether? I 'grew
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Pid,
On 2/5/13 3:17 AM, Pid wrote:
> On 05/02/2013 02:25, Zippy Zeppoli wrote:
>> Hello, I have a tomcat 7 cluster which I want to do rolling
>> deployments. I am using FarmDeployer. I am wondering, what is the
>> default behavior of FarmDeployer, d
I had exactly the same problem back in the day,play around with your port
address, tomcat uses port number 8080 by default check if any other process is
using the same port number if yes then change it to some other port by
modifying the configuration file,should help.
-vaibhav
On 2/5/2013 8:04 AM, Jukka Ruohonen wrote:
On Tue, Feb 05, 2013 at 04:37:42PM +0200, Karolis Monkus wrote:
I use fedora 17 and from yum downloaded tomcat-7.0.33 version. I changed
port from 8080 to 80 in server.xml, restarted tomcat and got the following
error in catalina.out file:
How are you
On Tue, Feb 05, 2013 at 04:37:42PM +0200, Karolis Monkus wrote:
> I use fedora 17 and from yum downloaded tomcat-7.0.33 version. I changed
> port from 8080 to 80 in server.xml, restarted tomcat and got the following
> error in catalina.out file:
How are you (re)starting Tomcat?
As far as I know,
> From: Karolis Monkus [mailto:karolis.mon...@dts-solutions.lt]
> Subject: Re: can't start tomcat on port 80
> Nothing running on 80 port, selinux and firewall disabled, so no
> need for writing iptables rules.
Good to kno.w
> What do you mean by saying i need support from Fedora?
The third-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 2/4/13 2:37 PM, André Warnier wrote:
> Thanks to all. I got more than I was bargaining for.
>
> To summarise thus, if I understand correctly what was said here,
> and asking forgiveness in advance for pretty bad English style :
>
> - any
Thanks for quick answer. Nothing running on 80 port, selinux and firewall
disabled, so no need for writing iptables rules.
What do you mean by saying i need support from Fedora? What kind of support?
Would everything be easier if i just download newest tomcat tar archive and
manually install/run
> From: Karolis Monkus [mailto:karolis.mon...@dts-solutions.lt]
> Subject: can't start tomcat on port 80
> I use fedora 17 and from yum downloaded tomcat-7.0.33 version.
You may need support from Fedora, since repackaged versions of Tomcat do not
always behave the way real ones do.
> I changed
Hi everyone,
I use fedora 17 and from yum downloaded tomcat-7.0.33 version. I changed port
from 8080 to 80 in server.xml, restarted tomcat and got the following error in
catalina.out file:
SEVERE: Failed to initialize end point associated with ProtocolHandler
["http-bio-80"]
java.net.BindExce
2013/2/5 Roberto :
> Hi,
>
> I need help with a seemingly trivial question: How to make tomcat use
> port 80.
>
> I have fresh Debian 6.0.6/64 bit install, with Tomcat 6 installed.
> Following some messages, I found in Debian a setting in
> /etc/default/tomcat that would solve my problem, which is
Hi,
I need help with a seemingly trivial question: How to make tomcat use
port 80.
I have fresh Debian 6.0.6/64 bit install, with Tomcat 6 installed.
Following some messages, I found in Debian a setting in
/etc/default/tomcat that would solve my problem, which is setting
AUTHBIND=yes. The problem
On Tue, Feb 5, 2013 at 2:16 AM, Caldarale, Charles R
wrote:
>> From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com]
>> Subject: Re: Severe Errrors encountered in Tomcat when running a Struts2
>> project...
>
>> Chuck, if you look at Tripti's details above (in OP), it seems as
>> though Trip
On 05/02/2013 02:25, Zippy Zeppoli wrote:
> Hello,
> I have a tomcat 7 cluster which I want to do rolling deployments.
> I am using FarmDeployer. I am wondering, what is the default behavior of
> FarmDeployer, does it undeploy and deploy the new app all at once?
>
> Is there any way to modify this
27 matches
Mail list logo
