On 7/14/06, Sunitha Kambhampati <[EMAIL PROTECTED]> wrote:
Francois Orsini (JIRA) wrote:
>So for now, USRSSBPWD is no longer the default after EUSRIDPWD in the client
until DERBY-926 is fixed or a temporary handling of the protocol exception
reported as in DERBY-926 is duoable in Derby's client driver.
>
>
I thought DERBY-926 was a server issue. Is that not the case ?
Hi Sunitha,
Yes it is - I meant to say that the DRDA protocol exception is
documented in DERBY-926 and that eventhough this bug has to be fixed
on the server side, it would be good to try and parse in the network
client, the list of SECMEC(s) returned by older servers which won't
have the fix to DERBY-926, even when this last one is fixed. I have
entered DERBY-1517 for that and was hoping to be able to parse the
current and incorrectly formatted list of SECMEC(s) returned, instead
of getting a DRDA protocol exception raised when a securityMechanism
is sent to a server which does not support it...
Cheers,
--francois
Thanks,
Sunitha.
