|
From: davidbeers <db...@gm...> - 2007-12-19 01:53:42
|
I have an executable jar with a main class whose name I've verified from the manifest (I built the jar myself). Wrapper seems unable to execute it, issuing a ClassNotFoundException. I've looked my wrapper classpath over and can't see what the problem could be. The salient bits of my wrapper.conf look like this: wrapper.java.classpath.1=../lib/wrapper.jar wrapper.java.classpath.2=../lib/tileserver.jar wrapper.java.library.path.1=../lib wrapper.app.parameter.1=com.pikesoft.TileServer tileserver.jar is my executable jar, it's located in the lib directory as described, and com.pikesoft.TileServer is the fully qualified name of its main class. From the FAQ it seems like this is all as it should be, but I'm obviously missing something! Probably something stupid... <sigh/> -- View this message in context: http://www.nabble.com/Executable-jar-ClassNotFoundException-tp14409676p14409676.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: Leif M. <le...@ta...> - 2007-12-19 11:35:21
|
David, Does your jar's manifest file specify a classpath like the following? Class-Path: log4j.jar If so, it is necessary to include all of those files in the classpath as well. The next question is what is the file class that is not being found? Cheers, Leif davidbeers wrote: > I have an executable jar with a main class whose name I've verified from the > manifest (I built the jar myself). Wrapper seems unable to execute it, > issuing a ClassNotFoundException. I've looked my wrapper classpath over and > can't see what the problem could be. The salient bits of my wrapper.conf > look like this: > > wrapper.java.classpath.1=../lib/wrapper.jar > wrapper.java.classpath.2=../lib/tileserver.jar > > wrapper.java.library.path.1=../lib > > wrapper.app.parameter.1=com.pikesoft.TileServer > > tileserver.jar is my executable jar, it's located in the lib directory as > described, and com.pikesoft.TileServer is the fully qualified name of its > main class. From the FAQ it seems like this is all as it should be, but I'm > obviously missing something! Probably something stupid... <sigh/> > |
|
From: davidbeers <db...@gm...> - 2007-12-19 13:36:37
|
Thanks for the quick reply, Leif! I think I'm going to like using this software. :) There's no classpath specified in the manifest, but I'm glad to know about this for the future. The class file that isn't being found is the main class: "WrapperSimpleApp: Unable to locate the class com.pikesoft.TileServer: java.lang.ClassNotFoundException: com.pikesoft.TileServer" -David Leif Mortenson-2 wrote: > > > Does your jar's manifest file specify a classpath like the following? > Class-Path: log4j.jar > > If so, it is necessary to include all of those files in the classpath as > well. > > The next question is what is the file class that is not being found? > > Cheers, > Leif > > davidbeers wrote: >> I have an executable jar with a main class whose name I've verified from >> the >> manifest (I built the jar myself). Wrapper seems unable to execute it, >> issuing a ClassNotFoundException. I've looked my wrapper classpath over >> and >> can't see what the problem could be. The salient bits of my wrapper.conf >> look like this: >> >> wrapper.java.classpath.1=../lib/wrapper.jar >> wrapper.java.classpath.2=../lib/tileserver.jar >> >> wrapper.java.library.path.1=../lib >> >> wrapper.app.parameter.1=com.pikesoft.TileServer >> >> tileserver.jar is my executable jar, it's located in the lib directory as >> described, and com.pikesoft.TileServer is the fully qualified name of its >> main class. From the FAQ it seems like this is all as it should be, but >> I'm >> obviously missing something! > -- View this message in context: http://www.nabble.com/Executable-jar-ClassNotFoundException-tp14409676p14416910.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: davidbeers <db...@gm...> - 2007-12-19 13:43:06
|
Perhaps I should also mention that I'm running x86 32-bit Linux (RHEL 4). I've done some floundering around with the configuration getting it to this point and thought I saw a message somewhere about how some environment variables are set the first time you run Wrapper. Is it possible that some bad config info from previous attempts to start Wrapper needs to be unset? If so, what do I do to clear that out? -David davidbeers wrote: > > Thanks for the quick reply, Leif! I think I'm going to like using this > software. :) > > There's no classpath specified in the manifest, but I'm glad to know about > this for the future. The class file that isn't being found is the main > class: "WrapperSimpleApp: Unable to locate the class > com.pikesoft.TileServer: java.lang.ClassNotFoundException: > com.pikesoft.TileServer" > > -David > > > Leif Mortenson-2 wrote: >> >> >> Does your jar's manifest file specify a classpath like the following? >> Class-Path: log4j.jar >> >> If so, it is necessary to include all of those files in the classpath as >> well. >> >> The next question is what is the file class that is not being found? >> >> Cheers, >> Leif >> >> davidbeers wrote: >>> I have an executable jar with a main class whose name I've verified from >>> the >>> manifest (I built the jar myself). Wrapper seems unable to execute it, >>> issuing a ClassNotFoundException. I've looked my wrapper classpath over >>> and >>> can't see what the problem could be. The salient bits of my >>> wrapper.conf >>> look like this: >>> >>> wrapper.java.classpath.1=../lib/wrapper.jar >>> wrapper.java.classpath.2=../lib/tileserver.jar >>> >>> wrapper.java.library.path.1=../lib >>> >>> wrapper.app.parameter.1=com.pikesoft.TileServer >>> >>> tileserver.jar is my executable jar, it's located in the lib directory >>> as >>> described, and com.pikesoft.TileServer is the fully qualified name of >>> its >>> main class. From the FAQ it seems like this is all as it should be, but >>> I'm >>> obviously missing something! >> > > -- View this message in context: http://www.nabble.com/Executable-jar-ClassNotFoundException-tp14409676p14417185.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: Leif M. <le...@ta...> - 2007-12-21 05:15:26
|
David, Can you set wrapper.debug=true in your configuration file and then post the resulting wrapper.log file? That should include notification if any of the jar files on the class path can not be loaded. Could you also most the manifest file of your tileserver.jar file? Thanks, Leif davidbeers wrote: > Thanks for the quick reply, Leif! I think I'm going to like using this > software. :) > > There's no classpath specified in the manifest, but I'm glad to know about > this for the future. The class file that isn't being found is the main > class: "WrapperSimpleApp: Unable to locate the class > com.pikesoft.TileServer: java.lang.ClassNotFoundException: > com.pikesoft.TileServer" > > -David > > > Leif Mortenson-2 wrote: > >> Does your jar's manifest file specify a classpath like the following? >> Class-Path: log4j.jar >> >> If so, it is necessary to include all of those files in the classpath as >> well. >> >> The next question is what is the file class that is not being found? >> >> Cheers, >> Leif >> >> davidbeers wrote: >> >>> I have an executable jar with a main class whose name I've verified from >>> the >>> manifest (I built the jar myself). Wrapper seems unable to execute it, >>> issuing a ClassNotFoundException. I've looked my wrapper classpath over >>> and >>> can't see what the problem could be. The salient bits of my wrapper.conf >>> look like this: >>> >>> wrapper.java.classpath.1=../lib/wrapper.jar >>> wrapper.java.classpath.2=../lib/tileserver.jar >>> >>> wrapper.java.library.path.1=../lib >>> >>> wrapper.app.parameter.1=com.pikesoft.TileServer >>> >>> tileserver.jar is my executable jar, it's located in the lib directory as >>> described, and com.pikesoft.TileServer is the fully qualified name of its >>> main class. From the FAQ it seems like this is all as it should be, but >>> I'm >>> obviously missing something! >>> > > |
|
From: Tim W. <tim...@or...> - 2007-12-20 22:47:20
|
Hi We've been using the Tanuki Service Wrapper for many years now, and it's a really important tool for us. To that end we build it regularly on all our supported platforms - currently we build 3.2.3 on: - HP-UX PA-RISC2 - HP-UX IA64 - Solaris SPARC 64 - AIX 5L PPC64 - Linux x86 - Linux x86_64 - Windows x86 - Windows x64 (yes I know there are issues, but it works fine for us) We'd like to contribute binaries for wider use, as the platform support for binary releases is somewhat patchy historically, and we'd be able to produce these binaries with a good degree of regularity. How would I go about doing this? cheers tim |
|
From: Marcus L. <ml...@un...> - 2007-12-19 19:07:29
|
Just a wild guess since it matches the problem: From where do you run the wrapper executable? Is the folder ../lib really accessible from that location? As I said, just wild guessing. Cheers, Marcus. On 20/12/2007, at 0:43 , davidbeers wrote: > > Perhaps I should also mention that I'm running x86 32-bit Linux > (RHEL 4). > I've done some floundering around with the configuration getting it > to this > point and thought I saw a message somewhere about how some environment > variables are set the first time you run Wrapper. Is it possible > that some > bad config info from previous attempts to start Wrapper needs to be > unset? > If so, what do I do to clear that out? > > -David > > > davidbeers wrote: >> >> Thanks for the quick reply, Leif! I think I'm going to like using >> this >> software. :) >> >> There's no classpath specified in the manifest, but I'm glad to >> know about >> this for the future. The class file that isn't being found is the >> main >> class: "WrapperSimpleApp: Unable to locate the class >> com.pikesoft.TileServer: java.lang.ClassNotFoundException: >> com.pikesoft.TileServer" >> >> -David >> >> >> Leif Mortenson-2 wrote: >>> >>> >>> Does your jar's manifest file specify a classpath like the >>> following? >>> Class-Path: log4j.jar >>> >>> If so, it is necessary to include all of those files in the >>> classpath as >>> well. >>> >>> The next question is what is the file class that is not being found? >>> >>> Cheers, >>> Leif >>> >>> davidbeers wrote: >>>> I have an executable jar with a main class whose name I've >>>> verified from >>>> the >>>> manifest (I built the jar myself). Wrapper seems unable to >>>> execute it, >>>> issuing a ClassNotFoundException. I've looked my wrapper >>>> classpath over >>>> and >>>> can't see what the problem could be. The salient bits of my >>>> wrapper.conf >>>> look like this: >>>> >>>> wrapper.java.classpath.1=../lib/wrapper.jar >>>> wrapper.java.classpath.2=../lib/tileserver.jar >>>> >>>> wrapper.java.library.path.1=../lib >>>> >>>> wrapper.app.parameter.1=com.pikesoft.TileServer >>>> >>>> tileserver.jar is my executable jar, it's located in the lib >>>> directory >>>> as >>>> described, and com.pikesoft.TileServer is the fully qualified >>>> name of >>>> its >>>> main class. From the FAQ it seems like this is all as it should >>>> be, but >>>> I'm >>>> obviously missing something! >>> >> >> > > -- > View this message in context: http://www.nabble.com/Executable-jar-ClassNotFoundException-tp14409676p14417185.html > Sent from the Java Service Wrapper mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services > for just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |