[keycloak-user] java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9990

Bruno Oliveira bruno at abstractj.org
Wed Apr 19 14:39:11 EDT 2017 

On Tue, Apr 18, 2017 at 8:32 PM Tanudjaja, Francisco <
francisco.tanudjaja at bina.roche.com> wrote:

> Thanks for the reply.
>
>
> I didn't exactly catch what you mean ... both the auth-server and
> vanilla-client are running wildfly ?
>

What I meant was, if you're running your server in different port. You must
specify it during deployment. For example:

If my app was deployed on WildFly, using the the port offset 1910.
Certainly the correct url to WF admin console is: http://127.0.0.1:11900 and
of course, you must specify it to Maven plugin:

mvn install -DskipTests wildfly:deploy -Dwildfly.port=10090


> I've restarted my auth-server using the command =>
>
> ./standalone.sh -Djboss.socket.binding.port-offset=1910
>
All the examples point to the Keycloak server on port 8180 like specified
at the README(
https://github.com/keycloak/keycloak-quickstarts/blob/master/README.md)
file. So if you're going to change it, make sure to change to the proper
port.

>
> Then I checked that I was able to login to the admin console on =>
>
> http://localhost:9990/auth
>


> Like I mentioned, all the examples, assume port 8180.


>
> Ran my vanilla client using the command =>
>
> mvn install -DskipTests wildfly:deploy
>
>
> Now I got a different error message =>
>
> [ERROR] }': java.net.ConnectException: JBAS012174: Could not connect to
> http-remoting://127.0.0.1:9990. The connection failed: For now upgrade
> responses must have a content length of zero.
>

I could not reproduce the steps to your issue. maybe try to start the
server with $WILDFLY_HOME/bin/standalone.sh -b 0.0.0.0

>
>
> Also, checking out keycloak repo and running mvn install helped to some
> extent, but still running 'mvn install wildfly:deploy' has issues
>
>
> 1. keycloak-test-helpers dependency on the parent pom.xml may not have
> been defined correctly.
>

It was fixed here:
https://github.com/keycloak/keycloak-quickstarts/commit/692bfd38049fbab70bd4c73d7bfb07dbe4520d78

I got this compilation error
>
> [ERROR] COMPILATION ERROR :
>
> [INFO] -------------------------------------------------------------
>
> [ERROR]
> /Users/tanudjaf/git/keycloak-quickstarts/app-profile-jee-vanilla/src/test/java/org/keycloak/quickstart/ArquillianProfileJeeVanillaTest.java:[41,25]
> package org.keycloak.test does not exist
>
> [ERROR]
> /Users/tanudjaf/git/keycloak-quickstarts/app-profile-jee-vanilla/src/test/java/org/keycloak/quickstart/ArquillianProfileJeeVanillaTest.java:[42,34]
> package org.keycloak.test.builders does not exist
>
> [ERROR]
> /Users/tanudjaf/git/keycloak-quickstarts/app-profile-jee-vanilla/src/test/java/org/keycloak/quickstart/ArquillianProfileJeeVanillaTest.java:[51,32]
> package org.keycloak.test does not exist
>
>
> Seems to at least compile if I add the dependency manually on the child
> pom.xml
>
> +       <dependency>
>
> +               <groupId>org.keycloak</groupId>
>
> +               <artifactId>keycloak-test-helper</artifactId>
>
> +               <version>${version.keycloak}</version>
>
> +               <scope>test</scope>
>
> +       </dependency>
>
>
> 2. Still after it compiles there's a runtime exception thrown
>

The runtime exception will happen if you don't copy the artifact, like I
mentioned, keycloak-test-helper was not released yet. You have to use the
artifact generated by -Pdistribution located at
keycloak-repo/distribution/server-dist/target/keycloak-3.1.0.CR1-SNAPSHOT.tar.gz

Yep, it sucks and will be fixed on the next release.


