I dont think the version of proton-j used by ActiveMQ should be an
issue. The 0.10.0 client uses that broker/client version in some of
its tests, and the broker test suite uses the 0.9.0 client, so they
should run together.

The only thing I notice from the partial tree info that directly
relates to the client is that you have a very old version of SLF4J in
there, whereas the client uses a more recent version normally. Not
sure if that would cause problems or not. Hard to say if the stuff you
trimmed is of any interest.

In terms of what calls the sucess/failure methods on the request,
follow from org.apache.qpid.jms.provider.amqp.AmqpProvider.create(...),
look in the processConnectionInfo section. Looking at it quickly, I
imagine either an error is being thrown and not caught or something
similar, you could try sticking it under a debugger and looking.

On 19 July 2016 at 13:28, DraCzech <[email protected]> wrote:
> One thing I found out is that activemq-amqp artifact has proton-j compile
> dependency:
>
> +- org.apache.activemq:activemq-amqp:jar:5.13.3:compile
> |  \- org.apache.qpid:proton-j:jar:0.12.1:compile
>
> But that one was overridden by direct dependency when I used it (and the
> issue had occurred even at that time). I now removed the activemq-amqp
> dependency from the project so the tree now look like this:
>
> --- maven-dependency-plugin:2.8:tree (default-cli) @ databroker ---
> com.openmatics.box:databroker:bundle:3.6.0-SNAPSHOT
> +- org.osgi:org.osgi.core:jar:4.2.0:compile
> +- org.osgi:org.osgi.compendium:jar:4.2.0:compile
> +- joda-time:joda-time:jar:1.6.2:compile
> +- log4j:log4j:jar:1.2.14:compile
> +- org.sonatype.tycho:org.eclipse.osgi:jar:3.5.1.R35x_v20090827:compile
> -------------------- > Bunch of company bundles < --------------------
> +- org.glassfish.main.admin:javax.management.j2ee:jar:3.1.2:compile
> |  \- org.glassfish.main.ejb:javax.ejb:jar:3.1.2:compile
> |     +- org.glassfish.main.transaction:javax.transaction:jar:3.1.2:compile
> |     \- org.glassfish.main.javaee-api:javax.annotation:jar:3.1.2:compile
> +- org.jasypt:jasypt:jar:1.7:compile
> +- org.slf4j:slf4j-api:jar:1.6.1:compile
> +- org.slf4j:slf4j-log4j12:jar:1.6.1:compile
> +- org.springframework:spring-context:jar:3.0.3.RELEASE:compile
> +- org.springframework:spring-aop:jar:3.0.3.RELEASE:compile
> |  \- aopalliance:aopalliance:jar:1.0:compile
> +- org.springframework:spring-beans:jar:3.0.3.RELEASE:compile
> +- org.springframework:spring-core:jar:3.0.3.RELEASE:compile
> +- org.springframework:spring-expression:jar:3.0.3.RELEASE:compile
> +- org.springframework:spring-asm:jar:3.0.3.RELEASE:compile
> +- org.apache.activemq:activemq-broker:jar:5.13.3:compile
> |  \- org.apache.activemq:activemq-openwire-legacy:jar:5.13.3:compile
> +- org.apache.activemq:activemq-client:jar:5.13.3:compile
> |  +- org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar:1.1.1:compile
> |  \-
> org.apache.geronimo.specs:geronimo-j2ee-management_1.1_spec:jar:1.0.1:compile
> +- org.apache.activemq:activemq-kahadb-store:jar:5.13.3:compile
> |  +- org.apache.activemq.protobuf:activemq-protobuf:jar:1.1:compile
> |  \- commons-net:commons-net:jar:2.2:compile
> +- org.apache.activemq:activemq-spring:jar:5.13.3:compile
> |  +- org.apache.activemq:activemq-pool:jar:5.13.3:compile
> |  |  \- org.apache.activemq:activemq-jms-pool:jar:5.13.3:compile
> |  +- org.apache.geronimo.specs:geronimo-jta_1.0.1B_spec:jar:1.0.1:compile
> |  \- org.apache.commons:commons-pool2:jar:2.4.2:compile
> +- org.apache.activemq:activemq-mqtt:jar:5.13.3:compile
> +- org.apache.qpid:qpid-jms-client:jar:0.10.0:compile
> |  +- org.apache.qpid:proton-j:jar:0.13.0:compile
> |  +- io.netty:netty-buffer:jar:4.0.17.Final:compile
> |  +- io.netty:netty-common:jar:4.0.17.Final:compile
> |  +- io.netty:netty-handler:jar:4.0.17.Final:compile
> |  |  \- io.netty:netty-codec:jar:4.0.17.Final:compile
> |  \- io.netty:netty-transport:jar:4.0.17.Final:compile
> +- io.netty:netty-all:jar:4.0.17.Final:compile
> +- org.fusesource.mqtt-client:mqtt-client:jar:1.2:compile
> +- org.fusesource.hawtdispatch:hawtdispatch-transport:jar:1.9:compile
> |  \- org.fusesource.hawtdispatch:hawtdispatch:jar:1.9:compile
> +- org.fusesource.hawtbuf:hawtbuf:jar:1.9:compile
> +- junit:junit:jar:4.5:test
> +- org.mockito:mockito-all:jar:1.8.5:test
> +- org.apache.xbean:xbean-spring:jar:3.7:test
> \- com.google.code.findbugs:annotations:jar:2.0.2:compile
>
> I still haven't checked what the counterpart for calling *onSuccess()* or
> *onFailure* methods on the affected *ProviderFuture* instance. But I guess
> that will be my focus now.
>
> And one more question: is there any possible issue with connecting to the
> remote server on the netty side? I've noticed that different versions of the
> library suffer from various issues of their own...
>
>
>
> --
> View this message in context: 
> http://qpid.2158936.n2.nabble.com/Cannot-conect-while-using-ActiveMQ-with-Qpid-JMS-client-tp7647859p7647872.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to