I have been unsuccessful in getting any assistance off the JRUN Online Forums, or from JRUN technical support, so I am hoping someone on this list will have seen this problem before and be able to provide us with some advice. Otherwise, I'm looking at a complete rebuild job of a soon to be "live" web server, which I am REALLY hoping to avoid.
We have recently ported a JRUN 3.01 application over to JRUN 3.1. Our test server does have BOTH JRUN 3.01 and JRUN 3.1 on it, and has been set up to successfully run both versions of JRUN for the porting effort. Part of the reason we ported the application over was to take advantage of some of JRUN's new tab library's features, particularly using the stored procedure tag. The application works find on our test server running ONLY JRUN 3.1, and does successfully use the stored procedure tag, so I do know that we are using the correct jruntags.jar file on the test server. We built a new web server last week for "live" use using Windows 2000, IIS 5.0, and JRUN 3.1.26414. Note that I did use the "jrun31-win-us-26414.exe" file downloaded from Allaire's site for the installation of JRUN 3.1 on the new server. When we moved our application over to the new server, the application immediately died with the compiler error message listed below, within JRUN's own tag libraries. As a second test, I started up JRUN's own demo application on the "live" server. The servlets and JSP's ran fine, but the segment of the demo for the tag libraries died with the same exact error message. So whatever the problem is, it is consistent. As a third try, I copied the jruntags.jar file for JRUN 3.1 from our test server to our new yet to be "live" server, and restarted JRUN. I still got the same error message on JRUN's demo for the tag libraries. Just to make sure I did copy over the correct jruntag.jar file, I opened both the jar file on the test server, and the one on the yet to be "live" server using winzip, and compared the contents. They are exactly the same. Again, JRUN 3.1 and the JRUN 3.1 demo work fine on our test server, and we are using some of the new features that are only in JRUN 3.1's tag library successfully on our test server. So I know that we are "using" the correct jruntag.jar file on the "ported" code on the test server. But JRUN 3.1 does not work on the new server. I've uninstalled and reinstalled JRUN 3.1 two times since the first original install with the same results. After the second uninstall, I actually went into the registry on the server and removed EVERY registry key associated with JRUN, and then deleted the remaining file subdirectory structure under C:\Program Files\Allaire. I then reinstalled JRUN 3.1 for the third time, this time at a top level subdirectory (ie. C:\JRUN3.1) and still got the same error message. Again, pure HTML or pure JSP code that does NOT use the JRUN taglibraries does work on the new "live" server. It is only the tag library code that the complier throws an error on. My only other recourse is to completely wipe the new server, including the registry, and try another reinstall of the operating system, IIS 5.0 and JRUN 3.1. Does anyone have any other suggestions that I might try before going through a complete rebuild of a server??? My thanks in advance for any advice or insight that anyone can provide. Celeste ---------------------------------------------------------------------------- -------- The compiler error we get is: 500 Internal Server Error /OrderDemo/jsp/jr~logon.jsp: null java.lang.NoSuchMethodError at allaire.jrun.jsp.JRunTagLibraryInfo.buildAttributeInfo(JRunTagLibraryInfo.ja va:716) at allaire.jrun.jsp.JRunTagLibraryInfo.buildTagInfo(JRunTagLibraryInfo.java:683 ) at allaire.jrun.jsp.JRunTagLibraryInfo.initialize(JRunTagLibraryInfo.java:627) at allaire.jrun.jsp.JRunTagLibraryInfo.<init>(JRunTagLibraryInfo.java:199) at allaire.jrun.jsp.JRunTagLibraryInfo.lookupTLI(JRunTagLibraryInfo.java:109) at allaire.jrun.jsp.JSPParser.taglibDirective(JSPParser.java:843) at allaire.jrun.jsp.JSPParser.directive(JSPParser.java:974) at allaire.jrun.jsp.JSPParser.parse(JSPParser.java:922) at allaire.jrun.jsp.JSPParser.writeXML(JSPParser.java:137) at allaire.jrun.jsp.JSPParser.generateXML(JSPParser.java:107) at allaire.jrun.jsp.JSPParser.generateXML(JSPParser.java:64) at allaire.jrun.jsp.Translator.parsePage(Translator.java:192) at allaire.jrun.jsp.Translator.translate(Translator.java:390) at allaire.jrun.jsp.Translator.translate(Translator.java:92) at allaire.jrun.jsp.JSPTranslator.translate(JSPTranslator.java:75) at allaire.jrun.jsp.JSPTranslator.translate(JSPTranslator.java:67) at allaire.jrun.jsp.JSPServlet.service(JSPServlet.java:216) at allaire.jrun.jsp.JSPServlet.service(JSPServlet.java:196) at allaire.jrun.servlet.JRunSE.service(JRunSE.java:1417) at allaire.jrun.session.JRunSessionService.service(JRunSessionService.java:1088 ) at allaire.jrun.servlet.JRunSE.runServlet(JRunSE.java:1271) at allaire.jrun.servlet.JRunRequestDispatcher.forward(JRunRequestDispatcher.jav a:89) at allaire.jrun.servlet.JRunSE.service(JRunSE.java:1557) at allaire.jrun.servlet.JRunSE.service(JRunSE.java:1547) at allaire.jrun.servlet.JvmContext.dispatch(JvmContext.java:364) at allaire.jrun.jrpp.ProxyEndpoint.run(ProxyEndpoint.java:388) at allaire.jrun.ThreadPool.run(ThreadPool.java:272) at allaire.jrun.WorkerThread.run(WorkerThread.java:75) ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
