activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <>
Subject [jira] [Assigned] (ARTEMIS-344) amqpnetlite client cannot connect a broker running as a service
Date Thu, 21 Jan 2016 18:53:40 GMT


Justin Bertram reassigned ARTEMIS-344:

    Assignee: Justin Bertram

> amqpnetlite client cannot connect a broker running as a service
> ---------------------------------------------------------------
>                 Key: ARTEMIS-344
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 1.2.0
>         Environment: Broker: Windows Server 2012 R2
> Client: amqpnetlite- on Windows Server 2012 R2, built in Microsoft Visual Studio
>            Reporter: Petra Svobodova
>            Assignee: Justin Bertram
> Sending (or receiving) a message to the Artemis broker running as a service fails; the
client cannot connect the broker.
> Steps to reproduce:
> 1. Unpack the artemis package and create a broker instance.
> 2. Install the artemis as Windows service: ~/bin/artemis-service.exe install
> 3 Open the Services console and start the installed artemis service (check if the service
is running).
> 4. Unpack and compile the amqpnetlite client.
> 5. Try to send a message: Interop.Spout.exe --broker amqp://admin:admin@
--address jms.queue.test --content hello --count 1
> The client cannot connect the broker and after some time period is shut down. 
> This issue does not occur if the Artemis is started directly by "Artemis.cmd" command.
> Also it does not occur in Linux platform (clients can connect the Artemis broker running
directly and also as a service).

This message was sent by Atlassian JIRA

View raw message