Hi Timo, Traffic directed to all app instances (incl tomcat) within the same farm. You need to either create your admin role using base shared role as ancestor or to create a new farm with a single app role.
Nick 2009/7/27 ts <[email protected]>: > > Hi, > > We have the following setup : > 1 www role > 1 mysql master > 1 mysql slave > 1 custom tomcat role on x64 > 1 custom app role on x32 > > We currently send the www requests to custom tomcat role for the > xxx.com domain. We don't want the custom app role within the xxx.com > pool as we access it by admin.xxxx.com name. We have set the config > for the app role for not being included in the dns zone but every time > after it crashes and starts up it gets included in the www pool which > messes up our xxx.com traffic. > > How do we solve this problem? We want the custom app role to stay out > of the xxx.com traffic and only be accessible through the > admin.xxx.com name. > > Can the support team pls take a look at the setup and fix the issue > with the custom app role getting included in the xxx.com traffic as > also advise the best way to handle the admin.xxxx.com traffic. > > Thanks. > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
