Creating A New Server On Glassfish 2.1 Server Instance Fails with DASCommunicationException

(Doc ID 1343914.1)

Last updated on APRIL 04, 2017

Applies to:

Oracle GlassFish Server - Version 9.0 and later
Information in this document applies to any platform.

Symptoms

The creation of a new server instance fails when the Glassfish Domain Administration Server (DAS) is configured for SSL.

The node agent starts up successfully (using asadmin start-node-agent --startinstances=false). However, when creating a new server instance associated with this node agent either through the admin console or via command line, the creation fails when trying to start this new instance. The node agent log shows the following error:

com.sun.enterprise.ee.synchronization.DASCommunicationException: Unable to communicate with Domain Administration Server.
       at com.sun.enterprise.ee.synchronization.BaseSynchronizationDriver.synchronizeInternal(BaseSynchronizationDriver.java:281)
       at com.sun.enterprise.ee.synchronization.BaseSynchronizationDriver.synchronize(BaseSynchronizationDriver.java:129)
       at com.sun.enterprise.ee.synchronization.SynchronizationMain.main(SynchronizationMain.java:126)
[#|2011-07-14T14:13:16.005-0400|SEVERE|sun-appserver2.1|javax.ee.enterprise.system.nodeagent|_ThreadID=20;_ThreadName=RMI TCP Connection(6)-x.x.x.x;inst03;FAILED!;1304;|NAGT0039:Synchronization for inst03 - FAILED! and took 1304 milliseconds|#]


This happens with GlassFish enterprise profile where the Domain Administration Server is SSL enabled.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms