1 Reply Latest reply on Feb 6, 2013 9:52 AM by jbertram

Jbos migration 4.2.2 -> 6.1.0 hornetq

vpolakis Feb 5, 2013 7:01 PM

Hi,

I am trying to migrate a jboss 4.2.2 to Jboss 6.1.0.Final

In 4.2.2 the ?????-service.xml

<mbean code="org.jboss.mq.server.jmx.Topic"

name="jboss.mq.destination:service=Topic,name=ALARMNOTIFICATIONS">

<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>

<depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>

</security>

</attribute>

</mbean>

</server>

Now as far as I have found the found in the web in order to migrate to HornetQ I need to add

???-hornetq-jms.xml to the …\server\default\deploy directory

<configuration xmlns="urn:hornetq"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="urn:hornetq ../schemas/hornetq-jms.xsd ">

<connection-factory name="ConnectionFactory">

<connector-ref connector-name="netty"/>

</connectors>

</entries>

</connection-factory>

</topic>

</configuration>

But I get

14:48:38,694 INFO [HornetQServerImpl] trying to deploy queue jms.topic.OSNOTIFICATIONS

Is this OK??

Many thx for the help

Full log:

14:48:19,634 INFO [AbstractServer] Starting: JBossAS [6.1.0.Final "Neo"]

14:48:21,027 INFO [ServerInfo] Java version: 1.6.0_35,Sun Microsystems Inc.

14:48:21,027 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_35-b10)

14:48:21,028 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 20.10-b01,Sun Microsystems Inc.

14:48:21,028 INFO [ServerInfo] OS-System: Windows 7 6.1,amd64

14:48:21,028 INFO [ServerInfo] VM arguments: -Dprogram.name=run.bat -Dlogging.configuration=file:logging.properties -Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -Djava.endorsed.dirs=D:\PROJECTS\JBOSS\jboss\AS6\lib\endorsed

14:48:21,070 INFO [JMXKernel] Legacy JMX core initialized

14:48:27,919 INFO [AbstractServerConfig] JBoss Web Services - Stack CXF Server 3.4.1.GA

14:48:28,445 INFO [JSFImplManagementDeployer] Initialized 3 JSF configurations: [Mojarra-1.2, MyFaces-2.0, Mojarra-2.0]

14:48:34,272 WARNING [FileConfigurationParser] AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal

14:48:34,464 INFO [JMXConnector] starting JMXConnector on host 127.0.0.1:1090

14:48:34,545 INFO [MailService] Mail Service bound to java:/Mail

14:48:35,292 INFO [HornetQServerImpl] live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=D:\PROJECTS\JBOSS\jboss\AS6\server\default\data/hornetq/journal,bindingsDirectory=D:\PROJECTS\JBOSS\jboss\AS6\server\default\data/hornetq/bindings,largeMessagesDirectory=D:\PROJECTS\JBOSS\jboss\AS6\server\default\data/hornetq/largemessages,pagingDirectory=D:\PROJECTS\JBOSS\jboss\AS6\server\default\data/hornetq/paging)

14:48:35,294 INFO [HornetQServerImpl] Waiting to obtain live lock

14:48:35,352 INFO [JournalStorageManager] Using NIO Journal

14:48:35,377 WARNING [HornetQServerImpl] Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this.

14:48:35,473 INFO [FileLockNodeManager] Waiting to obtain live lock

14:48:35,473 INFO [FileLockNodeManager] Live Server Obtained live lock

14:48:36,345 INFO [NettyAcceptor] Started Netty Acceptor version 3.2.3.Final-r${buildNumber} 127.0.0.1:5445 for CORE protocol

14:48:36,348 INFO [NettyAcceptor] Started Netty Acceptor version 3.2.3.Final-r${buildNumber} 127.0.0.1:5455 for CORE protocol

14:48:36,351 INFO [HornetQServerImpl] Server is now live

14:48:36,351 INFO [HornetQServerImpl] HornetQ Server version 2.2.5.Final (HQ_2_2_5_FINAL_AS7, 121) [2f742069-39f0-11e2-9b60-d067e5498ea4] started

14:48:36,395 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/

14:48:36,541 INFO [jbossatx] ARJUNA-32010 JBossTS Recovery Service (tag: JBOSSTS_4_14_0_Final) - JBoss Inc.

14:48:36,546 INFO [arjuna] ARJUNA-12324 Start RecoveryActivators

14:48:36,561 INFO [arjuna] ARJUNA-12296 ExpiredEntryMonitor running at Mon, 4 Feb 2013 14:48:36

14:48:36,615 INFO [arjuna] ARJUNA-12310 Recovery manager listening on endpoint 127.0.0.1:4712

14:48:36,616 INFO [arjuna] ARJUNA-12344 RecoveryManagerImple is ready on port 4712

14:48:36,616 INFO [jbossatx] ARJUNA-32013 Starting transaction recovery manager

14:48:36,632 INFO [arjuna] ARJUNA-12163 Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 4713

