Re: [Wrapper-user] Wrapper binarie doesn't work with pdf Printer

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Leif
We are running the wrapper as a service, I confirm that we have 2 processus : java.exe and wrapper.exe as SYSTEM user.
Our pdf Printer is a registered printer.
Here the wrapper.conf, Attached the log.
I currently doing test following your advice.

#encoding=UTF-8
# Configuration files must begin with a line specifying the encoding
#  of the the file.

#********************************************************************
# Wrapper License Properties (Ignored by Community Edition)
#********************************************************************
# Professional and Standard Editions of the Wrapper require a valid
#  License Key to start.  Licenses can be purchased or a trial license
#  requested on the following pages:
# http://wrapper.tanukisoftware.com/purchase
# http://wrapper.tanukisoftware.com/trial

# Include file problems can be debugged by removing the first '#'
#  from the following line:
##include.debug

# The Wrapper will look for either of the following optional files for a
#  valid License Key.  License Key properties can optionally be included
#  directly in this configuration file.
#include ../conf/wrapper-license.conf
#include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf

# The following property will output information about which License Key(s)
#  are being found, and can aid in resolving any licensing problems.
#wrapper.license.debug=TRUE

#********************************************************************
# Wrapper Localization
#********************************************************************
# Specify the locale which the Wrapper should use.  By default the system
#  locale is used.
#wrapper.lang=en_US # en_US or ja_JP

# Specify the location of the Wrapper's language resources.  If these are
#  missing, the Wrapper will default to the en_US locale.
wrapper.lang.folder=../lang

#********************************************************************
# Wrapper Java Properties
#********************************************************************
# Java Application
#  Locate the java binary on the system PATH:
wrapper.java.command=java
#  Specify a specific java binary:
#set.JAVA_HOME=/java/path
#wrapper.java.command=%JAVA_HOME%/bin/java

# Tell the Wrapper to log the full generated Java command line.
#wrapper.java.command.loglevel=INFO

