Skip to content
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

Android lambda exceptions for client #246

Closed
hakangs opened this issue Feb 25, 2017 · 2 comments
Closed

Android lambda exceptions for client #246

hakangs opened this issue Feb 25, 2017 · 2 comments

Comments

@hakangs
Copy link

hakangs commented Feb 25, 2017

Expected behavior

I have an android app, in which I have added Pulsar Client with gradle. It compiles fine with these additional settings in build.gradle file:

jackOptions {
    enabled true
}

compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
}

Actual behavior

But when I run the app, I get the following exceptions and it fails:

Error:ChannelManager.java:363-364: Lambda coming from jar file need their interfaces on the classpath to be compiled, unknown interfaces are io.netty.util.concurrent.GenericFutureListener
Error:NettyReactiveStreamsBody.java:113-114: Lambda coming from jar file need their interfaces on the classpath to be compiled, unknown interfaces are java.lang.Runnable
Error:AsyncHttpClientConfigHelper.java:65-66: Lambda coming from jar file need their interfaces on the classpath to be compiled, unknown interfaces are java.util.function.Function
Error:AsyncHttpClientConfigDefaults.java:86-87: Lambda coming from jar file need their interfaces on the classpath to be compiled, unknown interfaces are java.util.function.IntFunction

How can we reproduce the issue

Can it be because Android does not accept lambdas by default ? How can I achieve Pulsar Client to run in Android ?

Is there a 1.7 version compiled version of client jars ?

System configuration

Pulsar version: 1.16

@agarman
Copy link

agarman commented Feb 26, 2017

Have you considered using the WebSocket client?

It'll be simpler than getting a bunch of Java 8 libraries to work (stably) in Dalvik.

sijie pushed a commit to sijie/pulsar that referenced this issue Mar 4, 2018
* removing snapshotting

* cleaning up
@sijie
Copy link
Member

sijie commented Aug 22, 2018

the minimal requirement for java is java8. and there is a websocket proxy, so you can use websocket api.

@sijie sijie closed this as completed Aug 22, 2018
hangc0276 pushed a commit to hangc0276/pulsar that referenced this issue May 26, 2021
Fixes apache#312

These tests were ignored temporarily just because they rely on the outdated methods that convert between MessageId and Kafka offset. So this PR fixes these tests and deletes these outdated methods.

The exception is testBrokerRespectsPartitionsOrderAndSizeLimits, it's a broken test that is easily affected by some params. apache#287 and apache#246 are tracking the test.
nicoloboschi pushed a commit to nicoloboschi/pulsar that referenced this issue May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants