Bug 1146766

Summary: [GSS] (6.3.x) @UseAsyncMethod doesn't seem to work on JBoss
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Tadayoshi Sato <tasato>
Component: Web ServicesAssignee: Alessio Soldano <asoldano>
Status: CLOSED NOTABUG QA Contact: Rostislav Svoboda <rsvoboda>
Severity: high Docs Contact: Russell Dickenson <rdickens>
Priority: high    
Version: 6.3.0CC: asoldano, myarboro, rdickens, rsvoboda
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1146764 Environment:
Last Closed: 2014-09-29 01:18:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1146764    
Bug Blocks:    
Description Flags
reproducer none

Description Tadayoshi Sato 2014-09-26 03:13:16 UTC
Created attachment 941359 [details]

+++ This bug was initially created as a clone of Bug #1146764 +++

Description of problem:
Platform BZ for https://issues.jboss.org/browse/JBWS-3833

I developed the following WS endpoint that uses @UseAsyncMethod:

public class GreetingServiceImpl implements GreetingService {
    public String hello(String name) { ... }

    public Future<HelloResponse> helloAsync(final String name, final AsyncHandler<HelloResponse> asyncHandler) { ... }

My expectation with @UseAsyncMethod is that whenever the hello() operation is invoked helloAsync() is eventually executed on JBoss (WildFly 8 or EAP 6). However, it really is not.

I tested the same endpoint by launching it using Endpoint.publish(...) as well and it works as expected, so I don't think it's an issue with CXF itself but with JBoss WS integration.

Attached please see the complete reproducer project async.zip for detail.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Deploy the reproducer (async.zip).
2. Invoke the 'hello' operation from SoapUI or any other WS client.
3. Check the server log.

Actual results:
You'll see the following message in the server log:
INFO  [com.redhat.samples.ws.GreetingServiceImpl] (default task-13) Hello, SoapUI! (SYNC)

Expected results:
The following message should be seen in the server log instead:
INFO  [com.redhat.samples.ws.GreetingServiceImpl] (default task-13) Hello, SoapUI! (ASYNC)

Comment 1 JBoss JIRA Server 2014-09-26 12:55:10 UTC
Alessio Soldano <asoldano> updated the status of jira JBWS-3833 to Resolved

Comment 2 Tadayoshi Sato 2014-09-29 01:18:36 UTC
Closed the ticket as it's not a bug.

Comment 4 JBoss JIRA Server 2015-04-25 20:27:51 UTC
Alessio Soldano <asoldano> updated the status of jira JBWS-3833 to Closed