[jira] [Commented] (TOMEE-1723) Hazelcast integration in TomEE

["Romain Manni-Bucau (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TOMEE-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175576#comment-15175576 ] 

Romain Manni-Bucau commented on TOMEE-1723:
-------------------------------------------

Hi Praveen,

to investigate we need a maven project on a public source repository (github/bitbucket/...) with tomee maven plugin setup and reproducing the issue (you can do a cluster using arquillian tomee remote using tomee itself and the test JVM).

Side note: used hazelcast 3.5 executor service with tomee 1.7.3 without issues so can also be a config/network issue.

> Hazelcast integration in TomEE
> ------------------------------
>
>                 Key: TOMEE-1723
>                 URL: https://issues.apache.org/jira/browse/TOMEE-1723
>             Project: TomEE
>          Issue Type: Bug
>          Components: TomEE Core Server
>    Affects Versions: 1.7.2
>         Environment: J2EE application deployed in TomEE, using Hazelcast distributed executor APIs
>            Reporter: Praveen 
>             Fix For: 1.7.3
>
>
> Tomee has Hazelcast jar in it's library. I am using TomEE1.7.2 which has  Hazelcast 3.5 version. The application is deployed in multiple tomee instances and Hazelcast cluster has formed successfully. However when i tried distributed executor to execute the task on other JVM, the task executed successfully on other JVM but the control is not coming back to the source JVM. Finally the Future task timeouts and returns null. Other Hazelcast features (distributed map, cluster formation etc.) are working fine except distributed executor. I have used same version of Hazelcast in pom.xml with scope provided. 
> Surprising behavior is - deleting the Hazelcast jar from Tomee library and including explicit dependency on Hazelcast jar of same version (3.5) in the application is working fine. Not able to comprehend this behavior.
> Using latest versions of Hazelcast (3.6.1) in TomEE also didn't solve the issue. 
> Looks like an integration issue of TomEE with Hazelcast.
>  Please investigate and let us know the solution and root cause.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)