Error while mounting TeamSpace on server repository: <server-name>

Hello!

After server restart (v4.0) we get an error in localhost.YYYY-MM-DD.log file (under apache /logs):

[Mon Jun 01 15:56:14 CEST 2015] WARNING com.knime.enterprise.server.rmi.KNIMEExecutorImpl addTeamSpaceMountInRMI: 
Error while mounting TeamSpace on server repository: knime.server.com
java.lang.IllegalArgumentException: knime.server.com
        at org.knime.workbench.explorer.ExplorerMountTable.checkMountID(ExplorerMountTable.java:179)
        at org.knime.workbench.explorer.ExplorerMountTable.mountOrRestore(ExplorerMountTable.java:261)
        at org.knime.workbench.explorer.ExplorerMountTable.mount(ExplorerMountTable.java:245)
        at com.knime.enterprise.slave.SlaveManager$2.call(SlaveManager.java:346)
        at com.knime.enterprise.slave.SlaveManager$2.call(SlaveManager.java:1)
        at com.knime.enterprise.slave.RMIUtil.runWithContextFinder(RMIUtil.java:89)
        at com.knime.enterprise.slave.SlaveManager.addTeamSpaceMountPoint(SlaveManager.java:338)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
        at sun.rmi.transport.Transport$1.run(Unknown Source)
        at sun.rmi.transport.Transport$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.rmi.transport.Transport.serviceCall(Unknown Source)
        at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
        at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:276)

[...sic...]

Is this critical or not? Also, is it possible to prevent mounting TeamSpace? Should we?

Regards,

Primož

The mountpoint ID for a teamspace must not start with "knime." as this is a reserved identifier. If you don't use linked metanodes on the server you can disable mounting a team space in the RMI instance in the server configuration (com.knime.server.executor.skip_teamspace_mount=true). Apart from that it is non-critial (otherwise it would be an error and not a warning).

Lets say we would like to use linked metanodes on the server. Do we need to rename our server? Currently the name is knime. .si.

You need to use a different default mount point ID, which is completely independent of the server's DNS name.

I have changed this server setting to a name that does not start with "knime" and now everything looks OK in the logs.

com.knime.server.default_mount_id=
Specifies the name of the default mount ID. This is fetched, when clients set up their mount point to the server. Defaults to the server’s hostname.

Thanks.

Primož