java.io.FileNotFoundException: /root/bimn/bimserver/home/templates/VM_global_library.vm (No such file or directory)

[navneetccna]

Every time i start my bimserver getting this exception this is normal ? my bimserver is working but just want to no what is the use of Velocimacro ?

8-04-2014 17:10:40 DEBUG velocity - Velocimacro : "velocimacro.library" is not set. Trying default library: VM_global_library.vm
08-04-2014 17:10:40 DEBUG velocity - URLResourceLoader: Exception when looking for 'VM_global_library.vm' at 'file:/root/bimn/bimserver/home/templates/'
java.io.FileNotFoundException: /root/bimn/bimserver/home/templates/VM_global_library.vm (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:146)
at java.io.FileInputStream.(FileInputStream.java:101)
at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
at org.apache.velocity.runtime.resource.loader.URLResourceLoader.getResourceStream(URLResourceLoader.java:115)
at org.apache.velocity.runtime.resource.loader.ResourceLoader.resourceExists(ResourceLoader.java:224)
at org.apache.velocity.runtime.resource.ResourceManagerImpl.getLoaderForResource(ResourceManagerImpl.java:629)
at org.apache.velocity.runtime.resource.ResourceManagerImpl.getLoaderNameForResource(ResourceManagerImpl.java:612)
at org.apache.velocity.runtime.RuntimeInstance.getLoaderNameForResource(RuntimeInstance.java:1595)
at org.apache.velocity.runtime.VelocimacroFactory.initVelocimacro(VelocimacroFactory.java:159)
at org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:274)
at org.apache.velocity.app.VelocityEngine.init(VelocityEngine.java:93)
at org.bimserver.templating.TemplateEngine.init(TemplateEngine.java:76)
at org.bimserver.BimServer.start(BimServer.java:337)
at org.bimserver.JarBimServer.start(JarBimServer.java:84)
at org.bimserver.JarBimServer.main(JarBimServer.java:53)

[rubendel]

Nothing to worry about (that's why it's logging in DEBUG level). But it's been fixed in the next release.

1e67915