[Wrapper-user] Segmentation fault on Mac OSX 10.5.8 ( PowerPC G4 processor)

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

Hi all,

We are using the Java Service Wrapper for one of our applications.
Here are the brief details of the machines we are testing the wrapper application.

1. Mac OSX 10.5.8 (PowerPC G4 processor)
2. Mac OSX 10.5.8 (Core Duo Intel processor)
-  Java version on both the machines is 1.5.0_20

The wrapper works fine on the Core Duo processor machine but fails on the PowerPC processor machine with a segmentation fault. Unfortunately there is not much detailed information about the problem.
FYI, we are running the wrapper from a console.

Here is the log on the console:

Running ActivityLogger Application...
wrapper  | --> Wrapper Started as Console
wrapper  | Java Service Wrapper Community Edition 32-bit 3.3.6
wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All Rights Reserved.
wrapper  |     http://wrapper.tanukisoftware.org
./ActivityLogger: line 492:  2652 Segmentation fault      "/Users/applog/Desktop/PCActivityApp_Mac/executables/./wrapper" "/Users/applog/Desktop/PCActivityApp_Mac/executables/../conf/wrapper.conf" wrapper.syslog.ident="ActivityLogger" wrapper.pidfile="/Users/applog/Desktop/PCActivityApp_Mac/executables/./ActivityLogger.pid" wrapper.name="ActivityLogger" wrapper.displayname="ActivityLogger Application"

Here is the conf file of our wrapper for your perusal.

#********************************************************************
# Wrapper License Properties (Ignored by Community Edition)
#********************************************************************
# Include file problems can be debugged by removing the first '#'
#  from the following line:
##include.debug
#include ../conf/wrapper-license.conf
#include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf

#********************************************************************
# Wrapper Java Properties
#********************************************************************
# Java Application
wrapper.java.command=java

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

# 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=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.app.parameter.1=com.activitylogger.ActivityLogger

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

# 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=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.waitForStartMain=TRUE
wrapper.java.additional.2=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.maxStartMainWait=60
wrapper.java.additional.3=-Dcommand.logData=activewin_mac -logData
wrapper.java.additional.4=-DdatabaseLocation=../executables/data/activitylog

# 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

# 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=../logs/wrapper.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
wrapper.logfile.loglevel=DEBUG

# 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.adviser=TRUE

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

# Title to use when running as a console
wrapper.console.title=ActivityLogger Application (console mode)

#********************************************************************
# 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=ActivityLogger

# Display name of the service
wrapper.displayname=ActivityLogger Application

# Description of the service
wrapper.description=Logs the system activity

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

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

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

We have also re-installed the OS to see if it fixes the problem, but it's still the same.
Having invested a huge amount of time in figuring out the issue and still not finding the solution,
we have decided to post a question in this forum.

May I ask if any one had this problem, and if yes what is the solution?

Many thanks,
JBrain