Why do you think it had to do with the service name string?
-----Original Message-----
From: Kerry Bonin [mailto:kerrybonin@gmail.com]
Sent: Montag, 27. September 2010 20:10
To: dev@qpid.apache.org
Subject: Re: [jira] Updated: (QPID-2519) Allow Windows Broker to run as a Service
If you don't specify an account to run under, then it defaults (via
SCM) to LocalService. If I try and specify "LocalService" then it I get that error, which
led me to suspect it had to do with the service name string.
On Mon, Sep 27, 2010 at 1:06 PM, Daniel Sack <Daniel.Sack@techtalk.at> wrote:
> I tried it out to run it as LocalService but if I try to start the broker with service.mmc
I 'll get the message:
>
> Windows could not start the qpidd service on Local Computer.
> Error 1053: The service did not respond to the start or control request in a timely fashion.
>
> There is also not qpid broker process running.
>
> Lg,
> Daniel
>
> -----Original Message-----
> From: Kerry Bonin [mailto:kerrybonin@gmail.com]
> Sent: Montag, 27. September 2010 19:18
> To: Daniel Sack
> Subject: Re: [jira] Updated: (QPID-2519) Allow Windows Broker to run
> as a Service
>
> By default I believe it runs as LocalService. I added support for the SCM API to allow
specification of an alternative user, but when I tested it I couldn't get it to work as NetworkService.
I suspect that was only because I wasn't specifying the user in the string format that SCM
expected (something like {hostname}/{account name}), but I got distracted after playing for
a few mins and haven't returned yet.
>
>
> On Mon, Sep 27, 2010 at 11:55 AM, Daniel Sack <Daniel.Sack@techtalk.at> wrote:
>> Hi,
>>
>> Just a small question:
>>
>> Currently it's only possible for me to run the qpid-broker service under some user
credentials which are not built in service users like: "LocalSystem" or "NetworkService"
>>
>> If we want to start the broker as "LocalSystem" it won't start with error 1503.
>> Can you answer me why?
>>
>> We have tried to use xyntservice (http://www.codeproject.com/KB/system/xyntservice.aspx)
which was not really working with qpid 0.6 cpp broker.
>> It' always crashed somewhere in kernel.dll with some corrupted heap, .......
>> But we were able to run the broker as "Local System" account, maybe is the problem
why the broker crashes, I don't know.
>>
>> Br,
>> Daniel Sack
>>
>> -----Original Message-----
>> From: Kerry Bonin [mailto:kerrybonin@gmail.com]
>> Sent: Montag, 27. September 2010 18:43
>> To: dev@qpid.apache.org
>> Subject: Re: [jira] Updated: (QPID-2519) Allow Windows Broker to run
>> as a Service
>>
>> Thanks for working on this cleanup, I've been a bit swamped and haven't had time
to return to change the style or fix the logging.
>> For what its worth, we've been using this in a major product release in system test
for a few months, zero issues on the service to date...
>>
>> On Mon, Sep 27, 2010 at 11:40 AM, Daniel Sack (JIRA) <qpid-dev@incubator.apache.org>
wrote:
>>>
>>> [
>>> https://issues.apache.org/jira/browse/QPID-2519?page=com.atlassian.j
>>> i r a.plugin.system.issuetabpanels:all-tabpanel ]
>>>
>>> Daniel Sack updated QPID-2519:
>>> ------------------------------
>>>
>>> Attachment: broker_as_service_Qpid_Logging.patch
>>>
>>> Hi,
>>> Scince we need this patch for our production system, I tried to
>>> implement parts of the comments 1. Please reformat according to Qpid
>>> coding style (http://qpid.apache.org/qpid-c-documentation.html) - no
>>> tabs, consistent brace style
>>> -> didn't have the time for it
>>>
>>> 2. There's a global WinService in QpiddBroker.cpp - what's that for?
>>> -> Responsible for all the daemon stuff which is needed for the windows platform.
>>>
>>> 3. Lots of printfs and no Qpid logging statements, and no exception throwing
on error. Please review these and probably should be throwing on errors; outputs should probably
be using logging to be redirected as the user specified.
>>> -> triedto fix this
>>>
>>>> Allow Windows Broker to run as a Service
>>>> ----------------------------------------
>>>>
>>>> Key: QPID-2519
>>>> URL:
>>>> https://issues.apache.org/jira/browse/QPID-2519
>>>> Project: Qpid
>>>> Issue Type: New Feature
>>>> Components: C++ Broker
>>>> Reporter: Kerry Bonin
>>>> Attachments: broker_as_service_Qpid_Logging.patch,
>>>> broker_as_service_r921371.patch
>>>>
>>>>
>>>> The Windows version of the C++ Broker should have the ability to run as a
Windows Service, to correspond with the ability of the *nix version to run as a daemon, as
this is a common requirement for critical software infrastructure elements of enterprise class
software on the Windows platform.
>>>
>>> --
>>> This message is automatically generated by JIRA.
>>> -
>>> You can reply to this email to add a comment to the issue online.
>>>
>>>
>>> --------------------------------------------------------------------
>>> - Apache Qpid - AMQP Messaging Implementation
>>> Project: http://qpid.apache.org
>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
|