Re: Tomcat 8.5 Error related to Encoding Detector

[Guang Chao]

On Tue, Jan 15, 2019 at 8:31 PM prasoon sharma 
wrote:

> Hi
> I used the tutorial at
> https://www.rosehosting.com/blog/how-to-install-tomcat-8-on-a-centos-6-vps/
> and
> some tips from
>
> https://www.openprogrammer.info/2015/06/14/how-to-install-java-8-and-tomcat-8-on-centos-6-as-service/
> I have configured it at 8081 port
>
>
Did you also use Centos 6?


>
> On Tue, Jan 15, 2019 at 4:14 PM Mark Thomas  wrote:
>
> > On 15/01/2019 10:33, prasoon sharma wrote:
> > > Hi
> > > I am facing issue with Tomcat 8.5 on my Centos Server.
> > >
> > > I am getting HTTP 500 error as
> > >
> > > javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could
> > > not initialize class org.apache.jasper.compiler.EncodingDetector
> > >
> > >
> > > Check the detailed description at
> > >
> >
> https://stackoverflow.com/questions/54076418/java-lang-noclassdeffounderror-could-not-initialize-class-org-apache-jasper-com
> >
> > What steps did you take to install Apache Tomcat?
> >
> > Mark
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: users-h...@tomcat.apache.org
> >
> >
>


-- 
Guang 

Re: Tomcat 8.5 Error related to Encoding Detector

[Mark Thomas]

On 15/01/2019 12:31, prasoon sharma wrote:
> Hi
> I used the tutorial at
> https://www.rosehosting.com/blog/how-to-install-tomcat-8-on-a-centos-6-vps/ 
> and
> some tips from
> https://www.openprogrammer.info/2015/06/14/how-to-install-java-8-and-tomcat-8-on-centos-6-as-service/
> I have configured it at 8081 port

Which Tomcat version did you install?

Are you sure the download was not corrupted?

Does the manifest of $CATALINA_HOME/lib/jasper.jar show the same version?

Does your web application include any Tomcat JARs in WEB-INF/lib?

Mark

> 
> 
> On Tue, Jan 15, 2019 at 4:14 PM Mark Thomas  wrote:
> 
>> On 15/01/2019 10:33, prasoon sharma wrote:
>>> Hi
>>> I am facing issue with Tomcat 8.5 on my Centos Server.
>>>
>>> I am getting HTTP 500 error as
>>>
>>> javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could
>>> not initialize class org.apache.jasper.compiler.EncodingDetector
>>>
>>>
>>> Check the detailed description at
>>>
>> https://stackoverflow.com/questions/54076418/java-lang-noclassdeffounderror-could-not-initialize-class-org-apache-jasper-com
>>
>> What steps did you take to install Apache Tomcat?
>>
>> Mark
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: How to Disable / turn off the ETag header of Tomcat 7.0.92

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Ravi,

On 1/15/19 09:41, Ravi Kumar wrote:
> Please find my web.xml configuration file attached.

I don't see anything configured that looks like it might be an
"ignoreETagFilter". Did you configure it somewhere else?

- -chris

> On Tue, Jan 15, 2019 at 7:44 PM Christopher Schultz 
>  > wrote:
> 
> Mark,
> 
> On 1/15/19 06:12, Mark Thomas wrote:
>> On 15/01/2019 10:43, Ravi Kumar wrote:
>>> Hi All,
>>> 
>>> I am facing an issue. It is kind of Security issue as Tomcat's 
>>> ETag header in Response header can reveal vital info.
> 
>> What vital info? The ETag is constructed from the content length 
>> and the last modified date.
> 
>>> We want to disable / turnoff this ETag header of Tomcat 
>>> webserver. Referred this link :- 
>>> https://serverfault.com/questions/232763/how-to-disable-etag-headers
- -
>
>>> 
in-tomcat
> 
>>>
>>>
>
> 
but couldn't get success to disable this ETag.
>>> 
>>> Appreciate your help !
> 
>> The approached described in that link won't work if the response 
>> is sufficiently large that the response has already been
>> committed. You'd need to wrap the response, override
>> setHeader(String, String) and NO-OP and calls that try to set the
>> "ETag" header.
> 
> That's what Tim's SO answer suggests.
> 
> Ravi, I suspect that you haven't mapped the filter to your servlet 
> correctly. Can you post your configuration for your , 
> , and the URL you are trying to request?
> 
> -chris
> 
> -
>
> 
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>  For additional
> commands, e-mail: users-h...@tomcat.apache.org 
> 
> 
> 
> 
> -
>
> 
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlw+RyYACgkQHPApP6U8
pFjJrw//Sb1Y/Y6HXu5UQJLxtcacZgHI9jbXHcJFLVJmd//WmqQlmiGpWQ69NlgI
/d8R2DU934DDWAihRhKAl054VNILvYG52yhyUHBYmAdB6z1Y/xAmSdIgM3YCS5e+
NAaZXexrZKllWe9KUII00iaMfp+fP/kEH3v0nY7qrdKg3LELaM/wjgLtdrXcvjFP
4VQOeSRt6AnXOfUiyOTRXOwhe9S28vM3lZwv98da4+iwor8X2HJgIXwIScnu/Nxc
6EMrNMwgR2htsR92a31vDf2R111BaajrLgIBN7jzdEQlcFxwU4/SrS50Ha4NWEYB
C39t8Bvymrdmqn9+WXm4ht9JX8872BqXH8G0zhMxqufRYZ+zWru7FKSxWI0d2QJ/
QdUUH11GgEfueYM+sGUQRbQ6hlWAILPCTqAz7ClrNRzdJAbxpTmwOzuyGyTzQ4Ew
cvSQCNxWkF9Cu1R+lPyEf3A7SIJmrEBeoD6RNKrn+kxOcgDuHCYqL3/7CjHiV6UX
upI3D7bqYAhR5hpa+7G6YoaFx2MeotYoUVwKy2L7B+kiUVN/8vJwVNEOhHziDDw/
JOg07wifi31GnJ1L+i/4aCNCx9uCxT+IHz+5ZfHE7rheaJY/Q2BAYtzpzf36J/QS
nOiM7Mz6CH7FdXOjSVlWHcLwBR2dJISh9O7esYHW5h5FaFKtdHo=
=4WKz
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: StaticMembers within Multiple Clusters

[Mark Thomas]

On 15/01/2019 18:36, Tim K wrote:

> Question: what's considered a "large" cluster  I've seen a lot of
> documentation about small vs large but I'd like to know what is considered
> large.  Could the DeltaManager handle one single cluster (all-to-all) with
> 8 members with 8GB allocated to each jvm, separate servers?  Not storing
> much in the session besides 3-4 short strings.

It depends more on the frequency and size of session updates.

With the DeltaManager traffic volume is proportional to n(n-1) where n
is the number of nodes. With the BackupManager it is proportional to n.

With 8 nodes the DeltaManager generates 7 times the cluster traffic that
the BackManager generates. Whether your network will cope with that will
depend on the app and usage pattern.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: StaticMembers within Multiple Clusters

[Tim K]

