-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using two Karaf instances in one VM #87
Comments
Hello @amarsico, When I tested the NetIDE Engine before Brussels Meeting I obtained a similar error when I run the ODL shim and the Java Core. Now, when I run the Java Core and the Onos shim (in this order and in two different karaf instances) I also obtain an exception in the onos terminal: onos> Exception in thread "JMX Connector Thread [service:jmx:rmi://0.0.0.0:44444/jndi/rmi://0.0.0.0:1099/karaf-root]" java.lang.RuntimeException: |
Hello @sergiotamu, That issue is solved in the readme odl-shim.
|
Ok, but this solution is for ODL and its Karaf instance. For ONOS is different, since there are BASH scripts that interacts with Karaf and you have to change them. I think we might change the Karaf Core configuration and add the following lines to the Java Core README:
However, changing these values creates an issue in loading the composition file ( We have to agree to a common modification, since we are going to deploy also automatically the Engine with ODL or ONOS as servers. Let me know what you think. Best |
@amarsico The url for loadcomposition is static because I and Tim did not know how to set karaf config attributes in another way. There is probably a better way that does not depend on the port. I will have to check that. |
Along with the @amarsico changes, you also need to change HTTP port in ./etc/org.ops4j.pax.web.cfg, after that try to restart the karaf, issue will be resolved. org.osgi.service.http.port=8183 |
Dear all,
I have a question that never comes from you, but when I was testing the Core with ONOS it happens.
If I have one virtual machine and two Karaf instances I always get errors like this one when I start the second instance:
This is because Karaf uses several services, such as Java RMI and SSH daemon, that bind host ports. I never get issue from you, but I tried to change the default ports of the Karaf instance of NetIDE Core, it does not raise errors but it becomes unstable. (e.g. the loadcomposition command does not work properly).
Has anyone resolved or encountered the issue?
The text was updated successfully, but these errors were encountered: