	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.0

Sun Java Application Server Ver 9.1 : 2nd instance can't start with DAS synchronization error

Asked by sunhux in Sun Java System Web Server, Sun Solaris, Jboss Application Server

Tags: Sun Java Application Server Ver 9.1 : glassfish

Hi

I have Sun Java App running on Solaris 10. 1st instance created could be started
but subsequent instances could not. Below are the errors / logs :
(let me know any other logs or information needed; pls indicate
exact directory & filename).

Nothing useful is found in /var/adm/messages. I have yet to connect up
a hard console to the console port to see if there's any messages being
flashed on the console.

avaecapp2 # cat server.log
[#|2009-09-15T14:22:11.660+0800|INFO|sun-appserver9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=10;_ThreadName=main;|IdentityManager Data: User:admin|#]

[#|2009-09-15T14:22:18.474+0800|INFO|sun-appserver9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=10;_ThreadName=main;|SYNC001: Unable to communicate with Domain Administration Server. Skipping synchronization.|#]

[#|2009-09-15T14:22:18.480+0800|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=10;_ThreadName=main;|SYNC029: There was an exception during synchronization. Please try again and a full synchronization will be initiated. If the problem persists for a server instance, you may backup and remove the cache repository (for example, directories under nodeagents/na1/server1/) and restart the node-agent (ex. asadmin stop-node-agent; start-node-agent --startinstances=false) and the server instance (ex. asadmin start-instance). All necessary configuration for the server instance (server1 in example) will be downloaded from Domain Administration Server by synchronization.
com.sun.enterprise.ee.synchronization.DASCommunicationException: Unable to communicate with Domain Administration Server.
at com.sun.enterprise.ee.synchronization.BaseSynchronizationDriver.synchronizeInternal(BaseSynchronizationDriver.java:277)
at com.sun.enterprise.ee.synchronization.BaseSynchronizationDriver.synchronize(BaseSynchronizationDriver.java:129)
at com.sun.enterprise.ee.synchronization.SynchronizationMain.main(SynchronizationMain.java:126)
|#]

[#|2009-09-15T18:34:02.989+0800|INFO|sun-appserver9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=10;_ThreadName=main;|IdentityManager Data: User:admin|#]

[#|2009-09-15T18:34:09.626+0800|INFO|sun-appserver9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=10;_ThreadName=main;|SYNC001: Unable to communicate with Domain Administration Server. Skipping synchronization.|#]

[#|2009-09-15T18:34:09.632+0800|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=10;_ThreadName=main;|SYNC029: There was an exception during synchronization. Please try again and a full synchronization will be initiated. If the problem persists for a server instance, you may backup and remove the cache repository (for example, directories under nodeagents/na1/server1/) and restart the node-agent (ex. asadmin stop-node-agent; start-node-agent --startinstances=false) and the server instance (ex. asadmin start-instance). All necessary configuration for the server instance (server1 in example) will be downloaded from Domain Administration Server by synchronization.
com.sun.enterprise.ee.synchronization.DASCommunicationException: Unable to communicate with Domain Administration Server.
at com.sun.enterprise.ee.synchronization.BaseSynchronizationDriver.synchronizeInternal(BaseSynchronizationDriver.java:277)
at com.sun.enterprise.ee.synchronization.BaseSynchronizationDriver.synchronize(BaseSynchronizationDriver.java:129)
at com.sun.enterprise.ee.synchronization.SynchronizationMain.main(SynchronizationMain.java:126)
|#]

[#|2009-10-01T09:42:47.473+0800|INFO|sun-appserver9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=10;_ThreadName=main;|IdentityManager Data: User:admin|#]

[#|2009-10-01T09:42:54.900+0800|INFO|sun-appserver9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=10;_ThreadName=main;|SYNC001: Unable to communicate with Domain Administration Server. Skipping synchronization.|#]

[#|2009-10-01T09:42:54.911+0800|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.synchronization|_ThreadID=10;_ThreadName=main;|SYNC029: There was an exception during synchronization. Please try again and a full synchronization will be initiated. If the problem persists for a server instance, you may backup and remove the cache repository (for example, directories under nodeagents/na1/server1/) and restart the node-agent (ex. asadmin stop-node-agent; start-node-agent --startinstances=false) and the server instance (ex. asadmin start-instance). All necessary configuration for the server instance (server1 in example) will be downloaded from Domain Administration Server by synchronization.
com.sun.enterprise.ee.synchronization.DASCommunicationException: Unable to communicate with Domain Administration Server.
at com.sun.enterprise.ee.synchronization.BaseSynchronizationDriver.synchronizeInternal(BaseSynchronizationDriver.java:277)
at com.sun.enterprise.ee.synchronization.BaseSynchronizationDriver.synchronize(BaseSynchronizationDriver.java:129)
at com.sun.enterprise.ee.synchronization.SynchronizationMain.main(SynchronizationMain.java:126)
|#]

avaecapp2 # pwd
/app/SUNWappserver/nodeagents/agent-psi/instance-obls/logs

errors access Tcp 443

/app/common/eclips/xml/dsm/Inbox/Inbox.xml (Permission denied)]
[org.dsm.builders.StateBuilder.buildState(StateBuilder.java:304)]

Timeout waiting for server instance instance-obls to go to starting state.
CLI137 Command start-instance failed

from: /app/SUNWappserver/nodeagents/agent-server1/instance-server1/logs/server*log*

[#|2009-09-30T21:44:11.556+0800|WARNING|sun-appserver9.1|javax.enterprise.resource.resourceadapter|_ThreadID=26;
_ThreadName=Timer-4;farmsPool;Connection could not be allocated because: Io exception: The Network Adapter could
not establish the connection;_RequestID=e4860442-1908-4d32-9007-487cec7c11b6;|RAR5038:Unexpected exception whil
e creating resource for pool farmsPool. Exception : Connection could not be allocated because: Io exception: The
Network Adapter could not establish the connection|#]

Connection could not be allocated because: Io exception: The Network Adapter could
not establish the connection

Get your answer NOW

20091111-EE-VQP-89 - Hierarchy / EE_QW_3_20080625

Hall of Fame

1. objects18,450
2. mwvisa18,500
3. ksivananth7,500
4. KeremE5,000
5. rajesh_b...4,500
6. basav_com3,500
7. a_b3,300
8. yuzh3,250
9. Christofer...3,200
10. CEHJ3,000
10. allen-dav...3,000
12. rsneale2,700
13. Chris-Dent2,500
13. cj_19692,500
15. kadaba2,100
16. abel2,000
16. gr8gonzo2,000
16. pkwan2,000
16. Venabili2,000
16. J4M3S_...2,000
16. amit20002,000
16. sompol_k...2,000
16. brunoguim...2,000
16. gacus2,000
16. _agx_2,000
16. omarfarid2,000
16. dzamfir2,000
16. darkapple2,000
16. tillgeffken2,000
16. ai_ja_nai2,000
16. sublifer2,000
16. kalamarius2,000
16. lucius_the2,000
16. ajayk12022,000
16. avdej2,000
16. Rh1no2,000
16. testez2,000
16. Protuhj2,000
16. rajan-vora2,000

1. objects69,622
2. CEHJ41,946
3. mayankea...18,843
4. yuzh16,750
5. girionis13,408
6. mwvisa111,675
7. bloodredsun10,800
8. suprapto4510,350
9. rama_kri...10,200
10. Ajay-Singh9,740
11. TimYates9,140
12. ksivananth8,972
13. Javatm8,380
14. Venabili8,320
15. zzynx7,305
16. rrz@87...6,000
17. Kelvin_King5,400
18. heyhey_5,160
19. Giant25,080
20. KeremE5,000
21. mbvvsatish4,950
22. aozarov4,939
23. ravindra764,920
24. ahoffmann4,900
25. rajesh_b...4,600

Sun Java Application Server Ver 9.1 : 2nd instance can't start with DAS synchronization error

Asked by sunhux in Sun Java System Web Server, Sun Solaris, Jboss Application Server

Tags: Sun Java Application Server Ver 9.1 : glassfish

About this solution