1) When creating a new protocol session, it fails with a Configuration Error.
It's likely the context for the given protocol doesn't contain enough information for a session to be created, or it's just wrong. Use the protocols:context command to register a context with corrected information. Check that the URI contains the user/password, host, schema, etc... Concrete context information, however, depends on the underlying protocol implementation.
2) When trying to start a new resource, it fails with the following error: "The subsystem request failed".
The netconf subsystem for ssh connections is not set in the router. You can find the problem description and it solution at http://jira.i2cat.net:8080/browse/OPENNAAS-238
3) When building OpenNaaS, the build randomly fails with a: java.lang.OutOfMemoryError: PermGen space
This is due to the space that the JVM devotes to loaded classes running out. The reason for this is probably some uncleaned reference on a ClassLoader that prevents the GC to do its job.The temporary workaround is to prepend this to the maven calls:
MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=128m" mvn install
Related to known bug: jira.i2cat.net/browse/OPENNAAS-417
4) In a Windows XP System, I only have 175 available commands.
The reason is that non of the bundles are loaded, so the total amount of commands are not exported. OpenNaaS uses Fuse 4.4 version, which requires either a Windows 2003 Server, a Windows 2008 Server or Windows 7. Some of our developers use Windows 7, so we recommend to use this choice.