<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:57:07 UTC 2024

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 append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[JAVA-2408] java-mongodb-driver test case failure</title>
                <link>https://jira.mongodb.org/browse/JAVA-2408</link>
                <project id="10006" key="JAVA">Java Driver</project>
                    <description>&lt;p&gt;I try to run testcases for java-mongodb-driver, before making any changes to the source code.&lt;br/&gt;
7 testcases are failed as shown below.&lt;/p&gt;

&lt;p&gt;$ ./gradlew check -Dorg.mongodb.test.uri=mongodb://&amp;lt;ip&amp;gt;:27017/&lt;/p&gt;

&lt;p&gt;:driver-core:test&lt;br/&gt;
i) One test with error &quot;ns not found&quot; as follow:&lt;br/&gt;
should deliver started and completed command events for split unacknowleded inserts&lt;/p&gt;

&lt;p&gt;com.mongodb.MongoCommandException: Command failed with error -1: &apos;ns not found&apos; on server &amp;lt;ip&amp;gt;:27017. The full response is &lt;/p&gt;
{ &quot;ok&quot; : 0.0, &quot;errmsg&quot; : &quot;ns not found&quot; }
&lt;p&gt;	at com.mongodb.connection.ProtocolHelper.getCommandFailureException(ProtocolHelper.java:115)&lt;br/&gt;
	at com.mongodb.connection.CommandProtocol.execute(CommandProtocol.java:114)&lt;br/&gt;
	at com.mongodb.connection.WriteProtocolCommandEventSpecification.should deliver started and completed command events for split unacknowleded inserts(WriteProtocolCommandEventSpecification.groovy:145)&lt;/p&gt;

&lt;p&gt;com.mongodb.MongoCommandException: Command failed with error -1: &apos;ns not found&apos; on server &amp;lt;ip&amp;gt;:27017. The full response is &lt;/p&gt;
{ &quot;ok&quot; : 0.0, &quot;errmsg&quot; : &quot;ns not found&quot; }
&lt;p&gt;	at com.mongodb.connection.ProtocolHelper.getCommandFailureException(ProtocolHelper.java:115)&lt;br/&gt;
	at com.mongodb.connection.CommandProtocol.execute(CommandProtocol.java:114)&lt;br/&gt;
	at com.mongodb.connection.WriteProtocolCommandEventSpecification.should deliver started and completed command events for split unacknowleded inserts(WriteProtocolCommandEventSpecification.groovy:145)&lt;/p&gt;



&lt;p&gt;ii) Following 6 testcases failed with error as shown&lt;br/&gt;
should continue writing on write error when an unordered unacknowledged inserts must be split&lt;br/&gt;
should execute split acknowledged inserts&lt;br/&gt;
should execute split unacknowledged inserts&lt;br/&gt;
should not report write errors on split unacknowledged inserts&lt;br/&gt;
should report write errors on split acknowledged inserts&lt;br/&gt;
should stop writing on write error when an ordered unacknowledged inserts must be split&lt;/p&gt;

