git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Artemis (JBoss EAP 7) to HornetQ (EAP 6) elaboration on RedHat example


This looks more like an application server issue than a message broker
issue (whether that's ActiveMQ Artemis or HornetQ).  If you could (mostly)
eliminate the application server from the picture and narrow down your
question to just the broker and/or broker client you may get some help on
this list otherwise I think your best bet is the application server forum.


Justin

On Tue, Aug 7, 2018 at 12:22 PM, JGlass <jason.glass@xxxxxxxxxxxx> wrote:

> Hi All!
>
> I posted a question in the JBoss forums:
> https://developer.jboss.org/thread/278535
> <https://developer.jboss.org/thread/278535>
>
> But thought I might get a little quicker help here.  The problem I am
> having
> and trying to solve is that as per that article I had originally gone the
> route of trying to bundle the JBoss EAP 6 related libraries with the EJB
> application and specifying the following in the EAR
> jboss-deployment-structure:
> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
>     <deployment>
>         <exclude-subsystems>
>             <subsystem name="messaging-activemq"></subsystem>
>         </exclude-subsystems>
>         <exclusions>
>             <module name="javax.jms.api"></module>
>             <module name="org.jboss.ejb"></module>
>             <module name="org.jboss.as.remoting"></module>
>         </exclusions>
>     </deployment>
> </jboss-deployment-structure>
>
> Which works on initial deployment however when I restart the server I get
> the following exception when trying to send a JMS message so it appears
> that
> the jboss-deployment-structure isn't always being honored.  I also end up
> getting that exception at random intervals (a day, days or weeks later) and
> when it occurs all future JMS messages fail to be sent almost as if JBoss
> forgets the application is supposed to be using its own libraries.
>
> Caused by: java.lang.LinkageError: loader constraint violation: when
> resolving method
> "org.jboss.ejb.client.EJBClientContext.registerConnection(Lorg/jboss/
> remoting3/Connection;)V"
> the class loader (instance of org/jboss/modules/ModuleClassLoader) of the
> current class,
> org/jboss/naming/remote/client/ejb/RemoteNamingStoreEJBClientHandler, and
> the class loader (instance of org/jboss/modules/ModuleClassLoader) for the
> method's defining class, org/jboss/ejb/client/EJBClientContext, have
> different Class objects for the type org/jboss/remoting3/Connection used in
> the signature
>
> So as per that same forum post, I'm now trying to use Red Hats overly
> simplified (at least to me) example here:
> https://access.redhat.com/documentation/en-us/red_hat_
> jboss_enterprise_application_platform/7.0/html/configuring_
> messaging/messaging_forward_and_backward_compatiblity#messaging_backward_
> compatiblity
> <https://access.redhat.com/documentation/en-us/red_hat_
> jboss_enterprise_application_platform/7.0/html/configuring_
> messaging/messaging_forward_and_backward_compatiblity#messaging_backward_
> compatiblity>
>
> But since I was using JNDI - I'm really confused as to how to setup the
> connection factory and queue - does anyone by chance have a working
> example?
> I can add all the code after I clean it up a bit if it helps!
>
> Thank you!
>
> Jay
>
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>