-
Notifications
You must be signed in to change notification settings - Fork 61
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
Port connection not reached #162
Comments
Seems to work properly for me with your provided sample project. I see the following output when run with
BTW: Did you intend to post your password in the code sample? |
I've just realized that I'm getting different messages when I'm using When I perform
Otherwise, using
This is my last gradle script. |
I've been trying it for a some days ago, and I'm not able reach my server. Nevertheless, I'm able to log in using web interface. Any ideas? |
My guess is that you'll have to change the HTTP management port explicitly by a property. That's pre-set by Cargo. For more information see In your task creation you'll have to assign something to the property
|
Thanks @bmuschko
Nevertheless, I keep getting the same message:
I'd like you look at
Am I using the correct dependencies in order to connect cargo with a wildfly 10 instance? |
In that I case I do not know. I suggest you ask about this on the Cargo user mailing list. |
I have briefly checked the management-http functionality from Codehaus Cargo side, it should work if cargo.jboss.management-http.port is set in Cargo configuration. |
Thanks @sutaakar for your comment. Nevertheless, I don't quite know what you exactly mean to... I mean, I don't know how to dig into Codehaus Cargo from my gradle script... Do you mean I take a look on debug? Nevertheless, how can I get this exactly information? Are you thinking about configuring any logger? I think the messages I get from the task execution shows ho gradle plugin is reporting me correct port:
Nevertheless, it seems that it's trying to connect to 9990 instead of 9992:
Sorry. |
I meant, I'm absolutly willing to help out adquiring that information, but I don't quite how exactly get it. Could you give me some lights? |
@jeusdi Can you please debug your Cargo execution? Can you please put a breakpoint there and check if |
Is there some tutorial showing how to debug and set a breakpoint to an Ant plugin from gradle? |
You may try to use GRADLE_OPTS, see https://discuss.gradle.org/t/how-do-you-attach-a-debugger-to-gradle-so-that-i-can-debug-it-running-a-task/7526 . |
Put a breakpoint to https://github.com/codehaus-cargo/cargo/blob/master/core/containers/wildfly/src/main/java/org/codehaus/cargo/container/wildfly/internal/AbstractWildFlyRemoteDeployer.java#L85 . This line should definitely be reached. If it is so check the value of management port. If it is 9990 then it is default value. |
Try to put breakpoint to constructor - line 74. |
It's not reached 😧 |
Seems that java debug has to be activated differently: https://docs.gradle.org/current/dsl/org.gradle.api.tasks.JavaExec.html try to use parameter --debug-jvm |
I'm getting this message:
|
Hmm, from https://discuss.gradle.org/t/how-do-you-attach-a-debugger-to-gradle-so-that-i-can-debug-it-running-a-task/7526/5 it seems that it can be possible to debug if you set jvm args in gradle.properties file. |
I've ben able to reach this code: https://github.com/codehaus-cargo/cargo/blob/master/extensions/ant/tasks/src/main/java/org/codehaus/cargo/ant/CargoTask.java#L772 As you can see on image the port is 9990, instead of 9992! Nevertheless, I've laso just realized 9992 value is set on |
Can you please check property |
@bmuschko I think the bug is around https://github.com/bmuschko/gradle-cargo-plugin/blob/master/src/main/groovy/com/bmuschko/gradle/cargo/tasks/remote/RemoteCargoContainerTask.groovy#L85 And it seems not reached: Line 102 in 7fe72e9
Could you take a look, please? |
@bmuschko , could I help out with anything more? |
@bmuschko could you give us some feedback. Do you thing it's an issue related with gradle plugin? |
@jeusdi I might be able to have a look within the next 2 weeks but I can't promise it. |
@bmuschko Please, sorry for asking you for it again. Nevertheless, I'm still sticking in solving that. Nevertheless, it would be really a great work around if it was ready... Have you been able to take a look? |
I'm getting this message:
Nevertheless, my task sets the port to connect to is 9992 instead of used 9990!
So, the connection is refused! How could I change the port?
The text was updated successfully, but these errors were encountered: