Hello list,
I have a strange classloading problem, that only occurs when my webapp is
deployed by tomcat (aka when tomcat expands the .war file during startup).
I'm using Tomcat 8, Java 8 and a few old Axis webservices.
The very first call to the webservice now fails with a RuntimeException
Jesse Barnum wrote:
On Jan 14, 2015, at 12:29 AM, Konstantin Kolinko knst.koli...@gmail.com wrote:
2015-01-14 6:28 GMT+03:00 Christopher Schultz Jesse,
On 1/13/15 6:29 PM, Jesse Barnum wrote:
I need the ability to examine the POST data from a request,
examine it, and either respond to it or
John Doe wrote:
Hello list,
I have a strange classloading problem, that only occurs when my webapp is
deployed by tomcat (aka when tomcat expands the .war file during startup).
I'm using Tomcat 8, Java 8 and a few old Axis webservices.
The very first call to the webservice now fails with a
On 15/01/2015 15:46, Leonid Rozenblyum wrote:
Hello.
I have 2 web-applications which are running on the same host.
The Valve SingleSignOn is enabled.
Application1 has security-constraint and login-config elements in web.xml
Application2, 3 etc has no such definitions
Technically
On Jan 16, 2015, at 4:37 AM, André Warnier a...@ice-sa.com wrote:
If you do have an Apache httpd front-end anyway, it still seems a bit of a
shame to have to use any Tomcat bandwidth and resources in order to catch
this kind of thing, and not be able to do it at the Apache httpd level,
Hello Mark.
We do explicit forced expiration of http session in one of SSO enabled
apps (Application1 : session.invalidate() )
and it didn't cause session expiration in other Apps
(only workaround with adding security-constraint to other apps that I
mentioned above helped).
Tomcat version is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jesse,
On 1/16/15 9:02 AM, Jesse Barnum wrote:
On Jan 16, 2015, at 4:37 AM, André Warnier a...@ice-sa.com
wrote:
If you do have an Apache httpd front-end anyway, it still seems a
bit of a shame to have to use any Tomcat bandwidth and
On Jan 16, 2015, at 10:38 AM, Christopher Schultz
ch...@christopherschultz.net wrote:
This is for a license check phone-home server. Old versions of our
products had bugs that could cause them to endlessly make
phone-home requests as fast as possible. We need to examine the
POST data,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Joshua,
On 1/16/15 1:36 AM, Joshua Wang wrote:
But i see sessionCookiePath, sessionCookieName and
sessionCookieDomain configures, what is those used for?
Those are used for customizing the details that Tomcat will use when
creating a JSESSIONID
Hello,
I am trying to upgrade a JSP-based application, which is usually hosted on
Tomcat (currently 7.0.57) to Version 8.0.15.
Unfortunately I am facing a massive performance degradation - only 40% of
the performance of 7.0.56 is reached when running the exact same JMeter
Test with Tomcat8.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Théo,
On 1/13/15 1:38 PM, Théo Chamley wrote:
I have setup a Tomcat cluster and I am now trying to get the
FarmWarDeployer to work. However, it seems that the Deployer never
checks my watchDir and therefore never finds my new wars to
deploy.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jason,
On 12/12/14 5:53 PM, jason.stu...@talk21.com wrote:
I am attempting to run a simple RESTful service on Tomcat 7.0.57 on
Linux 2.6.32-504 with Jersey 2.13, JDK 1.7.0_71. I have deployed
Apache and it starts Ok. I have deployed the compiled
Current working setup:
apache 2.2 using mod_jk to pass 443 requests to tomcat on 8443.
We are migrating from SLES 11 SP3 to SLEs 12. On SLES 11 we use alfresco 5.0.c
which includes tomact 7.x i believe. SLES 11 has apache 2.2.10. SLES 12 has
apache 2.4 and we use the same version of alfresco
2015-01-17 2:31 GMT+03:00 Chris Arnold carn...@electrichendrix.com:
Current working setup:
apache 2.2 using mod_jk to pass 443 requests to tomcat on 8443.
We are migrating from SLES 11 SP3 to SLEs 12. On SLES 11 we use alfresco
5.0.c which includes tomact 7.x i believe. SLES 11 has apache
On 16/01/2015 16:01, Dirk Högemann wrote:
Hello,
I am trying to upgrade a JSP-based application, which is usually hosted on
Tomcat (currently 7.0.57) to Version 8.0.15.
Unfortunately I am facing a massive performance degradation - only 40% of
the performance of 7.0.56 is reached when
Am 17.01.2015 um 00:31 schrieb Chris Arnold:
Current working setup:
apache 2.2 using mod_jk to pass 443 requests to tomcat on 8443.
We are migrating from SLES 11 SP3 to SLEs 12. On SLES 11 we use alfresco 5.0.c which
includes tomact 7.x i believe. SLES 11 has apache 2.2.10. SLES 12 has
No JkMount?
mod_jk uses the JkMount directive to decide, which requests should be
forwarded. Something like
JkMount /myapp|/* balancer
The directive should be put into the VirtualHost that is used in your
Apache web server config to serve the requests for /myapp.
When i look at the existing
Am 17.01.2015 um 01:51 schrieb Konstantin Kolinko:
2015-01-17 2:31 GMT+03:00 Chris Arnold carn...@electrichendrix.com:
Current working setup:
apache 2.2 using mod_jk to pass 443 requests to tomcat on 8443.
We are migrating from SLES 11 SP3 to SLEs 12. On SLES 11 we use alfresco 5.0.c which
Am 17.01.2015 um 03:43 schrieb Chris Arnold:
No JkMount?
mod_jk uses the JkMount directive to decide, which requests should be
forwarded. Something like
JkMount /myapp|/* balancer
The directive should be put into the VirtualHost that is used in your
Apache web server config to serve the
When i look at the apache log for that request, i dont see where the request
is even making it to apache or tomcat.
Try to request a static file from DocumentRoot directory.
If you cannot, then your HTTPS is not configured correctly. Get that
working first.
Yeah, I overlooked that in my
Am 17.01.2015 um 04:05 schrieb Chris Arnold:
When i look at the apache log for that request, i dont see where the request is
even making it to apache or tomcat.
Try to request a static file from DocumentRoot directory.
If you cannot, then your HTTPS is not configured correctly. Get that
#This rewrites https://share.anydomain.tld to our share server
RewriteEngine On
RewriteCond %{HTTP_HOST} ^share\.
RewriteCond %{HTTPS} on
RewriteCond %{REQUEST_URI} !^/share/
RewriteRule ^/(.*) https://share.domain.tld:8443/share/ [P]
That will forward any
22 matches
Mail list logo
