[jboss-jira] [JBoss JIRA] (WFLY-10137) EJB lookup over HTTP fails if object is used in the signiture

Parul Sharma (Jira) issues at jboss.org
Tue Mar 24 07:14:42 EDT 2020 

    [ https://issues.redhat.com/browse/WFLY-10137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007187#comment-14007187 ] 

Parul Sharma commented on WFLY-10137:
-------------------------------------

[~crazycradd] Can you quickly see below issues: is this issues were you facing? otherwise we need to look into that forum.
Adding 204 and 340 via the remote stateless calculator deployed on the server
Exception in thread "main" javax.ejb.EJBException: javax.naming.AuthenticationException: WFHTTP000013: Authentication failed (full response ClientResponse{responseHeaders={www-authenticate=[Digest realm="ApplicationRealm", nonce="AAAAAgAANmMw7plvVHUZLnwvMwkp9bw9JstLLmulwvu6Bm+r0XWoiyiTsYI=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth], content-length=[77], content-type=[text/html], date=[Tue, 24 Mar 2020 11:07:46 GMT]}, responseCode=401, status='', protocol=HTTP/2.0})
	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:221)
	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:125)
	at com.sun.proxy.$Proxy2.add(Unknown Source)
	at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.invokeStatelessBean(RemoteEJBClient.java:59)
	at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:40)
Caused by: javax.naming.AuthenticationException: WFHTTP000013: Authentication failed (full response ClientResponse{responseHeaders={www-authenticate=[Digest realm="ApplicationRealm", nonce="AAAAAgAANmMw7plvVHUZLnwvMwkp9bw9JstLLmulwvu6Bm+r0XWoiyiTsYI=", opaque="00000000000000000000000000000000", algorithm=MD5, qop=auth], content-length=[77], content-type=[text/html], date=[Tue, 24 Mar 2020 11:07:46 GMT]}, responseCode=401, status='', protocol=HTTP/2.0})
	at org.wildfly.httpclient.common.HttpTargetContext$1$1.lambda$completed$4(HttpTargetContext.java:232)
	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
	at java.lang.Thread.run(Thread.java:748)
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
    at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404)
    at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:804)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:751)
    at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:313)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.256 s
[INFO] Finished at: 2020-03-24T16:37:47+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:exec (default-cli) on project ejb-remote-client: Command execution failed.: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException


> EJB lookup over HTTP fails if object is used in the signiture
> -------------------------------------------------------------
>
>                 Key: WFLY-10137
>                 URL: https://issues.redhat.com/browse/WFLY-10137
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB, Remoting
>    Affects Versions: 11.0.0.Final
>            Reporter: peter craddock
>            Assignee: Parul Sharma
>            Priority: Major
>
> I have a swing client that makes calls to the EJB tier via RMI the majority of the calls work fine using the workaround from WFLY-9636. 
> The following calls was failing when connected over HTTP but was fine when using the original TCP connection
> public EntityList getAllWorkingSetsForCube( ModelRef modelRef, FinanceCubeRef financeCubeRef, int userId, Integer[] allowedStates )
> I worked round this and found that creating a method without the Integer[] as part of the signature works.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)

More information about the jboss-jira mailing list