You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Chris Howe (JIRA)" <ji...@apache.org> on 2006/11/11 09:09:39 UTC
[jira] Commented: (OFBIZ-447) Better error message when Unable to
bind RMIDispatcher to RMI
[ http://issues.apache.org/jira/browse/OFBIZ-447?page=comments#action_12448944 ]
Chris Howe commented on OFBIZ-447:
----------------------------------
+1 on an improved error message.
since a possible reason why RMI is unable to bind is that one of those values is null, how about something to the effect of:
+ throw new ContainerException(
"Unable to bind RMIDispatcher to RMI on " + "//host[" + host + "]:port[" + port + "]/name[" + name + "] - with remote=" + remote , e);
> Better error message when Unable to bind RMIDispatcher to RMI
> -------------------------------------------------------------
>
> Key: OFBIZ-447
> URL: http://issues.apache.org/jira/browse/OFBIZ-447
> Project: OFBiz (The Open for Business Project)
> Issue Type: Improvement
> Components: framework
> Affects Versions: SVN trunk
> Environment: all
> Reporter: Jacques Le Roux
> Assigned To: Jacques Le Roux
> Priority: Trivial
> Fix For: SVN trunk
>
> Attachments: RmiServiceContainer.java.patch
>
>
> I propose to add some more informations to ease debugging when there is a problem binding RMIDispatcher to RMI.
> Please see patch.
> Thanks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira