Can someone shed some light on why my UAA local run got stuck at cargoRunLocal?
I don't think the service is up because I don't see anything listening to port 8080.

When I did a Ctrl-C, everything ended.

I am using Oracle Java 1.8

thanks,
alex

:cargoRunLocal
Press Ctrl-C to stop the container...

:cargoRunLocal took 254765ms

:run
:run took 0ms

BUILD SUCCESSFUL

Total time: 6 mins 27.502 secs
Task timings:
642ms :cloudfoundry-identity-common:compileJava
690ms :cloudfoundry-identity-common:processResources
1279ms :cloudfoundry-identity-common:jar
19984ms :cloudfoundry-identity-common:javadoc
946ms :cloudfoundry-identity-common:javadocJar
3346ms :cloudfoundry-identity-scim:compileJava
1213ms :cloudfoundry-identity-login:compileJava
4263ms :cloudfoundry-identity-scim:javadoc
4022ms :cloudfoundry-identity-login:javadoc
11868ms :cloudfoundry-identity-uaa:war
3286ms :cloudfoundry-identity-samples:cloudfoundry-identity-api:javadoc
7085ms :cloudfoundry-identity-samples:cloudfoundry-identity-api:war
1969ms :cloudfoundry-identity-samples:cloudfoundry-identity-app:javadoc
6920ms :cloudfoundry-identity-samples:cloudfoundry-identity-app:war
254765ms :cargoRunLocal

./gradlew run --info

The --info flag will print out the UAA and Tomcat logs to screen.

the server will then be accessible on http://localhost:8080/uaa

and yes, you will see gradle stuck on

Tomcat 7.x started on port [8080]
[ant:cargo] Press Ctrl-C to stop the container...
Press Ctrl-C to stop the container...

Building 97% > :cargoRunLocal

Until you hit Ctrl+C

Filip


On Fri, Aug 21, 2015 at 2:48 PM, Filip Hanik <fhanik(a)pivotal.io> wrote:

./gradlew run --info

The --info flag will print out the UAA and Tomcat logs to screen.

the server will then be accessible on http://localhost:8080/uaa



On Fri, Aug 21, 2015 at 2:43 PM, Alex Lam <alex.c.lam(a)intel.com> wrote:

Can someone shed some light on why my UAA local run got stuck at
cargoRunLocal?
I don't think the service is up because I don't see anything listening to
port 8080.

When I did a Ctrl-C, everything ended.

I am using Oracle Java 1.8

thanks,
alex

:cargoRunLocal
Press Ctrl-C to stop the container...

:cargoRunLocal took 254765ms

:run
:run took 0ms

BUILD SUCCESSFUL

Total time: 6 mins 27.502 secs
Task timings:
642ms :cloudfoundry-identity-common:compileJava
690ms :cloudfoundry-identity-common:processResources
1279ms :cloudfoundry-identity-common:jar
19984ms :cloudfoundry-identity-common:javadoc
946ms :cloudfoundry-identity-common:javadocJar
3346ms :cloudfoundry-identity-scim:compileJava
1213ms :cloudfoundry-identity-login:compileJava
4263ms :cloudfoundry-identity-scim:javadoc
4022ms :cloudfoundry-identity-login:javadoc
11868ms :cloudfoundry-identity-uaa:war
3286ms
:cloudfoundry-identity-samples:cloudfoundry-identity-api:javadoc
7085ms :cloudfoundry-identity-samples:cloudfoundry-identity-api:war
1969ms
:cloudfoundry-identity-samples:cloudfoundry-identity-app:javadoc
6920ms :cloudfoundry-identity-samples:cloudfoundry-identity-app:war
254765ms :cargoRunLocal

Hi Filip,

Yes, the "--info" help to know tomcat is up @ 8080.
However, it's still aint working properly..
I see this on my browser..

Uh oh.
Something went amiss.

© 2015 Pivotal Software, Inc. All Rights Reserved.

And these are the logs on the console.