# Java Main class.  This class must implement the WrapperListener interface
#  or guarantee that the WrapperManager class is initialized.  Helper
#  classes are provided to do this for you.  See the Integration section
#  of the documentation for details.
wrapper.java.mainclass=ad6.printserver.server.AD6PrintServerAppWR

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=ad6printserver.jar
wrapper.java.classpath.2=lib/*.jar
wrapper.java.classpath.3=lib/*.zip

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=lib

# Java Bits.  On applicable platforms, tells the JVM to run in 32 or 64-bit mode.
wrapper.java.additional.auto_bits=TRUE

# Java Additional Parameters
wrapper.java.additional.1=

# Initial Java Heap Size (in MB)
#wrapper.java.initmemory=3

# Maximum Java Heap Size (in MB)
#wrapper.java.maxmemory=64

# Application parameters.  Add parameters as needed starting from 1
wrapper.app.parameter.1=

#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Enables Debug output from the Wrapper.
wrapper.debug=TRUE
wrapper.environment.dump=TRUE

# Format of output for the console.  (See docs for formats)
wrapper.console.format=PM

# Log Level for console output.  (See docs for log levels)
wrapper.console.loglevel=INFO

# Log file to use for wrapper output logging.
wrapper.logfile=conf/wrapper.log
#wrapper.logfile=ad6printserver.log

# Format of output for the log file.  (See docs for formats)
wrapper.logfile.format=LPTM

# Log Level for log file output.  (See docs for log levels)
wrapper.logfile.loglevel=INFO

# Maximum size that the log file will be allowed to grow to before
#  the log is rolled. Size is specified in bytes.  The default value
#  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
#  'm' (mb) suffix.  For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=0

# Maximum number of rolled log files which will be allowed before old
#  files are deleted.  The default value of 0 implies no limit.
wrapper.logfile.maxfiles=0

# Log Level for sys/event log output.  (See docs for log levels)
wrapper.syslog.loglevel=NONE

#********************************************************************
# Wrapper General Properties
#********************************************************************
# Allow for the use of non-contiguous numbered properties
wrapper.ignore_sequence_gaps=TRUE

# Do not start if the pid file already exists.
wrapper.pidfile.strict=TRUE

# Title to use when running as a console
wrapper.console.title=Test Wrapper Sample Application

#********************************************************************
# Wrapper JVM Checks
#********************************************************************
# Detect DeadLocked Threads in the JVM. (Requires Standard Edition)
wrapper.check.deadlock=TRUE
wrapper.check.deadlock.interval=10
wrapper.max_failed_invocations=99
wrapper.console.fatal_to_stderr=FALSE
wrapper.console.error_to_stderr=FALSE
wrapper.check.deadlock.action=RESTART
wrapper.check.deadlock.output=FULL

# Out Of Memory detection.
# (Simple match)
wrapper.filter.trigger.1000=java.lang.OutOfMemoryError
# (Only match text in stack traces if -XX:+PrintClassHistogram is being used.)
#wrapper.filter.trigger.1000=Exception in thread "*" java.lang.OutOfMemoryError
#wrapper.filter.allow_wildcards.1000=TRUE
wrapper.filter.action.1000=RESTART
wrapper.filter.message.1000=The JVM has run out of memory.

#********************************************************************
# Wrapper Email Notifications. (Requires Professional Edition)
#********************************************************************
# Common Event Email settings.
#wrapper.event.default.email.debug=TRUE
#wrapper.event.default.email.smtp.host=<SMTP_Host>
#wrapper.event.default.email.smtp.port=25
#wrapper.event.default.email.subject=[%WRAPPER_HOSTNAME%:%WRAPPER_NAME%:%WRAPPER_EVENT_NAME%] Event Notification
#wrapper.event.default.email.sender=<Sender email>
#wrapper.event.default.email.recipient=<Recipient email>

# Configure the log attached to event emails.
#wrapper.event.default.email.attach_log=TRUE
#wrapper.event.default.email.maillog.lines=50
#wrapper.event.default.email.maillog.format=LPTM
#wrapper.event.default.email.maillog.loglevel=INFO

# Enable specific event emails.
#wrapper.event.wrapper_start.email=TRUE
#wrapper.event.jvm_prelaunch.email=TRUE
#wrapper.event.jvm_start.email=TRUE
#wrapper.event.jvm_started.email=TRUE
#wrapper.event.jvm_deadlock.email=TRUE
#wrapper.event.jvm_stop.email=TRUE
#wrapper.event.jvm_stopped.email=TRUE
#wrapper.event.jvm_restart.email=TRUE
#wrapper.event.jvm_failed_invocation.email=TRUE
#wrapper.event.jvm_max_failed_invocations.email=TRUE
#wrapper.event.jvm_kill.email=TRUE
#wrapper.event.jvm_killed.email=TRUE
#wrapper.event.jvm_unexpected_exit.email=TRUE
#wrapper.event.wrapper_stop.email=TRUE

# Specify custom mail content
wrapper.event.jvm_restart.email.body=The JVM was restarted.\n\nPlease check on its status.\n

#********************************************************************
# Wrapper Windows NT/2000/XP Service Properties
#********************************************************************
# WARNING - Do not modify any of these properties when an application
#  using this configuration file has been installed as a service.
#  Please uninstall the service before modifying this section.  The
#  service can then be reinstalled.

# Name of the service
wrapper.name=AD6PrintServer

# Display name of the service
wrapper.displayname=AD6PrintServer

# Description of the service
wrapper.description=AD6PrintServer Description

# Service dependencies.  Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=

# Mode in which the service is installed.  AUTO_START, DELAY_START or DEMAND_START
wrapper.ntservice.starttype=DEMAND_START

# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false

  ----- Original Message ----- 
  From: Leif Mortenson 
  To: Wrapper User List 
  Sent: Thursday, May 07, 2015 4:34 AM
  Subject: Re: [Wrapper-user] Wrapper binarie doesn't work with pdf Printer

  Etienne

  How are you running the Wrapper?  As a service?
  If so then it will be running as the SYSTEM user by default.
  The SYSTEM user has its own environment and path, as well as restrictions on network access.

  I am not clear, is your pdf printer a registered printer?  Or an executable you are trying to run?

  You can debug the active environment with the following property:
  wrapper.environment.dump=TRUE

  http://wrapper.tanukisoftware.com/doc/english/prop-environment-dump.html

  You may need to setup your printer in a specific user and then configure the Wrapper to run as that user.
  Please read over the following:
  http://wrapper.tanukisoftware.com/doc/english/prop-ntservice-account.html

  It is also possible to configure the Wrapper so it can access remote Printers and Network Shares without having to first set them up in that account.  Not sure if this is useful to you:
  http://wrapper.tanukisoftware.com/doc/english/prop-share-general.html

  Cheers,
  Leif

  On Thu, May 7, 2015 at 12:00 AM, Tu T. Nguyen <ttn...@ra...> wrote:

    Please see the following link for information regarding windows services.

    http://windows.microsoft.com/en-us/windows-vista/manage-services-in-windows-vista-from-windows-vista-inside-out

    Under startup options you can see the tab for “Log On”  Make sure you choose “This Account:” and specify a username and password that has at least local administrator privileges. 

    From: Etienne de Dieuleveult [mailto:e.d...@ad...] 
    Sent: Tuesday, May 05, 2015 6:04 AM
    To: wra...@li...

    Subject: Re: [Wrapper-user] Wrapper binarie doesn't work with pdf Printer

    I' don't know if it's a matter of administrator account, we reproduce this problem on other PC and we are connected as Administrator.

    If you know how to assign an administrator account to the Windows Service ?

    When we send documents to pdf Printer, the System launch binaries such PDFCreator.exe, maybe we need to manage permission in the 

    wrapper to execute binaries ?

    ----- Original Message ----- 

      From: Tu T. Nguyen 

      To: wra...@li... 

      Sent: Monday, May 04, 2015 6:35 PM

      Subject: Re: [Wrapper-user] Wrapper binarie doesn't work with pdf Printer

      Maybe this is a permissions issue.  Have you tried assigning the Windows service an administrator account instead of using the service account?

      From: Etienne de Dieuleveult [mailto:e.d...@ad...] 
      Sent: Monday, May 04, 2015 6:46 AM
      To: wra...@li...
      Subject: [Wrapper-user] Wrapper binarie doesn't work with pdf Printer

      I,

      We use your wrapper (wrapper-windows-x86-32-3.5.26) to launch a java application as a Windows Service (Vista OS).

      Our java application generates documents, whose sent to physical Printer (Canon, HP ...) for the printing, and that's works fine.

      If we send document to pdf Printer (PDFCreator or doPDF) it doesn't work ! And we have no Error and no trace in log file.

      Perhap's, there is a parameter to be matched in the wrapperapp.conf, we would not have seen ?

      Thank's for your help.

      E. de Dieuleveult.

------------------------------------------------------------------------------

  ------------------------------------------------------------------------------
  One dashboard for servers and applications across Physical-Virtual-Cloud 
  Widest out-of-the-box monitoring support with 50+ applications
  Performance metrics, stats and reports that give you Actionable Insights
  Deep dive visibility with transaction tracing using APM Insight.
  http://ad.doubleclick.net/ddm/clk/290420510;117567292;y

------------------------------------------------------------------------------

  _______________________________________________
  Wrapper-user mailing list
  Wra...@li...
  https://lists.sourceforge.net/lists/listinfo/wrapper-user