Using maven-xap plugin to deploy the pu on docker

I am unable to deploy the pu to docker instance - I followed the following example -

https://github.com/Gigaspaces/fraud-d...

The command is able to find LUS and connect to it but then says could not find an GSM within a group. I see the GSM process is started and exposed from the container to the host.

Same behavior with xap and xap-enterprise image for docker.

λ mvn xap:deploy -Dgroups=xap-14.5.0 -Dlocators=localhost:4174 [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] frauddetection
[pom] [INFO] common
[jar] [INFO] user
[jar] [INFO] feeder
[jar] [INFO] vendor
[jar] [INFO] [INFO] -------< com.gigaspaces.blueprint.frauddetection:frauddetection

------- [INFO] Building frauddetection 1.0-SNAPSHOT
[1/5] [INFO] --------------------------------[ pom ]--------------------------------- [INFO] [INFO] --- xap-maven-plugin:14.2.0:deploy (default-cli) @ frauddetection --- [INFO] Deploying processing unit: frauddetection-user [INFO] Arguments list: [-groups, xap-14.5.0, -locators, localhost:4174, -timeout, 10000, user/target/frauddetection-user.jar] 2019-08-20 11:18:14,527 CONFIG [com.gigaspaces.logger] - Log file: .m2\repository\org\gigaspaces\logs\2019-08-20~11.18-gigaspaces-service-10.0.75.1-14156.log

Aug 20, 2019 11:18:14 AM org.openspaces.pu.container.servicegrid.deploy.Deploy info INFO: Deploying [frauddetection-user.jar] with name [frauddetection-user] under groups [xap-14.5.0] and locators [jini://localhost:4174/] Aug 20, 2019 11:18:14 AM org.openspaces.pu.container.servicegrid.deploy.Deploy info INFO: Searching for GSM in groups [xap-14.5.0] and locators [[jini://localhost:4174/]] Aug 20, 2019 11:18:16 AM net.jini.discovery.LookupLocatorDiscovery$LocatorReg tryGetProxy INFO: Connected to LUS using locator localhost:4174 [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary for frauddetection 1.0-SNAPSHOT: [INFO] [INFO] frauddetection ..................................... FAILURE [ 13.787 s] [INFO] common ............................................. SKIPPED [INFO] user ............................................... SKIPPED [INFO] feeder ............................................. SKIPPED [INFO] vendor ............................................. SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 14.583 s [INFO] Finished at: 2019-08-20T11:18:26-07:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:xap-maven-plugin:14.2.0:deploy (default-cli) on project frauddetection: Failed to find GSM with groups [xap-14.5.0] and timeout [10000] -> [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/di...

asked 2019-08-20 13:43:04 -0600

vinny
1 ●4 ●5 ●5

edit retag flag offensive close merge delete

add a comment

0

No progress still - The pu is not getting fully deployed as a GSC could not be started.

6:00:24,052 GSM INFO [com.gigaspaces.grid.gsm] - Deploying data-feeder {type=stateless, instances=1} [manager][1/172] 2019-09-03 06:00:24,095 GSM WARNING [com.gigaspaces.grid.gsm] - A GSC could not be obtained to provision [data-feeder [1]], count [0] [manager][1/172] 2019-09-03 06:00:24,098 GSM INFO [net.jini.discovery.LookupLocatorDiscovery] - Connected to LUS using locator localhost:4174 [manager][1/172] 2019-09-03 06:00:24,100 GSM WARNING [com.gigaspaces.grid.gsm] - ServiceBeanInstantiatorListener notification; Caused by: java.rmi.ConnectException: Connect Failed to [NIO://127.0.1.1:46621/pid[22576]/1218729939416018_1_6672016023861786237_details[class org.openspaces.pu.container.servicegrid.deploy.Deploy$DeployListener]]; nested exception is: [manager][1/172] java.io.IOException: java.util.concurrent.ExecutionException: java.net.ConnectException: Connection refused [manager][1/172] 2019-09-03 06:00:24,101 GSM WARNING [com.gigaspaces.grid.gsm] - Pending allocation request for [data-feeder [1]] until an available GSC is obtained, and all dependencies are met.

answered 2019-09-03 01:12:29 -0600

vinny
1 ●4 ●5 ●5

edit flag offensive delete link

add a comment

0

Seems like an issue with Windows docker - It worked well with Docker on Linux.

I do not see a running GSC though and the pu is deployed as broken.

answered 2019-08-22 01:25:19 -0600

vinny
1 ●4 ●5 ●5

edit flag offensive delete link

add a comment

0

Looks like the LUS is returning the LMRI url for the GSM which is internal docker ip and its not accessible from outside. How can we have the xap-maven plugin treat the url as localhost ?? - Might need a code change in the maven plugin.

Aug 21, 2019 1:40:13 PM org.openspaces.pu.container.servicegrid.deploy.Deploy info INFO: Deploying [frauddetection-user.jar] with name [frauddetection-user] under groups [xap-14.5.0] and locators [jini://localhost:4174/] Aug 21, 2019 1:40:13 PM org.openspaces.pu.container.servicegrid.deploy.Deploy info INFO: Searching for GSM in groups [xap-14.5.0] and locators [[jini://localhost:4174/]] Aug 21, 2019 1:40:15 PM net.jini.discovery.LookupLocatorDiscovery$LocatorReg tryGetProxy INFO: Connected to LUS using locator localhost:4174 Aug 21, 2019 1:40:37 PM net.jini.discovery.LookupLocatorDiscovery$InternalDiscoverylListener discovered WARNING: Exception in InternalDiscoveryListener.discovered() going to discard the discoveryEvent: net.jini.discovery.DiscoveryEvent[source=net.jini.discovery.LookupLocatorDiscovery@70108c41] java.rmi.ConnectException: Connect Failed to [NIO://172.17.0.3:8200/pid[3036]/15822764219032_2_4682337568227496397_details[class com.gigaspaces.grid.lookup.ServiceGridRegistrar]]; nested exception is: java.io.IOException: java.util.concurrent.ExecutionException: java.net.ConnectException: Connection timed out: no further information

answered 2019-08-21 16:17:52 -0600