On 12/4/2014 4:32 PM, Jason Ricles wrote:
Yes it was a bug so we will try to get a waiver to use 7.0.57 for our
environment instead of 7.0.53
So it works as expected in 7.0.57?
On Thu, Dec 4, 2014 at 1:20 PM, Jason Ricles wrote:
Well the trace is fine so I will upgrade and try and see wha
Yes it was a bug so we will try to get a waiver to use 7.0.57 for our
environment instead of 7.0.53
On Thu, Dec 4, 2014 at 1:20 PM, Jason Ricles wrote:
> Well the trace is fine so I will upgrade and try and see what happens.
> If it is not fixed I assume I should file a bug report.
>
> On Thu, De
Hello,
I have a Tomcat cluster (7.0.42) that is configured to use the DeltaManager
for session replication. It also uses the ClusterSingleSignOn valve for SSO
and for propagating authentication to the other nodes in the cluster. If I
log into Tomcat1, the session state and the single sign on state
Well the trace is fine so I will upgrade and try and see what happens.
If it is not fixed I assume I should file a bug report.
On Thu, Dec 4, 2014 at 1:19 PM, Mark Thomas wrote:
> On 04/12/2014 18:04, Jason Ricles wrote:
>> Due to some regulations out of my control right now we can only use
>> to
On 04/12/2014 18:04, Jason Ricles wrote:
> Due to some regulations out of my control right now we can only use
> tomcat 7.0.53. I also did a wireshark bug trace and going over the
> line the reserved bits are 0 but when computed in tomcat that is when
> the reserved are set to invalid bits. Is ther
Due to some regulations out of my control right now we can only use
tomcat 7.0.53. I also did a wireshark bug trace and going over the
line the reserved bits are 0 but when computed in tomcat that is when
the reserved are set to invalid bits. Is there any possible solution
or am I just out of luck
On 04/12/2014 15:26, Jason Ricles wrote:
> I have tomcat 7.0.53 and have been having a problem with the following
> error when sending a binary message "CloseReason: code [1002], reason
> [The client frame set the reserved bits to [x] which was not supported
> by this endpoint]" where x is between
I have tomcat 7.0.53 and have been having a problem with the following
error when sending a binary message "CloseReason: code [1002], reason
[The client frame set the reserved bits to [x] which was not supported
by this endpoint]" where x is between 1-7 when printed out. So I
remote debugged and st
On 04/12/2014 08:48, m...@ow2.org wrote:
> Hi,
>
> Is anyone can help me to find out what I am missing ?
There are lots of nasty edge cases in the deployment process. This has
been cleaned up in 7.0.x and 8.0.x but not in 6.0.x.
See
http://tomcat.apache.org/tomcat-8.0-doc/config/automatic-deploy
True, using a Validator which checks if validateAction == VALIDATE_INIT and
then performs the initSql itself will work. In my situation the
validatorClassName was a configurable property, so I ended up creating a simple
wrapper Validator which chooses between executing the initSql or calling the
On 04/12/2014 09:05, Roman Chrenko wrote:
> Hi, all.
>
> Is it possible to restrict JMX for Tomcat 7?
Yes. If you want a more specific answer, you'll need to ask a more
specific question.
> I use Tomcat 7.0.42.
Time to upgrade, especially if you are using JMX.
> I configured Tomcat as describe
2014-12-04 9:48 GMT+01:00 m...@ow2.org :
> Hi,
>
> Is anyone can help me to find out what I am missing ?
> Thanks
Hi:
I asked a similar question time ago
http://grokbase.com/t/tomcat/users/13chhkj0qx/modify-content-in-meta-inf-context-xml
I hope it helps you
Regards
>
> Le 02/12/2014 10:36
Hi folks,
we are experiencing a popular issue with MS .NET clients sending "Expect:
100-continue"
and Tomcat failing with HTTP 505.
We use Apache Tomcat 6.0.41 with APR connector on a corporate network.
The request look like this in Wireshark:
1. Client sends empty request with one TCP packet
2
Hi, all.
Is it possible to restrict JMX for Tomcat 7?
I use Tomcat 7.0.42. I configured Tomcat as described in
http://tomcat.apache.org/tomcat-7.0-doc/monitoring.html.
I used JmxRemoteLifecycleListener in server.xml, as described in
http://tomcat.apache.org/tomcat-7.0-doc/config/listeners.html
Hi,
Is anyone can help me to find out what I am missing ?
Thanks
Le 02/12/2014 10:36, m...@ow2.org a écrit :
> Hello,
>
> I'm facing an issue with tomcat 6. In order to setup a JDNI, we
> added a context.xml file to our application (XWiki) in the
> already-deployed folder webapps/xwiki/META-INF/
15 matches
Mail list logo