You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Steve Carmichael (JIRA)" <ji...@apache.org> on 2007/06/12 23:16:32 UTC
[jira] Created: (SM-965) jbi:projectDeploy with
-Dhost=xxx.xxx.xxx.xxx option ignores host name and uses localhost
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.
[jira] Commented: (SM-965) jbi:projectDeploy with
-Dhost=xxx.xxx.xxx.xxx option ignores host name and uses localhost
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (SM-965) Allow use of -Dhost, -Dport, -Dusername
and -Dpassword on jbi:projectDeploy
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen updated SM-965:
-------------------------------
Issue Type: Improvement (was: Bug)
Summary: Allow use of -Dhost, -Dport, -Dusername and -Dpassword on jbi:projectDeploy (was: jbi:projectDeploy with -Dhost=xxx.xxx.xxx.xxx option ignores host name and uses localhost)
> Allow use of -Dhost, -Dport, -Dusername and -Dpassword on jbi:projectDeploy
> ---------------------------------------------------------------------------
>
> Key: SM-965
> URL: https://issues.apache.org/activemq/browse/SM-965
> Project: ServiceMix
> Issue Type: Improvement
> 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.
[jira] Resolved: (SM-965) Allow use of -Dhost, -Dport, -Dusername
and -Dpassword on jbi:projectDeploy
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen resolved SM-965.
--------------------------------
Resolution: Fixed
Fix Version/s: 3.2
3.1.2
Added the necessary expression=${...}
http://svn.apache.org/viewvc?view=rev&revision=547183
> Allow use of -Dhost, -Dport, -Dusername and -Dpassword on jbi:projectDeploy
> ---------------------------------------------------------------------------
>
> Key: SM-965
> URL: https://issues.apache.org/activemq/browse/SM-965
> Project: ServiceMix
> Issue Type: Improvement
> Components: tooling
> Affects Versions: 3.1
> Reporter: Steve Carmichael
> Fix For: 3.1.2, 3.2
>
>
> 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.