Here is the error from the cfx_openimage tag when running as a service vs. manual start using start.jar.
UnsatisfiedLinkError invoking CFXNativeLib method Rob On Dec 17, 6:52 am, Rob <[email protected]> wrote: > Hi Anthony, > > Here is the snippet from bluedragon.xml: > <nativecustomtags> > <mapping name="cfx_openimage"> > <function>ProcessTagRequest</function> > <keeploaded>true</keeploaded> > <name>cfx_openimage</name> > <displayname>CFX_openimage</displayname> > <module>D:/Explorers_Log/webroot_cfmlapps/customtags/ > cfx_openimage.dll</module> > <description></description> > </mapping> > </nativecustomtags> > <file> > <maxfiles>1000</maxfiles> > <trustcache>false</trustcache> > </file> > <cfmlcustomtags> > <mapping name="cf"> > <directory>D:/Explorers_Log/webroot_cfmlapps/customtags</ > directory> > <name>cf</name> > </mapping> > </cfmlcustomtags> > > I created a test page, with one regular custom tag, and cfx_openimage. > When starting jetty/openBD as a service, the custom tag worked, the > cfx tag did not. > > I then stopped the service, and launched jetty/openBD using the > start.jar via a bat file, and both the customtag and the cfx tag > worked... > > Here is part of my jetty-service.conf file... > > wrapper.java.classpath.1=../lib/win32/*.jar > wrapper.java.classpath.2=../lib/*.jar > wrapper.java.classpath.3=../start.jar > wrapper.java.library.path.1=../lib/win32/ > wrapper.java.additional.1=-Djetty.home=../ > wrapper.java.additional.2=-Djetty.logs=../logs > wrapper.java.initmemory=3 > wrapper.java.maxmemory=64 > wrapper.java.mainclass=org.mortbay.jetty.win32service.JettyServiceWrapperListener > wrapper.app.parameter.1=../etc/jetty.xml > wrapper.console.format=PM > wrapper.console.loglevel=INFO > wrapper.logfile=../logs/jetty-service.log > wrapper.logfile.format=LPTM > > Any thoughts? > > Rob > > On Dec 17, 3:53 am, "Anthony Hixon, Jr." <[email protected]> wrote: > > > > > I know you said you've tried various combinations of absolute and relative > > paths, but what exact paths have you tried in your > > <jetty_home>/etc/openbd/bluedragon.xml file in the <cfmlcustomtags> <mapping > > name="cf"> <directory>? > > > On Tue, Dec 16, 2008 at 10:31 PM, Rob <[email protected]> wrote: > > > > Well, a little premature on the joy... > > > > After many hours of testing this, it looks like adding the dot to the > > > webdefault.xml file makes the Jetty service work, but then breaks the > > > links to the custom tags... > > > > I have tried many different combinations of absolute and relative > > > paths, to no avail. > > > > When I hard code the path like this... > > > > <servlet> > > > <servlet-name>cfmServlet</servlet-name> > > > > <servlet-class>com.naryx.tagfusion.cfm.cfServlet</servlet-class> > > > <init-param> > > > > <param-name>BLUEDRAGON_WORKING_DIRECTORY</param-name> > > > > <param-value>D:/Explorers_Log/logs/openbd</param-value> > > > </init-param> > > > <init-param> > > > <param-name>BLUEDRAGON_XML</param-name> > > > > <param-value>D:/Explorers_Log/etc/openbd/bluedragon.xml</param- > > > value> > > > </init-param> > > > <load-on-startup>0</load-on-startup> > > > </servlet> > > > > I get this error when running Jetty as a windows service > > > Native library does not exist: ./webroot_cfmlapps/customtags/ > > > cfx_openimage.dll > > > > When I stop the service and launch openBD/Jetty from the start.jar > > > (via a bat file), the custom tag works. > > > > I don't see anywhere in the jetty.xml to set paths for the customtags, > > > and in the bluedragon.xml I have tried various combinations of > > > absolute and relative paths. > > > > Again, I have renamed the Jetty folder to Explorers_Log, but don't see > > > where that should affect the jetty service, as all else works except > > > custom tags (so far) and it all works when I launch from the > > > start.jar. > > > > Thanks for your time, > > > > Rob > > > > On Dec 16, 11:26 am, Rob <[email protected]> wrote: > > > > Aloha Paul, > > > > > Thanks - that was the trick - please disregard my previous post about > > > > removing the hyphen in the jetty-service.conf file - I accidentally > > > > had a previous session running, so that was incorrect. > > > > > I was able to see the failed path to bluedragon.xml by launching jetty- > > > > service.exe without the parameters and conf file - just didn't know > > > > where to fix it. > > > > > Thanks Paul! > > > > > Rob > > > > > On Dec 16, 10:56 am, Paul Bonfanti <[email protected]> wrote: > > > > > > Another person said they solved this problem doing this: > > > > > > Hi everybody, > > > > > I think I have found the problem! > > > > > I checked logs/jetty-service.log and it indicated that the > > > > > bluedragon.xml could not be loaded. > > > > > > Then In /etc/webdefault.xml I changed the line (added a dot): > > > > > > <param-name>BLUEDRAGON_XML</param-name> > > > > > <param-value>./etc/openbd/bluedragon.xml</param-value> > > > > > > to: > > > > > > <param-name>BLUEDRAGON_XML</param-name> > > > > > <param-value>../etc/openbd/bluedragon.xml</param-value> > > > > > > restarted the service for jetty and then it works! > > > > > > Paul > > > > > > -----Original Message----- > > > > > From: [email protected] [mailto:[email protected]] On > > > Behalf Of Rob > > > > > Sent: Tuesday, December 16, 2008 3:38 PM > > > > > To: Open BlueDragon > > > > > Subject: [OpenBD] Re: Installation on IIS Windows 2003 Server > > > > > > I have tried the jetty wrapper - > > > > > > All looks good during install, but I get: HTTP ERROR: 500 > > > > > > INTERNAL_SERVER_ERROR > > > > > > RequestURI=/ > > > > > Caused by: > > > > > > java.lang.NullPointerException > > > > > at com.naryx.tagfusion.cfm.engine.cfEngine.service(Unknown > > > Source) > > > > > at com.naryx.tagfusion.cfm.cfServlet.service(Unknown Source) > > > > > at > > > > > javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > > > > > at > > > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: > > > > > 502) > > > > > at org.mortbay.jetty.servlet.ServletHandler.handle > > > > > (ServletHandler.java:363) > > > > > at org.mortbay.jetty.security.SecurityHandler.handle > > > > > (SecurityHandler.java:216) > > > > > at org.mortbay.jetty.servlet.SessionHandler.handle > > > > > (SessionHandler.java:181) > > > > > at org.mortbay.jetty.handler.ContextHandler.handle > > > > > (ContextHandler.java:757) > > > > > at > > > org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java: > > > > > 416) > > > > > at > > > org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:334) > > > > > at > > > org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126) > > > > > at > > > org.mortbay.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java: > > > > > 463) > > > > > at > > > > > javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > > > > > at > > > > > javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > > > > > at > > > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: > > > > > 502) > > > > > at org.mortbay.jetty.servlet.ServletHandler.handle > > > > > (ServletHandler.java:363) > > > > > at org.mortbay.jetty.security.SecurityHandler.handle > > > > > (SecurityHandler.java:216) > > > > > at org.mortbay.jetty.servlet.SessionHandler.handle > > > > > (SessionHandler.java:181) > > > > > at org.mortbay.jetty.handler.ContextHandler.handle > > > > > (ContextHandler.java:757) > > > > > at > > > org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java: > > > > > 416) > > > > > at org.mortbay.jetty.handler.HandlerCollection.handle > > > > > (HandlerCollection.java:114) > > > > > at org.mortbay.jetty.handler.HandlerWrapper.handle > > > > > (HandlerWrapper.java:152) > > > > > at org.mortbay.jetty.Server.handle(Server.java:324) > > > > > at > > > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java: > > > > > 502) > > > > > at > > > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete > > > > > (HttpConnection.java:826) > > > > > at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:523) > > > > > at > > > org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211) > > > > > at > > > org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:377) > > > > > at org.mortbay.io.nio.SelectChannelEndPoint.run > > > > > (SelectChannelEndPoint.java:409) > > > > > at org.mortbay.thread.QueuedThreadPool$PoolThread.run > > > > > (QueuedThreadPool.java:497) > > > > > > My jetty-service.conf looks like... > > > > > > wrapper.java.classpath.1=../lib/win32/*.jar > > > > > wrapper.java.classpath.2=../lib/*.jar > > > > > wrapper.java.classpath.3=../start.jar > > > > > wrapper.java.library.path.1=../lib/win32/ > > > > > wrapper.java.additional.1=-Djetty.home=../ > > > > > wrapper.java.additional.2=-Djetty.logs=../logs > > > > > wrapper.java.initmemory=3 > > > > > wrapper.java.maxmemory=64 > > > > wrapper.java.mainclass=org.mortbay.jetty.win32service.JettyServiceWrapperListener > > > > > wrapper.app.parameter.1=../etc/jetty.xml > > > > > wrapper.console.format=PM > > > > > wrapper.console.loglevel=INFO > > > > > wrapper.logfile=../logs/jetty-service.log > > > > > wrapper.logfile.format=LPTM > > > > > wrapper.logfile.loglevel=INFO > > > > > wrapper.logfile.maxsize=0 > > > > > wrapper.logfile.maxfiles=0 > > > > > wrapper.syslog.loglevel=NONE > > > > > wrapper.ntservice.name=Jetty > > > > > wrapper.ntservice.displayname=Jetty6-Service > > > > > wrapper.ntservice.description=Jetty is an open-source, standards- > > > > > based, full-featured web server implemented entirely in java > > > > > wrapper.ntservice.starttype=AUTO_START > > > > > wrapper.ntservice.interactive=false > > > > > > wrapper.filter.trigger.1=java.lang.OutOfMemoryError- Hide quoted text > > > > > - > > - Show quoted text -... > > read more » --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official blog @ http://blog.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
