2 Replies Latest reply on May 6, 2016 5:13 PM by Adrian PECA

    Jboss EAP 6.4 Failed to performance blast: java.lang.IllegalArgumentException: Record is too large to store 131072

    Adrian PECA Newbie

      Hi Every body,

       

      Can you help me with this, issue

       

      17:05:30,701 ERROR [org.hornetq.journal] (hornetq-perfblast-thread) HQ144005: Failed to performance blast: java.lang.IllegalArgumentException: Record is too large to store 131072

        at org.hornetq.core.journal.impl.JournalImpl.switchFileIfNecessary(JournalImpl.java:3147) [hornetq-journal-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

        at org.hornetq.core.journal.impl.JournalImpl.appendRecord(JournalImpl.java:2773) [hornetq-journal-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

        at org.hornetq.core.journal.impl.JournalImpl.access$900(JournalImpl.java:79) [hornetq-journal-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

        at org.hornetq.core.journal.impl.JournalImpl$PerfBlast.run(JournalImpl.java:3036) [hornetq-journal-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

       

       

      17:05:30,704 INFO  [org.hornetq.core.server] (Thread-0 (HornetQ-scheduled-threads-1255119321)) HQ221004:

      **** Server Dump ****

      date:            Thu Apr 28 17:05:30 CDT 2016

      free memory:      708.76 MiB

      max memory:       982.00 MiB

      total memory:     982.00 MiB

      available memory: 72.18%

      # of thread:     102

      # of conns:      0

      ********************

       

       

      17:05:30,909 INFO  [org.hornetq.core.server] (Thread-1 (HornetQ-scheduled-threads-1255119321)) HQ221004:

      **** Server Dump ****

      date:            Thu Apr 28 17:05:30 CDT 2016

      free memory:      708.07 MiB

      max memory:       982.00 MiB

      total memory:     982.00 MiB

      available memory: 72.11%

      # of thread:     103

      # of conns:      0

      ********************

       

       

      17:05:30,912 INFO  [org.hornetq.core.server] (Thread-0 (HornetQ-scheduled-threads-1255119321)) HQ221004:

      **** Server Dump ****

      date:            Thu Apr 28 17:05:30 CDT 2016

      free memory:      933.08 MiB

      max memory:       982.00 MiB

      total memory:     982.00 MiB

      available memory: 95.02%

      # of thread:     104

      # of conns:      0

      ********************

       

       

      17:05:30,914 INFO  [org.hornetq.core.server] (Thread-2 (HornetQ-scheduled-threads-1255119321)) HQ221004:

      **** Server Dump ****

      date:            Thu Apr 28 17:05:30 CDT 2016

      free memory:      932.44 MiB

      max memory:       982.00 MiB

      total memory:     982.00 MiB

      available memory: 94.95%

      # of thread:     105

      # of conns:      0

      ********************

       

      ..........

      .........

       

      17:05:31,053 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221007: Server is now live

      17:05:31,053 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221001: HornetQ Server version 2.3.25.Final (2.3.x, 123) [51f72559-0d8d-11e6-b24f-b1d294715443]

      17:05:31,055 INFO  [org.hornetq.core.server] (Thread-2 (HornetQ-scheduled-threads-1255119321)) HQ221004:

      **** Server Dump ****

      date:            Thu Apr 28 17:05:31 CDT 2016

      free memory:      913.26 MiB

      max memory:       982.00 MiB

      total memory:     982.00 MiB

      available memory: 93.00%

      # of thread:     123

      # of conns:      0

      ********************

       

      ....

       

      17:05:31,061 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 53) HQ221003: trying to deploy queue jms.queue.MessageQueue

      17:05:31,063 INFO  [org.hornetq.core.server] (Thread-2 (HornetQ-scheduled-threads-1255119321)) HQ221004:

      **** Server Dump ****

      date:            Thu Apr 28 17:05:31 CDT 2016

      free memory:      912.73 MiB

      max memory:       982.00 MiB

      total memory:     982.00 MiB

      available memory: 92.95%

      # of thread:     123

      # of conns:      0

      ********************

       

       

      17:05:31,063 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 52) MSC000001: Failed to start service jboss.messaging.MessageQueue.jms.connection-factory.Queue: org.jboss.msc.service.StartException in service jboss.messaging.MessageQueue.jms.connection-factory.Queue: JBAS011639: No logró crear connection-factory

        at org.jboss.as.messaging.jms.ConnectionFactoryService$1.run(ConnectionFactoryService.java:70) [jboss-as-messaging-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]

        at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]

        at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]

      Caused by: HornetQException[errorType=ILLEGAL_STATE message=HQ129005: Connector 'in-vm' not found on the main configuration file]

        at org.hornetq.jms.server.impl.JMSServerManagerImpl.internalCreateCFPOJO(JMSServerManagerImpl.java:1417) [hornetq-jms-server-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

        at org.hornetq.jms.server.impl.JMSServerManagerImpl.internalCreateCF(JMSServerManagerImpl.java:1364) [hornetq-jms-server-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

        at org.hornetq.jms.server.impl.JMSServerManagerImpl.access$1300(JMSServerManagerImpl.java:108) [hornetq-jms-server-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

        at org.hornetq.jms.server.impl.JMSServerManagerImpl$5.runException(JMSServerManagerImpl.java:1210) [hornetq-jms-server-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

        at org.hornetq.jms.server.impl.JMSServerManagerImpl.runAfterActive(JMSServerManagerImpl.java:1902) [hornetq-jms-server-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

        at org.hornetq.jms.server.impl.JMSServerManagerImpl.createConnectionFactory(JMSServerManagerImpl.java:1196) [hornetq-jms-server-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

        at org.jboss.as.messaging.jms.ConnectionFactoryService$1.run(ConnectionFactoryService.java:67) [jboss-as-messaging-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]

        ... 4 more

       

      Thaks.

        • 1. Re: Jboss EAP 6.4 Failed to performance blast: java.lang.IllegalArgumentException: Record is too large to store 131072
          Justin Bertram Master

          17:05:30,701 ERROR [org.hornetq.journal] (hornetq-perfblast-thread) HQ144005: Failed to performance blast: java.lang.IllegalArgumentException: Record is too large to store 131072

            at org.hornetq.core.journal.impl.JournalImpl.switchFileIfNecessary(JournalImpl.java:3147) [hornetq-journal-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

            at org.hornetq.core.journal.impl.JournalImpl.appendRecord(JournalImpl.java:2773) [hornetq-journal-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

            at org.hornetq.core.journal.impl.JournalImpl.access$900(JournalImpl.java:79) [hornetq-journal-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

            at org.hornetq.core.journal.impl.JournalImpl$PerfBlast.run(JournalImpl.java:3036) [hornetq-journal-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

          This indicates that you are configuring <perf-blast-pages> with something other than "-1" which is the default value.  If you configure this to "-1" or just leave it unset then you won't get this error.

           

          17:05:31,063 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 52) MSC000001: Failed to start service jboss.messaging.MessageQueue.jms.connection-factory.Queue: org.jboss.msc.service.StartException in service jboss.messaging.MessageQueue.jms.connection-factory.Queue: JBAS011639: No logró crear connection-factory

            at org.jboss.as.messaging.jms.ConnectionFactoryService$1.run(ConnectionFactoryService.java:70) [jboss-as-messaging-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]

            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]

            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]

            at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]

            at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]

          Caused by: HornetQException[errorType=ILLEGAL_STATE message=HQ129005: Connector 'in-vm' not found on the main configuration file]

            at org.hornetq.jms.server.impl.JMSServerManagerImpl.internalCreateCFPOJO(JMSServerManagerImpl.java:1417) [hornetq-jms-server-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

            at org.hornetq.jms.server.impl.JMSServerManagerImpl.internalCreateCF(JMSServerManagerImpl.java:1364) [hornetq-jms-server-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

            at org.hornetq.jms.server.impl.JMSServerManagerImpl.access$1300(JMSServerManagerImpl.java:108) [hornetq-jms-server-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

            at org.hornetq.jms.server.impl.JMSServerManagerImpl$5.runException(JMSServerManagerImpl.java:1210) [hornetq-jms-server-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

            at org.hornetq.jms.server.impl.JMSServerManagerImpl.runAfterActive(JMSServerManagerImpl.java:1902) [hornetq-jms-server-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

            at org.hornetq.jms.server.impl.JMSServerManagerImpl.createConnectionFactory(JMSServerManagerImpl.java:1196) [hornetq-jms-server-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1]

            at org.jboss.as.messaging.jms.ConnectionFactoryService$1.run(ConnectionFactoryService.java:67) [jboss-as-messaging-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]

            ... 4 more

          This indicates that you've configured a connection factory which references a non-existent "connector."  You need to either add the missing connector or change the connection-factory configuration.

          1 of 1 people found this helpful