-
Notifications
You must be signed in to change notification settings - Fork 453
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected protocol: <empty> #300
Comments
If you dig deep enough in the engine and session objects, you can see the protocol version ist TLSv1.2 But the applicationProtocol property of ApplicationProtocolAccessor is null and never set. The only place I could find is the JdkBaseApplicationProtocolNegotiator where the applicationProtocol is set but this code is never called. |
I don't want to just dismiss this problem outright, but I would like to begin by noting that at least one APNs development server has been afflicted by evil spirits for some time now. To help isolate the problem, does this happen all the time? Can you give us the IP of the server that isn't working? And does this happen in production, too? |
Yes, it happens 'all the time'. Just one time there was a timeout.
I switched to apnsClient.connect(ApnsClient.PRODUCTION_APNS_HOST); and got the same logging:
I debugged the call chain a bit and found a place where protocols to check are: ["h2"] but somewhere along the way I could not find the part where the actual check against the supported protocols is performed. |
Understood. Thanks for the clarification! Will investigate shortly. |
I should have mentioned, that the application is a web archive in a Wildly application server. In order to get rid of as many as possible side effects as possible I recreated the necessary code for push in a plain Java application and it works. So I have to continue searching for the root problem, maybe the way the certificate is loaded. |
Hello Jon, please consider the issue as resolved. For those of you with a similar problem:
The 'solution' for the JBoss/Wildfly application server:
and expose the alpn classes to your application see also: https://docs.jboss.org/author/display/WFLY8/Class+Loading+in+WildFly |
Yow. Thanks, @ddrachau, for the detailed explanation! This will certainly be a big help to others. |
Hello, |
With the version this should not be needed. I have 0.9.3 and 2.0.0.Final of Having the following dependency on the WAR's pom, file is good enought:
|
…and, conveniently enough, Pushy now depends on
`netty-tcnative-boringssl-static` directly, so it reduces even further to
just:
<dependency>
<groupId>com.relayrides</groupId>
<artifactId>pushy</artifactId>
<version>0.9.3</version>
</dependency>
Cheers!
…-Jon
On Mon, Apr 10, 2017 at 11:07 AM, Matthias Wessendorf < ***@***.***> wrote:
With the version this should not be needed.
I have 0.9.3 and 2.0.0.Final of netty-tcnative-boringssl-static this
should not be needed.
Having the following dependency on the WAR's pom, file is good enought:
<dependency>
<groupId>com.relayrides</groupId>
<artifactId>pushy</artifactId>
<version>0.9.3</version>
</dependency>
<dependency>
<groupId>io.netty</groupId>
<artifactId>netty-tcnative-boringssl-static</artifactId>
<version>2.0.0.Final</version>
</dependency>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#300 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAB6eJjbkTCqaTtxmUq5gik96NGw74Fsks5rukXIgaJpZM4IkRT7>
.
|
Please, someone can clarify where the alpn-boot jar has to be put? Thanks |
Please see https://github.com/relayrides/pushy/wiki/Using-a-JDK-SSL-provider and https://groups.google.com/d/msg/pushy-apns/CWvgNPp9yqk/PR1sXViBDAAJ. In the future, please go directly to the mailing list for support; comments added to long-closed issues are likely to go unnoticed. |
I am not able to connect to Apple's development apn Using pushy-0.7.2 with Java 8 (various versions with the matching alpn-boot lib).
The ssl negotiation should have been successful but the protocol is empty
The text was updated successfully, but these errors were encountered: