Return-Path: Delivered-To: apmail-qpid-dev-archive@www.apache.org Received: (qmail 50894 invoked from network); 30 Sep 2010 14:29:33 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 Sep 2010 14:29:33 -0000 Received: (qmail 88113 invoked by uid 500); 30 Sep 2010 14:29:33 -0000 Delivered-To: apmail-qpid-dev-archive@qpid.apache.org Received: (qmail 87916 invoked by uid 500); 30 Sep 2010 14:29:29 -0000 Mailing-List: contact dev-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@qpid.apache.org Delivered-To: mailing list dev@qpid.apache.org Received: (qmail 87908 invoked by uid 99); 30 Sep 2010 14:29:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Sep 2010 14:29:28 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Daniel.Sack@techtalk.at designates 80.245.197.108 as permitted sender) Received: from [80.245.197.108] (HELO ttv-mail02.techtalk.at) (80.245.197.108) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Sep 2010 14:29:21 +0000 Received: from ttv-mail02.corp.techtalk.at ([192.168.0.240]) by ttv-mail02.corp.techtalk.at ([192.168.0.240]) with mapi; Thu, 30 Sep 2010 16:28:56 +0200 From: Daniel Sack To: "dev@qpid.apache.org" , "kerrybonin@gmail.com" Date: Thu, 30 Sep 2010 16:29:00 +0200 Subject: RE: [jira] Updated: (QPID-2519) Allow Windows Broker to run as a Service Thread-Topic: [jira] Updated: (QPID-2519) Allow Windows Broker to run as a Service Thread-Index: Acteb1dklItSZbHpSl2GhFj3cUtV8wCPGBzw Message-ID: <4E25318A57275043A57FA9CAB71775AA31FBA6BFCE@ttv-mail02.corp.techtalk.at> References: <555957.90291271776909192.JavaMail.jira@thor> <30876504.422501285605632546.JavaMail.jira@thor> <4E25318A57275043A57FA9CAB71775AA31FBA6BA16@ttv-mail02.corp.techtalk.at> <4E25318A57275043A57FA9CAB71775AA31FBA6BA2D@ttv-mail02.corp.techtalk.at> In-Reply-To: Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE, en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Why do you think it had to do with the service name string? -----Original Message----- From: Kerry Bonin [mailto:kerrybonin@gmail.com]=20 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 S= ervice 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 th= at 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 wrot= e: > 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 i= n 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=20 > as a Service > > By default I believe it runs as LocalService. =A0I 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. =A0I suspect that was only be= cause I wasn't specifying the user in the string format that SCM expected (= something like {hostname}/{account name}), but I got distracted after playi= ng for a few mins and haven't returned yet. > > > On Mon, Sep 27, 2010 at 11:55 AM, Daniel Sack w= rote: >> 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: "LocalSys= tem" or "NetworkService" >> >> If we want to start the broker as "LocalSystem" it won't start with erro= r 1503. >> Can you answer me why? >> >> We have tried to use xyntservice (http://www.codeproject.com/KB/system/x= yntservice.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 t= he 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=20 >> 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) wrote: >>> >>> =A0 =A0 [ >>> https://issues.apache.org/jira/browse/QPID-2519?page=3Dcom.atlassian.j >>> i r a.plugin.system.issuetabpanels:all-tabpanel ] >>> >>> Daniel Sack updated QPID-2519: >>> ------------------------------ >>> >>> =A0 =A0Attachment: broker_as_service_Qpid_Logging.patch >>> >>> Hi, >>> Scince we need this patch for our production system, I tried to=20 >>> implement parts of the comments 1. Please reformat according to Qpid=20 >>> coding style (http://qpid.apache.org/qpid-c-documentation.html) - no=20 >>> 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 thr= owing on error. Please review these and probably should be throwing on erro= rs; outputs should probably be using logging to be redirected as the user s= pecified. >>> -> triedto fix this >>> >>>> Allow Windows Broker to run as a Service >>>> ---------------------------------------- >>>> >>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Key: QPID-2519 >>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 URL:=20 >>>> https://issues.apache.org/jira/browse/QPID-2519 >>>> =A0 =A0 =A0 =A0 =A0 =A0 Project: Qpid >>>> =A0 =A0 =A0 =A0 =A0Issue Type: New Feature >>>> =A0 =A0 =A0 =A0 =A0Components: C++ Broker >>>> =A0 =A0 =A0 =A0 =A0 =A0Reporter: Kerry Bonin >>>> =A0 =A0 =A0 =A0 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 a= s 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 infr= astructure 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: =A0 =A0 =A0http://qpid.apache.org >>> Use/Interact: mailto:dev-subscribe@qpid.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> Apache Qpid - AMQP Messaging Implementation >> Project: =A0 =A0 =A0http://qpid.apache.org >> Use/Interact: mailto:dev-subscribe@qpid.apache.org >> >> > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: =A0 =A0 =A0http://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