Wondering if anyone has yet validated ther new Server side security feature introduced since DOORS 9.4.
Have been trying to setup this feature and always ending up with the DB situation from which cannot be started again.
The secure mode works with custom certificates, however the server never starts when trying to use the arguments for "-serversecurityenable" along with our standard parameters.
After this even the -serversecuritydisable never works and the DB instance can never be used.
...
...
...
09/18/12 17:02:37 (PID 25433): IPC failure: ipcClientSocket(127.0.0.1:44099.5): connect() failed; Connection refused
09/18/12 17:02:37 (PID 25433): starting server on XXXXX via port XXXX
09/18/12 17:02:37 (PID 25433): Initialising message producer 'Server Side Security' (broker='tcp://doors10.rd.copintra.net:61616?socket.tcpNoDelay=true&wireFormat.maxInactivityDuration=0', channel='TLOGIC.INTEROP')
09/18/12 17:02:37 (PID 25433): A CMS exception occurred initialising a message producer: 'Success'
-
-
-
-
............
Please share your story if any.
regards
Baldeep
anandbaldeep - Wed Sep 19 09:32:47 EDT 2012 |