JON server fails to start with Invalid authentication attempt, principal=null

Issue

• Our JON Server is failing to start in our QA environment

• The rhq-server-log4j.log contains the following warning:

   WARN  [org.jboss.system.ServiceController] Problem starting service jboss.mq:service=PersistenceManager
  org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions.  Message recovery may not be accurate; - nested throwable: (java.lang.SecurityException: Invalid authentication attempt, principal=null)
      at org.jboss.mq.pm.jdbc2.PersistenceManager.resolveAllUncommitedTXs(PersistenceManager.java:489)
      at org.jboss.mq.pm.jdbc2.PersistenceManager.startService(PersistenceManager.java:1842)
      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
  

• Followed by the below error:

  ERROR [org.rhq.jbossatx.jta.recovery.AppServerJDBCXARecovery] AppServerJDBCXARecovery.createDataSource got exception java.lang.NumberFormatException: For input string: "J"
  java.lang.NumberFormatException: For input string: "J"
      at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
      at java.lang.Integer.parseInt(Integer.java:447)...