Looking at the node agent logs on the rig, it doesn't appear that the node
agent is being multiple times. But I'll look closer at that.
The 1074 port is being chosen randomly for some RMI bootstrapping thing in
glassfish...not sure what. The other machines that have exhibited this
problem have a different port number mentioned. And even on the same
machine, that port will be different from reboot to reboot...when the issue
shows up that is. It has been rather sporadic.
Perhaps there's a way to configure RMIStubRegistryHandler to make use of a
statically configured port?
Thanks for your input!
John
On Wed, Aug 12, 2009 at 3:08 PM, <glassfish_at_javadesktop.org> wrote:
> The error message says that the port is already in use and so it almost
> certainly is.
> Either your node-agent is being started multiple times and the second one
> is failing, or some other process/service is snaffling the port temporarily.
>
> 1074 is above 1023 so [b]could[/b] be handed out to someone else, such as
> an incoming connection, but AFAIK most O/S's don't allocate connection ports
> below some fairly high value [I have NO idea what Windows XP does here], so
> this is unlikely.
>
> I have no idea how to track this down on Windows, sorry.
> [Message sent by forum member 'matterbury' (matterbury)]
>
> http://forums.java.net/jive/thread.jspa?messageID=360154
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>