tag:blogger.com,1999:blog-8840085855436806841.post4009408624635234285..comments2011-10-04T02:25:30.046-04:00Ryanhttp://www.blogger.com/profile/12120844691062261364noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-8840085855436806841.post-59253902821088519882011-06-28T07:56:55.948-04:002011-06-28T07:56:55.948-04:00nice article <br />i liked it<br />================<br /><a href="http://www.webicon.co.in/" rel="nofollow">webicon it solutions</a>Elenahttp://www.blogger.com/profile/08881310670518255979noreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-8772715365165256392008-04-22T17:07:00.000-04:002008-04-22T17:07:00.000-04:00Jason, <BR/><BR/>Cluster instances do not run on the same ports as glassfish would with the development profile (8080,8081), instead, in my experience, they run on ports 38080, 38081, etc. The admin server runs on 4848, but the cluster instances won't use that port so there's no conflict there. <BR/><BR/>The cluster setup assumes a load balancer in front of this whole thing that distributes requests among the cluster instances (i.e. http://your.domain.com:80/ is actually a load balancer, not any of the glassfish instances). So, basically, the cluster instances aren't intended to be accessed directly (though, I have found that accessing them directly via their ip:port can be quite useful for testing specific instances).<BR/><BR/>That said, there might be a way to make the glassfish cluster instances run on 8080, instead of 38080, but I haven't ever tried so I'm sure how you might do that. I'd say reconsider why you want to do that, because having users go directly to a glassfish instance without a load balancer distributing requests kind of defeats the purpose of the cluster because at that point one instance is handling everything. Perhaps I misunderstood the question? Otherwise, I hope that helps.Ryanhttp://www.blogger.com/profile/12120844691062261364noreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-55664310160192391772008-04-22T09:13:00.000-04:002008-04-22T09:13:00.000-04:00Ryan,<BR/><BR/>Nice article and very helpful. One question I have about ports in this setup is the following:<BR/><BR/>Since your DAS is currently started, isn't it using the defaults ports (8080, 8081, 7676, 3700...) and your cluster instance is just using free ports. So any cluster instance deployed apps would not run on the default ports? How do you suggest allowing the cluster instance to use the default ports but still keep the admin console up and running on the default domain server? Thanks<BR/><BR/>JasonJasonhttp://www.blogger.com/profile/16259524050066479721noreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-80787990443502197192008-04-03T16:17:00.000-04:002008-04-03T16:17:00.000-04:00Hi,Ryan Wilson,<BR/><BR/> I follow your's step deploy to debian 4 in VMware,but the final step :"asadmin start-node-agent --syncinstances=true g2-a1",when i run it,the system return :"Node Agent g2-a1 failed to startup. Please check the server log for more details.<BR/>CLI137 Command start-node-agent failed. "<BR/><BR/> I try it 6 times,every result is same.The password I never change it.<BR/> <BR/> Please give me a advise,thank you very much.Xiehttp://www.blogger.com/profile/09142498904062460170noreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-45962474841808405502008-03-03T09:52:00.000-05:002008-03-03T09:52:00.000-05:00./ant -f setup-cluster.xml create-node-agent -Ddas.host=hostname -Dnodeagent.name=your-na <BR/><BR/>should also do the trick but without the need to edit the buildfile.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-77869626122425644372008-02-19T08:56:00.000-05:002008-02-19T08:56:00.000-05:00@alessandro<BR/><BR/>Great find! i figured there had to be a way but had never investigated it. Thanks for letting us all know! I've updated the post to note your comment.Ryanhttp://www.blogger.com/profile/12120844691062261364noreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-57293458997805448742008-02-18T05:20:00.000-05:002008-02-18T05:20:00.000-05:00"I don't know if there is a way to specify the port and name for the node-agent at the time of creation"<BR/><BR/>I found it!!<BR/><BR/>In the setup-cluster.xml<BR/><BR/>property name="nodeagent.name" value="na"<BR/><BR/>Change the value before the command<BR/><BR/>./ant -f setup-cluster.xml create-node-agent -Ddas.host=hostname<BR/><BR/>;-)Alessandrohttp://www.blogger.com/profile/06160175847509164155noreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-45550027430099356582008-01-10T10:11:00.000-05:002008-01-10T10:11:00.000-05:00So it is. Thanks for noticing that! It's updated to reflect the change.Ryanhttp://www.blogger.com/profile/12120844691062261364noreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-90130156803844534782008-01-09T22:37:00.000-05:002008-01-09T22:37:00.000-05:00HI..<BR/><BR/> a NICE ARTICLES..<BR/><BR/>i want to edit the 9th step in machine 1 and 7th step in machine 2. you wrote: --node-agent<BR/><BR/>it should be : --nodeagent..<BR/><BR/>Thank you<BR/><BR/>The Curious <BR/>From IndonesiaThe Curioushttp://www.blogger.com/profile/17651512289062761263noreply@blogger.com