Hi,

I am able to create events using curl. It seems like a dependency issue to
me between io.netty and com.ning.httpckirnt but I don't know how to find
the compatible versions for them to avoid this error. Any pointers?

Thanks,
Anshu

On 26-Jul-2017 8:50 PM, "Vaghawan Ojha" <vaghawan...@gmail.com> wrote:

> Hi,
>
> Are you able to import the events using curl?
>
> I think you could probably see this line "lang.NoSuchMethodError:
> org.jboss.netty.handler.codec.http.HttpRequest.setHeader(Lja
> va/lang/String;Ljava/lang/Object;)V "
>
> I've not worked with java app, but have worked with python sdk. Probably
> something wrong with your request if you're able to import the events using
> curl.
>
> Thanks
>
> On Thu, Jul 27, 2017 at 3:18 AM, Anshu Rajendra <anshurajen...@gmail.com>
> wrote:
>
>> Hi,
>>
>> When I try to create a event in my java app using io.prediction client, I
>> get this error :
>>
>> ```org.jboss.netty.handler.codec.http.HttpRequest.setHeader(
>> Ljava/lang/String;Ljava/lang/Object;)V"java.lang.NoSuchMethodError:
>> org.jboss.netty.handler.codec.http.HttpRequest.setHeader(Lja
>> va/lang/String;Ljava/lang/Object;)V at com.ning.http.client.providers
>> .netty.NettyAsyncHttpProvider.construct(NettyAsyncHttpProvider.java:704)
>> at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.
>> buildRequest(NettyAsyncHttpProvider.java:655) at
>> com.ning.http.client.providers.netty.NettyConnectListener$Builder.build(NettyConnectListener.java:145)
>> at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.
>> doConnect(NettyAsyncHttpProvider.java:1069) at
>> com.ning.http.client.providers.netty.NettyAsyncHttpProvider.
>> execute(NettyAsyncHttpProvider.java:938) at
>> com.ning.http.client.AsyncHttpClient.executeRequest(AsyncHttpClient.java:499)
>> at io.prediction.EventClient.createEventAsFuture(EventClient.java:116)
>> at io.prediction.EventClient.createEvent(EventClient.java:131) ```
>>
>> It seems to be a library issue but I cannot figure out. Can someone help
>> me debug this error?
>>
>> Thanks,
>> Anshu
>
>
>

Reply via email to