Hi,I hope the issue is resolved till now but if not try to use PDB instead of CDB in the connection string, Note: Even if it is possible, it is not allowed to install IFS Cloud in the CDB and there are no warnings in the IFS Installer Tool if you try to do this. You must always install IFS Cloud in the PDB.
Thanks :)
Thanks Zapior, Print agent is working fine no error in logs also it suddenly stopped working nothing has been changed from IFS side.We have Netscalar configured for application URL and on which batch is running, Batch is not able communicating with URL. Thanks,Anshul
Thanks William for the quick reply.Restart just like you suggested but it’s not working also tried to delete old print job but no luck.Still the same issue. Regards,Anshul
Thanks for the Quick Reply,Yes I have checked all services are up and running,Server and application status are good.Regarding Reconfiguration it’s a production environment we are avoiding it as of now. Regards,Anshul
You can try below things, Make sure that the dedicated session timeout is set properly in both Managed Servers. Mind you that if you perform a reconfiguration and changed the dedicated session timeout then you need to recreate the cluster to make it visible to the cluster node. You can also bypass the LB and connect directly to MWS and verify whether the issue still exists. This will help to eliminate any timeout in the LB. You have to change your connection URL in the login dialogue for this test. If there’s no luck then try to shut down one Managed Server and see the difference. PS: I assume that you have not enabled heartbeat and you do not have a DB RAC. Hi Tharindu, Thanks for your response. We have dedicated session timeout is set for 90 Min. and both manager server are in sync. While doing the testing without LB we are not getting the error but it is taking time to complete. We don’t have DB RAC also no heartbeat. Can you tell me what can we check on NetScalar(LB) ?
Thanks Srikanth for your quick response. I have check all the logs of Database and Application but didn’t find this warning/error on Logs which resembles to this issue. We are facing this issue across different environments eg: Test, Dev etc... Also we are using IFS MWS as middle server. Regards, Anshul
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.