or Create a profile

Home → SMB Enterprise (Suggestions) →

Saffron cluster shouldn't start with bad configuration

Jay Zylstra's Avatar

Jay Zylstra

09 Nov, 2010 01:50 AM via web

We had inadvertently configured a node in SaffronCluster.xml to have a Lookup service with no Cache service. We have since learned that this is an unsupported configuration, but didn't know so at the time, nor suspected anything was wrong because the cluster appeared to startup fine. It wasn't until we began getting errors running Saffron that we realized something was wrong, but what? Saffron should validate its configuration at startup, and not start up if misconfigured, giving a useful error message describing the misconfiguration. Fail early.

  1. Support Staff 2 Posted by Jim Fleming on 17 Nov, 2010 12:49 AM

    Jim Fleming's Avatar

    Thanks Jay, this issue has been submitted to development.

Reply to this discussion

Internal reply

Formatting help or Preview

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

4 people watching.

  • New Issue

  • Conversation Started

  • The developers are involved

    The Saffron developers are involved and working on the discussion

    #735 state: open

  • Close the discussion

Recent Discussions

29 Jun, 2011 03:54 PM obtaining [data] types
11 May, 2011 09:21 PM min and max settings.
06 May, 2011 03:36 PM Installing and Using Code Extensions (Custom Beans)
10 Mar, 2011 01:47 PM Unable to publish a space that has been copied from another cluster(4864)
03 Mar, 2011 08:02 PM Fractional date formats?

Recent Articles

SaffronSierra Billing
Amazon Payment Authorization