2017 up to now  | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007

(older archive entries before 2007 are not shown here, but included in the onsite-search)

Mailing List - Entries of 2011


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [QF-Test] [BULK] No "*sys-package-mgr*: processing new jar" log message for JAR file in classpath


  • Subject: Re: [QF-Test] [BULK] No "*sys-package-mgr*: processing new jar" log message for JAR file in classpath
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Tue, 28 Jun 2011 11:14:40 +0200

Hi Barry,

whether or not your jar is available to the JVM is a Java thing.
QF-Test cannot tell what might be going on in the SUT that causes Java
to pick up that jar or not and it's not going to start guessing :-).

As Ivan said, the most likely cause is some typo. QF-Test logs the
command line that it uses to start the SUT. Perhaps you can find the
error there. If you send the log of your startup sequence I may also
be able to spot what's wrong.

Best regards,
    Greg

"Barry Kierstein" <bkierste@?.us> writes:

> Ivan,
>  
>     The new JAR file is ydoclet-runtime.jar.  It is in the JVM classpath with around 30+ other JAR
> files that load successfully according to the logging messages in QF-Test.  All the JAR files are
> in the same directory.  This directory is set in the Directory field of the Start Java SUT client
> node.  The ydoclet-runtime.jar properties show I own the file and have rw access to it.
>     The classpath looks like this:  -cp ydoclet-runtime.jar:file1:file2:...  The logging for
> QF-Test shows that file1, file2, etc. are loaded with the *sys-package-mgr* log message.  Also,
> each of the successfully loaded JAR files has an entry in ~/.qftest/jython-cachedir/packages
> directory.
>     I agree there is something odd with this file (path? security?), but what?  Is there some
> logging for QF-Test that would output what QF-Test finds - no such file, file corrupt, file not at
> right version?  That would make the debugging happen quicker.
>     Much thanks!
>  
> Barry
>
> Barry Kierstein
> Division of Technology
> (518) 285-8345
> BKierste@?.US
>
> [cid]   ..Please consider the environment before printing this email.
>
>>>> Ivan Boelle <ivan.boelle@?.com> 6/25/2011 6:55 AM >>>
> Hello,
>
> In my opinion a difference between Windows and Linux suggest a path typo problem.
>
> Is there any special character in the jar path or name ?
>
> What is the path to the jar ?
>
> Regards,
>
> Le 24 juin 2011 à 22:06, "Barry Kierstein" <bkierste@?.us> a écrit :
>
>     Hello,
>      
>         I recently added a new JAR file to the -cp argument for a Start Java SUT client node. 
>     When the node runs, log messages for the other JAR files in the classpath are shown in the
>     Terminal window.  However, the new JAR file does not have a log message, and the application
>     fails with a java.lang.NoClassDefFoundError: message for a class that is inside the new JAR
>     file.  I confirmed that the JAR file is in the same directory as the other JAR files, that the
>     owner and protection is correct (running Ubuntu), and opened the JAR file and did an integrity
>     test to verify that the JAR file is not corrupt.
>         What is interesting is that a fellow co-worker has the same setup, but is running under
>     Windows, and the JAR file is logged in the Terminal window, and the application works fine.
>         Any ideas on what to look for?  Thanks!
>      
>     Barry Kierstein
>
>     Barry Kierstein
>     Division of Technology
>     (518) 285-8345
>      BKierste@?.US
>
>     <mime-attachment>..Please consider the environment before printing this email.

-- 
Gregor Schmid                                Gregor.Schmid@?.de
Quality First Software GmbH                     http://www.qfs.de
Tulpenstr. 41                               Tel: +49 8171 38648-0
DE-82538 Geretsried                         Fax: +49 8171 3864816
GF: Gregor Schmid, Karlheinz Kellerer          HRB München 140833