&lt;p&gt;io.netty.util.internal.OutOfDirectMemoryError: failed to allocate 16777216 byte(s) of direct memory (used: 50367344, max: 67108864)&lt;br/&gt;
	at io.netty.util.internal.PlatformDependent.incrementMemoryCounter(PlatformDependent.java:624)&lt;br/&gt;
	at io.netty.util.internal.PlatformDependent.allocateDirectNoCleaner(PlatformDependent.java:578)&lt;br/&gt;
	at io.netty.buffer.UnpooledUnsafeNoCleanerDirectByteBuf.allocateDirect(UnpooledUnsafeNoCleanerDirectByteBuf.java:30)&lt;br/&gt;
	at io.netty.buffer.UnpooledUnsafeDirectByteBuf.&amp;lt;init&amp;gt;(UnpooledUnsafeDirectByteBuf.java:68)&lt;br/&gt;
	at io.netty.buffer.UnpooledUnsafeNoCleanerDirectByteBuf.&amp;lt;init&amp;gt;(UnpooledUnsafeNoCleanerDirectByteBuf.java:25)&lt;br/&gt;
	at io.netty.buffer.UnsafeByteBufUtil.newUnsafeDirectByteBuf(UnsafeByteBufUtil.java:625)&lt;br/&gt;
	at io.netty.buffer.PooledByteBufAllocator.newDirectBuffer(PooledByteBufAllocator.java:265)&lt;br/&gt;
	at io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:179)&lt;br/&gt;
	at io.netty.buffer.AbstractByteBufAllocator.buffer(AbstractByteBufAllocator.java:115)&lt;br/&gt;
	at com.mongodb.connection.netty.NettyStream.getBuffer(NettyStream.java:93)&lt;br/&gt;
	at com.mongodb.connection.InternalStreamConnection.getBuffer(InternalStreamConnection.java:514)&lt;br/&gt;
	at com.mongodb.connection.ByteBufferBsonOutput.getByteBufferAtIndex(ByteBufferBsonOutput.java:91)&lt;br/&gt;
	at com.mongodb.connection.ByteBufferBsonOutput.getCurrentByteBuffer(ByteBufferBsonOutput.java:86)&lt;br/&gt;
	at com.mongodb.connection.ByteBufferBsonOutput.writeBytes(ByteBufferBsonOutput.java:62)&lt;br/&gt;
	at org.bson.io.OutputBuffer.writeBytes(OutputBuffer.java:51)&lt;br/&gt;
	at org.bson.BsonBinaryWriter.doWriteBinaryData(BsonBinaryWriter.java:163)&lt;br/&gt;
	at org.bson.AbstractBsonWriter.writeBinaryData(AbstractBsonWriter.java:360)&lt;br/&gt;
	at org.bson.codecs.BsonBinaryCodec.encode(BsonBinaryCodec.java:31)&lt;br/&gt;
	at org.bson.codecs.BsonBinaryCodec.encode(BsonBinaryCodec.java:28)&lt;br/&gt;
	at org.bson.codecs.EncoderContext.encodeWithChildContext(EncoderContext.java:91)&lt;br/&gt;
	at org.bson.codecs.BsonDocumentCodec.writeValue(BsonDocumentCodec.java:136)&lt;br/&gt;
	at org.bson.codecs.BsonDocumentCodec.encode(BsonDocumentCodec.java:115)&lt;br/&gt;
	at org.bson.codecs.BsonDocumentCodec.encode(BsonDocumentCodec.java:41)&lt;br/&gt;
	at com.mongodb.connection.RequestMessage.addDocument(RequestMessage.java:253)&lt;br/&gt;
	at com.mongodb.connection.RequestMessage.addCollectibleDocument(RequestMessage.java:219)&lt;br/&gt;
	at com.mongodb.connection.InsertMessage.encodeMessageBodyWithMetadata(InsertMessage.java:73)&lt;br/&gt;
	at com.mongodb.connection.RequestMessage.encodeWithMetadata(RequestMessage.java:160)&lt;br/&gt;
	at com.mongodb.connection.WriteProtocol.execute(WriteProtocol.java:89)&lt;br/&gt;
	at com.mongodb.connection.InsertProtocol.execute(InsertProtocol.java:68)&lt;br/&gt;
	at com.mongodb.connection.InsertProtocol.execute(InsertProtocol.java:39)&lt;br/&gt;
	at com.mongodb.connection.ProtocolTestHelper.execute(ProtocolTestHelper.java:31)&lt;br/&gt;
	at com.mongodb.connection.WriteProtocolSpecification.should continue writing on write error when an unordered unacknowledged inserts must be split(WriteProtocolSpecification.groovy:201)&lt;/p&gt;

&lt;p&gt;java.lang.ClassCastException: io.netty.util.internal.OutOfDirectMemoryError incompatible with java.lang.RuntimeException&lt;br/&gt;
	at com.mongodb.async.FutureResultCallback.get(FutureResultCallback.java:77)&lt;br/&gt;
	at com.mongodb.connection.ProtocolTestHelper.execute(ProtocolTestHelper.java:29)&lt;br/&gt;
	at com.mongodb.connection.WriteProtocolSpecification.should continue writing on write error when an unordered unacknowledged inserts must be split(WriteProtocolSpecification.groovy:201)&lt;/p&gt;


