Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

java.net.ConnectException with two modules #63

Open
loic-seguin opened this issue Feb 21, 2017 · 7 comments
Open

java.net.ConnectException with two modules #63

loic-seguin opened this issue Feb 21, 2017 · 7 comments

Comments

@loic-seguin
Copy link

Hi,

I tried your plugin following this page http://dynamodb.jcabi.com/usage.html.
I used the three goals 'start', 'create-tables' and 'stop'.

It works well with one module.

But when we have two modules, if we run 'mvn clean verify' in each module everything goes well but if we run this command at the pom parent level, we get a java.net.ConnectException at the 'create-tables' goal for the second module which is compiled by maven.

Here is a really simple project with no code at all
example-project-two-modules.zip

(You can try it if you want)

There are only a pom parent, two modules with their own pom and that's it.

If I run the command 'mvn clean verify' in moduleA or in moduleB, everything is ok.

If I run the command at the pom parent level, module A is processed by maven without any problem. The goals 'start', 'create-tables' and 'stop' are done well. When module B is processed by maven we got multiple times java.net.ConnectException during the goal 'create-tables' until the connection works.

I directly though of aws problem regarding the logs below :

at com.amazonaws.services.dynamodbv2.util.TableUtils.waitUntilExists(TableUtils.java:100)
at com.jcabi.dynamodb.core.Tables.exists(Tables.java:160)

So I clone your project jcabi-dynamodb-maven-plugin and I upgrade these two dependencies aws-java-sdk-core and aws-java-sdk-dynamodb to 1.11.25. Under this version, we got the same exception.

I compiled it and used it instead of 0.8 version. And it worked.

Can I do a PR about this issue ?

Regards

@0crat
Copy link

0crat commented Feb 21, 2017

@yegor256 please, pay attention to this issue

@loic-seguin
Copy link
Author

Hi,

Could I have feedback concerning this issue ?

@yegor256
Copy link
Member

yegor256 commented Apr 3, 2017

@loic-seguin yes, please submit a pull request. Thanks!

@yegor256
Copy link
Member

@rultor release tag is 0.9.1

@yegor256
Copy link
Member

@loic-seguin your PR #66 was merged, let me release a new version and ask you to try again

@rultor
Copy link
Contributor

rultor commented Apr 28, 2017

@rultor release tag is 0.9.1

@yegor256 OK, I will release it now. Please check the progress here

@rultor
Copy link
Contributor

rultor commented Apr 28, 2017

@rultor release tag is 0.9.1

@yegor256 Done! FYI, the full log is here (took me 12min)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants