This chapter provides some quick checks for isolating problems when trying to run the samples.
Compiler errors
Wrong compliance level
Error occurs when trying to build the Java project. To run the SDK samples, the compliance level must be set to 5.0 since the samples use Java 2 Standard Edition (J2SE) 5.0 features. To change the compliance level, create a new project and set the compliance level in the EGO Project dialog.
![]()
Incorrect number of arguments
Each Java sample requires a specific number of arguments to be passed to its main method. Click the Arguments tab and enter the arguments. For example, Sample 5 requires the following arguments in the given order:
Connection errors
note:
Users should be familiar with the EGO runtime setup before trying to run the client samples.
Incorrect username or password
Check the EGO runtime setup. The samples use "egoadmin" as the username and password when logging on to EGO.
Platform EGO not running
Check that the Platform EGO runtime has been installed, configured, and running on a host cluster. For C clients, check that the EGO daemon port numbers in the ego.conf file match the port numbers configured for the EGO master host. The C samples reads the information in the ego.conf file when opening a connection to Platform EGO.
Incorrect URL
For Java clients, try to connect to the Web Service Gateway using a browser by entering the URL or IP address and port number of the gateway. If you cannot connect through the browser, verify the URL of the gateway and check that it is running. The gateway is installed as part of Platform EGO. It comes with a configuration file called wsg.conf where the port number for the gateway can be defined. By default the port number is 9090. The default location for the wsg.conf file is /opt/ego/kernel/conf/. The gateway URL can then be formed by using the host name where the gateway is running and the port number, i.e., http://host:port.
If you can connect to the gateway from a browser but cannot connect to it using the samples, verify that the URL of the gateway matches the URL that is passed as an argument to the client sample. This URL consists of an IP address or host name and a port number.
DNS cannot resolve host name
Verify that the TCP/IP configuration of the client host is properly set up. Check that it does not have an external DNS server, such as a DNS server from an Internet service provider (ISP). If the client is configured to use an external DNS server, it may be unable to resolve internal names. This can also cause problems with conflicting internal and external namespaces. Likewise, the Web Service gateway should be properly configured and have an appropriate DNS.
Notification problems
Platform EGO communicates notifications such as allocation request responses and state changes to the client using a customer designated port number on the client host. This port number or endpoint implements the EGO notification WSDL interface. Platform EGO will send notifications to the client using this endpoint. If the port is busy, i.e., already in use by another application, Platform EGO will be unable to send the notifications to the client. Verify that the selected port number is available.
[ Top ]
[ Platform Documentation ]
Date Modified: July 12, 2006
Platform Computing: www.platform.com
Platform Support: support@platform.com
Platform Information Development: doc@platform.com
Copyright © 1994-2006 Platform Computing Corporation. All rights reserved.