Working with the ORB

To create an IIOP listener, select Configuration > ORB > IIOP Listeners and click New in the Admin Console. Alternatively, you can use the following asadmin command to create IIOP listeners: create-iiop-listener(1) and create-ssl(1).

To edit an IIOP listener, select Configuration > ORB > IIOP Listeners and select the listener to be modified in the Admin Console. Modify the settings. If you have changed the port number, restart the server. The ORB uses thread pools to respond to requests from remote clients of enterprise beans and other clients that communicate via RMI-IIOP.

To delete an IIOP listener, select Configuration > ORB > IIOP Listeners and select the listener to be deleted in the Admin Console. Alternatively, you can use the delete-iiop-listener(1) command.

The ORBCommunicationsRetryTimeout property specifies the number of seconds the ORB client will try to establish a connection to an unreachable ORB back-end. The default value is 60 seconds. With this default setting, you may see a large number of CORBA exceptions in the logs, as well as high network usage if the ORB back-end is not reachable.

In such cases, set the ORBCommunicationsRetryTimeout to a lower value.

Third-party ORBs

The Sun Java System Application Server can be used in conjunction with third-party ORB software. To support such third-party ORBs, you need to revise the server-side settings.

To implement the support for a third-party ORB in Application Server, you need to edit the files, domain.xml and server.policy. For detailed instructions on how to configure a sample third-party ORB, see Configuring Sun Java System Application Server for Third-Party ORBs