In our project, we have implemented SOAP webservices using Apache CXF
framework. Clients used to request the server for some command execution.
The request consists of host, port and the protocol used for connection. If
the client uses a HTTPS configured port number and specify the protocol as
Cassian Raja Thomas wrote:
In our project, we have implemented SOAP webservices using Apache CXF
framework. Clients used to request the server for some command execution.
The request consists of host, port and the protocol used for connection. If
the client uses a HTTPS configured port number
I can retrieve the information prior to getting the connection refused
message and then compare the port numbers with the one sent in the request
parameters. Thereby, I can handle the exception and throw it with nice
error code and message
On Tue, Aug 19, 2014 at 12:19 PM, André Warnier
On tomcat7 and tomcat8, documentation about deployment on Tomcat
startup
http://tomcat.apache.org/tomcat-8.0-doc/deployer-howto.html#Deployment_on_Tomcat_startup
says:
The following deployment sequence will occur on Tomcat startup in that case:
1. Any Context Descriptors will be deployed
On 19/08/2014 10:50, Alexandre Garnier wrote:
On tomcat7 and tomcat8, documentation about deployment on Tomcat
startup
http://tomcat.apache.org/tomcat-8.0-doc/deployer-howto.html#Deployment_on_Tomcat_startup
says:
The following deployment sequence will occur on Tomcat startup in that case:
On 8/19/2014 4:36 AM, Cassian Raja Thomas wrote:
I can retrieve the information prior to getting the connection refused
message and then compare the port numbers with the one sent in the request
parameters. Thereby, I can handle the exception and throw it with nice
error code and message
Not
2014-08-19 12:21 GMT+02:00 Mark Thomas ma...@apache.org:
On 19/08/2014 10:50, Alexandre Garnier wrote:
On tomcat7 and tomcat8, documentation about deployment on Tomcat
startup
http://tomcat.apache.org/tomcat-8.0-doc/deployer-howto.html#Deployment_on_Tomcat_startup
says:
The following
On 19/08/2014 13:30, Alexandre Garnier wrote:
2014-08-19 12:21 GMT+02:00 Mark Thomas ma...@apache.org:
On 19/08/2014 10:50, Alexandre Garnier wrote:
On tomcat7 and tomcat8, documentation about deployment on Tomcat
startup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Carl,
On 8/17/14, 7:18 PM, carl hansen wrote:
I can do /usr/bin/apr-1-config and I get the usage page for APR.
I assume that means it is there.
Don't assume. Your command lines said is was in /usr/lib/apr Is it
in /usr/lib/apr? from what you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sapna,
On 8/18/14, 3:52 AM, Sapna Kumari wrote:
my bad, correct way to set JAVA_OPTS is
*set JAVA_OPTS=-Xms512M -Xmx1024M*
No, the correct way is to use CATALINA_OPTS.
Do you really need a 512M heap to send a shutdown request to Tomcat?
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Wes,
On 8/18/14, 1:05 PM, Wes Clark wrote:
One of the primary conditions for which we want to mark the
connection for death is when a rollback fails with an exception.
An example of this kind of error is a network error.
Won't this happen
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: OutOfMemory:PermGen with Tomcat App Server
On 8/18/14, 3:52 AM, Sapna Kumari wrote:
my bad, correct way to set JAVA_OPTS is
*set JAVA_OPTS=-Xms512M -Xmx1024M*
No, the correct way is to use CATALINA_OPTS.
Do
Christopher:
ldd /usr/local/apr/lib/libtcnative-1.so
linux-vdso.so.1 = (0x7fff145fe000)
libssl.so.10 = /lib64/libssl.so.10 (0x7f5642498000)
libcrypto.so.10 = /lib64/libcrypto.so.10 (0x7f56420b3000)
libapr-1.so.0 = /lib64/libapr-1.so.0
Yeah.. Now I got it. Thanks for the information
On Tue, Aug 19, 2014 at 5:59 PM, David kerber dcker...@verizon.net wrote:
On 8/19/2014 4:36 AM, Cassian Raja Thomas wrote:
I can retrieve the information prior to getting the connection refused
message and then compare the port numbers with
Besides setting for the 2 different ports, how do deal with the
Environment Variables of Path, CATALINA_HOME? They are having the
values for the 7 for now and JAVA_HOME could be using the the same one
for Tomcat 7 and 6?
Thanks!
On Sun, Aug 17, 2014 at 4:54 AM, André Warnier a...@ice-sa.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Neil,
On 8/19/14, 11:53 AM, Neil Aggarwal wrote:
Christopher:
ldd /usr/local/apr/lib/libtcnative-1.so
linux-vdso.so.1 = (0x7fff145fe000) libssl.so.10 =
/lib64/libssl.so.10 (0x7f5642498000) libcrypto.so.10 =
/lib64/libcrypto.so.10
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
To whom it may concern,
On 8/19/14, 1:32 PM, NEW IT wrote:
Besides setting for the 2 different ports, how do deal with the
Environment Variables of Path, CATALINA_HOME? They are having the
values for the 7 for now and JAVA_HOME could be using
On 19/08/14 16:26, Christopher Schultz ch...@christopherschultz.net
wrote:
On 8/18/14, 1:05 PM, Wes Clark wrote:
One of the primary conditions for which we want to mark the
connection for death is when a rollback fails with an exception.
An example of this kind of error is a network error.
Hi Chris,
So you meant after I fired up the Tomcat 7 then change the environment
variables for the version 6 and startup there too?
CATALINA_HOME could set to version 7 and
CATALINA_BASE set to version 6 OK?
Thank you,
Shawn
On Tue, Aug 19, 2014 at 10:43 AM, Christopher Schultz
Is there a way to route all errors to a single web page?
Something like:
error-page
error-codeall/error-code
locationmyerror.jsp/location
/error-page
Basically I want to control the content of everything that goes out of my
service.
Thanks
Mark
On 19/08/2014 21:05, Mark Haroldson wrote:
Is there a way to route all errors to a single web page?
Leave out the error-code tag and you define the default error page.
That will work in Tomcat 8 and I think in 7 as well.
Mark
Something like:
error-page
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 8/19/14, 2:31 PM, NEW IT wrote:
So you meant after I fired up the Tomcat 7 then change the
environment variables for the version 6 and startup there too?
Yes, you can do that, but...
CATALINA_HOME could set to version 7 and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bertrand,
On 8/19/14, 2:23 PM, Bertrand Renuart wrote:
On 19/08/14 16:26, Christopher Schultz
ch...@christopherschultz.net wrote:
On 8/18/14, 1:05 PM, Wes Clark wrote:
One of the primary conditions for which we want to mark the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
Does anyone know if it is possible to build mod_jk on Mac OS X given
the stock httpd that comes with the OS? I don't think httpd is
installed with a stock Mavericks, but my computer is old enough to
have been upgraded from a version of Mac OS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
On 8/19/14, 5:45 PM, Christopher Schultz wrote:
All,
Does anyone know if it is possible to build mod_jk on Mac OS X
given the stock httpd that comes with the OS? I don't think httpd
is installed with a stock Mavericks, but my computer
Christopher:
Do the tcnative*.so files have the execute bit set?
Doing a ls -lah gives me this:
-rw-r--r-- 1 root root 1.7M Aug 17 08:57 libtcnative-1.a
-rwxr-xr-x 1 root root 1.1K Aug 17 08:57 libtcnative-1.la
lrwxrwxrwx 1 root root 23 Aug 17 08:57 libtcnative-1.so -
libtcnative-1.so.0.1.31
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 8/19/14, 2:31 PM, NEW IT wrote:
So you meant after I fired up the Tomcat 7 then change the
environment variables for the version 6 and startup there too?
Yes, you can do that, but...
CATALINA_HOME could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/19/2014 3:19 PM, Neil Aggarwal wrote:
Christopher:
Do the tcnative*.so files have the execute bit set?
Doing a ls -lah gives me this: -rw-r--r-- 1 root root 1.7M Aug 17
08:57 libtcnative-1.a -rwxr-xr-x 1 root root 1.1K Aug 17 08:57
28 matches
Mail list logo