[2015-08-21 14:01:10.154] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-5] .... DEBUG --- UaaRequestMatcher: [loginAuthenticateRequestMatcher] Checking match of request : '/uaa/login'; '/uaa/authenticate' with parameters={} and headers {Authorization=[bearer ], accept=[application/json]}
[2015-08-21 14:01:10.154] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-5] .... DEBUG --- UaaRequestMatcher: [loginAuthorizeRequestMatcher] Checking match of request : '/uaa/login'; '/uaa/oauth/authorize' with parameters={source=login} and headers {accept=[application/json]}
[2015-08-21 14:01:10.154] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-5] .... DEBUG --- UaaRequestMatcher: [loginTokenRequestMatcher] Checking match of request : '/uaa/login'; '/uaa/oauth/token' with parameters={source=login, grant_type=password, add_new=} and headers {Authorization=[bearer ], accept=[application/json]}
[2015-08-21 14:01:10.155] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-5] .... DEBUG --- UaaRequestMatcher: [loginAuthorizeRequestMatcherOld] Checking match of request : '/uaa/login'; '/uaa/oauth/authorize' with parameters={login={} and headers {accept=[application/json]}
[2015-08-21 14:01:10.155] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-5] .... DEBUG --- UaaRequestMatcher: [passcodeTokenMatcher] Checking match of request : '/uaa/login'; '/uaa/oauth/token' with parameters={grant_type=password, passcode=} and headers {accept=[application/json, application/x-www-form-urlencoded]}
[2015-08-21 14:01:10.155] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-5] .... DEBUG --- UaaRequestMatcher: [oauthAuthorizeRequestMatcher] Checking match of request : '/uaa/login'; '/uaa/oauth/authorize' with parameters={response_type=token, source=credentials} and headers {accept=[application/json, application/x-www-form-urlencoded]}
[2015-08-21 14:01:10.155] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-5] .... DEBUG --- UaaRequestMatcher: [oauthAuthorizeRequestMatcherOld] Checking match of request : '/uaa/login'; '/uaa/oauth/authorize' with parameters={response_type=token, credentials={} and headers {accept=[application/json, application/x-www-form-urlencoded]}
[2015-08-21 14:01:10.156] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-5] .... DEBUG --- UaaRequestMatcher: [autologinAuthorizeRequestMatcher] Checking match of request : '/uaa/login'; '/uaa/oauth/authorize' with parameters={response_type=code, code=} and headers {}
[2015-08-21 14:01:30.557] cloudfoundry-identity-uaa/uaa - ???? [ZoneAwareMetadataManager.Refresh[metadata]] .... DEBUG --- ZoneAwareMetadataManager: Running SAML IDP refresh[ZoneAwareMetadataManager.Refresh[metadata]-1297020509] - ignoreTimestamp=false

and http://localhost:8080/uaa
returned the same


Uh oh.
Something went amiss.

© 2015 Pivotal Software, Inc. All Rights Reserved.

hi Alex, can you confirm that.

java -version
javac -version

both return Java 8

"Uh oh, something went amiss" means that Tomcat is indeed up, but the app
is not working.

So try

./gradlew clean assemble run --info


Filip

Hi Filip,

$ java -version
java version "1.8.0_60"
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)

$ javac -version
javac 1.8.0_60


And one thing, I want to add... the sad_cloud.png logo in the "Uh oh, something went amiss" page did not come out either. Perhaps the path to certain resources are broken?

And here are latest output from a "clean assemble run --info"