&lt;p&gt;Initially I used to get test search not found error, solved after mongodb server started with text search enabled.&lt;/p&gt;


&lt;p&gt;Regards,&lt;/p&gt;

&lt;p&gt;Hadi&lt;/p&gt;

</description>
                <environment></environment>
        <key id="338714">JAVA-2408</key>
            <summary>java-mongodb-driver test case failure</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="5">Cannot Reproduce</resolution>
                                        <assignee username="ross@mongodb.com">Ross Lawley</assignee>
                                    <reporter username="ravi_ss">ravi_ss</reporter>
                        <labels>
                    </labels>
                <created>Wed, 14 Dec 2016 06:23:56 +0000</created>
                <updated>Mon, 18 Sep 2017 13:49:56 +0000</updated>
                            <resolved>Mon, 18 Sep 2017 13:49:56 +0000</resolved>
                                                                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="1675297" author="ross@10gen.com" created="Mon, 18 Sep 2017 13:49:56 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ravi_ss&quot; class=&quot;user-hover&quot; rel=&quot;ravi_ss&quot;&gt;ravi_ss&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;We have been unable to reproduce the errors and as such we&apos;re closing this ticket as &quot;Cannot Reproduce&quot;.  We&apos;ve been unable to identify a probable cause, so at this time have no way of taking this ticket forward.&lt;/p&gt;

&lt;p&gt;If you are able to provide any new information or insight we&apos;ll happily reopen this ticket and investigate further.&lt;/p&gt;

&lt;p&gt;Ross&lt;/p&gt;</comment>
                            <comment id="1472390" author="ross@10gen.com" created="Mon, 9 Jan 2017 11:24:42 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ravi_ss&quot; class=&quot;user-hover&quot; rel=&quot;ravi_ss&quot;&gt;ravi_ss&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;I&apos;ve not been able to reproduce the issue locally or via our test machines.  &lt;/p&gt;

&lt;p&gt;At the moment I&apos;m blocked on this issue until I can either reproduce locally or on a test machine.&lt;/p&gt;

&lt;p&gt;Ross&lt;/p&gt;</comment>
                            <comment id="1462853" author="ravi_ss" created="Wed, 21 Dec 2016 05:54:43 +0000"  >&lt;p&gt;Hi Ross,&lt;br/&gt;
Any updates on this issue&lt;/p&gt;

&lt;p&gt;Ravi_SS&lt;/p&gt;</comment>
                            <comment id="1459708" author="ravi_ss" created="Fri, 16 Dec 2016 11:33:32 +0000"  >&lt;p&gt;Hi,&lt;br/&gt;
I have uploaded logs which were executed with -Dio.netty.leakDetection.level=advanced flag and also the mogodb server log&lt;/p&gt;

&lt;p&gt;Thanks &amp;amp; regards,&lt;br/&gt;
Ravi_SS&lt;/p&gt;</comment>
                            <comment id="1459690" author="ross@10gen.com" created="Fri, 16 Dec 2016 10:11:32 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ravi_ss&quot; class=&quot;user-hover&quot; rel=&quot;ravi_ss&quot;&gt;ravi_ss&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;Many thanks for all your help with trying to debug this issue, unfortunately, I&apos;m still no closer to identifying the cause as I&apos;m not able to replicate the failures locally, on travis or on our own CI servers.&lt;/p&gt;

&lt;p&gt;Could you run the tests with extra netty leak detection on by passing the command line flag: &lt;tt&gt;-Dio.netty.leakDetection.level=advanced&lt;/tt&gt; and attach the logs to the ticket.  Could you also provide the MongoD logs for the duration of the test.  &lt;/p&gt;

&lt;p&gt;Perhaps that will help shed more light on the cause for the failures.&lt;/p&gt;

&lt;p&gt;Ross&lt;/p&gt;</comment>
                            <comment id="1459635" author="ravi_ss" created="Fri, 16 Dec 2016 05:57:10 +0000"  >&lt;p&gt;Hi Ross,&lt;/p&gt;

