[
https://issues.apache.org/activemq/browse/SM-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39367
]
Gert Vanthienen commented on SM-965:
------------------------------------
It's not a bug apparently, but a feature that hasn't been implemented yet.
There are no expression annotations on any of the properties in
AbstractDeployableMojo.
An example:
{code}
/**
* @parameter default-value="localhost" expression="${jbi.host}"
*/
private String host;
{code}
After the change, I'm able to use this command succesfully:
{{mvn jbi:projectDeploy -Djbi.host=kiwi}}
> jbi:projectDeploy with -Dhost=xxx.xxx.xxx.xxx option ignores host name and
> uses localhost
> -----------------------------------------------------------------------------------------
>
> Key: SM-965
> URL: https://issues.apache.org/activemq/browse/SM-965
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
> Affects Versions: 3.1
> Reporter: Steve Carmichael
>
> when I run the following command:
> >mvn jbi:projectDeploy -Dhost=XXX.X.X.XXX -Dusername=XXX -Dpassword=XXX
> (where XXX = real values)
> to deploy to a remote server running ServiceMix standalone, I get the
> following error:
> Caused by: java.io.IOException: Failed to retrieve RMIServer stub:
> javax.naming.ServiceUnavailableException [Root e
> xception is java.rmi.ConnectException: Connection refused to host: localhost;
> nested exception is:
> java.net.ConnectException: Connection refused: connect]
> at
> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:317)
> at
> javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
>
> at
> org.apache.servicemix.jbi.management.task.JbiTask.getJMXConnector(JbiTask.java:77)
>
> at
> org.apache.servicemix.jbi.management.task.JbiTask.connect(JbiTask.java:85)
> at
> org.apache.servicemix.jbi.management.task.JbiTask.execute(JbiTask.java:252)
> ... 21 more
> Caused by: javax.naming.ServiceUnavailableException [Root exception is
> java.rmi.ConnectException: Connection refuse
> Notice that localhost is being invoked (not the hostname I indicated in the
> -D option)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
