[jbertram]

Adding to what Andy's already said...

At this point, a slimmed-up EAP 6 profile with just HornetQ (and anything else you might like in there) is almost certainly superior to standalone HornetQ because of the management capabilities of EAP.  Along with the traditional management options you get with HornetQ (JMX, JMS/core management API, etc.) with EAP you get powerful CLI and HTTP interfaces you can leverage (which modify the XML configuration on disk so everything is consistent).  Plus, you can configure multiple HornetQ nodes into a single domain and manage them as a group.

Lastly, there's no specific need to remove modules unless you just trying to save disk space.  My recommendation would be to start with the standalone-full.xml and then just take out the bits you don't want (e.g. Infinispan, EJB, etc.).  Everything is pretty well isolated into their own subsystems so it should be simple to strip things out.

[yairogen]

interesting. can you point me to eap-hornetq documentation? i.e. what and where I need to change to implement current configuration I have in stand-alone hornetq with EAP?

[jbertram]

Try this.

[yairogen]

I've found this:

https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Administration_and_Configuration_Guide/index.html#chap-Messaging

I don't understand where do I find the hornetq config files under EAP? also - I see latest EAP doesn't contain latest hornetq version. Can I just replace the jars with latest?

[jbertram]

I don't understand where do I find the hornetq config files under EAP?

You should probably read some of the more general documentation about JBoss EAP 6.x as it appears you're completely unfamiliar with it. 

In any event, in a previous comment I said, "My recommendation would be to start with the standalone-full.xml..."  Did you take a look at that file?  If so, did you see the "messaging" subsystem and the <hornetq-server> element which contained all the HornetQ configuration?  If you didn't take a look at it I would encourage you to do so.  It's in <JBOSS_HOME>/standalone/configuration (along with all the other standalone profiles).

I see latest EAP doesn't contain latest hornetq version. Can I just replace the jars with latest?

One of the goals of EAP is to provide a solid, stable application platform.  To that end, the entire platform goes through rigorous QA cycles.  EAP doesn't simply use the latest of each of the corresponding community projects (e.g. HornetQ) since it takes time and man-power to QA each release and since such frequent changes wouldn't align well with most corporate software upgrade policies.  If there happens to be something fixed in an upstream community release that you need fixed in EAP then you can typically work with Red Hat support and get a patch for it.  Red Hat only supports official patches.  You are technically free to upgrade arbitrary jars but that would invalidate your support agreement and there's no guarantee it would work anyway.

At the end of the day, it appears to me that you want a lot of support, and you're simply not likely to get that on a community forum.  At the very least I encourage you to read more documentation (both HornetQ and EAP).  Quite a few of the questions you've asked on various threads are addressed there.  Furthermore, when you do have an issue do your best to create a reproducible test-case to demonstrate it.

[yairogen]

I have seen the "standalone-full.xml" - but the relationship between the old standalone configuration to the new configuration is not clear. Doesn't look they share the same xsd do they?

I've opened a discussion on this regard in the EAP area.

I appreciate all your support and indeed looks like we will purchase support.

Side note: I did read the manuals  - but not cover to cover. They are very lengthy and are hard to comprehend without trying things hands-on parallel to the read.

[jbertram]

I have seen the "standalone-full.xml" - but the relationship between the old standalone configuration to the new configuration is not clear. Doesn't look they share the same xsd do they?

The standalone-full.xml to which I was referring is for JBoss EAP which is a Java EE application server.  It incorporates HornetQ into the platform to server as the JMS implementation (which is a requirement of Java EE).  Obviously, the standalone-full.xml for JBoss EAP does not share the same XSD as standalone HornetQ.  The "messaging" subsystem (which is configured in standalone-full.xml) has a schema that's very close to standalone HornetQ, but even that's not exactly the same at the very least because everything is configured in the same place in the messaging subsystem whereas there are several different schemas for the individual HornetQ configuration files (e.g. hornetq-configuration.xml, hornetq-jms.xml, etc.).

[yairogen]

Thought so.

Thing is that:

1. EAP messaging section is so much shorter than the HornetQ user-guide. Which one should I use?
2. Couldn't find relevant guide/xsd etc to implement my standalone configuration as part of EAP. can you share link?
3. one thing that stands out - Must I use hornetq as part of EAP as a JMS provider? Even I want to use only core features (specifically multiple queues bonded to the same address)?

[jbertram]

EAP messaging section is so much shorter than the HornetQ user-guide. Which one should I use?

The EAP documentation for the messaging subsystem is largely based on the HornetQ User Guide.  I tend to refer people to the HornetQ User Guide more often than anything else because it has quite a bit more detail.

Couldn't find relevant guide/xsd etc to implement my standalone configuration as part of EAP. can you share link?

The schema for the messaging subsystem is in <JBOSS_HOME>/docs/schema.  See, for example, jboss-as-messaging_1_4.xsd.

As I mentioned, the schema there is very close to those in standalone HornetQ.  For the most part you can cut/paste your configuration.

one thing that stands out - Must I use hornetq as part of EAP as a JMS provider? Even I want to use only core features (specifically multiple queues bonded to the same address)?

The JMS API is a pretty thin layer on top of HornetQ core.  All the core functionality of HornetQ is available in EAP just as it available in standalone.  You can certainly configure multiple queues bound to the same address. 

[yairogen]

I've started working with EAP. First using the full configuration.

Although listening correctly and viewing connection established via netstat, clients code (that worked fine with standalone hornetq) failes on:

HornetQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT message=HQ119013: Timed out waiting to receive cluster topology. Group:null]

[jbertram]

I've started working with EAP. First using the full configuration.

Did you purchase a support subscription for EAP?  If so, I recommend you open a ticket with Red Hat regarding your issue.

Couple of additional thoughts:

1. This thread is way off-topic at this point.  It's probably best to stop using it.
2. You provided no configuration and no code to go along with the exception message you pasted.  In this case, it is impossible to help without more information.

[yairogen]

Opened a case on Redhat, thanks for your help \till now. Much appreciated.