This content has been marked as final. Show 3 replies
The fact that bouncing EBS fixes the issue temporarily indicates that the problem is most likely on the EBS end, but we haven't encountered that specific issue. What OS are you using to host EBS? Are you purging the J2EE cache when you bounce the services?
Feel free to reach out to Anne or myself if you'd like to dive into this. We could test with an alternate content server to see if that helps isolate the problem.
We are hosting EBS with On Demand on Linux 64-bit. We are only bouncing apache and not purging any cache. Testing against another server is an option but will take a while to get all the required pots opened. Let me know if you have any further suggestions. We restarted services last sunday and it worked fine until today I am getting same error> 'Content server is not running'. Thanks