&lt;p&gt;I am using netty 4.1.5.Final, Also I have tried with 4.1.6.Final facing the same issue.&lt;/p&gt;

&lt;p&gt;Thanks &amp;amp; regards,&lt;br/&gt;
Ravi_SS&lt;/p&gt;</comment>
                            <comment id="1458803" author="ross@10gen.com" created="Thu, 15 Dec 2016 12:40:28 +0000"  >&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;My apologies, I misread the clirr baseline version to be the driver version.  Could you confirm the version of netty you are using? Travis is running against 4.1.5.Final without any memory leaks.&lt;/p&gt;

&lt;p&gt;The &apos;ns not found&apos; errors in the &lt;tt&gt;WriteProtocolCommandEventSpecification&lt;/tt&gt; looks to be a race condition in the test when calling the cleanup.&lt;/p&gt;

&lt;p&gt;Ross&lt;/p&gt;</comment>
                            <comment id="1458793" author="ravi_ss" created="Thu, 15 Dec 2016 12:08:33 +0000"  >&lt;p&gt;Hi,&lt;br/&gt;
I have build the java mongodb version:r3.4.0&lt;br/&gt;
mongo-java-driver]$ git branch&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;(detached from r3.4.0)&lt;br/&gt;
  master&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;the mongodb server is&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;./mongod --version&lt;br/&gt;
db version v2.4.9-rc0&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;I can see the similar log in &lt;a href=&quot;https://travis-ci.org/mongodb/mongo-java-driver/jobs/183972445&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://travis-ci.org/mongodb/mongo-java-driver/jobs/183972445&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Thanks &amp;amp; regards,&lt;br/&gt;
Ravi_SS&lt;/p&gt;</comment>
                            <comment id="1458778" author="ross@10gen.com" created="Thu, 15 Dec 2016 11:58:50 +0000"  >&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;Could it be running against the driver version 3.2.0? I&apos;m seeing the following in the logs:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;All projects evaluated.&lt;br/&gt;
bson: baseline has been set to org.mongodb:bson:3.2.0&lt;br/&gt;
driver: baseline has been set to org.mongodb:mongodb-driver:3.2.0&lt;br/&gt;
driver-async: baseline has been set to org.mongodb:mongodb-driver-async:3.2.0&lt;br/&gt;
driver-core: baseline has been set to org.mongodb:mongodb-driver-core:3.2.0&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;There have been over &lt;a href=&quot;https://jira.mongodb.org/issues/?jql=project%20%3D%20JAVA%20AND%20issuetype%20%3D%20BUG%20AND%20fixVersion%20%3E%203.2.0%20and%20fixVersion%20%3C%203.4.1&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;50 bugfixes&lt;/a&gt; since version 3.2.0.  Including &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-2302&quot; title=&quot;Memory leak on Java async driver + Netty 4.1.x&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-2302&quot;&gt;&lt;del&gt;JAVA-2302&lt;/del&gt;&lt;/a&gt;, which is a fix for a memory leak with netty 4.1 and a warning for a leak can be observed in your tests.&lt;/p&gt;

&lt;p&gt;Ross&lt;/p&gt;</comment>
                            <comment id="1458776" author="ravi_ss" created="Thu, 15 Dec 2016 11:46:16 +0000"  >&lt;p&gt;Hi Ross,&lt;br/&gt;
I have built the latest version r3.4.0.&lt;/p&gt;

&lt;p&gt;sorry for that,&lt;/p&gt;

&lt;p&gt;Regards,&lt;br/&gt;
Ravi_SS&lt;/p&gt;</comment>
                            <comment id="1458775" author="ross@10gen.com" created="Thu, 15 Dec 2016 11:44:36 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ravi_ss&quot; class=&quot;user-hover&quot; rel=&quot;ravi_ss&quot;&gt;ravi_ss&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;Can you confirm the version of the driver is r3.0.4 ?  The test logs show a test in the  &lt;tt&gt;WriteProtocolCommandEventSpecification&lt;/tt&gt; is failing but that test case wasn&apos;t present in version 3.0.4 of the driver.&lt;/p&gt;

