|
From: Leif M. <le...@ta...> - 2009-07-17 04:57:16
|
Hi, What you are trying to do should be possible. I was not clear however where the error is being encountered. Is it when the JVM is being launched? Or within your application? Could you please reply with your wrapper.conf, the contents of your wrapper.log as well as the policy file you are using. Cheers, Leif On Fri, Jul 17, 2009 at 8:06 AM, <dp...@ro...> wrote: > > > I have the following situation on a server, and I"m hoping there is a way > to accomplish this with the wrapper.conf file. > > This server has 1 install of Java, and several JVMs running. I need to > add to this server a new JVM, running under the control of a wrapper. The > other JVMs require standard SSL support, and the java.security file > specifies the standard ssl.socketfactory.provider= and > ssl.serversocketfactory.provider= > > This new JVM requires a custom ssl.socketfactory.provider and > ssl.serversocketfactory.provider and the custom ones, are not suitable for > the other JVMs on this server. > > I tried adding to the java.policy file that I specify in the wrapper.conf > ssl.socketfactory.provider=custom > ssl.serversocketfactory.provider=custom > > but the JVM does not start, giving a syntax error saying it expected ";" > but found 'ssl.socketfactory.provider'. > > > Thanks for any help |