# RSS Feed ContainerException: Unknown namedPipeline JaxrsRestFeedPipeline

**URL:** <https://community.bloomreach.com/t/rss-feed-containerexception-unknown-namedpipeline-jaxrsrestfeedpipeline/1731>\
**Category:** Experience Manager (PaaS/OnPrem)\
**Created:** [February 6, 2020, 9:40am UTC](https://community.bloomreach.com/t/rss-feed-containerexception-unknown-namedpipeline-jaxrsrestfeedpipeline/1731 "2020-02-06T09:40:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![katie](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/katie/32/1479_2.png) [@katie](https://community.bloomreach.com/u/katie)\
**Post date:** [February 6, 2020, 9:40am UTC](https://community.bloomreach.com/t/rss-feed-containerexception-unknown-namedpipeline-jaxrsrestfeedpipeline/1731/1 "2020-02-06T09:40:43Z")

</div>

We’re getting the following exception having followed the instructions to install the RSS Feed:

`ContainerException for 'Request{ method='GET', scheme='http', host='localhost:8080', requestURI='/site/feed/syndication/rss.xml', queryString='null'}': org.hippoecm.hst.core.container.ContainerException: Unknown namedPipeline JaxrsRestFeedPipeline. Request processing cannot continue.`

We did a spike a while back and it worked fine, but now we wish to implement it we can’t get it working and I’m wondering if something changes with the class JaxrsRestFeedPipeline for v5.x of the plugin which has stopped it working for v4.0.1?

We’re using v12.6.3 of Bloomreach so followed the instructions here: [https://htmlpreview.github.io/?https://github.com/bloomreach-forge/feeds/blob/feed-4.0.1/docs/install.html](https://htmlpreview.github.io/?https://github.com/bloomreach-forge/feeds/blob/feed-4.0.1/docs/install.html)  
[https://htmlpreview.github.io/?https://github.com/bloomreach-forge/feeds/blob/feed-4.0.1/docs/usage.html](https://htmlpreview.github.io/?https://github.com/bloomreach-forge/feeds/blob/feed-4.0.1/docs/usage.html)  
To ensure I’m using the correct documentation for the version compatible with v12.x of Bloomreach (v4.0.1 of the feed plugin)

Here are some screenshots of the config:  
 ![Screen Shot 2020-02-04 at 14.54.25](https://canada1.discourse-cdn.com/flex027/uploads/bloomreach1/original/1X/08f6a87eb43d1bbe9d68bb541cb1a6908176e6bc.png)

 ![Screen Shot 2020-02-04 at 14.54.49](https://canada1.discourse-cdn.com/flex027/uploads/bloomreach1/original/1X/843f71c8732ca8dda3a4e0a3729097dcaa4d038b.png)

 ![Screen Shot 2020-02-04 at 14.55.41](https://canada1.discourse-cdn.com/flex027/uploads/bloomreach1/original/1X/c2eba5d4ca173ae701ec9de5e06f9031c130cbba.png)

---

<div class="post-metadata">

**Author:** ![katie](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/katie/32/1479_2.png) [@katie](https://community.bloomreach.com/u/katie)\
**Post date:** [February 7, 2020, 11:33am UTC](https://community.bloomreach.com/t/rss-feed-containerexception-unknown-namedpipeline-jaxrsrestfeedpipeline/1731/2 "2020-02-07T11:33:22Z")

</div>

UPDATE!

My colleague ran through the instructions from scratch but with the latest instructions [https://bloomreach-forge.github.io/feeds/install.html](https://bloomreach-forge.github.io/feeds/install.html) (having done it once before and seeing the same problem) and it appears to be working 🤷‍♀️.

We wonder if it’s a bootstrapping issue so that once it’s caused an issue, the problem is retained as comparing the versions of code (and updating my install to match exactly) maintains the issue.

---

<div class="post-metadata">

**Author:** ![jasper.floor](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/jasper.floor/32/28_2.png) [@jasper.floor](https://community.bloomreach.com/u/jasper.floor)\
**Post date:** [February 7, 2020, 12:14pm UTC](https://community.bloomreach.com/t/rss-feed-containerexception-unknown-namedpipeline-jaxrsrestfeedpipeline/1731/3 "2020-02-07T12:14:38Z")

</div>

The pipeline should be loaded by spring, so it’s not a bootstrap error I think. Check your logs as tomcat is starting for any errors there. Also check if you have any dependency version issues.