We're working on updating some really old JMS drivers we have to work
with EMS and as such have started by using the JMS-TIBCO template in the
IDM 3.6.1 install. After migrating over all of our pub/sub policies,
the problem we have is that we're getting this message during startup:

769611520 DVRS: [2012/09/07 17:00:24.906] EMSTest
ST:java.lang.IllegalStateException: Unable to decode base64-encoded GUID
'[encrypted]'. java.io.StreamCorruptedException: Miscalculated data
length! index = 6, out.length = 9

which then leads to this:

692111104 DVRS: [2012/09/07 17:00:24.959] EMSTest
PT:java.lang.IllegalStateException: Unable to obtain one or more Driver,
Subscriber, or Publisher GUIDs. The likely cause is policy
interference. Please double-check your policies to ensure they do not
inadevertently block XDS queries or XDS query responses.

and shuts down the driver.

I haven't been able to come up with anything while searching that
explains what that error means (aside from the obvious literal
translation) and what I'm supposed to do in order to fix it. Since I
can start the driver without any policies assigned, I'm assuming it's
something that isn't coming over correctly from the old JMS driver, or
that isn't being handled correctly. If I pull out the subscriber
policies, it seems to start OK, so there's probably something within
those policies that's not playing nicely. I'm just not sure where to
start looking. The driver does have the necessary rights to itself and
the tree, so I don't think it's an issue of it not being able to find
it. We're running this on SLES11.1 64bit (non-OES) using eDir
64bit and IDM 3.6.1a. Thanks!

infinity9999's Profile: https://forums.netiq.com/member.php?userid=1343
View this thread: https://forums.netiq.com/showthread.php?t=2977