RE: WO application failing to load UNIXClassPath.txt
Chuck,
I tried putting the wolips.properties file on the Unix build server in the PATH
and we are still seeing the same issue of the application starting without
loading the CLASSPATH and the launch script being created incorrectly.
Is it necessary to have the wolips.properties file in a particular directory?
Any other information on how the launch scripts are built? Any other ideas?
Thanks,
Terry Soles
214-273-3916
(v922) 3916
-Original Message-
From: webobjects-deploy-bounces+terry.soles=verizon@lists.apple.com
[mailto:webobjects-deploy-bounces+terry.soles=verizon@lists.apple.com] On
Behalf Of Soles, James T
Sent: Wednesday, April 03, 2013 8:39 AM
To: Chuck Hill
Cc: webobjects-deploy@lists.apple.com
Subject: RE: WO application failing to load UNIXClassPath.txt
Chuck,
I'm a little confused. In the text of the link you provided it mentions a
wolips.properties file but in your email you mention a WebObjects.properties
file. Which file should I be looking for?
On the Mac where we are getting a good build I find a wolips.properties file at
/Users/terrysoles/Library/Application Support/WOLips and the
WebObjects.properties file does not have an entry in it for the wo.bootstrapjar.
On the Unix server where the build is not generating the correct files, these
files do not exist as you speculated. Assuming that the file I am looking for
and need to put on the Unix server is wolips.properties, where should this file
be placed? Does it just need to be somewhere within the PATH?
Thanks,
Terry Soles
214-273-3916
(v922) 3916
-Original Message-
From: Chuck Hill [mailto:ch...@global-village.net]
Sent: Friday, March 29, 2013 12:19 PM
To: Soles, James T
Cc: webobjects-deploy@lists.apple.com
Subject: Re: WO application failing to load UNIXClassPath.txt
Hi Terry,
Now I see! The machine on which the app is getting built is missing a file or
has it in the wrong location. The build process uses this to determine which
version of WebObjects the app is being built for and based on that it creates a
different launch script. When it can't find this file, it assumes a very old
version of WO.
See http://comments.gmane.org/gmane.comp.web.webobjects.woproject.devel/15616
In your webobjects.properties file you can set (or correct!) the path for this
file:
wo.bootstrapjar=/System/Library/WebObjects/JavaApplications/wotaskd.woa/WOBootstrap.jar
I _think_ that should fix your problem.
Chuck
On 2013-03-29, at 6:55 AM, Soles, James T wrote:
Chuck,
Thanks for the direction on this. I have compared the DecisionQJava (launch
script) created by the two servers and there are significant differences.
Just as an example of one that is likely the primary issue:
* from Mac build that works - eval exec ${JAVA_EXECUTABLE}
${JAVA_EXECUTABLE_ARGS} -classpath WOBootstrap.jar
com.webobjects._bootstrap.WOBootstrap ${COMMAND_LINE_ARGS}
* from New Unix server build that gets errors - eval exec
${JAVA_EXECUTABLE} ${JAVA_EXECUTABLE_ARGS} -classpath ${THE_CLASSPATH}
${APPLICATION_CLASS} ${COMMAND_LINE_ARGS}
Do you know what creates these launch scripts? Where should I look for the
details on how this script gets created and the options it decides to use in
building them?
Thanks,
Terry Soles
214-273-3916
(v922) 3916
-Original Message-
From: Chuck Hill [mailto:ch...@global-village.net]
Sent: Thursday, March 28, 2013 3:25 PM
To: Soles, James T
Cc: webobjects-deploy@lists.apple.com
Subject: Re: WO application failing to load UNIXClassPath.txt
If it is from an NSLog rather than System.out.println then at least part of
the classpath is getting loaded. You might want to call code like this from
main to see what sort of classpath is getting generated:
static public String dumpJVMConfiguration()
{
StringBuffer output = new StringBuffer(\nSystem Properties
Follow\n);
Properties systemProperties = System.getProperties();
Enumeration propertyNames = systemProperties.propertyNames();
while (propertyNames.hasMoreElements())
{
String propertyName = (String) propertyNames.nextElement();
if (propertyName.equals(java.class.path) ||
propertyName.equals(com.webobjects.classpath))
{
output.append(Classpath\n);
String pathSeparator =
systemProperties.getProperty(path.separator);
NSArray classPathComponents =
NSArray.componentsSeparatedByString(systemProperties.getProperty(propertyName),
pathSeparator);
Enumeration classpathEnumeration =
classPathComponents.objectEnumerator();
while (classpathEnumeration.hasMoreElements())
{
String jarPath = (String)
classpathEnumeration.nextElement();
output.append(jarPath + \n
Re: WO application failing to load UNIXClassPath.txt
Hi Terry,
Yes, it needs to be in a specific place. See
http://wiki.wocommunity.org/display/WOL/wolips.properties
Chuck
On 2013-04-08, at 6:25 AM, Soles, James T wrote:
Chuck,
I tried putting the wolips.properties file on the Unix build server in the
PATH and we are still seeing the same issue of the application starting
without loading the CLASSPATH and the launch script being created incorrectly.
Is it necessary to have the wolips.properties file in a particular directory?
Any other information on how the launch scripts are built? Any other ideas?
Thanks,
Terry Soles
214-273-3916
(v922) 3916
-Original Message-
From: webobjects-deploy-bounces+terry.soles=verizon@lists.apple.com
[mailto:webobjects-deploy-bounces+terry.soles=verizon@lists.apple.com] On
Behalf Of Soles, James T
Sent: Wednesday, April 03, 2013 8:39 AM
To: Chuck Hill
Cc: webobjects-deploy@lists.apple.com
Subject: RE: WO application failing to load UNIXClassPath.txt
Chuck,
I'm a little confused. In the text of the link you provided it mentions a
wolips.properties file but in your email you mention a WebObjects.properties
file. Which file should I be looking for?
On the Mac where we are getting a good build I find a wolips.properties file
at /Users/terrysoles/Library/Application Support/WOLips and the
WebObjects.properties file does not have an entry in it for the
wo.bootstrapjar.
On the Unix server where the build is not generating the correct files, these
files do not exist as you speculated. Assuming that the file I am looking
for and need to put on the Unix server is wolips.properties, where should
this file be placed? Does it just need to be somewhere within the PATH?
Thanks,
Terry Soles
214-273-3916
(v922) 3916
-Original Message-
From: Chuck Hill [mailto:ch...@global-village.net]
Sent: Friday, March 29, 2013 12:19 PM
To: Soles, James T
Cc: webobjects-deploy@lists.apple.com
Subject: Re: WO application failing to load UNIXClassPath.txt
Hi Terry,
Now I see! The machine on which the app is getting built is missing a file
or has it in the wrong location. The build process uses this to determine
which version of WebObjects the app is being built for and based on that it
creates a different launch script. When it can't find this file, it assumes
a very old version of WO.
See http://comments.gmane.org/gmane.comp.web.webobjects.woproject.devel/15616
In your webobjects.properties file you can set (or correct!) the path for
this file:
wo.bootstrapjar=/System/Library/WebObjects/JavaApplications/wotaskd.woa/WOBootstrap.jar
I _think_ that should fix your problem.
Chuck
On 2013-03-29, at 6:55 AM, Soles, James T wrote:
Chuck,
Thanks for the direction on this. I have compared the DecisionQJava (launch
script) created by the two servers and there are significant differences.
Just as an example of one that is likely the primary issue:
* from Mac build that works - eval exec ${JAVA_EXECUTABLE}
${JAVA_EXECUTABLE_ARGS} -classpath WOBootstrap.jar
com.webobjects._bootstrap.WOBootstrap ${COMMAND_LINE_ARGS}
* from New Unix server build that gets errors - eval exec
${JAVA_EXECUTABLE} ${JAVA_EXECUTABLE_ARGS} -classpath ${THE_CLASSPATH}
${APPLICATION_CLASS} ${COMMAND_LINE_ARGS}
Do you know what creates these launch scripts? Where should I look for the
details on how this script gets created and the options it decides to use in
building them?
Thanks,
Terry Soles
214-273-3916
(v922) 3916
-Original Message-
From: Chuck Hill [mailto:ch...@global-village.net]
Sent: Thursday, March 28, 2013 3:25 PM
To: Soles, James T
Cc: webobjects-deploy@lists.apple.com
Subject: Re: WO application failing to load UNIXClassPath.txt
If it is from an NSLog rather than System.out.println then at least part of
the classpath is getting loaded. You might want to call code like this from
main to see what sort of classpath is getting generated:
static public String dumpJVMConfiguration()
{
StringBuffer output = new StringBuffer(\nSystem Properties
Follow\n);
Properties systemProperties = System.getProperties();
Enumeration propertyNames = systemProperties.propertyNames();
while (propertyNames.hasMoreElements())
{
String propertyName = (String) propertyNames.nextElement();
if (propertyName.equals(java.class.path) ||
propertyName.equals(com.webobjects.classpath))
{
output.append(Classpath\n);
String pathSeparator =
systemProperties.getProperty(path.separator);
NSArray classPathComponents =
NSArray.componentsSeparatedByString(systemProperties.getProperty(propertyName),
pathSeparator);
Enumeration classpathEnumeration
RE: WO application failing to load UNIXClassPath.txt
Chuck,
I'm a little confused. In the text of the link you provided it mentions a
wolips.properties file but in your email you mention a WebObjects.properties
file. Which file should I be looking for?
On the Mac where we are getting a good build I find a wolips.properties file at
/Users/terrysoles/Library/Application Support/WOLips and the
WebObjects.properties file does not have an entry in it for the wo.bootstrapjar.
On the Unix server where the build is not generating the correct files, these
files do not exist as you speculated. Assuming that the file I am looking for
and need to put on the Unix server is wolips.properties, where should this file
be placed? Does it just need to be somewhere within the PATH?
Thanks,
Terry Soles
214-273-3916
(v922) 3916
-Original Message-
From: Chuck Hill [mailto:ch...@global-village.net]
Sent: Friday, March 29, 2013 12:19 PM
To: Soles, James T
Cc: webobjects-deploy@lists.apple.com
Subject: Re: WO application failing to load UNIXClassPath.txt
Hi Terry,
Now I see! The machine on which the app is getting built is missing a file or
has it in the wrong location. The build process uses this to determine which
version of WebObjects the app is being built for and based on that it creates a
different launch script. When it can't find this file, it assumes a very old
version of WO.
See http://comments.gmane.org/gmane.comp.web.webobjects.woproject.devel/15616
In your webobjects.properties file you can set (or correct!) the path for this
file:
wo.bootstrapjar=/System/Library/WebObjects/JavaApplications/wotaskd.woa/WOBootstrap.jar
I _think_ that should fix your problem.
Chuck
On 2013-03-29, at 6:55 AM, Soles, James T wrote:
Chuck,
Thanks for the direction on this. I have compared the DecisionQJava (launch
script) created by the two servers and there are significant differences.
Just as an example of one that is likely the primary issue:
* from Mac build that works - eval exec ${JAVA_EXECUTABLE}
${JAVA_EXECUTABLE_ARGS} -classpath WOBootstrap.jar
com.webobjects._bootstrap.WOBootstrap ${COMMAND_LINE_ARGS}
* from New Unix server build that gets errors - eval exec
${JAVA_EXECUTABLE} ${JAVA_EXECUTABLE_ARGS} -classpath ${THE_CLASSPATH}
${APPLICATION_CLASS} ${COMMAND_LINE_ARGS}
Do you know what creates these launch scripts? Where should I look for the
details on how this script gets created and the options it decides to use in
building them?
Thanks,
Terry Soles
214-273-3916
(v922) 3916
-Original Message-
From: Chuck Hill [mailto:ch...@global-village.net]
Sent: Thursday, March 28, 2013 3:25 PM
To: Soles, James T
Cc: webobjects-deploy@lists.apple.com
Subject: Re: WO application failing to load UNIXClassPath.txt
If it is from an NSLog rather than System.out.println then at least part of
the classpath is getting loaded. You might want to call code like this from
main to see what sort of classpath is getting generated:
static public String dumpJVMConfiguration()
{
StringBuffer output = new StringBuffer(\nSystem Properties
Follow\n);
Properties systemProperties = System.getProperties();
Enumeration propertyNames = systemProperties.propertyNames();
while (propertyNames.hasMoreElements())
{
String propertyName = (String) propertyNames.nextElement();
if (propertyName.equals(java.class.path) ||
propertyName.equals(com.webobjects.classpath))
{
output.append(Classpath\n);
String pathSeparator =
systemProperties.getProperty(path.separator);
NSArray classPathComponents =
NSArray.componentsSeparatedByString(systemProperties.getProperty(propertyName),
pathSeparator);
Enumeration classpathEnumeration =
classPathComponents.objectEnumerator();
while (classpathEnumeration.hasMoreElements())
{
String jarPath = (String)
classpathEnumeration.nextElement();
output.append(jarPath + \n);
try
{
File jarFile = new File(jarPath);
output.append((jarFile.isFile() ? -- Exists\n :
*** -- Does not Exist!\n));
}
catch (Throwable t)
{
output.append(Exception validating classpath: + t +
\n);
}
}
}
else
{
output.append(propertyName + = +
systemProperties.getProperty(propertyName) + \n);
}
}
return output.toString();
}
Otherwise, take a look at the launch script in the .woa bundle and see what
it is doing (bash).
Chuck
On 2013-03-28, at 11:09 AM, Soles, James T wrote
Re: WO application failing to load UNIXClassPath.txt
On 2013-04-03, at 5:39 AM, Soles, James T wrote:
Chuck,
I'm a little confused. In the text of the link you provided it mentions a
wolips.properties file but in your email you mention a WebObjects.properties
file. Which file should I be looking for?
wolips.properties
On the Mac where we are getting a good build I find a wolips.properties file
at /Users/terrysoles/Library/Application Support/WOLips and the
WebObjects.properties file does not have an entry in it for the
wo.bootstrapjar.
On the Unix server where the build is not generating the correct files, these
files do not exist as you speculated. Assuming that the file I am looking
for and need to put on the Unix server is wolips.properties, where should
this file be placed? Does it just need to be somewhere within the PATH?
See http://wiki.wocommunity.org/display/WOL/wolips.properties
Chuck
Thanks,
Terry Soles
214-273-3916
(v922) 3916
-Original Message-
From: Chuck Hill [mailto:ch...@global-village.net]
Sent: Friday, March 29, 2013 12:19 PM
To: Soles, James T
Cc: webobjects-deploy@lists.apple.com
Subject: Re: WO application failing to load UNIXClassPath.txt
Hi Terry,
Now I see! The machine on which the app is getting built is missing a file
or has it in the wrong location. The build process uses this to determine
which version of WebObjects the app is being built for and based on that it
creates a different launch script. When it can't find this file, it assumes
a very old version of WO.
See http://comments.gmane.org/gmane.comp.web.webobjects.woproject.devel/15616
In your webobjects.properties file you can set (or correct!) the path for
this file:
wo.bootstrapjar=/System/Library/WebObjects/JavaApplications/wotaskd.woa/WOBootstrap.jar
I _think_ that should fix your problem.
Chuck
On 2013-03-29, at 6:55 AM, Soles, James T wrote:
Chuck,
Thanks for the direction on this. I have compared the DecisionQJava (launch
script) created by the two servers and there are significant differences.
Just as an example of one that is likely the primary issue:
* from Mac build that works - eval exec ${JAVA_EXECUTABLE}
${JAVA_EXECUTABLE_ARGS} -classpath WOBootstrap.jar
com.webobjects._bootstrap.WOBootstrap ${COMMAND_LINE_ARGS}
* from New Unix server build that gets errors - eval exec
${JAVA_EXECUTABLE} ${JAVA_EXECUTABLE_ARGS} -classpath ${THE_CLASSPATH}
${APPLICATION_CLASS} ${COMMAND_LINE_ARGS}
Do you know what creates these launch scripts? Where should I look for the
details on how this script gets created and the options it decides to use in
building them?
Thanks,
Terry Soles
214-273-3916
(v922) 3916
-Original Message-
From: Chuck Hill [mailto:ch...@global-village.net]
Sent: Thursday, March 28, 2013 3:25 PM
To: Soles, James T
Cc: webobjects-deploy@lists.apple.com
Subject: Re: WO application failing to load UNIXClassPath.txt
If it is from an NSLog rather than System.out.println then at least part of
the classpath is getting loaded. You might want to call code like this from
main to see what sort of classpath is getting generated:
static public String dumpJVMConfiguration()
{
StringBuffer output = new StringBuffer(\nSystem Properties
Follow\n);
Properties systemProperties = System.getProperties();
Enumeration propertyNames = systemProperties.propertyNames();
while (propertyNames.hasMoreElements())
{
String propertyName = (String) propertyNames.nextElement();
if (propertyName.equals(java.class.path) ||
propertyName.equals(com.webobjects.classpath))
{
output.append(Classpath\n);
String pathSeparator =
systemProperties.getProperty(path.separator);
NSArray classPathComponents =
NSArray.componentsSeparatedByString(systemProperties.getProperty(propertyName),
pathSeparator);
Enumeration classpathEnumeration =
classPathComponents.objectEnumerator();
while (classpathEnumeration.hasMoreElements())
{
String jarPath = (String)
classpathEnumeration.nextElement();
output.append(jarPath + \n);
try
{
File jarFile = new File(jarPath);
output.append((jarFile.isFile() ? -- Exists\n :
*** -- Does not Exist!\n));
}
catch (Throwable t)
{
output.append(Exception validating classpath: + t +
\n);
}
}
}
else
{
output.append(propertyName + = +
systemProperties.getProperty(propertyName) + \n);
}
}
return output.toString();
}
Otherwise
RE: WO application failing to load UNIXClassPath.txt
Chuck,
Thanks for the direction on this. I have compared the DecisionQJava (launch
script) created by the two servers and there are significant differences.
Just as an example of one that is likely the primary issue:
* from Mac build that works - eval exec ${JAVA_EXECUTABLE}
${JAVA_EXECUTABLE_ARGS} -classpath WOBootstrap.jar
com.webobjects._bootstrap.WOBootstrap ${COMMAND_LINE_ARGS}
* from New Unix server build that gets errors - eval exec
${JAVA_EXECUTABLE} ${JAVA_EXECUTABLE_ARGS} -classpath ${THE_CLASSPATH}
${APPLICATION_CLASS} ${COMMAND_LINE_ARGS}
Do you know what creates these launch scripts? Where should I look for the
details on how this script gets created and the options it decides to use in
building them?
Thanks,
Terry Soles
214-273-3916
(v922) 3916
-Original Message-
From: Chuck Hill [mailto:ch...@global-village.net]
Sent: Thursday, March 28, 2013 3:25 PM
To: Soles, James T
Cc: webobjects-deploy@lists.apple.com
Subject: Re: WO application failing to load UNIXClassPath.txt
If it is from an NSLog rather than System.out.println then at least part of the
classpath is getting loaded. You might want to call code like this from main
to see what sort of classpath is getting generated:
static public String dumpJVMConfiguration()
{
StringBuffer output = new StringBuffer(\nSystem Properties
Follow\n);
Properties systemProperties = System.getProperties();
Enumeration propertyNames = systemProperties.propertyNames();
while (propertyNames.hasMoreElements())
{
String propertyName = (String) propertyNames.nextElement();
if (propertyName.equals(java.class.path) ||
propertyName.equals(com.webobjects.classpath))
{
output.append(Classpath\n);
String pathSeparator =
systemProperties.getProperty(path.separator);
NSArray classPathComponents =
NSArray.componentsSeparatedByString(systemProperties.getProperty(propertyName),
pathSeparator);
Enumeration classpathEnumeration =
classPathComponents.objectEnumerator();
while (classpathEnumeration.hasMoreElements())
{
String jarPath = (String)
classpathEnumeration.nextElement();
output.append(jarPath + \n);
try
{
File jarFile = new File(jarPath);
output.append((jarFile.isFile() ? -- Exists\n :
*** -- Does not Exist!\n));
}
catch (Throwable t)
{
output.append(Exception validating classpath: + t +
\n);
}
}
}
else
{
output.append(propertyName + = +
systemProperties.getProperty(propertyName) + \n);
}
}
return output.toString();
}
Otherwise, take a look at the launch script in the .woa bundle and see what it
is doing (bash).
Chuck
On 2013-03-28, at 11:09 AM, Soles, James T wrote:
Chuck,
The DecisionQ version 3.0 is coming from an NSLog.out in the application main
(DecisionQ is the application name). The other reason I don't believe that
the classpath is actually being loaded is because once the application does
get started we get some other errors that indicate the class was not found
(java.lang.NoClassDefFoundError).
Here is an example from the log file of one of the errors that I am seeing:
handleRequest: Unknown error occured: java.lang.NoClassDefFoundError:
com/equifax/xml/xmlschema/interconnect/InternationalAddressType
java.lang.NoClassDefFoundError:
com/equifax/xml/xmlschema/interconnect/InternationalAddressType
at GenericHandler.getICData(Unknown Source)
at DecisionQHandler.handleRequest(Unknown Source)
at DecisionQ.processRequest(Unknown Source)
at DecisionQ.main(Unknown Source)
at DecisionQ_main.main(Unknown Source)
Thanks,
Terry Soles
214-273-3916
(v922) 3916
-Original Message-
From: Chuck Hill [mailto:ch...@global-village.net]
Sent: Thursday, March 28, 2013 1:58 PM
To: Soles, James T
Cc: webobjects-deploy@lists.apple.com
Subject: Re: WO application failing to load UNIXClassPath.txt
Where does DecisionQ version 3.0 get output from? If the classpath was not
getting loaded, I would not expect the launch to get very far. More likely
that log output is getting re-directed elsewhere.
Chuck
On 2013-03-28, at 7:47 AM, Soles, James T wrote:
All,
I am in the process of trying to move our build environment and am getting
different results when starting an application from the new build
environment. I'm not sure what we may have missed when setting up the new
build environment but when the application starts
WO application failing to load UNIXClassPath.txt
All, I am in the process of trying to move our build environment and am getting different results when starting an application from the new build environment. I'm not sure what we may have missed when setting up the new build environment but when the application starts from code built there it does not load the UNIXClassPath.txt. The current build environment is a MacBook and we are moving to building on a Solaris Unix platform. The application builds, using ANT, with no issues but when it is deployed, on a different Solaris Unix server, it does not load the UNIXClassPath.txt. When I run the application built on the MacBook I get this at the beginning of the log file: Loading /app/software/Apple/Local/Library/WebObjects/Applications/DecisionQJava.woa/Contents/UNIX/UNIXClassPath.txt Generated classpath: When I run the application built on the Solaris Unix server the first thing in the log file is: DecisionQ version 3.0 (no indication that the classpath file is being loaded). Any thoughts on what we may have failed to load/move to the new build server? Let me know if there are more details that you might need. Thanks, Terry Soles 214-273-3916 (v922) 3916 ___ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to arch...@mail-archive.com
RE: WO application failing to load UNIXClassPath.txt
Chuck, The DecisionQ version 3.0 is coming from an NSLog.out in the application main (DecisionQ is the application name). The other reason I don't believe that the classpath is actually being loaded is because once the application does get started we get some other errors that indicate the class was not found (java.lang.NoClassDefFoundError). Here is an example from the log file of one of the errors that I am seeing: handleRequest: Unknown error occured: java.lang.NoClassDefFoundError: com/equifax/xml/xmlschema/interconnect/InternationalAddressType java.lang.NoClassDefFoundError: com/equifax/xml/xmlschema/interconnect/InternationalAddressType at GenericHandler.getICData(Unknown Source) at DecisionQHandler.handleRequest(Unknown Source) at DecisionQ.processRequest(Unknown Source) at DecisionQ.main(Unknown Source) at DecisionQ_main.main(Unknown Source) Thanks, Terry Soles 214-273-3916 (v922) 3916 -Original Message- From: Chuck Hill [mailto:ch...@global-village.net] Sent: Thursday, March 28, 2013 1:58 PM To: Soles, James T Cc: webobjects-deploy@lists.apple.com Subject: Re: WO application failing to load UNIXClassPath.txt Where does DecisionQ version 3.0 get output from? If the classpath was not getting loaded, I would not expect the launch to get very far. More likely that log output is getting re-directed elsewhere. Chuck On 2013-03-28, at 7:47 AM, Soles, James T wrote: All, I am in the process of trying to move our build environment and am getting different results when starting an application from the new build environment. I'm not sure what we may have missed when setting up the new build environment but when the application starts from code built there it does not load the UNIXClassPath.txt. The current build environment is a MacBook and we are moving to building on a Solaris Unix platform. The application builds, using ANT, with no issues but when it is deployed, on a different Solaris Unix server, it does not load the UNIXClassPath.txt. When I run the application built on the MacBook I get this at the beginning of the log file: Loading /app/software/Apple/Local/Library/WebObjects/Applications/DecisionQJava.woa/Contents/UNIX/UNIXClassPath.txt Generated classpath: When I run the application built on the Solaris Unix server the first thing in the log file is: DecisionQ version 3.0 (no indication that the classpath file is being loaded). Any thoughts on what we may have failed to load/move to the new build server? Let me know if there are more details that you might need. Thanks, Terry Soles 214-273-3916 (v922) 3916 ___ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-deploy/chill%40global-village.net This email sent to ch...@global-village.net -- Chuck Hill Executive Managing Partner, VP Development and Technical Services Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/gvc/practical_webobjects Global Village Consulting ranks 13th in 2012 in BIV's Top 100 Fastest Growing Companies in B.C! Global Village Consulting ranks 76th in 24th annual PROFIT 200 ranking of Canada's Fastest-Growing Companies by PROFIT Magazine! ___ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: WO application failing to load UNIXClassPath.txt
If it is from an NSLog rather than System.out.println then at least part of the
classpath is getting loaded. You might want to call code like this from main
to see what sort of classpath is getting generated:
static public String dumpJVMConfiguration()
{
StringBuffer output = new StringBuffer(\nSystem Properties
Follow\n);
Properties systemProperties = System.getProperties();
Enumeration propertyNames = systemProperties.propertyNames();
while (propertyNames.hasMoreElements())
{
String propertyName = (String) propertyNames.nextElement();
if (propertyName.equals(java.class.path) ||
propertyName.equals(com.webobjects.classpath))
{
output.append(Classpath\n);
String pathSeparator =
systemProperties.getProperty(path.separator);
NSArray classPathComponents =
NSArray.componentsSeparatedByString(systemProperties.getProperty(propertyName),
pathSeparator);
Enumeration classpathEnumeration =
classPathComponents.objectEnumerator();
while (classpathEnumeration.hasMoreElements())
{
String jarPath = (String)
classpathEnumeration.nextElement();
output.append(jarPath + \n);
try
{
File jarFile = new File(jarPath);
output.append((jarFile.isFile() ? -- Exists\n :
*** -- Does not Exist!\n));
}
catch (Throwable t)
{
output.append(Exception validating classpath: + t +
\n);
}
}
}
else
{
output.append(propertyName + = +
systemProperties.getProperty(propertyName) + \n);
}
}
return output.toString();
}
Otherwise, take a look at the launch script in the .woa bundle and see what it
is doing (bash).
Chuck
On 2013-03-28, at 11:09 AM, Soles, James T wrote:
Chuck,
The DecisionQ version 3.0 is coming from an NSLog.out in the application main
(DecisionQ is the application name). The other reason I don't believe that
the classpath is actually being loaded is because once the application does
get started we get some other errors that indicate the class was not found
(java.lang.NoClassDefFoundError).
Here is an example from the log file of one of the errors that I am seeing:
handleRequest: Unknown error occured: java.lang.NoClassDefFoundError:
com/equifax/xml/xmlschema/interconnect/InternationalAddressType
java.lang.NoClassDefFoundError:
com/equifax/xml/xmlschema/interconnect/InternationalAddressType
at GenericHandler.getICData(Unknown Source)
at DecisionQHandler.handleRequest(Unknown Source)
at DecisionQ.processRequest(Unknown Source)
at DecisionQ.main(Unknown Source)
at DecisionQ_main.main(Unknown Source)
Thanks,
Terry Soles
214-273-3916
(v922) 3916
-Original Message-
From: Chuck Hill [mailto:ch...@global-village.net]
Sent: Thursday, March 28, 2013 1:58 PM
To: Soles, James T
Cc: webobjects-deploy@lists.apple.com
Subject: Re: WO application failing to load UNIXClassPath.txt
Where does DecisionQ version 3.0 get output from? If the classpath was not
getting loaded, I would not expect the launch to get very far. More likely
that log output is getting re-directed elsewhere.
Chuck
On 2013-03-28, at 7:47 AM, Soles, James T wrote:
All,
I am in the process of trying to move our build environment and am getting
different results when starting an application from the new build
environment. I'm not sure what we may have missed when setting up the new
build environment but when the application starts from code built there it
does not load the UNIXClassPath.txt.
The current build environment is a MacBook and we are moving to building on
a Solaris Unix platform. The application builds, using ANT, with no issues
but when it is deployed, on a different Solaris Unix server, it does not
load the UNIXClassPath.txt.
When I run the application built on the MacBook I get this at the beginning
of the log file:
Loading
/app/software/Apple/Local/Library/WebObjects/Applications/DecisionQJava.woa/Contents/UNIX/UNIXClassPath.txt
Generated classpath:
When I run the application built on the Solaris Unix server the first thing
in the log file is:
DecisionQ version 3.0 (no indication that the classpath file is being
loaded).
Any thoughts on what we may have failed to load/move to the new build
server? Let me know if there are more details that you might need.
Thanks,
Terry Soles
214-273-3916
(v922) 3916
___
Do not post admin requests to the list
