I just double checked oak-segment-tar v1.22.9 that's available on the central maven repository. It uses netty v4.1.66 which contains the bug. Attaching a screenshot here for your reference. I'd recommend trying oak-segment-tar v1.24.0. In the meantime you could create an adobe support ticket if you...

Hello there,As mentioned earlier on this thread, the bug resides in a third party library called netty that oak-segment-tar uses. Note that this bug was fixed in netty version 4.1.68. Ensure that whatever version of oak-segment-tar you're using incorporates a non faulty version of netty. netty versi...

We noticed the exact same error this morning!! I'm so relieved that at least I can see a relevant error. It was frustrating having to just monitor things with no luck. Also, I created two fresh AEM 6.5 instances and setting up this connection between the two was a breeze, so that confirms that the s...

@milind_bachani yes we had already upgraded to 6.5.11.0 using the service pack, hence we can rule out the possibility of it being a service pack related issue. 

Update: I did some more digging and realised I have all the right configurations in place. The TCP port '8088' (This is the one we're using instead of the default 8023) on primary is active and listening. However, the standby isn't able to establish a connection with it. I tried using curl commands ...

Hey @Pavan_Kalyan . Unfortunately, I haven't had any luck resolving it. I did follow every step as mentioned here. My last resort is to try and remove all the old config files on the primary instance, set up new configuration files and then derive a standby instance from it. I'm going to try it in a...

Hello there,As part of our 6.5 upgrade, we've decided to derive a standby instance from the primary author instance. I've thoroughly followed the steps mentioned in the official adobe documentation. However, when I goto the JMX console on the primary author, It says 'channel unregistered'. Whereas, ...