search

hoccer / hoccer-talk-spike

Android Client & Backend Software
0 stars 0 forks source link

Investigate Android L incompatibility #550

Closed xadh00m closed 9 years ago

xadh00m commented 10 years ago

As tested in #494 Hoccer XO fails to connect to the talk server with the latest preview of Android L.

Things to investigate/test:

superquadratic commented 10 years ago

Findings:

2014/11/10 16:07:13 [info] 9279#0: *722 peer closed connection in SSL handshake while SSL handshaking, client: 10.0.2.2, server: 0.0.0.0:443
2014/11/10 16:07:39 [info] 9279#0: *723 client closed connection while waiting for request, client: 10.0.2.2, server: 0.0.0.0:443
2014/11/10 16:08:08 [info] 9279#0: *726 peer closed connection in SSL handshake while SSL handshaking, client: 10.0.2.2, server: 0.0.0.0:443
2014/11/10 16:08:52 [info] 9279#0: *727 client closed connection while waiting for request, client: 10.0.2.2, server: 0.0.0.0:443
2014/11/10 16:09:09 [info] 9279#0: *730 client closed connection while waiting for request, client: 10.0.2.2, server: 0.0.0.0:443
2014/11/10 16:09:15 [info] 9279#0: *731 peer closed connection in SSL handshake while SSL handshaking, client: 10.0.2.2, server: 0.0.0.0:443
2014/11/10 16:09:36 [info] 9279#0: *732 peer closed connection in SSL handshake while SSL handshaking, client: 10.0.2.2, server: 0.0.0.0:443
2014/11/10 16:10:41 [info] 9279#0: *735 peer closed connection in SSL handshake while SSL handshaking, client: 10.0.2.2, server: 0.0.0.0:443
javax.net.ssl.SSLProtocolException: SSL handshake terminated: ssl=0xaf53a200: Failure in SSL library, usually a protocol error
error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number (external/openssl/ssl/s3_pkt.c:338 0xac4d4e61:0x00000000)

javax.net.ssl.SSLProtocolException: SSL handshake terminated: ssl=0xaf53a400: Failure in SSL library, usually a protocol error
error:1408E0F4:SSL routines:SSL3_GET_MESSAGE:unexpected message (external/openssl/ssl/s3_both.c:498 0xac4d4e61:0x00000000)

javax.net.ssl.SSLProtocolException: SSL handshake terminated: ssl=0xaf53ac00: Failure in SSL library, usually a protocol error
error:1408E0F4:SSL routines:SSL3_GET_MESSAGE:unexpected message (external/openssl/ssl/s3_both.c:498 0xac4d4e61:0x00000000)

javax.net.ssl.SSLProtocolException: SSL handshake terminated: ssl=0xaf53ae00: Failure in SSL library, usually a protocol error
error:1408E0F4:SSL routines:SSL3_GET_MESSAGE:unexpected message (external/openssl/ssl/s3_both.c:498 0xac4d4e61:0x00000000)

javax.net.ssl.SSLProtocolException: SSL handshake terminated: ssl=0xaf53b000: Failure in SSL library, usually a protocol error
error:1408E0F4:SSL routines:SSL3_GET_MESSAGE:unexpected message (external/openssl/ssl/s3_both.c:498 0xac4d4e61:0x00000000)

javax.net.ssl.SSLProtocolException: SSL handshake terminated: ssl=0xa303a200: Failure in SSL library, usually a protocol error
error:1408E0F4:SSL routines:SSL3_GET_MESSAGE:unexpected message (external/openssl/ssl/s3_both.c:498 0xac4d4e61:0x00000000)

javax.net.ssl.SSLProtocolException: SSL handshake terminated: ssl=0xa333a200: Failure in SSL library, usually a protocol error
error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number (external/openssl/ssl/s3_pkt.c:338 0xac4d4e61:0x00000000)

javax.net.ssl.SSLProtocolException: SSL handshake terminated: ssl=0xa313b200: Failure in SSL library, usually a protocol error
error:1408E0F4:SSL routines:SSL3_GET_MESSAGE:unexpected message (external/openssl/ssl/s3_both.c:498 0xac4d4e61:0x00000000)
xadh00m commented 10 years ago

The issue has been reported to Google and the Jetty Community.

superquadratic commented 9 years ago

We got a reply from the Jetty people, with no solution yet.

superquadratic commented 9 years ago 
Hi Guido,

Just a quick note that we are looking at it and trying to sort out what it
will take to resolve in that Jetty version.  I'll follow up soon with more
details.

Thanks for reporting the issue and following up with us :)

cheers,
Jesse

---
Jesse McConnell <jesse@intalio.com>
http://webtide.com - advice and support for jetty and cometd.
http://intalio.com - the modern way to build business applications.
superquadratic commented 9 years ago 
Guido,

I spoke with Joakim on this and he is under the impression there is nothing
to fix here, it is simply a configuration change and perhaps a
documentation task to clean up some of the verbiage.  He had tried the
version you asked about on there but there was nothing to do past that.  I
am not really sure what to say aside from pointing out that we can't fix
something we can't reproduce, is there something that is perhaps missing
from your bug and specific scenario?

Outside of a business relationship there is little we can do to work with
you to resolve the problem in situations like this, if we can't replicate
in simple fashion and triage/fix from bugzilla there is not a lot of time
available to do free support.  And from your perspective I can't imagine
you want to enter a yearly support agreement for what looks to amount to a
configuration issue.  If you have more information that could help us
reproduce either reopen the issue or create a new one with more details.  I
will explain how we normally do business and let you decide if you would
like to pursue that approach. :)

Webtide is the company behind both the Jetty and CometD projects, employing
all of the active committers on the projects and fully funding the
development through services and support contracts with companies like
yours.  Our entry support level is what we call a 'Lifecycle Support' which
is a yearly subscription which provides you with access to a private
message board where some number of your developers are able to ask
unlimited and unmetered support directly to the developers of these
projects.  Additionally our support options include production support for
an unlimited number of instances of Jetty and there are never any licensing
fees or anything like that associated with your usage of Jetty.  For
Webtide and the Jetty project, the 'professional' version is our open
source distributions.  With a subscription in place we allow our clients to
purchase Custom Hours which can be used for a variety of purposes including
sponsorship of features, etc.  Resolving bugs or issues within Jetty itself
is considered a part of the service and we do not seek recompense for fixed
these, they are fixed in open source and are just part of the project.
Client issues receive priority for resolution and we will create releases
as needed within the open source project based on our aggregate client
needs.

If you are interested in pursuing one of these lifecycle support
subscriptions let me know and we can have a call or trade some emails to
figure out which option is most appropriate and I can provide pricing
options.  Just to be clear, these yearly subscriptions are our only product
and we do not offer a 'per bug' support option or the direct purchase of
hours without a corresponding subscription.

cheers,
Jesse

---
Jesse McConnell <jesse@intalio.com>
http://webtide.com - advice and support for jetty and cometd.
http://intalio.com - the modern way to build business applications.