> -------------------------------------------------------
>
>  T E S T S
>
> -------------------------------------------------------
>
> Running org.keycloak.quickstart.ArquillianProfileJeeVanillaTest
>
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.179 sec
> <<< FAILURE!
>
> org.keycloak.quickstart.ArquillianProfileJeeVanillaTest  Time elapsed:
> 1.177 sec  <<< ERROR!
>
> java.lang.RuntimeException: Could not create new instance of class
> org.jboss.arquillian.test.impl.EventTestRunnerAdaptor
>
> at
> org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:166)
>
> at
> org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:103)
>
> at
> org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder.build(TestRunnerAdaptorBuilder.java:52)
>
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:114)
>
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
>
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
>
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:497)
>
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
>
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
>
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
>
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
>
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
>
> Caused by: java.lang.reflect.InvocationTargetException
>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
>
> at
> org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:162)
>
> ... 15 more
>
>
> On Tue, Apr 18, 2017 at 1:25 PM, Bruno Oliveira <bruno at abstractj.org>
> wrote:
>
>> If you're starting WildFly on port 8180. I believe that you should
>> specify -Dwildfly.port=10090 for deployment.
>>
>> The quickstarts depend on keycloak-tests-helper, which wasn't released
>> yet. That's the reason why it points to the same release specified on
>> Keycloak master branch. Here's what you can do to workaround this while we
>> fix:
>>
>> - git clone https://github.com/keycloak/keycloak.git && cd keycloak &&
>> mvn clean install -Pdistribution -DskipTests=true
>>
>> I hope it helps.
>>
>>
>> On Tue, Apr 18, 2017 at 2:52 PM Tanudjaja, Francisco <
>> francisco.tanudjaja at bina.roche.com> wrote:
>>
>>> Hi,
>>>
>>> I've followed the instructions on
>>> https://keycloak.gitbooks.io/documentation/content/
>>> authorization_services/topics/getting-started/hello-world/deploy.html
>>>
>>> I have the following keycloak.json in the 'config' directory of
>>> ~/path/to/keycloak-quickstarts/app-profile-jee-vanilla
>>>
>>> """
>>> {
>>>   "realm": "Foo",
>>>   "auth-server-url": "http://localhost:8180/auth",
>>>   "ssl-required": "external",
>>>   "resource": "fclient",
>>>   "credentials": {
>>>     "secret": "0749b4fc-db40-410a-ac2c-8837ce206c5d"
>>>   },
>>>   "policy-enforcer": {}
>>> }
>>> """
>>>
>>> Got the following error and wasn't able to find any references to port
>>> 9990
>>> in the configuration.
>>>
>>> [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-
>>> maven-plugin:1.0.1.Final:deploy (default-cli) on project
>>> keycloak-app-profile-jee-vanilla: Could not execute goal deploy on
>>>
>>> /Users/tanudjaf/git/keycloak-quickstarts/app-profile-jee-vanilla/target/vanilla.war.
>>> Reason: I/O Error could not execute operation '{
>>> [ERROR] "operation" => "read-attribute",
>>> [ERROR] "address" => [],
>>> [ERROR] "name" => "launch-type"
>>> [ERROR] }': java.net.ConnectException: JBAS012144: Could not connect to
>>> http-remoting://127.0.0.1:9990. The connection timed out
>>> [ERROR] -> [Help 1]
>>>
>>> Please advise.
>>>
>>>
>>> -----------------------------------------------------
>>> Additional note:
>>>
>>> I jumped a few hoops while navigating the documentation. Its possible the
>>> issue is caused by my changes I've made. For reference, I've listed them
>>> below
>>>
>>> ## wrong link on github in https://keycloak.gitbooks.io/
>>> documentation/content/authorization_services/topics/
>>> getting-started/hello-world/deploy.html
>>>
>>> ** easy fix, looks like the folder was renamed
>>> - $ cd keycloak-quickstarts/app-authz-jee-vanilla
>>> + $ cd keycloak-quickstarts/app-profile-jee-vanilla
>>>
>>>
>>> ## wrong version on pom
>>> There is no '3.1.0.CR1-SNAPSHOT' published in maven repo
>>> See
>>> -> https://github.com/keycloak/keycloak/blob/3.0.x/boms/adapter/pom.xml
>>> ->
>>> https://mvnrepository.com/artifact/org.keycloak.bom/keycloak-adapter-bom
>>>
>>> ** resolved by changing pom.xml
>>> -        <version>3.1.0.CR1-SNAPSHOT</version>
>>> +        <version>3.0.0.Final</version>
>>>
>>>
>>> ## cannot compile test
>>> [ERROR] Failed to execute goal org.apache.maven.plugins:
>>> maven-compiler-plugin:3.1:testCompile (default-testCompile) on project
>>> keycloak-app-profile-jee-vanilla: Compilation failure: Compilation
>>> failure:
>>> [ERROR] /Users/tanudjaf/git/keycloak-quickstarts/app-profile-jee-
>>>
>>> vanilla/src/test/java/org/keycloak/quickstart/ArquillianProfileJeeVanillaTest.java:[41,25]
>>> package org.keycloak.test does not exist
>>> ...
>>>
>>> ** resolved by removing
>>> app-profile-jee-vanilla/src/test/java/org/keycloak/
>>> quickstart/ArquillianProfileJeeVanillaTest.java
>>> _______________________________________________
>>> keycloak-user mailing list
>>> keycloak-user at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/keycloak-user
>>>
>>
>

More information about the keycloak-user mailing list