<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Wed May 22 14:36:12 CDT 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://www.couchbase.com/issues/si/jira.issueviews:issue-xml/NCBC-207/NCBC-207.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Couchbase</title>
    <link>http://www.couchbase.com/issues</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>5.2.4</version>
        <build-number>845</build-number>
        <build-date>26-12-2012</build-date>
    </build-info>

<item>
            <title>[NCBC-207] Could not find the pool &apos;...&apos; at http://host:8091/pools : password-less buckets make the other buckets unavailable</title>
                <link>http://www.couchbase.com/issues/browse/NCBC-207</link>
                <project id="10046" key="NCBC">Couchbase .NET client library</project>
                        <description>Hi, we stumbled on a minor bug.&lt;br/&gt;
&lt;br/&gt;
After importing the beer bucket for testing purpose, we had this kind of errors : (Couchbase .Net 1.2 / mono client) &lt;br/&gt;
&lt;br/&gt;
2013-01-17 11:13:28 [DEBUG] 1 Couchbase.MessageStreamListener - Starting the listener. Queue=True&lt;br/&gt;
2013-01-17 11:13:28 [DEBUG] 11 Couchbase.MessageStreamListener - Started working.&lt;br/&gt;
2013-01-17 11:13:28 [DEBUG] 11 Couchbase.MessageStreamListener - Looking for the first working node.&lt;br/&gt;
2013-01-17 11:13:29 [WARN] 11 Couchbase.ConfigHelper - Could not find the pool &amp;#39;static&amp;#39; at &lt;a href=&quot;http://10.1.44.1:8091/pools&quot;&gt;http://10.1.44.1:8091/pools&lt;/a&gt;&lt;br/&gt;
2013-01-17 11:13:29 [WARN] 11 Couchbase.MessageStreamListener - Could not resolve url &lt;a href=&quot;http://10.1.44.1:8091/pools;&quot;&gt;http://10.1.44.1:8091/pools;&lt;/a&gt; trying the next in the list&lt;br/&gt;
2013-01-17 11:13:29 [WARN] 11 Couchbase.ConfigHelper - Could not find the pool &amp;#39;static&amp;#39; at &lt;a href=&quot;http://10.1.44.2:8091/pools&quot;&gt;http://10.1.44.2:8091/pools&lt;/a&gt;&lt;br/&gt;
2013-01-17 11:13:29 [WARN] 11 Couchbase.MessageStreamListener - Could not resolve url &lt;a href=&quot;http://10.1.44.2:8091/pools;&quot;&gt;http://10.1.44.2:8091/pools;&lt;/a&gt; trying the next in the list&lt;br/&gt;
2013-01-17 11:13:29 [WARN] 11 Couchbase.MessageStreamListener - Could not found a working node.&lt;br/&gt;
2013-01-17 11:13:29 [WARN] 11 Couchbase.MessageStreamListener - All nodes are dead, sleeping for a while.&lt;br/&gt;
2013-01-17 11:13:29 [INFO] 11 Couchbase.CouchbasePool - Received new configuration.&lt;br/&gt;
2013-01-17 11:13:29 [INFO] 11 Couchbase.CouchbasePool - Config is empty, all nodes are down.&lt;br/&gt;
2013-01-17 11:13:29 [DEBUG] 11 Couchbase.MessageStreamListener - Processing message: &lt;br/&gt;
&lt;br/&gt;
It appears that if a bucket with authentication is passwordless (like the beer sample bucket at creation), the client cannot find the other pools.&lt;br/&gt;
</description>
                <environment>Mono 2.10.8.1 (Debian 2.10.8.1-1ubuntu2.2) Ubuntu 12.04 / Couchbase server 2.0</environment>
            <key id="21812">NCBC-207</key>
            <summary>Could not find the pool &apos;...&apos; at http://host:8091/pools : password-less buckets make the other buckets unavailable</summary>
                <type id="1" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="4" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/minor.png">Minor</priority>
                    <status id="1" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="john">John Zablocki</assignee>
                                <reporter username="guillaume.pitel">guillaume.pitel</reporter>
                        <labels>
                    </labels>
                <created>Thu, 17 Jan 2013 04:54:03 -0600</created>
                <updated>Fri, 17 May 2013 15:39:11 -0500</updated>
                                                    <fixVersion>1.3</fixVersion>
                                                <votes>0</votes>
                        <watches>0</watches>
                                                    <comments>
                    <comment id="48109" author="john" created="Fri, 18 Jan 2013 16:56:12 -0600"  >Hi Guillaume,&lt;br/&gt;
&lt;br/&gt;
How did this affect the client&amp;#39;s behavior?  Did operations fail?  Could you describe a bit more what you were seeing?&lt;br/&gt;
&lt;br/&gt;
Thanks.&lt;br/&gt;
&lt;br/&gt;
-- John</comment>
                    <comment id="48120" author="guillaume.pitel" created="Sat, 19 Jan 2013 01:04:12 -0600"  >It&amp;#39;s the connection creation that fails, so every subsequent operation fails.</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                                                                                                                                                    <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>9235</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                                            </customfields>
    </item>
</channel>
</rss>