[jboss-jira] [JBoss JIRA] (WFLY-9788) EJB over HTTP fails with Arrays in Request

[jaikiran pai (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-9788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532788#comment-13532788 ] 

jaikiran pai commented on WFLY-9788:
------------------------------------

I have pushed a branch to my personal repo which contains a test case to try and reproduce this. You can checkout the repo here https://github.com/jaikiran/wildfly/tree/wfly-9788 and follows these steps to build and test it.

// after the repo is cloned locally
git checkout wfly-9788
mvn clean install -DskipTests=true
cd testsuite/integration/basic
mvn clean test -Dtest=HttpRemoteEJBJndiBasedInvocationTestCase

There are 2 test methods you can focus on (one stateless bean, one stateful bean) in {{org.jboss.as.test.integration.ejb.remote.jndi.HttpRemoteEJBJndiBasedInvocationTestCase}} - {{testRemoteSFSBInvocation}} and {{testRemoteSLSBInvocation}}. Please try and get these failing by changing them in whichever way you think reproduces this issue. 

Note that the branch that I have pointed you to use the 1.0.10-Final-SNAPSHOT of the EJB HTTP client library[1]. Please first build the PR that I have open to make sure this snapshot on your local system has those fixes, when you try and reproduce it.

[1] https://github.com/jaikiran/wildfly/commit/6361c8872c2ac17b717f64252fc45e4fe5de8b15

> EJB over HTTP fails with Arrays in Request
> ------------------------------------------
>
>                 Key: WFLY-9788
>                 URL: https://issues.jboss.org/browse/WFLY-9788
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 11.0.0.Final
>            Reporter: Heiko Lettmann
>         Attachments: Test.zip
>
>
> I stumbled over the issue WFLY-9573. Then I updated to wildfly-http-client-1.0.9.Final which made a few invocations work. There I discovered another issue. I attached a modified Quickstart version to demonstrate it!
> Exception is on the client side:
> Exception in thread "main" javax.ejb.EJBException: java.io.IOException: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String
> 	at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:128)
> 	at org.wildfly.httpclient.ejb.HttpInvocationHandler.lambda$handleInternal$0(HttpInvocationHandler.java:130)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 	at java.lang.Thread.run(Thread.java:748)
> Caused by: java.io.IOException: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String
> 	at org.wildfly.httpclient.ejb.HttpInvocationHandler$1.getRequestContent(HttpInvocationHandler.java:204)
> 	at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:126)
> 	... 4 more
> Caused by: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String
> 	at org.wildfly.httpclient.ejb.HttpInvocationHandler$1.getRequestContent(HttpInvocationHandler.java:178)
> 	... 5 more



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)