, SSLv3, TLSv1 and any combination of the three protocols
>> concatenated with a plus sign. Note that the protocol SSLv2 is inherently
>> unsafe.
>>
>>
>> SSLVerifyClient
>>
>> Ask client for certificate. The default is "none", meaning
On Mar 5, 2014 11:09 AM, "Christopher Schultz"
wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Howard,
>
> On 3/5/14, 9:45 AM, Howard W. Smith, Jr. wrote:
> > Chris,
> >
> > On Tue, Mar 4, 2014 at 4:18 PM, Christopher Schultz <
> > ch...@christopherschultz.net> wrote:
> >
> >> Dmi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Howard,
On 3/5/14, 9:45 AM, Howard W. Smith, Jr. wrote:
> Chris,
>
> On Tue, Mar 4, 2014 at 4:18 PM, Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
>> Dmitry,
>>
>> On 3/4/14, 2:48 AM, Dmitry Batiyevskiy wrote:
>>> Howard, My con
Chris,
On Tue, Mar 4, 2014 at 4:18 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> Dmitry,
>
> On 3/4/14, 2:48 AM, Dmitry Batiyevskiy wrote:
> > Howard, My connector config is the following (i've already posted
> > that):
> >
> > > enableLookups="false" disableUploadTimeout="tru
Maximum verification depth for client certificates. The default is "10".
>
>
>
> Tweak these Connector timeout parameters to acomodate your requirement
>
> asyncTimeout
>
> connectionTimeout
>
> connectionUploadTimeout
>
> disableUploa
ameters to acomodate your requirement
asyncTimeout
connectionTimeout
connectionUploadTimeout
disableUploadTimeout
executorTerminationTimeoutMillis
keepAliveTimeout
socket.soTimeout
socket.unlockTimeout
selectorTimeout
sessionTimeout
(yes..Mr Schultz is correct on the last statemen
Atmosphere upgrade didn't help
Regards,
Dmitry Batiyevskiy
Ardas Group Inc.
www.ardas.dp.ua
2014-03-05 9:39 GMT+02:00 Dmitry Batiyevskiy :
> We are ok with tomcat 7.0.42 and old tcnative now, and may be next
> tcnative update will work appropriately
> We will try updating atmosphere before t
We are ok with tomcat 7.0.42 and old tcnative now, and may be next tcnative
update will work appropriately
We will try updating atmosphere before trying NIO anyway
Regards,
Dmitry Batiyevskiy
Ardas Group Inc.
www.ardas.dp.ua
2014-03-04 23:18 GMT+02:00 Christopher Schultz :
> -BEGIN PGP S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dmitry,
On 3/4/14, 2:48 AM, Dmitry Batiyevskiy wrote:
> Howard, My connector config is the following (i've already posted
> that):
>
> enableLookups="false" disableUploadTimeout="true" acceptCount="100"
> scheme="https" secure="true" SSLEnabled="t
On Mar 4, 2014 2:49 AM, "Dmitry Batiyevskiy"
wrote:
>
> Howard,
> My connector config is the following (i've already posted that):
>
> maxThreads="15000"
> enableLookups="false" disableUploadTimeout="true"
> acceptCount="100" scheme="https"
Howard,
My connector config is the following (i've already posted that):
Also -Dhttps.protocols=TLSv1 option is passed to java machine
The reason for me to use apr connector is https performance, isn't NIO much
slower in that?
Regards,
Dmitry Batiyevskiy
Ardas Group Inc.
www.ardas.dp.
On Mon, Mar 3, 2014 at 11:22 AM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> Dmitry,
>
> On 3/3/14, 6:06 AM, Dmitry Batiyevskiy wrote:
> > Can you advice how we can find the problem in app/environment like
> > this? What are possible ways to debug this?
>
> Honestly, I'd try switc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Howard,
On 3/3/14, 10:09 AM, Howard W. Smith, Jr. wrote:
> On Mon, Mar 3, 2014 at 6:41 AM, Dmitry Batiyevskiy <
> dmitry.batiyevs...@ardas.dp.ua> wrote:
>
>> org.atmosphere.useNative
>> true
>>
>
> also, i wonder what your test results will b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dmitry,
On 3/3/14, 6:06 AM, Dmitry Batiyevskiy wrote:
> Can you advice how we can find the problem in app/environment like
> this? What are possible ways to debug this?
Honestly, I'd try switching to the NIO connector and resume your
testing. If al
On Mon, Mar 3, 2014 at 6:41 AM, Dmitry Batiyevskiy <
dmitry.batiyevs...@ardas.dp.ua> wrote:
>
> org.atmosphere.useNative
> true
>
>
also, i wonder what your test results will be if you comment out the lines
above from your web.xml.
On Mon, Mar 3, 2014 at 9:52 AM, Dmitry Batiyevskiy <
dmitry.batiyevs...@ardas.dp.ua> wrote:
> Thanks, I will try updating atmosphere and/or changing maxProcessingThreads
>
may not be completely related, but what is your maxThreads value in your
in server.xml ?
mine is below (found in tomee/conf
Thanks, I will try updating atmosphere and/or changing maxProcessingThreads
Regards,
Dmitry Batiyevskiy
Ardas Group Inc.
www.ardas.dp.ua
2014-03-03 16:33 GMT+02:00 Howard W. Smith, Jr. :
> On Mon, Mar 3, 2014 at 6:41 AM, Dmitry Batiyevskiy <
> dmitry.batiyevs...@ardas.dp.ua> wrote:
>
> > Atm
On Mon, Mar 3, 2014 at 6:41 AM, Dmitry Batiyevskiy <
dmitry.batiyevs...@ardas.dp.ua> wrote:
> Atmosphere dependencies from pom.xml:
>
>
> org.atmosphere.extensions
> atmosphere-gwt20-server
> 2.0.2
>
>
>
> org.atmosphere
> atmosphere-runtime
> 2.0.5
>
>
Looks good, but have you tried latest v
Atmosphere dependencies from pom.xml:
org.atmosphere.extensions
atmosphere-gwt20-server
2.0.2
org.atmosphere
atmosphere-runtime
2.0.5
Dependencies are in war file
Atmosphere config from web.xml:
AtmosphereServlet
AtmosphereServlet
org.atmosphere.cpr.AtmosphereServlet
1
true
org.atmosphe
On Mon, Mar 3, 2014 at 6:26 AM, Howard W. Smith, Jr. wrote:
>
> On Thu, Feb 20, 2014 at 11:00 AM, Dmitry Batiyevskiy <
> dmitry.batiyevs...@ardas.dp.ua> wrote:
>
>> We have upgraded tomcat 7.0.42 to 7.0.50
>> We have an app which is built around atmosphere framework and uses
>> websockets
>> Afte
On Thu, Feb 20, 2014 at 11:00 AM, Dmitry Batiyevskiy <
dmitry.batiyevs...@ardas.dp.ua> wrote:
> We have upgraded tomcat 7.0.42 to 7.0.50
> We have an app which is built around atmosphere framework and uses
> websockets
> After upgrade tomcat instance which has only this app dies in few hours
> aft
Can you advice how we can find the problem in app/environment like this?
What are possible ways to debug this?
Regards,
Dmitry Batiyevskiy
Ardas Group Inc.
www.ardas.dp.ua
2014-02-27 23:24 GMT+02:00 Christopher Schultz :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Dmitry,
>
> On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dmitry,
On 2/27/14, 3:27 PM, Dmitry Batiyevskiy wrote:
> This didn't helped, java process died with same error in about 5
> hours
Okay. The assert() call will in fact kill the process -- I had to check.
It seems that for the time being, your only
This didn't helped, java process died with same error in about 5 hours
Regards,
Dmitry Batiyevskiy
Ardas Group Inc.
www.ardas.dp.ua
2014-02-21 19:50 GMT+02:00 Dmitry Batiyevskiy <
dmitry.batiyevs...@ardas.dp.ua>:
> Ok thanks I will try setting org.apache.catalina.connector.RECYCLE_FACADES
>
Ok thanks I will try setting org.apache.catalina.connector.RECYCLE_FACADES
to true
Regards,
Dmitry Batiyevskiy
Ardas Group Inc.
www.ardas.dp.ua
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dmitry,
On 2/21/14, 11:17 AM, Dmitry Batiyevskiy wrote:
> 2014-02-21 18:10 GMT+02:00 Christopher Schultz
> > :
>
> Dmitry,
>
> On 2/20/14, 1:58 PM, Dmitry Batiyevskiy wrote:
When using tomcat 7.0.42 I used libtcnative 1.1.24-1 which
come
2014-02-21 18:10 GMT+02:00 Christopher Schultz :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Dmitry,
>
> On 2/20/14, 1:58 PM, Dmitry Batiyevskiy wrote:
> > When using tomcat 7.0.42 I used libtcnative 1.1.24-1 which comes
> > from debian repos Upgrade to tomcat 7.0.50 required upgrade
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dmitry,
On 2/20/14, 1:58 PM, Dmitry Batiyevskiy wrote:
> When using tomcat 7.0.42 I used libtcnative 1.1.24-1 which comes
> from debian repos Upgrade to tomcat 7.0.50 required upgrade of
> libtcnative also and there was no updated version in debi
When using tomcat 7.0.42 I used libtcnative 1.1.24-1 which comes from
debian repos
Upgrade to tomcat 7.0.50 required upgrade of libtcnative also and there
was no updated version in debian repos so I had to compile it from source
tarball downloaded here http://tomcat.apache.org/download-native.cgi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dmitry,
On 2/20/14, 11:00 AM, Dmitry Batiyevskiy wrote:
> We have upgraded tomcat 7.0.42 to 7.0.50 We have an app which is
> built around atmosphere framework and uses websockets After upgrade
> tomcat instance which has only this app dies in few ho
Dmitry Batiyevskiy wrote:
We have upgraded tomcat 7.0.42 to 7.0.50
We have an app which is built around atmosphere framework and uses
websockets
After upgrade tomcat instance which has only this app dies in few hours
after deploy (the whole java process dies)
The only error in log is following:
We have upgraded tomcat 7.0.42 to 7.0.50
We have an app which is built around atmosphere framework and uses
websockets
After upgrade tomcat instance which has only this app dies in few hours
after deploy (the whole java process dies)
The only error in log is following:
java: src/network.c:441: Jav
32 matches
Mail list logo