On Tue, Jan 15, 2019, 12:51 PM Tim K  On Tue, Jan 15, 2019, 4:10 AM Keiichi Fujino 
>> Hi
>>
>> If you use StaticMembershipInterceptor, you must set the
>> Cluster#channelStartOptions to 3 to avoid starting membershipservice.
>> If you are using Tomcat 9, you can also use StaticMembershipService
>> instead
>> of StaticMembershipInterceptor.
>>
>>
>> 2019年1月10日(木) 22:39 Tim K :
>>
>> > On Wed, Jan 9, 2019, 2:16 PM Christopher Schultz <
>> > ch...@christopherschultz.net wrote:
>> >
>> > > -BEGIN PGP SIGNED MESSAGE-
>> > > Hash: SHA256
>> > >
>> > > Tim,
>> > >
>> > > On 1/9/19 10:39, Tim K wrote:
>> > > > I'm trying to split 4 separate tomcat instances into 2 clusters
>> > > > (2x2) to try and avoid the all-to-all traffic, but even when
>> > > > setting up the Receiver and Static members to only speak to 1 other
>> > > > instance, some still seems to find and add the other members
>> > > > outside of the defined config to the wrong cluster.  I read that
>> > > > mcast is still used when you have StaticMembers, could that be
>> > > > causing this issue?
>> > >
>> > > Multicast is only used for membership, so if you are using static,
>> > > there should be no multicast.
>> > >
>> > > Do you want to post your configuration(s)?
>> > >
>> > > - -chris
>> > > -BEGIN PGP SIGNATURE-
>> > > Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>> > >
>> > > iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlw2SIEACgkQHPApP6U8
>> > > pFh//A//WldkBxcRVWZ0Nj/FVjFqdhxr8dkystbk114wk8pjF/h5JOSmncQjvUn6
>> > > 999ZT54rXToS+Dl2svp9imR266o0+56bUvJVXG2O4NK7TQZsEsBdOsqfnWPoHBM3
>> > > kYS7lhzhlpmw1SDFlKVW0PnRX9acah5+SfVci5gL0cWTVqSkdmm4P6v2wqH1z7ej
>> > > AeMZ0w2LaoRH0TTxJk8cD2vJpvnB3oNjrtUhHZCPJCraITPHhFNFMOSmhhf3+e1S
>> > > K63D6l9kE3x4WDNtxKBBjr+5FaULM6kL5DotQlJPo0j7I4mL9DBgt2HkgTfoS39m
>> > > M7QBGBR4tZ1zRIJiGXQRViMRhqL+Xjny61RxtU7zUlfWSChTEonUiv5z6aZ7q5n2
>> > > xz1Evrw+gLmoR+YecOazMHef/7z6GFNCGyE80BFbR8LgHeOubaPfY+zhYw6iWSQP
>> > > eHt32x48vzPewYlV1HLJR7C1oXhFPN9QVT2r+UENcsMtlDdWIhaflw6nb3qXhP8N
>> > > t4xqlUJebON1KolHRXXReNgz6TieKLmup1jSgRvVhohSYBOputLB01PY5S7E6vLy
>> > > 33EZGHbCOWlZzC1qyiXRd7jIfkdsQ9oRRHknty1gi0id/20M+iqYS22ZggnXMtFX
>> > > P0lORhhEiWBSyMHytrIb+uO7HglocrSuQfgVaoAkiaRUDtyBdHg=
>> > > =PM9e
>> > > -END PGP SIGNATURE-
>> > >
>> > > -
>> > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> > > For additional commands, e-mail: users-h...@tomcat.apache.org
>> >
>> >
>> > Essentially I'm trying to have server1 and server2 only in cluster1 and
>> > server3 and server4 in only cluster2, but for some reason, members are
>> > getting added to clusters that they aren't configured for.
>> >
>> >
>> >
>> > server1 config:
>> >
>> > > > channelSendOptions="8">
>> >
>> > > > className="org.apache.catalina.ha.session.DeltaManager"
>> > expireSessionsOnShutdown="false" notifyListenersOnReplication="true"/>
>> >
>> > > > className="org.apache.catalina.tribes.group.GroupChannel">
>> >
>> > > > className="org.apache.catalina.tribes.transport.nio.NioReceiver"
>> > address="auto" port="4000" autoBind="100" selectorTimeout="5000"
>> > maxThreads="6"/>
>> >
>> > > > className="org.apache.catalina.tribes.transport.ReplicationTransmitter">
>> >
>> > > >
>> className="org.apache.catalina.tribes.transport.nio.PooledParallelSender"/>
>> >
>> > 
>> >
>> > > >
>> >
>> className="org.apache.catalina.tribes.group.interceptors.EncryptInterceptor"
>> > encryptionKey="Removed" />
>> >
>> > > >
>> >
>> className="org.apache.catalina.tribes.group.interceptors.TcpPingInterceptor"/>
>> >
>> > > >
>> >
>> className="org.apache.catalina.tribes.group.interceptors.TcpFailureDetector"/>
>> >
>> > > >
>> >
>> className="org.apache.catalina.tribes.group.interceptors.MessageDispatchInterceptor"/>
>> >
>> > > >
>> >
>> className="org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor">
>> >
>> > > > className="org.apache.catalina.tribes.membership.StaticMember"
>> > host="server2" port="4000" domain="cluster1"
>> > uniqueId="{1,0,2,3,4,5,6,7,8,9,10,11,12,13,14,15}"/>
>> >
>> > 
>> >
>> > 
>> >
>> > > > className="org.apache.catalina.ha.tcp.ReplicationValve" filter=""/>
>> >
>> > > > className="org.apache.catalina.ha.session.JvmRouteBinderValve"/>
>> >
>> > > > className="org.apache.catalina.ha.session.ClusterSessionListener"/>
>> >
>> > 
>> >
>> >
>> >
>> > server2 [everything the same except the  is]:
>> >
>> > > > host="server1" port="4000" 

Re: StaticMembers within Multiple Clusters

[Tim K]

On Tue, Jan 15, 2019, 4:10 AM Keiichi Fujino  Hi
>
> If you use StaticMembershipInterceptor, you must set the
> Cluster#channelStartOptions to 3 to avoid starting membershipservice.
> If you are using Tomcat 9, you can also use StaticMembershipService instead
> of StaticMembershipInterceptor.
>
>
> 2019年1月10日(木) 22:39 Tim K :
>
> > On Wed, Jan 9, 2019, 2:16 PM Christopher Schultz <
> > ch...@christopherschultz.net wrote:
> >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA256
> > >
> > > Tim,
> > >
> > > On 1/9/19 10:39, Tim K wrote:
> > > > I'm trying to split 4 separate tomcat instances into 2 clusters
> > > > (2x2) to try and avoid the all-to-all traffic, but even when
> > > > setting up the Receiver and Static members to only speak to 1 other
> > > > instance, some still seems to find and add the other members
> > > > outside of the defined config to the wrong cluster.  I read that
> > > > mcast is still used when you have StaticMembers, could that be
> > > > causing this issue?
> > >
> > > Multicast is only used for membership, so if you are using static,
> > > there should be no multicast.
> > >
> > > Do you want to post your configuration(s)?
> > >
> > > - -chris
> > > -BEGIN PGP SIGNATURE-
> > > Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
> > >
> > > iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlw2SIEACgkQHPApP6U8
> > > pFh//A//WldkBxcRVWZ0Nj/FVjFqdhxr8dkystbk114wk8pjF/h5JOSmncQjvUn6
> > > 999ZT54rXToS+Dl2svp9imR266o0+56bUvJVXG2O4NK7TQZsEsBdOsqfnWPoHBM3
> > > kYS7lhzhlpmw1SDFlKVW0PnRX9acah5+SfVci5gL0cWTVqSkdmm4P6v2wqH1z7ej
> > > AeMZ0w2LaoRH0TTxJk8cD2vJpvnB3oNjrtUhHZCPJCraITPHhFNFMOSmhhf3+e1S
> > > K63D6l9kE3x4WDNtxKBBjr+5FaULM6kL5DotQlJPo0j7I4mL9DBgt2HkgTfoS39m
> > > M7QBGBR4tZ1zRIJiGXQRViMRhqL+Xjny61RxtU7zUlfWSChTEonUiv5z6aZ7q5n2
> > > xz1Evrw+gLmoR+YecOazMHef/7z6GFNCGyE80BFbR8LgHeOubaPfY+zhYw6iWSQP
> > > eHt32x48vzPewYlV1HLJR7C1oXhFPN9QVT2r+UENcsMtlDdWIhaflw6nb3qXhP8N
> > > t4xqlUJebON1KolHRXXReNgz6TieKLmup1jSgRvVhohSYBOputLB01PY5S7E6vLy
> > > 33EZGHbCOWlZzC1qyiXRd7jIfkdsQ9oRRHknty1gi0id/20M+iqYS22ZggnXMtFX
> > > P0lORhhEiWBSyMHytrIb+uO7HglocrSuQfgVaoAkiaRUDtyBdHg=
> > > =PM9e
> > > -END PGP SIGNATURE-
> > >
> > > -
> > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > > For additional commands, e-mail: users-h...@tomcat.apache.org
> >
> >
> > Essentially I'm trying to have server1 and server2 only in cluster1 and
> > server3 and server4 in only cluster2, but for some reason, members are
> > getting added to clusters that they aren't configured for.
> >
> >
> >
> > server1 config:
> >
> >  > channelSendOptions="8">
> >
> >  > className="org.apache.catalina.ha.session.DeltaManager"
> > expireSessionsOnShutdown="false" notifyListenersOnReplication="true"/>
> >
> >  > className="org.apache.catalina.tribes.group.GroupChannel">
> >
> >  > className="org.apache.catalina.tribes.transport.nio.NioReceiver"
> > address="auto" port="4000" autoBind="100" selectorTimeout="5000"
> > maxThreads="6"/>
> >
> >  > className="org.apache.catalina.tribes.transport.ReplicationTransmitter">
> >
> >  >
> className="org.apache.catalina.tribes.transport.nio.PooledParallelSender"/>
> >
> > 
> >
> >  >
> >
> className="org.apache.catalina.tribes.group.interceptors.EncryptInterceptor"
> > encryptionKey="Removed" />
> >
> >  >
> >
> className="org.apache.catalina.tribes.group.interceptors.TcpPingInterceptor"/>
> >
> >  >
> >
> className="org.apache.catalina.tribes.group.interceptors.TcpFailureDetector"/>
> >
> >  >
> >
> className="org.apache.catalina.tribes.group.interceptors.MessageDispatchInterceptor"/>
> >
> >  >
> >
> className="org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor">
> >
> >  > className="org.apache.catalina.tribes.membership.StaticMember"
> > host="server2" port="4000" domain="cluster1"
> > uniqueId="{1,0,2,3,4,5,6,7,8,9,10,11,12,13,14,15}"/>
> >
> > 
> >
> > 
> >
> >  > className="org.apache.catalina.ha.tcp.ReplicationValve" filter=""/>
> >
> >  > className="org.apache.catalina.ha.session.JvmRouteBinderValve"/>
> >
> >  > className="org.apache.catalina.ha.session.ClusterSessionListener"/>
> >
> > 
> >
> >
> >
> > server2 [everything the same except the  is]:
> >
> >  > host="server1" port="4000" domain="cluster1"
> > uniqueId="{0,0,2,3,4,5,6,7,8,9,10,11,12,13,14,15}"/>
> >
> >
> >
> > server3 [everything the same except the  is]:
> >
> >  > host="server4" port="4000" domain="

