This topic discusses programs found to be have issues when run on the same machine as TIBCO StreamBase®.
Oracle VM VirtualBox is a virtual machine hosting environment similar to VMware Workstation or Microsoft Hyper-V. VirutalBox can be installed on the same machine that hosts StreamBase, and can serve well was a host for guest operating systems that run StreamBase Applications.
However, on Windows, if VirtualBox is installed and any of its guests have their network adapters enabled, then installing and starting nodes with the epadmin command can be very slow.
If you encounter this issue, you can:
Disable the network adapters of your VirtualBox guests, or
Use epadmin with its adminport parameter instead of its servicename parameter to identify nodes.
Microsoft Hyper-V is a virtual machine hosting environment similar to VMware Workstation or Oracle VM VirtualBox. Hyper-V can serve well was a host for guest operating systems that run StreamBase Applications.
On some Windows 10 installations, having Hyper-V installed — just installed, not running or hosting a guest VM — prevents the StreamBase Runtime from maintaining more than one node at a time on the Windows host (not in Docker). This applies to nodes launched either from StreamBase Studio or from epadmin.
Hyper-V is enabled as a part of the Docker for Windows installation, and is required to run it.
If you encounter this issue, to work around it, you can:
Keep Hyper-V and Docker installed, and run only a single node at a time.
Uninstall Hyper-V in order to run multiple nodes on the host Windows machine. You do not need to uninstall Docker for Windows, but Docker does not run with Hyper-V removed. You can reinstall Hyper-V to allow you to run Docker on the same machine.