OK that was with the inprise jdk. I had to switch back to blackdown because the
Inprise jdk was core dumping on me. Now I'm getting the same 'invalid message
hash' ServerException with Blackdown and I can't fix it no matter what I do with
my policy file.
[EMAIL PROTECTED] wrote:
> They were in
I have no idea why the security mechanism was changed. All I can tell
you is that I had the same problem with RMI stuff (on Solaris, even)
until I both gave all permissions to jre/lib/ext codebase AND created a
.java.policy file in my home directory which was identical to the
default java.policy f
At 21:59 12/18/99 -0700, Jeff Galyan wrote:
>Actually, that makes sense. Java 2 has a different security structure
>than previous releases. If you took away permissions from the jre libs,
>then you'd get that error.
That error makes sense to you because of security being restriced?
HUH? in 1.1 t
[EMAIL PROTECTED] wrote:
>
> They were in sync. I discovered I got the same message after I killed the
> server! I had been playing with my policy file before, and I had removed
> the allpermission that had been granted to jdkhome/lib/ext. When I put
> that back all my problems went away. The
They were in sync. I discovered I got the same message after I killed the
server! I had been playing with my policy file before, and I had removed
the allpermission that had been granted to jdkhome/lib/ext. When I put
that back all my problems went away. The permission thing seems real
screwy
it means the method you were calling has somehow changed since the
server's _Skel class was compiled. I know you said they're in sink,
but verify that the client and server both have the same version of
the interface, the impl, the _Stub and the _Skel classes... also
verify that the _Stub and _Ske
