|
From: Ebtehal H. <h.e...@ya...> - 2014-09-17 11:03:40
|
Thanks Tomas it was sloved ________________________________ From: Tomas Gustavsson <to...@pr...> To: ejb...@li... Sent: Wednesday, 17 September 2014, 3:05:49 Subject: Re: [Ejbca-develop] Stress Test You need to uncheck "enforce unique public keys" for the CA. Cheers, Tomas On 2014-09-17 08:38, Ebtehal Hassan wrote: > Hello, > I want make stress test for CA in EJBCA v. 6.2.0 but it can be issued > just 1 certificate & after that the JBOSS was get some error > the command to stress test > Now the stress test show some result: > > > Server@ca2:/opt/ejbca/dist/clientToolBox$ ./ejbcaClientToolBox.sh > EjbcaWsRaCli stress AdminCA > Test client started, tail info and error files in this directory for output. > Statistic will be written to standard output each 10 second. > The test was started at Thu Sep 14 20:03:33 CEST 2011.008332292 > A test key for each thread is generated. This could take some time if > you have specified many threads and long keys. > Total # of successfully performed tests: 1 > Total # of failed tests: 30 > # of tests completed each second: 0.1 > # of tests completed each second in last period: 0.1 > Relative average time for different tasks (all should sum up to 1): > Relative time spent registring new users: 0.4267 > Relative time spent signing certificates: 0.0395 > Time spent with test client work: 0.5338 > Absolute extremes: > Min time for job 'Relative time spent registring new users' (ms): 114 > (Thu Sep 14 20:03:42 CEST 2011) > Max time per job 'Relative time spent registring new users' (ms): 186 > (Thu Sep 14 20:03:33 CEST 2011) > Min time for job 'Relative time spent signing certificates' (ms): 395 > (Thu Sep 14 20:03:34 CEST 2011) > Max time per job 'Relative time spent signing certificates' (ms): 395 > (Thu Sep 14 20:03:34 CEST 2011) > > > In th JBOSS log i see this: > Thu Sep 14 20:04:01 CEST 2011 : Command failure. Class > 'org.ejbca.core.protocol.ws.client.StressTestCommand.Pkcs10RequestCommand' > with this job data: Username 'WSTESTUSER-5377453774162515311' with > password 'foo123'. > org.ejbca.core.protocol.ws.client.gen.EjbcaException_Exception: User > 'WSTESTUSER-5377453774162515311' is not allowed to use same key as the > user(s) 'WSTESTUSER8587251972754523283' is/are using. > at > sun.reflect.GeneratedConstructorAccessor42.newInstance(Unknown Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:532) > at > com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:130) > at > com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108) > at > com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78) > at > com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107) > at $Proxy27.pkcs10Request(Unknown Source) > > > > Please help me to solve the problem > > > Best Regards; > Ebtehal Hassan > > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > > > > _______________________________________________ > Ejbca-develop mailing list > Ejb...@li... > https://lists.sourceforge.net/lists/listinfo/ejbca-develop > ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Ejbca-develop mailing list Ejb...@li... https://lists.sourceforge.net/lists/listinfo/ejbca-develop |