Using operations to create an org or spaces results in blocking error

[scottfrederick]

Attempting to create an organization or space using the operations API results in an error.

Either of these calls:

operations.organizations()
    .create(CreateOrganizationRequest.builder()
        .organizationName(orgName)
        .build())

operations.spaces()
    .create(CreateSpaceRequest.builder()
        .name(spaceName)
        .build());

Results in an exception with this at the top of the stack trace:

java.lang.IllegalStateException: block()/blockFirst()/blockLast() are blocking, which is not supported in thread reactor-http-nio-5
	at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:111) ~[reactor-core-3.2.0.RELEASE.jar:3.2.0.RELEASE]
	at reactor.core.publisher.Mono.block(Mono.java:1498) ~[reactor-core-3.2.0.RELEASE.jar:3.2.0.RELEASE]
	at org.cloudfoundry.reactor.uaa.UaaSigningKeyResolver.refreshKeys(UaaSigningKeyResolver.java:107) ~[cloudfoundry-client-reactor-3.13.0.RELEASE.jar:na]
	at org.cloudfoundry.reactor.uaa.UaaSigningKeyResolver.getKey(UaaSigningKeyResolver.java:89) ~[cloudfoundry-client-reactor-3.13.0.RELEASE.jar:na]
	at org.cloudfoundry.reactor.uaa.UaaSigningKeyResolver.resolveSigningKey(UaaSigningKeyResolver.java:59) ~[cloudfoundry-client-reactor-3.13.0.RELEASE.jar:na]
	at io.jsonwebtoken.impl.DefaultJwtParser.parse(DefaultJwtParser.java:316) ~[jjwt-0.9.1.jar:0.9.1]
	at io.jsonwebtoken.impl.DefaultJwtParser.parse(DefaultJwtParser.java:481) ~[jjwt-0.9.1.jar:0.9.1]
	at io.jsonwebtoken.impl.DefaultJwtParser.parseClaimsJws(DefaultJwtParser.java:541) ~[jjwt-0.9.1.jar:0.9.1]
	at org.cloudfoundry.reactor.uaa.UsernameProvider.getUsername(UsernameProvider.java:71) ~[cloudfoundry-client-reactor-3.13.0.RELEASE.jar:na]

A trivial app that shows this issue is here: https://github.com/scottfrederick/cf-java-client-block-error

[twoseat]

Thanks for this @scottfrederick - @ojhughes will be happy to see a reproducing app that I can't wriggle out of!

[twoseat]

@scottfrederick I've pushed a fix for this (but forgot the # that would tell it to auto-close!) We're having some CI issues at the moment so there may be a delay for a snapshot, but this will be in the next release.