We are upgrading our application from 8.0.5.0 to 9.0.2.1 and we found that pagination is broken only in places.

Steps: 1. Navigate to any community landing page which has more than 20+ content items

2. Click on All content ( it should render 20items and pagination gets enabled for the next 20 list items)

Issue: For example, we have a community with 300+ content and the pagination is not showing up, also we could see only 10items when we hit the "All Content". This is happening only in our staging environment. It doesn't show up with customizations in my local setup or in developer environment (All these environments have same customizations and themes deployed.).. REST is broken with /places/{placeID}/contents only in staging, I am trying to get some help through the source code, but no clue why its breaking ?

Do you have pointers why REST is broken with my staging instance ? and not with my developer/local instance which has exactly the same customizations as staging..

example: I have a community with 14 contents and through rest api endpoint.. /places/{placeID}/contents gives me only 10 contents. REST is broken.. since REST is broken with places in staging, the pagination is also broken, as the pagination is hitting the rest api for next 20 contents.

We've seen it with /api/core/v3/streams/XXXX/associations, but not with any of the other REST endpoints. The problem we saw with stream associations was logged as CUSTOM-1356, so you could check with Jive to see whether they got anywhere diagnosing the issue & whether it might affect more than just that area.

If you've got a any custom content types, maybe that's a factor in this issue?

You definitely need to raise this with your account manager if its affecting your upgrade from going live.

hey Matt, we are seeing this issue with or without customizations in staging(only in staging), its weird

We are not able to reproduce this issue in other environments, as Jive is gonna ask us how to reproduce the issue. I can't reproduce this on my personal mac local instance or my office laptop local instance, and also in our developer environment (with or without customizations).

staging is broken with following

pagination

-

/contents?filter=search(XXX) : is broken

/places?filter=search(XXXXXX) : is broken

/people/XXXXX/streams : New streams created are not appearing in the api endpoint ( /people/{id}/streams)

We started building our staging environment from scratch, if we still get the issue, we are gonna raise a sev1 case with jive.

We've seen it with /api/core/v3/streams/XXXX/associations, but not with any of the other REST endpoints. The problem we saw with stream associations was logged as CUSTOM-1356, so you could check with Jive to see whether they got anywhere diagnosing the issue & whether it might affect more than just that area.

In the meantime, I can't access CUSTOM-1356, as its a private case in your support group. Can you give me brief of the problem ?

We finally fixed this issue, we were using different JDBC drivers in developer and staging environments, and the one in staging has to have "fetchSizeSupported" property to be set to false, as its Oracle 12.

In oracle 12, its required to add a <fetchSizeSupported>false</> property to jive_startup.xml( which will bypass the count which by default is set to 10, and gets all the results).