Archived
This forum has been archived. Please start a new discussion on GitHub.
Problems with 3.0.1 cross-platform IceGrid
in Help Center
Has anybody out there experienced these problems?
We have compiled and re-compiled, downloaded the lastest version, looked in the source, read the manual, tested, re-tested, compared against what we've done in 1.4, etc, etc. All over a series of days. We are at a dead-end for what seems to be a simple problem on our part.
We have been using 1.4 successfully for a couple of years and are now trying to migrate to v3. What is described below, we have been doing using 1.4 all this time, but can't make work with v3. The migration is 99% done, but a weird, but seemingly simple issue still exists.
We downloaded and compiled Ice 3.0.0 C++ on solaris and 3.0.0 Java binary and installed that binary on Solaris and Windows.
Scenario 1: We successfully ran the grid registry, node, and admin to set up a domain solely on Solaris and our C++ and Java servants work fine. Everything works fine.
Scenario 2: We start the registry and a node on the Windows box, then add a node on Solaris and run icepackadmin on Solaris. When we run icepackadmin on Solaris, we get these messages:
icegridadmin: server is using unknown Slice type `::IceGrid::Adapter'
icegridadmin: server is using unknown Slice type `::IceGrid::AdapterActiveException'
icegridadmin: server is using unknown Slice type `::IceGrid::AdapterExistsException'
icegridadmin: server is using unknown Slice type `::IceGrid::AdapterNotActiveException'
icegridadmin: server is using unknown Slice type `::IceGrid::AdapterPrxDict'
icegridadmin: server is using unknown Slice type `::IceGrid::Node'
icegridadmin: server is using unknown Slice type `::IceGrid::NodeActiveException'
icegridadmin: server is using unknown Slice type `::IceGrid::NodeSession'
icegridadmin: server is using unknown Slice type `::IceGrid::Registry'
icegridadmin: server is using unknown Slice type `::IceGrid::Server'
In this same scenario, we go back to windows and use icepackadmin to deploy services on both the Solaris and Windows boxes. Everythings works and we can run our apps fine again, albeit with the above warning.
Scenario 3: Start registry and node on Solaris, add node on Windows. When icegridnode is run on Windows, it hangs for a minute or so and then says
icegridnode.exe:: warning: couldn't contact the IceGrid registry: connect failed: WSAETIMEDOUT
To eliminate the possibility of a bad build and also upgrade and get any fixes, we then downloaded, compiled, installed, and re-tested against 3.0.1 and the same exact problems exist. Do not see any core files.
Again, I emphasize, we have been doing all these steps successfully in 1.4 for a very long time. It is probably something very dumb that we are doing incorrectly using this new version, but we thing we have exhausted all avenues of investigation.
If anybody out there has any clues as to what we are doing wrong, any advice would be really appreciated. The spector of reverting to 1.4 looms and we really want to avoid that.
Thanks,
Brian
We have compiled and re-compiled, downloaded the lastest version, looked in the source, read the manual, tested, re-tested, compared against what we've done in 1.4, etc, etc. All over a series of days. We are at a dead-end for what seems to be a simple problem on our part.
We have been using 1.4 successfully for a couple of years and are now trying to migrate to v3. What is described below, we have been doing using 1.4 all this time, but can't make work with v3. The migration is 99% done, but a weird, but seemingly simple issue still exists.
We downloaded and compiled Ice 3.0.0 C++ on solaris and 3.0.0 Java binary and installed that binary on Solaris and Windows.
Scenario 1: We successfully ran the grid registry, node, and admin to set up a domain solely on Solaris and our C++ and Java servants work fine. Everything works fine.
Scenario 2: We start the registry and a node on the Windows box, then add a node on Solaris and run icepackadmin on Solaris. When we run icepackadmin on Solaris, we get these messages:
icegridadmin: server is using unknown Slice type `::IceGrid::Adapter'
icegridadmin: server is using unknown Slice type `::IceGrid::AdapterActiveException'
icegridadmin: server is using unknown Slice type `::IceGrid::AdapterExistsException'
icegridadmin: server is using unknown Slice type `::IceGrid::AdapterNotActiveException'
icegridadmin: server is using unknown Slice type `::IceGrid::AdapterPrxDict'
icegridadmin: server is using unknown Slice type `::IceGrid::Node'
icegridadmin: server is using unknown Slice type `::IceGrid::NodeActiveException'
icegridadmin: server is using unknown Slice type `::IceGrid::NodeSession'
icegridadmin: server is using unknown Slice type `::IceGrid::Registry'
icegridadmin: server is using unknown Slice type `::IceGrid::Server'
In this same scenario, we go back to windows and use icepackadmin to deploy services on both the Solaris and Windows boxes. Everythings works and we can run our apps fine again, albeit with the above warning.
Scenario 3: Start registry and node on Solaris, add node on Windows. When icegridnode is run on Windows, it hangs for a minute or so and then says
icegridnode.exe:: warning: couldn't contact the IceGrid registry: connect failed: WSAETIMEDOUT
To eliminate the possibility of a bad build and also upgrade and get any fixes, we then downloaded, compiled, installed, and re-tested against 3.0.1 and the same exact problems exist. Do not see any core files.
Again, I emphasize, we have been doing all these steps successfully in 1.4 for a very long time. It is probably something very dumb that we are doing incorrectly using this new version, but we thing we have exhausted all avenues of investigation.
If anybody out there has any clues as to what we are doing wrong, any advice would be really appreciated. The spector of reverting to 1.4 looms and we really want to avoid that.
Thanks,
Brian
0