[Xml-compile] Win32, disable Daemon log to windows eventlog

Robin V. robinsp at gmail.com
Mon Mar 15 00:02:14 GMT 2010


You were right, as soon as the script 'use
XML::Compile::SOAP::HTTPDaemon;', the logs go to windows eventlog via
sys::syslog.

Commenting line 15 of XML::Compile::SOAP::Daemon ( dispatcher SYSLOG
=> 'default'; ) is enough to get the messages back to the standard
output.

Using your example for callback registration (what I wrote was
definitely wrong), there is no more complains, neither in
HTTPDaemon->new, nor with $daemon->operationsFromWSDL.

The only unexpected message is (it doesn't seem to be very important):
Use of uninitialized value $version in hash element at
C:/strawberry/perl/site/lib/XML/Compile/SOAP/Daemon.pm line 262.
when I use $daemon->printIndex; Could it be that there's a soap
version missing in callback registration? $daemon->soapVersions only
reports SOAP11. That seems logical as that's the only port in this
wsdl.

Every issue were either bad wsdl file or wrong use of the API. Many
thanks again for helping me to solve problems.

So bad it doesn't work yet, but this problem will be solved elsewhere
as it seems to be a problem with Net Server on win32... I won't bother
you with that ;).

Best regards,
Robin

PS: just for the history
error: 2010/03/15-00:47:12 POSIX::sigemptyset not implemented on this
architecture at C:/strawberry/perl/site/lib/Net/Se
rver/Daemonize.pm line 233.

  at line 293 in file C:/strawberry/perl/site/lib/Net/Server.pm
 at C:/strawberry/perl/site/lib/XML/Compile/SOAP/Daemon.pm line 129
Net::Server::fatal(XML::Compile::SOAP::HTTPDaemon=HASH(0x36fdbc4),
"POSIX::sigemptyset not implemented on this architect
ure at C:/strawberry/perl/site/lib/Net/Server/Daemonize.pm line
233.\n") at C:/strawberry/perl/site/lib/Net/Server.pm li
ne 293
Net::Server::post_configure(XML::Compile::SOAP::HTTPDaemon=HASH(0x36fdbc4))
at C:/strawberry/perl/site/lib/Net/Server/Pr
eForkSimple.pm line 58
Net::Server::PreForkSimple::post_configure(XML::Compile::SOAP::HTTPDaemon=HASH(0x36fdbc4))
at C:/strawberry/perl/site/li
b/Net/Server/PreFork.pm line 73
Net::Server::PreFork::post_configure(XML::Compile::SOAP::HTTPDaemon=HASH(0x36fdbc4))
at C:/strawberry/perl/site/lib/XML/
Compile/SOAP/Daemon.pm line 119
XML::Compile::SOAP::Daemon::post_configure(XML::Compile::SOAP::HTTPDaemon=HASH(0x36fdbc4))
at C:/strawberry/perl/site/li
b/Net/Server.pm line 100
Net::Server::run(XML::Compile::SOAP::HTTPDaemon=HASH(0x36fdbc4),
"no_client_stdout", 1) at C:/strawberry/perl/site/lib/X
ML/Compile/SOAP/Daemon.pm line 143
XML::Compile::SOAP::Daemon::run(XML::Compile::SOAP::HTTPDaemon=HASH(0x36fdbc4))
at J:\XXX\test-xml-compile-siri-server.pl line 95



On Sun, Mar 14, 2010 at 11:41 PM, Mark Overmeer <mark at overmeer.net> wrote:
> * Robin V. (robinsp at gmail.com) [100314 21:02]:
>> I'm not sure the way it is registered is the good one:
>>
>> $daemon->operationsFromWSDL($wsdl,
>>    callbacks => { default_callback => \&my_callback } );
>
>  $daemon->operationsFromWSDL($wsdl,
>     default_callback => \&my_callback,
>     callbacks => {...} );
>
>> Anyway, do you have any clue on how to replace the Sys::Syslog used by
>> Log::Report::Dispatcher? I'd like to see logs on the standard error
>> instead of windows event logger used by sys::syslog, but I can't
>> easily find where to look for information on how to change this.
>
> I do not know how your script looks exactly.
> See XML/Compile/SOAP/Daemon::post_configure().
>
> The default logger is Log::Report.  Then, somewhere in the daemon,
> you start logging to syslog:
>
>    dispatcher SYSLOG => 'default';  # replace default output
>
> or
>    dispatcher SYSLOG => 'syslog';   # some other output name
>    dispatcher close  => 'default';  # then close perl out.
> --
> Regards,
>
>               MarkOv
>
> ------------------------------------------------------------------------
>       Mark Overmeer MSc                                MARKOV Solutions
>       Mark at Overmeer.net                          solutions at overmeer.net
> http://Mark.Overmeer.net                   http://solutions.overmeer.net
>
>



More information about the Xml-compile mailing list