geziefer / java-azure Goto Github PK

After managing to do the Iaas example, I tried Paas, but it didn't show the web page or react to the web service. I removed the resource group and started all over, but same result.
I connected the logs and saw this:
2019-09-13 12:41:57,581 INFO [org.jboss.as.server] (ServerService Thread Pool -- 45) WFLYSRV0010: Deployed "ROOT.war" (runtime-name : "ROOT.war")
2019-09-13 12:41:57,585 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status reportWFLYCTL0184: New missing/unsatisfied dependencies:service jboss.naming.context.java.jdbc.JavaEECafeDB (missing) dependents: [service jboss.persistenceunit."ROOT.war#coffees".FIRST_PHASE, service jboss.persistenceunit."ROOT.war#coffees"]WFLYCTL0448: 26 additional services are down due to their dependencies being missing or failed
2019-09-13 12:41:57,672 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
2019-09-13 12:41:57,676 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
2019-09-13 12:41:57,677 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
2019-09-13 12:41:57,679 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final) started (with errors) in 9707ms - Started 484 of 687 services (30 services failed or missing dependencies, 341

After the great talk on JakartaOne, I tried to do the iaas demo myself and stumpled upon 2 things which might be missing in the tutorial description:

• Postgres service was set to allwo ssl access only (which could be disabled for the demo)
• Postgres service was not accessable by ip of WildFly (which could be allowed for the demo)