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

Solution Verified - Updated -

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)...
    

Environment

  • JBoss Operations Network(JON) 2.4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.