Error:failed to create session - UNAVAILABLE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-10-18 12:28 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-10-18 01:56 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-10-18 03:29 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-10-18 10:38 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
27-10-18 11:13 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
31-08-20 08:24 PM
Hello John,
I have similar master-slave case where invoking the slave process on same resource with AutomateC, but also, I have all the objects run mode as Background and the concurrency limit is 20. And during this there is no other process running on the cluster (This is single resource setup I'm using to recreate the client's issue).
Adding to above, this issue started appearing only after upgrade to v6.8. Till v6.6 we didn't encounter this issue unless there was a pending session on the vm or an object running in Foreground/Exclusive mode blocking the session creation.
Could you please suggest how I can solve this.
Thanks
------------------------------
Pramod Bhade
Application Developer
IBM GBS
Asia/Kolkata
------------------------------
