qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robbie Gemmell <robbie.gemm...@gmail.com>
Subject Re: [VOTE] Release Qpid JMS 0.1.0
Date Thu, 19 Mar 2015 01:27:49 GMT
On 17 March 2015 at 16:56, Gordon Sim <gsim@redhat.com> wrote:
> On 03/16/2015 07:53 PM, Robbie Gemmell wrote:
>>
>> Hi all,
>>
>> We have reached a point that it would be useful to do an initial
>> release of the new Proton-based JMS client, so I have put up an RC for
>> folks to test and vote on.
>>
>> The source and binary archives can be grabbed from here:
>> https://dist.apache.org/repos/dist/dev/qpid/jms/0.1.0-rc1/
>>
>> Those and the other individual maven artifacts are also staged for now at:
>> https://repository.apache.org/content/repositories/orgapacheqpid-1030
>>
>> I will close the vote some point towards the end of the week. I'll be
>> off on vacation by then so the exact timing is a little fuzzy but it
>> will be after 72hrs are up, i.e after 8pm GMT on Thursday 19th.
>
>
> The binary tarball includes a netty jar, but I didn't see any mention of
> that in the notice? There is a mention in the license file of slf4j, but
> again not for netty. Although it is also Apache licensed, shouldn't there be
> some explicit note of it?
>
> For the source tarball, I got some test errors[1]. Not sure if this was just
> something I was missing (e.g. starting up some other broker). Not a
> show-stopper either.
>
> Ran the hello world example successfully against the 0.32 qpidd.
>
> Just to mention it, though not a blocker by any means, following the readme
> for the examples in the binary tarball doesn't work.
>

I just randomly recalled you had mentioned this and realised I forgot
to answer it.

Short answer, that is a side effect of the release process and is
expected behaviour based on how the examples are structured and how
maven works in general. I tried to convey this somewhat in the README
but obviously not clearly enough, ill see if I can reword it for
clarity.

Longer answer, the poms are looking for dependencies with a release
version 0.1.0, which as they havent been released dont yet exist in
any of the remote repositories the poms enable maven to access (i.e,
maven central by default and the apache snapshots repo if the parent
poms are also available - which they obviously are in the source
release, but arent for the binary archive unless retrievable from a
remote repo, such as central). As a result of this, during the release
process the instructions in the README for the binary tar will only
work if you first 'mvn install' the source release to make the
necessary dependencies available (via the local repo), or modify the
pom to provide the repository info for the temporary staging repo
(details included in the vote email for that reason).

As soon as the artifacts are actually released and sync to central
then the instructions in the binary tar will work without needing a
local install or modified pom, with maven then being able to grab the
needed dependencies from central.