Re: How to Disable / turn off the ETag header of Tomcat 7.0.92

[Ravi Kumar]

Hi Chris,

Please find my web.xml configuration file attached.

Thank you !

On Tue, Jan 15, 2019 at 7:44 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Mark,
>
> On 1/15/19 06:12, Mark Thomas wrote:
> > On 15/01/2019 10:43, Ravi Kumar wrote:
> >> Hi All,
> >>
> >> I am facing an issue. It is kind of Security issue as Tomcat's
> >> ETag header in Response header can reveal vital info.
> >
> > What vital info? The ETag is constructed from the content length
> > and the last modified date.
> >
> >> We want to disable / turnoff this ETag header of Tomcat
> >> webserver. Referred this link :-
> >> https://serverfault.com/questions/232763/how-to-disable-etag-headers-
> in-tomcat
> 
> >>
> >>
> but couldn't get success to disable this ETag.
> >>
> >> Appreciate your help !
> >
> > The approached described in that link won't work if the response
> > is sufficiently large that the response has already been committed.
> > You'd need to wrap the response, override setHeader(String, String)
> > and NO-OP and calls that try to set the "ETag" header.
>
> That's what Tim's SO answer suggests.
>
> Ravi, I suspect that you haven't mapped the filter to your servlet
> correctly. Can you post your configuration for your ,
> , and the URL you are trying to request?
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlw96tUACgkQHPApP6U8
> pFjnOBAAqvLfdCnYJn5UAmJtLEZ0JQTXOdcgTPulG+uckfxTSpHGggisc1HttA2M
> a8zhpVkTlhdXOFX3DcVJYa/YnM2ZwgF49S/PPQL+8kPfAK/HbSFSS1PGIgdO+W/9
> mnr46JrCUQETnRZksS6YStOrK7ST0pUhCr0n6DAfpDBc9Or6kRjX2RUrIfsDbV2o
> vJbXXzdacEUFNY4NpfkexWJPfXA7tnC4y7uJXT5ypwMd50oXrg+6sMZZt+ZUxO8L
> vDlEB3woIGpHSdL95UdSXUrvcSdL+XXDV+iDwj+G5Xj05DoEiVJG2p+rJHDeKtXY
> qRsz4fd4Hybyu7XrBrbufce/vXSndglSvRWbwjz41mFyNZYqV5PoRzqr6jssS7T3
> jDxOt84NuovsYQ3POBiSzLLHNeijAidoM/+hvmYhoogLryP8Tr7eBG2uvoesjMpq
> xYPAdUJPXAcw/CETtE+2q99ybuMyAnhhUNUgRn4W9CmUFFGwThCer+YlRAGng98L
> 80l10l7gytBxCRHZiuKg7ah0rek17svlskZNKYR3AFnP6oUqJoaWJab18oGifL7S
> uHhxsz3oAHN2THzPYSgWXIx30MN4X8GccdzZrCBw5DynxrAUyvxNDTEvj9rvrWjh
> MK8hqcfIKvE8Orx3S+YK0pZC1wv7Egx+gfYL3juM8L3JT9kieZM=
> =549e
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
http://java.sun.com/dtd/web-app_2_3.dtd";>





com.sales.administrator.AdministratorServlet
com.sales.uac.ui.PLEASE_USE_sales_administrator  



repo
com.sales.repo.RemoteRepoServlet
1



salesadmin_filter
com.sales.administrator.AdministratorServletFilter