14:48:36,633 INFO [arjuna] ARJUNA-12337 TransactionStatusManagerItem host: 127.0.0.1 port: 4713

14:48:36,638 INFO [arjuna] ARJUNA-12170 TransactionStatusManager started on port 4713 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService

14:48:36,670 INFO [jbossatx] ARJUNA-32017 JBossTS Transaction Service (JTA version - tag: JBOSSTS_4_14_0_Final) - JBoss Inc.

14:48:36,734 INFO [arjuna] ARJUNA-12202 registering bean jboss.jta:type=ObjectStore.

14:48:36,938 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.6.0_35\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Perl64\site\bin;C:\Perl64\bin;C:\Program Files\IBM\RationalSDLC\common;C:\Program Files (x86)\RSA SecurID Token Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\ooRexx;C:\Program Files\IBM\RationalSDLC\ClearCase\bin;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Tcl\bin;C:\SWS4\NTBIN;C:\SWS4\CMP\NTBIN;C:\SWS4\MED;C:\Program Files (x86)\IDM Computer Solutions\UltraEdit\;C:\Perl64\site\bin;C:\Perl64\bin;C:\Program Files\IBM\RationalSDLC\common;C:\Program Files (x86)\RSA SecurID Token Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\ooRexx;C:\Program Files\IBM\RationalSDLC\ClearCase\bin;C:\Windows\System32\WindowsPowerShell\v1.0\;.

14:48:37,070 INFO [TomcatDeployment] deploy, ctxPath=/invoker

14:48:37,437 INFO [ModClusterService] Initializing mod_cluster 1.1.0.Final

14:48:37,509 INFO [RARDeployment] Required license terms exist, view vfs:/D:/PROJECTS/JBOSS/jboss/AS6/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml

14:48:37,525 INFO [RARDeployment] Required license terms exist, view vfs:/D:/PROJECTS/JBOSS/jboss/AS6/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml

14:48:37,534 INFO [RARDeployment] Required license terms exist, view vfs:/D:/PROJECTS/JBOSS/jboss/AS6/server/default/deploy/jms-ra.rar/META-INF/ra.xml

14:48:37,552 INFO [HornetQResourceAdapter] HornetQ resource adaptor started

14:48:37,559 INFO [RARDeployment] Required license terms exist, view vfs:/D:/PROJECTS/JBOSS/jboss/AS6/server/default/deploy/mail-ra.rar/META-INF/ra.xml

14:48:37,575 INFO [RARDeployment] Required license terms exist, view vfs:/D:/PROJECTS/JBOSS/jboss/AS6/server/default/deploy/quartz-ra.rar/META-INF/ra.xml

14:48:37,684 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: Thread-2

14:48:37,722 INFO [SchedulerSignalerImpl] Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl

14:48:37,723 INFO [QuartzScheduler] Quartz Scheduler v.1.8.3 created.

14:48:37,725 INFO [RAMJobStore] RAMJobStore initialized.

14:48:37,727 INFO [QuartzScheduler] Scheduler meta-data: Quartz Scheduler (v1.8.3) 'JBossQuartzScheduler' with instanceId 'NON_CLUSTERED'

Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.

NOT STARTED.

Currently in standby mode.

Number of jobs executed: 0

Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.

Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.

14:48:37,728 INFO [StdSchedulerFactory] Quartz scheduler 'JBossQuartzScheduler' initialized from an externally opened InputStream.

14:48:37,728 INFO [StdSchedulerFactory] Quartz scheduler version: 1.8.3

14:48:37,728 INFO [QuartzScheduler] Scheduler JBossQuartzScheduler_$_NON_CLUSTERED started.

14:48:38,080 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'

14:48:38,264 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'

14:48:38,387 INFO [xnio] XNIO Version 2.1.0.CR2

14:48:38,396 INFO [nio] XNIO NIO Implementation Version 2.1.0.CR2

14:48:38,538 INFO [remoting] JBoss Remoting version 3.1.0.Beta2

14:48:38,613 INFO [TomcatDeployment] deploy, ctxPath=/

14:48:38,673 INFO [HornetQServerImpl] trying to deploy queue jms.queue.DLQ

14:48:38,694 INFO [HornetQServerImpl] trying to deploy queue jms.topic.OSNOTIFICATIONS

14:48:38,716 INFO [HornetQServerImpl] trying to deploy queue jms.queue.ExpiryQueue

14:48:38,733 INFO [service] Removing bootstrap log handlers

14:48:38,787 INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080

14:48:38,810 INFO [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009

14:48:38,811 INFO [org.jboss.bootstrap.impl.base.server.AbstractServer] JBossAS [6.1.0.Final "Neo"] Started in 19s:175ms

1. Re: Jbos migration 4.2.2 -> 6.1.0 hornetq

jbertram Feb 6, 2013 9:52 AM (in response to vpolakis)

That looks fine in general, but I would strongly recommend you use JBoss AS7 rather than AS 6 (which is no longer developed). Furthermore, AS7 would have a much newer version of HornetQ (2.2.5 is pretty old now).
Actions