Hi Claudio, On Fri, 12 Apr 2002, Vesco Claudio wrote:
> Now I have completed the testsuite with some patches to iiop tests. You have > reason that the problems are in client.policy, but you can test the iiop > only with (in testsuite): > > ./build.bat -Dtest=<test> iiop-test > > which in windows does not function (ant is called with "ant -Dtest <test> > iiop-test", the "=" is lost in hyperspace :-( ) > > If I remember well, I think this is the only mode which permits to set the > java.security.manager and java.security.policy properties. > > So, I have integrated the iiop tests in a new target, > tests-standard-stress-iiop, which invokes the tests and sets the properties. Sounds good. > With this new target, I have obtained that the iiop testsuite run but some > tests fail with a timeout error (junit error). When I have this timeout > error successive calls to jboss with corba fail and jboss does not go in > shutdown :-((( I don't get this error... I wonder what might be different in my environment... > I think that you have a security policy file in path (Have you tested with > jdk 1.4? And have you tested with jdk 1.4 in windows?) I removed my .java.policy... Yes, I tested with jdk 1.4, but only on Linux. > I have another question, when I allocate the ORB I have a warning (no > properties file found) by jacorb, I haven't problems with my test bed in > jython. > I think that at least for the server part (jboss server) we need this file > in the iiop sar. You can safely ignore this warning at the server side, as the relevant info JacORB would get from a .jacorb.properties file is already being explicitly passed to the ORB.init() call. But maybe we should have a dummy properties file just to prevent JacORB from complaining. Cheers, Francisco _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
