Job Server Issues?

Since the element14 Community started on Azure, we have had to regularly restart jobs on the job server almost every day, sometimes now it's every 2 days, else it's every weekend.

I don't have development/admin setup access to know what kind of message bus we're using beyond using Microsoft Azure Message Bus.

We're fortunate that (when we have server admins available) we can ask them to restart it, but we have had to setup monitoring automations or tasks that automatically flag there's a problem and then restart the servers/tasks.

Even then it doesn't catch everything.

For Microsoft Azure I thought it may be related to 'batch interval' and 'prefetch count' as Verint doesn't advise on optimal values for these in the setup documentation, but if you read into Microsoft's documentation they mention having to change them depending on the scale of your setup of listeners and such (I believe we have 3 web nodes and one job server, that sounds like something scaled up to me). The values recommended from contacting support seem to relate to having one server, but I admit I'm not entirely certain on values or on this as it's not my day job but appears to be a recommendation oversight.

I'd wonder what other's server setups/configurations are and if they're running on Azure or setup otherwise, more details may help present if it's a platform agnostic problem or if it is a problem of scale of server infrastructure or configuration, or sheer amount of content. The element14 Community has some 10+years of blog posts, wiki articles, forum posts, etc. We have tens of thousands of articles of content.

But ultimately, yes we have same/similar issues, and it's hurting our userbase.

Though I just realised this is posted in the v12 'ask the community' and we're on v11.

Hi Christopher, 

No worries. I was having Job Server issues on 11 as well.

And now we've upgraded to v12 we've still got issues with the job server.

And now we've upgraded to v12 we've still got issues with the job server.

Hi Matt, 

Same. We still can't run the Socket Message Bus and had to revert to the Data Message bus, which has it's own limitations.

Fyi, since we're running natively (as PaaS) in Azure, we're using the Azure Message Bus, not the Socket Message Bus... and yet still get issues with the job server.

My understanding is the Azure Message Bus and Socket Message Bus run similarly, where as the Data Message Bus retains the list of messages and eventually parses through them when the jobs server is ready to do so, but the other two types are essentially 'lossy' and drop messages/timeout.

 Rachel Jackson , on your Verint Community platform, do you have any custom widgets or extensions installed from the marketplace or otherwise developed? Or are you entirely using an out of the box solution with?

I'm wondering if there're any similarities between our platforms in this regard and may hint at a common cause.

Christopher G. Stanton For the most part we are out of the box. I installed the Unanswered Threads automation while we were on 11 and we have a handful of custom widgets, but I believe we've been having issues with the Job Servers since day 1. 

And when I say custom widgets, I believe all that was changed was font, color, etc. Nothing major. 

Thanks, that is both reassuring and not at the same time - reassuring that it's unlikely to be a problem with our customisations, but also that it's evidently a problem that's core to the platform.