Press Ctrl-C to stop the container...
[2015-08-21 14:37:14.647] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-2] .... DEBUG --- UaaRequestMatcher: [loginAuthenticateRequestMatcher] Checking match of request : '/uaa/'; '/uaa/authenticate' with parameters={} and headers {Authorization=[bearer ], accept=[application/json]}
[2015-08-21 14:37:14.655] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-2] .... DEBUG --- UaaRequestMatcher: [loginAuthorizeRequestMatcher] Checking match of request : '/uaa/'; '/uaa/oauth/authorize' with parameters={source=login} and headers {accept=[application/json]}
[2015-08-21 14:37:14.656] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-2] .... DEBUG --- UaaRequestMatcher: [loginTokenRequestMatcher] Checking match of request : '/uaa/'; '/uaa/oauth/token' with parameters={source=login, grant_type=password, add_new=} and headers {Authorization=[bearer ], accept=[application/json]}
[2015-08-21 14:37:14.656] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-2] .... DEBUG --- UaaRequestMatcher: [loginAuthorizeRequestMatcherOld] Checking match of request : '/uaa/'; '/uaa/oauth/authorize' with parameters={login={} and headers {accept=[application/json]}
[2015-08-21 14:37:14.656] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-2] .... DEBUG --- UaaRequestMatcher: [passcodeTokenMatcher] Checking match of request : '/uaa/'; '/uaa/oauth/token' with parameters={grant_type=password, passcode=} and headers {accept=[application/json, application/x-www-form-urlencoded]}
[2015-08-21 14:37:14.657] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-2] .... DEBUG --- UaaRequestMatcher: [oauthAuthorizeRequestMatcher] Checking match of request : '/uaa/'; '/uaa/oauth/authorize' with parameters={response_type=token, source=credentials} and headers {accept=[application/json, application/x-www-form-urlencoded]}
[2015-08-21 14:37:14.657] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-2] .... DEBUG --- UaaRequestMatcher: [oauthAuthorizeRequestMatcherOld] Checking match of request : '/uaa/'; '/uaa/oauth/authorize' with parameters={response_type=token, credentials={} and headers {accept=[application/json, application/x-www-form-urlencoded]}
[2015-08-21 14:37:14.657] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-2] .... DEBUG --- UaaRequestMatcher: [autologinAuthorizeRequestMatcher] Checking match of request : '/uaa/'; '/uaa/oauth/authorize' with parameters={response_type=code, code=} and headers {}
[2015-08-21 14:37:14.818] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-2] .... INFO --- TemplateEngine: [THYMELEAF] INITIALIZING TEMPLATE ENGINE
[2015-08-21 14:37:14.927] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-2] .... INFO --- AbstractTemplateResolver: [THYMELEAF] INITIALIZING TEMPLATE RESOLVER: org.thymeleaf.templateresolver.TemplateResolver
[2015-08-21 14:37:14.927] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-2] .... INFO --- AbstractTemplateResolver: [THYMELEAF] TEMPLATE RESOLVER INITIALIZED OK
[2015-08-21 14:37:14.927] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-2] .... INFO --- AbstractMessageResolver: [THYMELEAF] INITIALIZING MESSAGE RESOLVER: org.thymeleaf.spring4.messageresolver.SpringMessageResolver
[2015-08-21 14:37:14.928] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-2] .... INFO --- AbstractMessageResolver: [THYMELEAF] MESSAGE RESOLVER INITIALIZED OK
[2015-08-21 14:37:14.932] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-2] .... INFO --- CONFIG: [THYMELEAF] TEMPLATE ENGINE CONFIGURATION:
[THYMELEAF] * Cache Factory implementation: org.thymeleaf.cache.StandardCacheManager
[THYMELEAF] * Template modes:
[THYMELEAF] * VALIDXML
[THYMELEAF] * HTML5
[THYMELEAF] * XML
[THYMELEAF] * LEGACYHTML5
[THYMELEAF] * VALIDXHTML
[THYMELEAF] * XHTML
[THYMELEAF] * Template resolvers (in order):
[THYMELEAF] * org.thymeleaf.templateresolver.TemplateResolver
[THYMELEAF] * Message resolvers (in order):
[THYMELEAF] * org.thymeleaf.spring4.messageresolver.SpringMessageResolver
[THYMELEAF] * Dialect [1 of 3]: org.thymeleaf.spring4.dialect.SpringStandardDialect
[THYMELEAF] * Prefix: "th"
[THYMELEAF] * Dialect [2 of 3]: nz.net.ultraq.thymeleaf.LayoutDialect
[THYMELEAF] * Prefix: "layout"
[THYMELEAF] * Dialect [3 of 3]: org.thymeleaf.extras.springsecurity3.dialect.SpringSecurityDialect
[THYMELEAF] * Prefix: "sec"
[THYMELEAF] TEMPLATE ENGINE CONFIGURED OK
[2015-08-21 14:37:14.932] cloudfoundry-identity-uaa - ???? [http-bio-8080-exec-2] .... INFO --- TemplateEngine: [THYMELEAF] TEMPLATE ENGINE INITIALIZED
[2015-08-21 14:37:19.620] cloudfoundry-identity-uaa/uaa - ???? [ZoneAwareMetadataManager.Refresh[metadata]] .... DEBUG --- ZoneAwareMetadataManager: Running SAML IDP refresh[ZoneAwareMetadataManager.Refresh[metadata]-107518315] - ignoreTimestamp=false

thanks,
alex

Hi Filip,

It works now.
Does Tomcat only listen to "localhost"?
Can I not point a browser from another machine to Tomcat?

thanks,
alex

ok, so UAA is pretty picky about the "host names" that come in.

by default only

localhost and *.localhost where * is a zone name are allowed.
There is a property that configures that called

zones:
internal:
hostnames:
- 127.0.0.1
- some.other.hostname

in uaa.yml

Filip