> [1] test errors:
>
>> Running org.apache.qpid.jms.discovery.JmsAmqpDiscoveryTest
>> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 241.219
>> sec <<< FAILURE! - in org.apache.qpid.jms.discovery.JmsAmqpDiscoveryTest
>>
>> testDiscoversAndReconnectsToSecondaryBroker(org.apache.qpid.jms.discovery.JmsAmqpDiscoveryTest)
>> Time elapsed: 60.303 sec  <<< ERROR!
>> org.junit.runners.model.TestTimedOutException: test timed out after 60000
>> milliseconds
>>         at sun.misc.Unsafe.park(Native Method)
>>         at
>> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>>         at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
>>         at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
>>         at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
>>         at
>> java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
>>         at
>> org.apache.qpid.jms.provider.ProviderFuture.sync(ProviderFuture.java:86)
>>         at
>> org.apache.qpid.jms.JmsConnection.createResource(JmsConnection.java:616)
>>         at
>> org.apache.qpid.jms.JmsConnection.connect(JmsConnection.java:525)
>>         at org.apache.qpid.jms.JmsConnection.start(JmsConnection.java:318)
>>         at
>> org.apache.qpid.jms.discovery.JmsAmqpDiscoveryTest.testDiscoversAndReconnectsToSecondaryBroker(JmsAmqpDiscoveryTest.java:116)
>>
>>
>> testConnectionRestoresAfterBrokerRestarted(org.apache.qpid.jms.discovery.JmsAmqpDiscoveryTest)
>> Time elapsed: 60.23 sec  <<< ERROR!
>> org.junit.runners.model.TestTimedOutException: test timed out after 60000
>> milliseconds
>>         at sun.misc.Unsafe.park(Native Method)
>>         at
>> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>>         at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
>>         at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
>>         at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
>>         at
>> java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
>>         at
>> org.apache.qpid.jms.provider.ProviderFuture.sync(ProviderFuture.java:86)
>>         at
>> org.apache.qpid.jms.JmsConnection.createResource(JmsConnection.java:616)
>>         at
>> org.apache.qpid.jms.JmsConnection.connect(JmsConnection.java:525)
>>         at org.apache.qpid.jms.JmsConnection.start(JmsConnection.java:318)
>>         at
>> org.apache.qpid.jms.discovery.JmsAmqpDiscoveryTest.testConnectionRestoresAfterBrokerRestarted(JmsAmqpDiscoveryTest.java:96)
>>
>>
>> testRunningBrokerIsDiscovered(org.apache.qpid.jms.discovery.JmsAmqpDiscoveryTest)
>> Time elapsed: 60.344 sec  <<< ERROR!
>> org.junit.runners.model.TestTimedOutException: test timed out after 60000
>> milliseconds
>>         at sun.misc.Unsafe.park(Native Method)
>>         at
>> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>>         at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
>>         at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
>>         at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
>>         at
>> java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
>>         at
>> org.apache.qpid.jms.provider.ProviderFuture.sync(ProviderFuture.java:86)
>>         at
>> org.apache.qpid.jms.JmsConnection.createResource(JmsConnection.java:616)
>>         at
>> org.apache.qpid.jms.JmsConnection.connect(JmsConnection.java:525)
>>         at org.apache.qpid.jms.JmsConnection.start(JmsConnection.java:318)
>>         at
>> org.apache.qpid.jms.discovery.JmsAmqpDiscoveryTest.testRunningBrokerIsDiscovered(JmsAmqpDiscoveryTest.java:63)
>>
>>
>> testConnectionFailsWhenBrokerGoesDown(org.apache.qpid.jms.discovery.JmsAmqpDiscoveryTest)
>> Time elapsed: 60.342 sec  <<< ERROR!
>> org.junit.runners.model.TestTimedOutException: test timed out after 60000
>> milliseconds
>>         at sun.misc.Unsafe.park(Native Method)
>>         at
>> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>>         at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
>>         at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
>>         at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
>>         at
>> java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
>>         at
>> org.apache.qpid.jms.provider.ProviderFuture.sync(ProviderFuture.java:86)
>>         at
>> org.apache.qpid.jms.JmsConnection.createResource(JmsConnection.java:616)
>>         at
>> org.apache.qpid.jms.JmsConnection.connect(JmsConnection.java:525)
>>         at org.apache.qpid.jms.JmsConnection.start(JmsConnection.java:318)
>>         at
>> org.apache.qpid.jms.discovery.JmsAmqpDiscoveryTest.testConnectionFailsWhenBrokerGoesDown(JmsAmqpDiscoveryTest.java:77)
>>
>> Running org.apache.qpid.jms.JmsQueueConnectionTest
>> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.049 sec
>> - in org.apache.qpid.jms.JmsQueueConnectionTest
>> Running org.apache.qpid.jms.JmsSSLConnectionTest
>> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.854 sec
>> - in org.apache.qpid.jms.JmsSSLConnectionTest
>> Running org.apache.qpid.jms.bench.ProduceToOpenWireTest
>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0 sec - in
>> org.apache.qpid.jms.bench.ProduceToOpenWireTest
>> Running org.apache.qpid.jms.bench.ProduceToAMQPTest
>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0 sec - in
>> org.apache.qpid.jms.bench.ProduceToAMQPTest
>> Running org.apache.qpid.jms.bench.ConsumeFromAMQPTest
>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0 sec - in
>> org.apache.qpid.jms.bench.ConsumeFromAMQPTest
>> Running org.apache.qpid.jms.JmsConnectionCloseVariationsTest
>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.942 sec
>> - in org.apache.qpid.jms.JmsConnectionCloseVariationsTest
>> Running org.apache.qpid.jms.destinations.JmsTemporaryTopicTest
>> Tests run: 5, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.421 sec
>> - in org.apache.qpid.jms.destinations.JmsTemporaryTopicTest
>> Running org.apache.qpid.jms.destinations.JmsTemporaryQueueTest
>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.443 sec
>> - in org.apache.qpid.jms.destinations.JmsTemporaryQueueTest
>>
>> Results :
>>
>> Tests in error:
>>   JmsAmqpDiscoveryTest.testDiscoversAndReconnectsToSecondaryBroker:116 »
>> TestTimedOut
>>   JmsAmqpDiscoveryTest.testConnectionRestoresAfterBrokerRestarted:96 »
>> TestTimedOut
>>   JmsAmqpDiscoveryTest.testRunningBrokerIsDiscovered:63 » TestTimedOut
>> test time...
>>   JmsAmqpDiscoveryTest.testConnectionFailsWhenBrokerGoesDown:77 »
>> TestTimedOut t...
>>
>> Tests run: 360, Failures: 0, Errors: 4, Skipped: 12
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] QpidJMS ........................................... SUCCESS
>> [14.491s]
>> [INFO] QpidJMS Client .................................... SUCCESS
>> [45.361s]
>> [INFO] QpidJMS Discovery Library ......................... SUCCESS
>> [1.414s]
>> [INFO] QpidJMS Broker Interop Tests ...................... SUCCESS
>> [0.088s]
>> [INFO] QpidJMS ActiveMQ Interop Tests .................... FAILURE
>> [8:46.989s]
>> [INFO] QpidJMS Examples .................................. SKIPPED
>> [INFO] QpidJMS Docs ...................................... SKIPPED
>> [INFO] Apache Qpid JMS ................................... SKIPPED
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 9:49.285s
>> [INFO] Finished at: Tue Mar 17 16:30:21 GMT 2015
>> [INFO] Final Memory: 24M/159M
>> [INFO]
>> ------------------------------------------------------------------------
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message