salesadmin_XSSfilter
com.sales.administrator.AdministratorServletXSSFilter



  salesadmin_filter
  /servlet/*



  salesadmin_XSSfilter
  /servlet/*



sales_administrator
com.sales.administrator.AdministratorServlet
2



repo
/repo/*

   

sales_administrator
/servlet/sales_administrator



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 8.0.46

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Ismael,

On 1/15/19 06:32, Ismael López Quintero wrote:
> Great, then I must think that it must be an OOME error.

Don't guess: verify. It may take some time, but it's definitely worth
tracking this down to determine the real cause. Otherwise, you are
"solving" problems that do not exist, which is a waste of time.

Search your logs. Solve the mystery. Fix the problem.

- -chris

> -Mensaje original- De: Mark Thomas
> [mailto:ma...@apache.org] Enviado el: martes, 15 de enero de 2019
> 11:43 Para: users@tomcat.apache.org Asunto: Re: Tomcat 8.0.46
> 
> On 15/01/2019 10:24, Ismael López Quintero wrote:
>> Sorry by the late to answer but I've been ill.
>> 
>> The system were down on 2018/11/28 at night. It seems that is was
>> a Chinese attack (by the logged ips). Now I will show them...
>> 
>> These lines are from localhost_access_log_2018_11_28.txt
>> 
>> 85.137.148.55 - - [28/Nov/2018:22:38:41 +] "GET 
>> /api/webapi/chatucp/historicchats?idUser=4&idCustomer=1 HTTP/1.1"
>> 200 656 85.137.148.55 - - [28/Nov/2018:22:38:41 +] "GET 
>> /api/webapi/usersextcontact?idUser=4&idCustomer=1 HTTP/1.1" 200
>> 477 85.137.148.55 - - [28/Nov/2018:22:38:44 +] "GET 
>> /api/webapi/logout?idUser=4&idCustomer=1 HTTP/1.1" 200 - // Last
>> known IP 177.66.148.196 - - [28/Nov/2018:22:40:38 +] "GET /
>> HTTP/1.1" 200 11452 // Chinesse IP 180.97.106.164 - -
>> [28/Nov/2018:22:45:30 +] "-" 400 - // Chinesse IP 
>> 60.217.72.12 - - [28/Nov/2018:23:48:30 +] "GET / HTTP/1.1"
>> 200 11452 // Chinesse IP
>> 
>> In catalina.out for that day, I can find this crash:
>> 
>> 28-Nov-2018 22:45:30.227 INFO [http-nio-80-exec-149] 
>> org.apache.coyote.http11.AbstractHttp11Processor.process Error
>> parsing HTTP request header Note: further occurrences of HTTP
>> header parsing errors will be logged at DEBUG level. 
>> java.lang.IllegalArgumentException: Invalid character found in
>> method name. HTTP method names must be tokens at
>> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(Abst
ractNioInputBuffer.java:233)
>>
>> 
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11P
rocessor.java:1045)
>> at
>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(
AbstractProtocol.java:684)
>>
>> 
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint
.java:1539)
>> at
>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoin
t.java:1495)
>>
>> 
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.jav
a:1149)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:624)
>>
>> 
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThrea
d.java:61)
>> at java.lang.Thread.run(Thread.java:748)
> 
> That is not a crash. It is simply an invalid request that Tomcat
> has rejected. It will have no impact on the processing of future
> requests.
> 
> 
>> It seems that call "-" is not well parsed (obviously).
>> 
>> I can't find any info for syslog for that crash in those days.
>> 
>> Do you have any idea of the problem? It seems that Tomcat can
>> crash when no GET, POST, PUT, DELETE... request is done. The "-"
>> request seems to take Tomcat down.
> 
> There is no evidence (that has been presented in this thread) to
> support that conclusion.
> 
> Further, the above logs show that this conclusion is incorrect
> since the access log shows at least one request is processed after
> the "-" request.
> 
>> In have created a cron recurrent service to check if Tomcat is
>> listening in port 443, but I would like to solve this issue.
> 
> See Chris's previous response.
> 
> Mark
> 
> 
>> 
>> Thank you.
>> 
>> -- Fdo.: Ismael López Quintero. Ingeniero de Software. Correo
>> electrónico: ilopezqu...@gmail.com. Sitio Web:
>> http://www.desarrolladorsoftware.com/ Huelva. España.
>> 
>> -Mensaje original- De: Ismael López Quintero
>> [mailto:ilopezqu...@gmail.com] Enviado el: miércoles, 12 de
>> diciembre de 2018 10:32 Para: 'Tomcat Users List'
>>  Asunto: RE: Tomcat 8.0.46
>> 
>> Great! I will give more info. Please, forgive me by the content
>> shape faults. I'm new to this mail list.
>> 
>> I'll write ASAP.
>> 
>> Thank you!
>> 
>> PD: My system is Debian 8.
>> 
>> -- Fdo.: Ismael López Quintero. Ingeniero de Software. Correo
>> electrónico: ilopezqu...@gmail.com. Sitio Web:
>> http://www.desarrolladorsoftware.com/ Huelva. España.
>> 
>> -Mensaje original- De: Christopher Schultz
>> [mailto:ch...@christopherschultz.net] Enviado el: miércoles, 12
>> de diciembre de 2018 5:07 Para: users@tomcat.apache.org Asunto:
>> Re: Tomcat 8.0.46
>> 
>> Ismael,
>> 
>> On 12/11/18 08:45, Ismael López Quintero wrote:
>>> Hello! Crash: stop working. Process running and listenning in
>>> net ports 80 and 443 (SSL). After crashing, no process exist.
>> 
>> So... nothing in the Tomcat logs that says the process is going
>> down? For example, usual

Re: Tomcat 8.0.46

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Ismael,

On 1/15/19 05:24, Ismael López Quintero wrote:
> Sorry by the late to answer but I've been ill.
> 
> The system were down on 2018/11/28 at night. It seems that is was a
> Chinese attack (by the logged ips). Now I will show them...
> 
> These lines are from localhost_access_log_2018_11_28.txt
> 
> 85.137.148.55 - - [28/Nov/2018:22:38:41 +] "GET
> /api/webapi/chatucp/historicchats?idUser=4&idCustomer=1 HTTP/1.1"
> 200 656 85.137.148.55 - - [28/Nov/2018:22:38:41 +] "GET
> /api/webapi/usersextcontact?idUser=4&idCustomer=1 HTTP/1.1" 200
> 477 85.137.148.55 - - [28/Nov/2018:22:38:44 +] "GET
> /api/webapi/logout?idUser=4&idCustomer=1 HTTP/1.1"
200 - // Last known IP

The above are all from Spain.

> 177.66.148.196 - - [28/Nov/2018:22:40:38 +] "GET / HTTP/1.1"
> 200 11452 // Chinesse IP

No, this is Brazil.

> 180.97.106.164 - - [28/Nov/2018:22:45:30 +] "-" 400 - //
> Chinesse IP 60.217.72.12 - - [28/Nov/2018:23:48:30 +] "GET /
> HTTP/1.1" 200 11452 // Chinesse IP

These are from China. A request for "-"? Odd, but it was refused so
that's good, right?

I wouldn't call this an "attack". People from Brazil and China were
making requests to your web server. Presumably, you put it on the
internet so users could make web requests, right?

> In catalina.out for that day, I can find this crash:
> 
> 28-Nov-2018 22:45:30.227 INFO [http-nio-80-exec-149]
> org.apache.coyote.http11.AbstractHttp11Processor.process Error
> parsing HTTP request header Note: further occurrences of HTTP
> header parsing errors will be logged at DEBUG level. 
> java.lang.IllegalArgumentException: Invalid character found in
> method name. HTTP method names must be tokens at
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(Abstr
actNioInputBuffer.java:233)
>
> 
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11P
rocessor.java:1045)
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(A
bstractProtocol.java:684)
>
> 
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint
.java:1539)
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint
.java:1495)
>
> 
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.jav
a:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
java:624)
>
> 
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThrea
d.java:61)
> at java.lang.Thread.run(Thread.java:748)
> 
> It seems that call "-" is not well parsed (obviously).

Right.

> I can't find any info for syslog for that crash in those days.

Nothing crashed.

> Do you have any idea of the problem? It seems that Tomcat can
> crash when no GET, POST, PUT, DELETE... request is done. The "-"
> request seems to take Tomcat down.
ORLY? What evidence do you have of Tomcat being brought down by the
simplest of requests? Your own log file shows that Tomcat served a
request *after* the request for "-", so there is actually evidence
that Tomcat *survived* the "attack".

> In have created a cron recurrent service to check if Tomcat is 
> listening in port 443, but I would like to solve this issue.

Something else is definitely going on. Search your system logs for
"oom". Or reboots for that matter.

- -chris

> -Mensaje original- De: Ismael López Quintero
> [mailto:ilopezqu...@gmail.com] Enviado el: miércoles, 12 de
> diciembre de 2018 10:32 Para: 'Tomcat Users List'
>  Asunto: RE: Tomcat 8.0.46
> 
> Great! I will give more info. Please, forgive me by the content
> shape faults. I'm new to this mail list.
> 
> I'll write ASAP.
> 
> Thank you!
> 
> PD: My system is Debian 8.
> 
> -- Fdo.: Ismael López Quintero. Ingeniero de Software. Correo
> electrónico: ilopezqu...@gmail.com. Sitio Web:
> http://www.desarrolladorsoftware.com/ Huelva. España.
> 
> -Mensaje original- De: Christopher Schultz
> [mailto:ch...@christopherschultz.net] Enviado el: miércoles, 12 de
> diciembre de 2018 5:07 Para: users@tomcat.apache.org Asunto: Re:
> Tomcat 8.0.46
> 
> Ismael,
> 
> On 12/11/18 08:45, Ismael López Quintero wrote:
>> Hello! Crash: stop working. Process running and listenning in net
>>  ports 80 and 443 (SSL). After crashing, no process exist.
> 
> So... nothing in the Tomcat logs that says the process is going
> down? For example, usually Java OOME will show in catalina.out, but
> the JVM will not actually terminate.
> 
> My guess is Linux OOME killer (or similar). Check your syslog for
> "oome" (lowercase) if you are on Linux.
> 
> If you are *not* on Linux, that would seem to be very important
> information is you want to get some help.
> 
> Your original post was of the form "it didn't work; what went
> wrong?". We need much more information if we are going to be able
> to help you.
> 
> -chris
> 
>> -Mensaje original- De: Mark Thomas
>> [mailto:ma...@apache.org] Enviado el: martes, 11 de diciembre de 
>> 2018 14:

Re: How to Disable / turn off the ETag header of Tomcat 7.0.92

[Mark Thomas]

On 15/01/2019 14:14, Christopher Schultz wrote:
> Mark,
> 
> On 1/15/19 06:12, Mark Thomas wrote:
>> On 15/01/2019 10:43, Ravi Kumar wrote:
>>> Hi All,
>>>
>>> I am facing an issue. It is kind of Security issue as Tomcat's
>>> ETag header in Response header can reveal vital info.
> 
>> What vital info? The ETag is constructed from the content length
>> and the last modified date.
> 
>>> We want to disable / turnoff this ETag header of Tomcat
>>> webserver. Referred this link :- 
>>> https://serverfault.com/questions/232763/how-to-disable-etag-headers-
> in-tomcat
>>>
>>>
> but couldn't get success to disable this ETag.
>>>
>>> Appreciate your help !
> 
>> The approached described in that link won't work if the response
>> is sufficiently large that the response has already been committed.
>> You'd need to wrap the response, override setHeader(String, String)
>> and NO-OP and calls that try to set the "ETag" header.
> 
> That's what Tim's SO answer suggests.

Apologies. Too much context switching. I need to pay more attention.

Mark


> Ravi, I suspect that you haven't mapped the filter to your servlet
> correctly. Can you post your configuration for your ,
> , and the URL you are trying to request?
> 
> -chris
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: How to Disable / turn off the ETag header of Tomcat 7.0.92

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Mark,

On 1/15/19 06:12, Mark Thomas wrote:
> On 15/01/2019 10:43, Ravi Kumar wrote:
>> Hi All,
>> 
>> I am facing an issue. It is kind of Security issue as Tomcat's
>> ETag header in Response header can reveal vital info.
> 
> What vital info? The ETag is constructed from the content length
> and the last modified date.
> 
>> We want to disable / turnoff this ETag header of Tomcat
>> webserver. Referred this link :- 
>> https://serverfault.com/questions/232763/how-to-disable-etag-headers-
in-tomcat
>>
>> 
but couldn't get success to disable this ETag.
>> 
>> Appreciate your help !
> 
> The approached described in that link won't work if the response
> is sufficiently large that the response has already been committed.
> You'd need to wrap the response, override setHeader(String, String)
> and NO-OP and calls that try to set the "ETag" header.

That's what Tim's SO answer suggests.

Ravi, I suspect that you haven't mapped the filter to your servlet
correctly. Can you post your configuration for your ,
, and the URL you are trying to request?

- -chris
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlw96tUACgkQHPApP6U8
pFjnOBAAqvLfdCnYJn5UAmJtLEZ0JQTXOdcgTPulG+uckfxTSpHGggisc1HttA2M
a8zhpVkTlhdXOFX3DcVJYa/YnM2ZwgF49S/PPQL+8kPfAK/HbSFSS1PGIgdO+W/9
mnr46JrCUQETnRZksS6YStOrK7ST0pUhCr0n6DAfpDBc9Or6kRjX2RUrIfsDbV2o
vJbXXzdacEUFNY4NpfkexWJPfXA7tnC4y7uJXT5ypwMd50oXrg+6sMZZt+ZUxO8L
vDlEB3woIGpHSdL95UdSXUrvcSdL+XXDV+iDwj+G5Xj05DoEiVJG2p+rJHDeKtXY
qRsz4fd4Hybyu7XrBrbufce/vXSndglSvRWbwjz41mFyNZYqV5PoRzqr6jssS7T3
jDxOt84NuovsYQ3POBiSzLLHNeijAidoM/+hvmYhoogLryP8Tr7eBG2uvoesjMpq
xYPAdUJPXAcw/CETtE+2q99ybuMyAnhhUNUgRn4W9CmUFFGwThCer+YlRAGng98L
80l10l7gytBxCRHZiuKg7ah0rek17svlskZNKYR3AFnP6oUqJoaWJab18oGifL7S
uHhxsz3oAHN2THzPYSgWXIx30MN4X8GccdzZrCBw5DynxrAUyvxNDTEvj9rvrWjh
MK8hqcfIKvE8Orx3S+YK0pZC1wv7Egx+gfYL3juM8L3JT9kieZM=
=549e
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: StaticMembers within Multiple Clusters

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Keiichi,

On 1/15/19 04:10, Keiichi Fujino wrote:
> Hi
> 
> If you use StaticMembershipInterceptor, you must set the 
> Cluster#channelStartOptions to 3 to avoid starting
> membershipservice. If you are using Tomcat 9, you can also use
> StaticMembershipService instead of StaticMembershipInterceptor.

Is there any particular reason why the cluster components don't
perform sanity-checks about these kinds of things?

It seems like the StaticMembershipInterceptor could inspect those
options and issue warnings (or even refuse to start) if the
configuration does not make sense.

- -chris

> 2019年1月10日(木) 22:39 Tim K :
> 
>> On Wed, Jan 9, 2019, 2:16 PM Christopher Schultz < 
>> ch...@christopherschultz.net wrote:
>> 
> Tim,
> 
> On 1/9/19 10:39, Tim K wrote:
> I'm trying to split 4 separate tomcat instances into 2
> clusters (2x2) to try and avoid the all-to-all traffic, but
> even when setting up the Receiver and Static members to
> only speak to 1 other instance, some still seems to find
> and add the other members outside of the defined config to
> the wrong cluster.  I read that mcast is still used when
> you have StaticMembers, could that be causing this issue?
> 
> Multicast is only used for membership, so if you are using static, 
> there should be no multicast.
> 
> Do you want to post your configuration(s)?
> 
> -chris
>>> 
>>> 
- -
>>>
>>> 
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>> 
>> 
>> Essentially I'm trying to have server1 and server2 only in
>> cluster1 and server3 and server4 in only cluster2, but for some
>> reason, members are getting added to clusters that they aren't
>> configured for.
>> 
>> 
>> 
>> server1 config:
>> 
>> > channelSendOptions="8">
>> 
>> > expireSessionsOnShutdown="false"
>> notifyListenersOnReplication="true"/>
>> 
>> > className="org.apache.catalina.tribes.group.GroupChannel">
>> 
>> > className="org.apache.catalina.tribes.transport.nio.NioReceiver" 
>> address="auto" port="4000" autoBind="100" selectorTimeout="5000" 
>> maxThreads="6"/>
>> 
>> > className="org.apache.catalina.tribes.transport.ReplicationTransmitte
r">
>>
>>
>> 
> className="org.apache.catalina.tribes.transport.nio.PooledParallelSen
der"/>
>>
>>
>> 

>> 
>> > 
>> className="org.apache.catalina.tribes.group.interceptors.EncryptInter
ceptor"
>>
>> 
encryptionKey="Removed" />
>> 
>> > 
>> className="org.apache.catalina.tribes.group.interceptors.TcpPingInter
ceptor"/>
>>
>>
>> 
> 
>> className="org.apache.catalina.tribes.group.interceptors.TcpFailureDe
tector"/>
>>
>>
>> 
> 
>> className="org.apache.catalina.tribes.group.interceptors.MessageDispa
tchInterceptor"/>
>>
>>
>> 
> 
>> className="org.apache.catalina.tribes.group.interceptors.StaticMember
shipInterceptor">
>>
>>
>> 
> className="org.apache.catalina.tribes.membership.StaticMember" 
>> host="server2" port="4000" domain="cluster1" 
>> uniqueId="{1,0,2,3,4,5,6,7,8,9,10,11,12,13,14,15}"/>
>> 
>> 
>> 
>> 
>> 
>> > filter=""/>
>> 
>> > className="org.apache.catalina.ha.session.JvmRouteBinderValve"/>
>> 
>> > className="org.apache.catalina.ha.session.ClusterSessionListener"/>
>>
>>
>> 

>> 
>> 
>> 
>> server2 [everything the same except the  is]:
>> 
>> > className="org.apache.catalina.tribes.membership.StaticMember" 
>> host="server1" port="4000" domain="cluster1" 
>> uniqueId="{0,0,2,3,4,5,6,7,8,9,10,11,12,13,14,15}"/>
>> 
>> 
>> 
>> server3 [everything the same except the  is]:
>> 
>> > className="org.apache.catalina.tribes.membership.StaticMember" 
>> host="server4" port="4000" domain="cluster2" 
>> uniqueId="{4,0,2,3,4,5,6,7,8,9,10,11,12,13,14,15}"/>
>> 
>> 
>> 
>> server4 [everything the same except the  is]:
>> 
>> > className="org.apache.catalina.tribes.membership.StaticMember" 
>> host="server3" port="4000" domain="cluster2" 
>> uniqueId="{3,0,2,3,4,5,6,7,8,9,10,11,12,13,14,15}"/>
>> 
> 
> 
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlw96ewACgkQHPApP6U8
pFh5sxAAsdTpZFjxtH1o8ySD2vwZmS/PuKZEXCvZqsHl4IjDIsh1KnAOaE/jhm8u
N80eMQmQT8oMvYvSQ43gaiCpbnrclqCHgiPa8mQE91mdDB2jzjvhS/rwuoqMn1Kh
S99F6zH3WTaB8CGP4Sb6lgGRZMiuIrj2FKVXlOvuyHOq65Lm69lktc/ISQ3liC7F
+S5ii2cl9NJKF+ONi2IgEg+KJZXzl8Lo76ZEIwXLECE1LZyfN3cdUt3wOoKQCEfH
88Z3kzCjjGIiOneI/2WthJMybfl1eODv7ujzx5lQIf6cOaJvuBRi0GD9DSZ4LKqg
AOl5QbGos+CiugUo28bp/yaTEnzgQTa+bM/5x/VnO8ubNXqIAl/VbPCZO2CFhZAO
nuTrk2h+3VFVsQozNivIKI7sx7LYa2tN14embYDxiui8lQV7H2DmegODEG+dk7OA
7N8nljPn+T4T4txBk9uBBNheQpPaYNEG/csz+8j+lubo0pMa2jLoV9qoFiXTcja0
pkUxJ9jlGmhJ0uSFJttp1vTtzdsMBcxiwBjGwYmhMmlqRURPTBi4g2jTTG9GRh4x
t3gbFAWMQ5t7W5NY1KStnC4YFbdEDt372TRI+Cw32fakxsWPjBBS6ygCTI6Crc2K
BQXohOlTTHnMWAbux+2Bf5fLfATQx2uW64EvROupGx8vYz5B7RU=
=WI9r
-END PGP SIGNATURE-

---

Re: Tomcat 8.5 Error related to Encoding Detector

[prasoon sharma]

Hi
I used the tutorial at
https://www.rosehosting.com/blog/how-to-install-tomcat-8-on-a-centos-6-vps/ and
some tips from
https://www.openprogrammer.info/2015/06/14/how-to-install-java-8-and-tomcat-8-on-centos-6-as-service/
I have configured it at 8081 port


On Tue, Jan 15, 2019 at 4:14 PM Mark Thomas  wrote:

> On 15/01/2019 10:33, prasoon sharma wrote:
> > Hi
> > I am facing issue with Tomcat 8.5 on my Centos Server.
> >
> > I am getting HTTP 500 error as
> >
> > javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could
> > not initialize class org.apache.jasper.compiler.EncodingDetector
> >
> >
> > Check the detailed description at
> >
> https://stackoverflow.com/questions/54076418/java-lang-noclassdeffounderror-could-not-initialize-class-org-apache-jasper-com
>
> What steps did you take to install Apache Tomcat?
>
> Mark
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: How to Disable / turn off the ETag header of Tomcat 7.0.92

[Ravi Kumar]

Hi Mark,

Thank you for response. Could you please point me to any specific resource
/ link that would help achieve this?
Appreciate your help !

On Tue, Jan 15, 2019 at 4:42 PM Mark Thomas  wrote:

> On 15/01/2019 10:43, Ravi Kumar wrote:
> > Hi All,
> >
> > I am facing an issue. It is kind of Security issue as Tomcat's ETag
> header
> > in Response header can reveal vital info.
>
> What vital info? The ETag is constructed from the content length and the
> last modified date.
>
> > We want to disable / turnoff this ETag header of Tomcat webserver.
> > Referred this link :-
> >
> https://serverfault.com/questions/232763/how-to-disable-etag-headers-in-tomcat
> > but couldn't get success to disable this ETag.
> >
> > Appreciate your help !
>
> The approached described in that link won't work if the response is
> sufficiently large that the response has already been committed. You'd
> need to wrap the response, override setHeader(String, String) and NO-OP
> and calls that try to set the "ETag" header.
>
> Mark
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

RE: Tomcat 8.0.46

[Ismael López Quintero]

Great, then I must think that it must be an OOME error.

Thank you so much. 

--
Fdo.: Ismael López Quintero. 
Ingeniero de Software.
Correo electrónico: ilopezqu...@gmail.com.
Sitio Web: http://www.desarrolladorsoftware.com/
Huelva. España. 

-Mensaje original-
De: Mark Thomas [mailto:ma...@apache.org] 
Enviado el: martes, 15 de enero de 2019 11:43
Para: users@tomcat.apache.org
Asunto: Re: Tomcat 8.0.46

On 15/01/2019 10:24, Ismael López Quintero wrote:
> Sorry by the late to answer but I've been ill. 
> 
> The system were down on 2018/11/28 at night. It seems that is was a Chinese 
> attack (by the logged ips). Now I will show them...
> 
> These lines are from localhost_access_log_2018_11_28.txt
> 
> 85.137.148.55 - - [28/Nov/2018:22:38:41 +] "GET 
> /api/webapi/chatucp/historicchats?idUser=4&idCustomer=1 HTTP/1.1" 200 
> 656
> 85.137.148.55 - - [28/Nov/2018:22:38:41 +] "GET 
> /api/webapi/usersextcontact?idUser=4&idCustomer=1 HTTP/1.1" 200 477
> 85.137.148.55 - - [28/Nov/2018:22:38:44 +] "GET 
> /api/webapi/logout?idUser=4&idCustomer=1 HTTP/1.1" 200 - // Last known 
> IP
> 177.66.148.196 - - [28/Nov/2018:22:40:38 +] "GET / HTTP/1.1" 200 
> 11452 // Chinesse IP
> 180.97.106.164 - - [28/Nov/2018:22:45:30 +] "-" 400 - // Chinesse 
> IP
> 60.217.72.12 - - [28/Nov/2018:23:48:30 +] "GET / HTTP/1.1" 200 
> 11452 // Chinesse IP
> 
> In catalina.out for that day, I can find this crash:
> 
> 28-Nov-2018 22:45:30.227 INFO [http-nio-80-exec-149] 
> org.apache.coyote.http11.AbstractHttp11Processor.process Error parsing 
> HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
>  java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
> at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
> at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1045)
> at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
> at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1539)
> at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1495)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> at java.lang.Thread.run(Thread.java:748)

That is not a crash. It is simply an invalid request that Tomcat has rejected. 
It will have no impact on the processing of future requests.


> It seems that call "-" is not well parsed (obviously).
> 
> I can't find any info for syslog for that crash in those days.
> 
> Do you have any idea of the problem? It seems that Tomcat can crash when no 
> GET, POST, PUT, DELETE... request is done. The "-" request seems to take 
> Tomcat down.

There is no evidence (that has been presented in this thread) to support that 
conclusion.

Further, the above logs show that this conclusion is incorrect since the access 
log shows at least one request is processed after the "-" request.

> In have created a cron recurrent service to check if Tomcat is listening in 
> port 443, but I would like to solve this issue.

See Chris's previous response.

Mark


> 
> Thank you.
> 
> --
> Fdo.: Ismael López Quintero. 
> Ingeniero de Software.
> Correo electrónico: ilopezqu...@gmail.com.
> Sitio Web: http://www.desarrolladorsoftware.com/
> Huelva. España. 
> 
> -Mensaje original-
> De: Ismael López Quintero [mailto:ilopezqu...@gmail.com] Enviado el: 
> miércoles, 12 de diciembre de 2018 10:32
> Para: 'Tomcat Users List' 
> Asunto: RE: Tomcat 8.0.46
> 
> Great! I will give more info. Please, forgive me by the content shape faults. 
> I'm new to this mail list.
> 
> I'll write ASAP.
> 
> Thank you!
> 
> PD: My system is Debian 8.
> 
> --
> Fdo.: Ismael López Quintero. 
> Ingeniero de Software.
> Correo electrónico: ilopezqu...@gmail.com.
> Sitio Web: http://www.desarrolladorsoftware.com/
> Huelva. España. 
> 
> -Mensaje original-
> De: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Enviado el: miércoles, 12 de diciembre de 2018 5:07
> Para: users@tomcat.apache.org
> Asunto: Re: Tomcat 8.0.46
> 
> Ismael,
> 
> On 12/11/18 08:45, Ismael López Quintero wrote:
>> Hello! Crash: stop working. Process running and listenning in net 
>> ports 80 and 443 (SSL). After crashing, no process exist.
> 
> So... nothing in the Tomcat logs that says the process is going down?
> For example, usually Java OOME will show in catalina.out, but the JVM will 
> not actually terminate.
> 
> My guess is Linux OOME killer (or similar). Check your syslog for "oome" 
> (lowercase) if you are on Linux.
> 
> If you

Re: distinction between resource charset and format octet decoding

[Mark Thomas]

On 15/01/2019 03:39, Garret Wilson wrote:
> On 1/9/2019 2:30 AM, Mark Thomas wrote:
>> …
>> Create yourself an account at https://wiki.apache.org/tomcat (click
>> login then create an account) and let the list know your ID. Then one of
>> the admins can add you to the allowed editors.
> 
> 
> I was just ready to create an account, but I want to verify the details
> so I don't screw things up.
> 
>  * It asks for a "Name". Is this a username, I suppose? So we don't
>    maintain our "name" separate from our "login username"?

Yes, it is your username. Any linkage from that to your "public name"
would be maintained on your user page - if you wish.

>  * It says to use "FirstnameLastName". Are you literally wanting us to
>    use "JohnDoe", or can we use "johndoe"? Sorry for the questions; as
>    one who works with protocols all the time, I automatically assume
>    this stuff is important. But I prefer to use lowercase on my
>    usernames; I'm a little confused about why this would want
>    PascalCase for a login username. (I can't think of another system
>    that I use that requires PascalCase usernames.)

Think of it as a SHOULD rather than a MUST.

> My guess is that it's trying to maintain a "human name" and a "username"
> but combine them both into one field or something. I can't say this
> approach is typical…

Anything in PascalCase becomes a link to a wiki page of that name.
Usernames are created in this form so references to the user
automatically become links to that user's page in the wiki.

It isn't a feature we use much at the moment. A quick check shows that
most, but not all, contributors have created their user name in PascalCase.

For example, take a look at https://wiki.apache.org/tomcat/AndrewCarr

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: How to Disable / turn off the ETag header of Tomcat 7.0.92

[Mark Thomas]

On 15/01/2019 10:43, Ravi Kumar wrote:
> Hi All,
> 
> I am facing an issue. It is kind of Security issue as Tomcat's ETag header
> in Response header can reveal vital info.

What vital info? The ETag is constructed from the content length and the
last modified date.

> We want to disable / turnoff this ETag header of Tomcat webserver.
> Referred this link :-
> https://serverfault.com/questions/232763/how-to-disable-etag-headers-in-tomcat
> but couldn't get success to disable this ETag.
> 
> Appreciate your help !

The approached described in that link won't work if the response is
sufficiently large that the response has already been committed. You'd
need to wrap the response, override setHeader(String, String) and NO-OP
and calls that try to set the "ETag" header.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

How to Disable / turn off the ETag header of Tomcat 7.0.92

[Ravi Kumar]

Hi All,

I am facing an issue. It is kind of Security issue as Tomcat's ETag header
in Response header can reveal vital info.

We want to disable / turnoff this ETag header of Tomcat webserver.
Referred this link :-
https://serverfault.com/questions/232763/how-to-disable-etag-headers-in-tomcat
but couldn't get success to disable this ETag.

Appreciate your help !

Thanks,
Ravi

Re: Tomcat 8.5 Error related to Encoding Detector

[Mark Thomas]

On 15/01/2019 10:33, prasoon sharma wrote:
> Hi
> I am facing issue with Tomcat 8.5 on my Centos Server.
> 
> I am getting HTTP 500 error as
> 
> javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could
> not initialize class org.apache.jasper.compiler.EncodingDetector
> 
> 
> Check the detailed description at
> https://stackoverflow.com/questions/54076418/java-lang-noclassdeffounderror-could-not-initialize-class-org-apache-jasper-com

What steps did you take to install Apache Tomcat?

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 8.0.46

[Mark Thomas]

On 15/01/2019 10:24, Ismael López Quintero wrote:
> Sorry by the late to answer but I've been ill. 
> 
> The system were down on 2018/11/28 at night. It seems that is was a Chinese 
> attack (by the logged ips). Now I will show them...
> 
> These lines are from localhost_access_log_2018_11_28.txt
> 
> 85.137.148.55 - - [28/Nov/2018:22:38:41 +] "GET 
> /api/webapi/chatucp/historicchats?idUser=4&idCustomer=1 HTTP/1.1" 200 656
> 85.137.148.55 - - [28/Nov/2018:22:38:41 +] "GET 
> /api/webapi/usersextcontact?idUser=4&idCustomer=1 HTTP/1.1" 200 477
> 85.137.148.55 - - [28/Nov/2018:22:38:44 +] "GET 
> /api/webapi/logout?idUser=4&idCustomer=1 HTTP/1.1" 200 - // Last known IP
> 177.66.148.196 - - [28/Nov/2018:22:40:38 +] "GET / HTTP/1.1" 200 11452 // 
> Chinesse IP
> 180.97.106.164 - - [28/Nov/2018:22:45:30 +] "-" 400 - // Chinesse IP
> 60.217.72.12 - - [28/Nov/2018:23:48:30 +] "GET / HTTP/1.1" 200 11452 // 
> Chinesse IP
> 
> In catalina.out for that day, I can find this crash:
> 
> 28-Nov-2018 22:45:30.227 INFO [http-nio-80-exec-149] 
> org.apache.coyote.http11.AbstractHttp11Processor.process Error parsing HTTP 
> request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
>  java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
> at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
> at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1045)
> at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
> at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1539)
> at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1495)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> at java.lang.Thread.run(Thread.java:748)

That is not a crash. It is simply an invalid request that Tomcat has
rejected. It will have no impact on the processing of future requests.


> It seems that call "-" is not well parsed (obviously).
> 
> I can't find any info for syslog for that crash in those days.
> 
> Do you have any idea of the problem? It seems that Tomcat can crash when no 
> GET, POST, PUT, DELETE... request is done. The "-" request seems to take 
> Tomcat down.

There is no evidence (that has been presented in this thread) to support
that conclusion.

Further, the above logs show that this conclusion is incorrect since the
access log shows at least one request is processed after the "-" request.

> In have created a cron recurrent service to check if Tomcat is listening in 
> port 443, but I would like to solve this issue.

See Chris's previous response.

Mark


> 
> Thank you.
> 
> --
> Fdo.: Ismael López Quintero. 
> Ingeniero de Software.
> Correo electrónico: ilopezqu...@gmail.com.
> Sitio Web: http://www.desarrolladorsoftware.com/
> Huelva. España. 
> 
> -Mensaje original-
> De: Ismael López Quintero [mailto:ilopezqu...@gmail.com] 
> Enviado el: miércoles, 12 de diciembre de 2018 10:32
> Para: 'Tomcat Users List' 
> Asunto: RE: Tomcat 8.0.46
> 
> Great! I will give more info. Please, forgive me by the content shape faults. 
> I'm new to this mail list.
> 
> I'll write ASAP.
> 
> Thank you!
> 
> PD: My system is Debian 8.
> 
> --
> Fdo.: Ismael López Quintero. 
> Ingeniero de Software.
> Correo electrónico: ilopezqu...@gmail.com.
> Sitio Web: http://www.desarrolladorsoftware.com/
> Huelva. España. 
> 
> -Mensaje original-
> De: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Enviado el: miércoles, 12 de diciembre de 2018 5:07
> Para: users@tomcat.apache.org
> Asunto: Re: Tomcat 8.0.46
> 
> Ismael,
> 
> On 12/11/18 08:45, Ismael López Quintero wrote:
>> Hello! Crash: stop working. Process running and listenning in net 
>> ports 80 and 443 (SSL). After crashing, no process exist.
> 
> So... nothing in the Tomcat logs that says the process is going down?
> For example, usually Java OOME will show in catalina.out, but the JVM will 
> not actually terminate.
> 
> My guess is Linux OOME killer (or similar). Check your syslog for "oome" 
> (lowercase) if you are on Linux.
> 
> If you are *not* on Linux, that would seem to be very important information 
> is you want to get some help.
> 
> Your original post was of the form "it didn't work; what went wrong?".
> We need much more information if we are going to be able to help you.
> 
> -chris
> 
>> -Mensaje original- De: Mark Thomas [mailto:ma...@apache.org] 
>> Enviado el: martes, 11 de diciembre de
>> 2018 14:05 Para: users@tomcat.apache.org Asun

Tomcat 8.5 Error related to Encoding Detector

[prasoon sharma]

Hi
I am facing issue with Tomcat 8.5 on my Centos Server.

I am getting HTTP 500 error as

javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could
not initialize class org.apache.jasper.compiler.EncodingDetector


Check the detailed description at
https://stackoverflow.com/questions/54076418/java-lang-noclassdeffounderror-could-not-initialize-class-org-apache-jasper-com

Thanks

RE: Tomcat 8.0.46

[Ismael López Quintero]

Sorry by the late to answer but I've been ill. 

The system were down on 2018/11/28 at night. It seems that is was a Chinese 
attack (by the logged ips). Now I will show them...

These lines are from localhost_access_log_2018_11_28.txt

85.137.148.55 - - [28/Nov/2018:22:38:41 +] "GET 
/api/webapi/chatucp/historicchats?idUser=4&idCustomer=1 HTTP/1.1" 200 656
85.137.148.55 - - [28/Nov/2018:22:38:41 +] "GET 
/api/webapi/usersextcontact?idUser=4&idCustomer=1 HTTP/1.1" 200 477
85.137.148.55 - - [28/Nov/2018:22:38:44 +] "GET 
/api/webapi/logout?idUser=4&idCustomer=1 HTTP/1.1" 200 - // Last known IP
177.66.148.196 - - [28/Nov/2018:22:40:38 +] "GET / HTTP/1.1" 200 11452 // 
Chinesse IP
180.97.106.164 - - [28/Nov/2018:22:45:30 +] "-" 400 - // Chinesse IP
60.217.72.12 - - [28/Nov/2018:23:48:30 +] "GET / HTTP/1.1" 200 11452 // 
Chinesse IP

In catalina.out for that day, I can find this crash:

28-Nov-2018 22:45:30.227 INFO [http-nio-80-exec-149] 
org.apache.coyote.http11.AbstractHttp11Processor.process Error parsing HTTP 
request header
 Note: further occurrences of HTTP header parsing errors will be logged at 
DEBUG level.
 java.lang.IllegalArgumentException: Invalid character found in method name. 
HTTP method names must be tokens
at 
org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1045)
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1539)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1495)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)

It seems that call "-" is not well parsed (obviously).

I can't find any info for syslog for that crash in those days.

Do you have any idea of the problem? It seems that Tomcat can crash when no 
GET, POST, PUT, DELETE... request is done. The "-" request seems to take Tomcat 
down.

In have created a cron recurrent service to check if Tomcat is listening in 
port 443, but I would like to solve this issue.

Thank you.

--
Fdo.: Ismael López Quintero. 
Ingeniero de Software.
Correo electrónico: ilopezqu...@gmail.com.
Sitio Web: http://www.desarrolladorsoftware.com/
Huelva. España. 

-Mensaje original-
De: Ismael López Quintero [mailto:ilopezqu...@gmail.com] 
Enviado el: miércoles, 12 de diciembre de 2018 10:32
Para: 'Tomcat Users List' 
Asunto: RE: Tomcat 8.0.46

Great! I will give more info. Please, forgive me by the content shape faults. 
I'm new to this mail list.

I'll write ASAP.

Thank you!

PD: My system is Debian 8.

--
Fdo.: Ismael López Quintero. 
Ingeniero de Software.
Correo electrónico: ilopezqu...@gmail.com.
Sitio Web: http://www.desarrolladorsoftware.com/
Huelva. España. 

-Mensaje original-
De: Christopher Schultz [mailto:ch...@christopherschultz.net]
Enviado el: miércoles, 12 de diciembre de 2018 5:07
Para: users@tomcat.apache.org
Asunto: Re: Tomcat 8.0.46

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Ismael,

On 12/11/18 08:45, Ismael López Quintero wrote:
> Hello! Crash: stop working. Process running and listenning in net 
> ports 80 and 443 (SSL). After crashing, no process exist.

So... nothing in the Tomcat logs that says the process is going down?
For example, usually Java OOME will show in catalina.out, but the JVM will not 
actually terminate.

My guess is Linux OOME killer (or similar). Check your syslog for "oome" 
(lowercase) if you are on Linux.

If you are *not* on Linux, that would seem to be very important information is 
you want to get some help.

Your original post was of the form "it didn't work; what went wrong?".
We need much more information if we are going to be able to help you.

- -chris

> -Mensaje original- De: Mark Thomas [mailto:ma...@apache.org] 
> Enviado el: martes, 11 de diciembre de
> 2018 14:05 Para: users@tomcat.apache.org Asunto: Re: Tomcat 8.0.46
> 
> On 11/12/2018 12:38, Ismael López Quintero wrote:
>> Hello!
>> 
>> 
>> 
>> My Tomcat installation crashed some days ago.  It is deployed to 
>> serve a REST API using Jersey. Looking at localhost_access_log daily 
>> file, just before crashing it received the next requests…
>> 
>> 
>> 
>> X.X.X.X - - [28/Nov/2018:22:38:44 +] "GET 
>> /api/webapi/logout?idUser=4&idCustomer=1 HTTP/1.1" 200 -   ß-
>> This is the last known call before crashing
>> 
>> X.X.X.X - - [28/Nov/2018:22:40:38 +] "GET / HTTP/1.1" 200
>> 11452
>> 
>> X.X.X.X - - [28/Nov/2018:22:45:30 +] "-" 400 -
>> 
>> X.X.X.X - - [28/Nov/2018:23:

Re: StaticMembers within Multiple Clusters

[Keiichi Fujino]

Hi

If you use StaticMembershipInterceptor, you must set the
Cluster#channelStartOptions to 3 to avoid starting membershipservice.
If you are using Tomcat 9, you can also use StaticMembershipService instead
of StaticMembershipInterceptor.


2019年1月10日(木) 22:39 Tim K :

> On Wed, Jan 9, 2019, 2:16 PM Christopher Schultz <
> ch...@christopherschultz.net wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Tim,
> >
> > On 1/9/19 10:39, Tim K wrote:
> > > I'm trying to split 4 separate tomcat instances into 2 clusters
> > > (2x2) to try and avoid the all-to-all traffic, but even when
> > > setting up the Receiver and Static members to only speak to 1 other
> > > instance, some still seems to find and add the other members
> > > outside of the defined config to the wrong cluster.  I read that
> > > mcast is still used when you have StaticMembers, could that be
> > > causing this issue?
> >
> > Multicast is only used for membership, so if you are using static,
> > there should be no multicast.
> >
> > Do you want to post your configuration(s)?
> >
> > - -chris
> > -BEGIN PGP SIGNATURE-
> > Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
> >
> > iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlw2SIEACgkQHPApP6U8
> > pFh//A//WldkBxcRVWZ0Nj/FVjFqdhxr8dkystbk114wk8pjF/h5JOSmncQjvUn6
> > 999ZT54rXToS+Dl2svp9imR266o0+56bUvJVXG2O4NK7TQZsEsBdOsqfnWPoHBM3
> > kYS7lhzhlpmw1SDFlKVW0PnRX9acah5+SfVci5gL0cWTVqSkdmm4P6v2wqH1z7ej
> > AeMZ0w2LaoRH0TTxJk8cD2vJpvnB3oNjrtUhHZCPJCraITPHhFNFMOSmhhf3+e1S
> > K63D6l9kE3x4WDNtxKBBjr+5FaULM6kL5DotQlJPo0j7I4mL9DBgt2HkgTfoS39m
> > M7QBGBR4tZ1zRIJiGXQRViMRhqL+Xjny61RxtU7zUlfWSChTEonUiv5z6aZ7q5n2
> > xz1Evrw+gLmoR+YecOazMHef/7z6GFNCGyE80BFbR8LgHeOubaPfY+zhYw6iWSQP
> > eHt32x48vzPewYlV1HLJR7C1oXhFPN9QVT2r+UENcsMtlDdWIhaflw6nb3qXhP8N
> > t4xqlUJebON1KolHRXXReNgz6TieKLmup1jSgRvVhohSYBOputLB01PY5S7E6vLy
> > 33EZGHbCOWlZzC1qyiXRd7jIfkdsQ9oRRHknty1gi0id/20M+iqYS22ZggnXMtFX
> > P0lORhhEiWBSyMHytrIb+uO7HglocrSuQfgVaoAkiaRUDtyBdHg=
> > =PM9e
> > -END PGP SIGNATURE-
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
> Essentially I'm trying to have server1 and server2 only in cluster1 and
> server3 and server4 in only cluster2, but for some reason, members are
> getting added to clusters that they aren't configured for.
>
>
>
> server1 config:
>
>  channelSendOptions="8">
>
>  className="org.apache.catalina.ha.session.DeltaManager"
> expireSessionsOnShutdown="false" notifyListenersOnReplication="true"/>
>
>  className="org.apache.catalina.tribes.group.GroupChannel">
>
>  className="org.apache.catalina.tribes.transport.nio.NioReceiver"
> address="auto" port="4000" autoBind="100" selectorTimeout="5000"
> maxThreads="6"/>
>
>  className="org.apache.catalina.tribes.transport.ReplicationTransmitter">
>
>  className="org.apache.catalina.tribes.transport.nio.PooledParallelSender"/>
>
> 
>
> 
> className="org.apache.catalina.tribes.group.interceptors.EncryptInterceptor"
> encryptionKey="Removed" />
>
> 
> className="org.apache.catalina.tribes.group.interceptors.TcpPingInterceptor"/>
>
> 
> className="org.apache.catalina.tribes.group.interceptors.TcpFailureDetector"/>
>
> 
> className="org.apache.catalina.tribes.group.interceptors.MessageDispatchInterceptor"/>
>
> 
> className="org.apache.catalina.tribes.group.interceptors.StaticMembershipInterceptor">
>
>  className="org.apache.catalina.tribes.membership.StaticMember"
> host="server2" port="4000" domain="cluster1"
> uniqueId="{1,0,2,3,4,5,6,7,8,9,10,11,12,13,14,15}"/>
>
> 
>
> 
>
>  className="org.apache.catalina.ha.tcp.ReplicationValve" filter=""/>
>
>  className="org.apache.catalina.ha.session.JvmRouteBinderValve"/>
>
>  className="org.apache.catalina.ha.session.ClusterSessionListener"/>
>
> 
>
>
>
> server2 [everything the same except the  is]:
>
>  host="server1" port="4000" domain="cluster1"
> uniqueId="{0,0,2,3,4,5,6,7,8,9,10,11,12,13,14,15}"/>
>
>
>
> server3 [everything the same except the  is]:
>
>  host="server4" port="4000" domain="cluster2"
> uniqueId="{4,0,2,3,4,5,6,7,8,9,10,11,12,13,14,15}"/>
>
>
>
> server4 [everything the same except the  is]:
>
>  host="server3" port="4000" domain="cluster2"
> uniqueId="{3,0,2,3,4,5,6,7,8,9,10,11,12,13,14,15}"/>
>


-- 
Keiichi.Fujino