&lt;p&gt;Ross&lt;/p&gt;</comment>
                            <comment id="1458769" author="ravi_ss" created="Thu, 15 Dec 2016 11:21:33 +0000"  >&lt;p&gt;Hi Ross,&lt;br/&gt;
Thank you for your response,&lt;br/&gt;
I have built mongodb-driver for r3.0.4 version&lt;br/&gt;
platform s390x system&lt;br/&gt;
running the mongodb on remote server version 2.4, single node&lt;/p&gt;

&lt;p&gt;Attached the logs of first and second run, &lt;br/&gt;
Increased the memory available for jdk by &lt;br/&gt;
export GRADLE_OPTS=-XX:MaxDirectMemorySize=10g&lt;/p&gt;

&lt;p&gt;Thanks &amp;amp; regards,&lt;br/&gt;
Ravi_SS&lt;/p&gt;</comment>
                            <comment id="1458767" author="ross@10gen.com" created="Thu, 15 Dec 2016 11:20:22 +0000"  >&lt;p&gt;Thanks for that @ravi_ss,&lt;/p&gt;

&lt;p&gt;Can you provide the other information to help shed more light on the cause:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;What *driver version *are you running the tests on? The master branch or a tagged version?&lt;/li&gt;
	&lt;li&gt;What &lt;b&gt;platform&lt;/b&gt; are you running it on?&lt;/li&gt;
	&lt;li&gt;What &lt;b&gt;version&lt;/b&gt; of MongoDB are you running?&lt;/li&gt;
	&lt;li&gt;What &lt;b&gt;topology&lt;/b&gt; are you running? single node, replicaSet, sharded cluster, sharded cluster with replicaSets&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Ross&lt;/p&gt;</comment>
                            <comment id="1458750" author="ravi_ss" created="Thu, 15 Dec 2016 10:54:53 +0000"  >&lt;p&gt;Attached the logs of first and second run, &lt;br/&gt;
Increased the memory available for jdk by &lt;br/&gt;
export GRADLE_OPTS=-XX:MaxDirectMemorySize=10g&lt;/p&gt;</comment>
                            <comment id="1457253" author="ross@10gen.com" created="Wed, 14 Dec 2016 10:41:23 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ravi_ss&quot; class=&quot;user-hover&quot; rel=&quot;ravi_ss&quot;&gt;ravi_ss&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;Thanks for the ticket - you are correct the text search must be enabled for the test suite. Errors aren&apos;t expected when running the tests, we have a comprehensive continuous integration suite that runs the tests over various configurations.  As such I have a few questions to help diagnose the cause:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;What driver version are you running the tests on? The Master branch or a tagged version?&lt;/li&gt;
	&lt;li&gt;What platform are you running it on?&lt;/li&gt;
	&lt;li&gt;What version of MongoDB are you running?&lt;/li&gt;
	&lt;li&gt;What topology are you running? single node, replicaSet, sharded cluster, sharded cluster with replicaSets&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Can you attach logs from the whole test suite?  I would like to see where Spock errors when reporting the &lt;tt&gt;&apos;ns not found&apos;&lt;/tt&gt; issues.&lt;/p&gt;

&lt;p&gt;The out of memory issues indicate you may need to increase the memory available to your JDK - you can pass the &lt;tt&gt;-XX:MaxDirectMemorySize=&lt;/tt&gt; flag in the command line.&lt;/p&gt;

&lt;p&gt;Ross&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                                        </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="146206" name="log_mongodbServer.txt" size="815647" author="ravi_ss" created="Fri, 16 Dec 2016 11:30:25 +0000"/>
                            <attachment id="146074" name="log_run1.txt" size="1579767" author="ravi_ss" created="Thu, 15 Dec 2016 10:53:33 +0000"/>
                            <attachment id="146073" name="log_run2.txt" size="801542" author="ravi_ss" created="Thu, 15 Dec 2016 10:53:30 +0000"/>
                            <attachment id="146205" name="log_withLeakDetect.txt" size="1554598" author="ravi_ss" created="Fri, 16 Dec 2016 11:30:27 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hssuwv:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>