diff --git a/src/org/zaproxy/zap/extension/dynssl/ExtensionDynSSL.java b/src/org/zaproxy/zap/extension/dynssl/ExtensionDynSSL.java
index <HASH>..<HASH> 100644
--- a/src/org/zaproxy/zap/extension/dynssl/ExtensionDynSSL.java
+++ b/src/org/zaproxy/zap/extension/dynssl/ExtensionDynSSL.java
@@ -73,7 +73,7 @@ public class ExtensionDynSSL extends ExtensionAdaptor {
                     try {

                         createNewRootCa();

                     } catch (Exception e) {

-                        logger.error(e.getMessage(), e);

+                        logger.error("Failed to create new root CA certificate:", e);

                     }

                 }

             }).start();

@@ -92,10 +92,11 @@ public class ExtensionDynSSL extends ExtensionAdaptor {
 	}

 	

 	public void createNewRootCa() throws NoSuchAlgorithmException, UnrecoverableKeyException, KeyStoreException {

-		logger.info("Creating new root CA");

+		logger.info("Creating new root CA certificate");

 		KeyStore newrootca = SslCertificateUtils.createRootCA();

 		setRootCa(newrootca);

 		getParams().setRootca(newrootca);

+		logger.info("New root CA certificate created");

 	}

 

 	private DynamicSSLPanel getOptionsPanel() {
Log that the root CA certificate was created

The creation of root CA certificate, if successful, just logs "Creating
new root CA", which is very misleading giving the impression that ZAP
hanged, as reported in #<I>.
With the change it always logs something either that it was created or,
if something went wrong, the exception.
Tweak existing log messages to include "certificate", also change log of
the exception to explicitly say that the creation of root CA certificate
failed.