Thanks very much, Skip! :-) /charlie
> -----Original Message----- > From: Skip Klobucher [mailto:rklobucher@;macromedia.com] > Sent: Monday, November 04, 2002 1:57 PM > To: JRun-Talk > Subject: RE: JSP compilation error in Jrun 4.0 > > > Hi Charlie, > > I have to apologize to the JRun-Talk community at large for any > confusion on this topic - we are slightly out of sync in terms of > providing both the kits for SP1a and the general messaging about > the release. The kits are available, but the web site is > lagging. I hope to have the JRun Support Center web site updated > by the end of today to more accurately reflect the changes made to SP1a. > > The primary changes made to SP1a are the inclusion of the latest > JDBC drivers from Data Direct to correct several bugs and enhance > performance. The new kits were released approximately one week > ago. If you click on the first link that you specify in your > email below and download either of the kits (Unix or Windows) > from that page, you will be getting SP1a. If you have already > installed SP1, you will need to update to SP1a. The following > product issues were resolved in this kit: > > 48010 - (SP1a) The statement.setMaxRows() was not returning the > full ResultSet. This has been fixed with updated JDBC drivers. > 48585 - (SP1a) Stored procedures with a parameter were throwing > java.sql.SQLException exceptions. This has been fixed with > updated JDBC drivers. > 48626 - (SP1a) Pooled prepared statements were failing under > load. JRun would return "Object has been closed" or "No more data > available to read" errors. This has been fixed with updated JDBC drivers. > 48644 - (SP1a) Database performance has been increased. > > As I said, I'll be working to complete the web site modifications > by the end of today, and I appreciate your comments. Thanks! > > Skip > > -----Original Message----- > From: charlie arehart [mailto:carehart@;systemanage.com] > Sent: Monday, November 04, 2002 12:05 PM > To: JRun-Talk > Subject: RE: JSP compilation error in Jrun 4.0 > > > Folks, what's with this SP1a moniker for the JRun Service Pack 1? This is > the first I'd heard of it (previous notes referred to it simply > as SP1, and > I had already installed that). Should we who already have SP1 bother with > the upgrade? > > The info at > http://dynamic.macromedia.com/bin/MM/software/trial/hwswrec.jsp?pr > oduct=jrun_sp > doesn't really distinguish what's unique about the "a" release. It > points us to a FAQ and technote, but they talk about "new features" that > were a part of SP1. > > And they point to the release notes at > http://www.macromedia.com/support/jrun/releasenotes/4/releasenotes > _4_sp1.htm > l which are simply (and clearly named to be) the sp1 release > notes. Nothing > "a" about them. :-) > > Any clarification, here and in those pages, would be welcomed. > > /charlie > > > -----Original Message----- > > From: Theodore Zimmerman [mailto:tzimmerman@;macromedia.com] > > Sent: Friday, November 01, 2002 9:07 AM > > To: JRun-Talk > > Subject: RE: JSP compilation error in Jrun 4.0 > > > > > > This appears to be product issue 48585 which has been fixed with > > the updated JDBC drivers included in SP1a. You can get SP1a at > > http://www.macromedia.com/software/jrun/download/. There is a > > link for JRun 4 Service Pack 1a under Additional Downloads. > > > > HTH > > > > Ted Zimmerman > > > > -----Original Message----- > > From: Chhaya Nayak [mailto:nayak_c@;lycos.com] > > Sent: Friday, November 01, 2002 1:17 AM > > To: JRun-Talk > > Subject: RE: JSP compilation error in Jrun 4.0 > > > > > > > > Check for the kind of driver u are using > > > > If u use the jdbcOdbc driver this will not create a prob.. > > If u are using the SQLServer2000 driver for JDBC u need to follow the > > installation procedure given in the docs for the SQL server 2000 > > (Section : "Installing stored procedures for JTA") to make the > > stored procedures work > > > > > > > > On Thu, 10 Oct 2002 16:54:48 > > Ravi Vedire wrote: > > >It looks like the new JDBC drivers is buggy as well. Now my > calls to the > > >database throw an exception > > > > > >java.sql.SQLException: [Macromedia][SQLServer JDBC > > Driver][SQLServer]Line 1: > > >Incorrect syntax near '{'. > > > > > >This code works fine without the service pack and in JRun 3.1. > > > > > > final String query = > > > "{ CALL wss_Create_PositionMarker(?, ?, ?, ?, ?, ?, ?, ?, > > ?, ?, ?, ?, > > >?, ?, ?, ?) }"; > > > try > > > { > > > // set up statement > > > // > > > stmt = conn.prepareCall(query); > > > // initialize parameters. > > > ... > > > ... > > > .. > > > > > > rset = stmt.executeQuery(); > > > } > > > catch() > > > { > > > } > > > > > >I wasted lot of time with the JSP compiler bug, now that is > > fixed they broke > > >some thing else. Its been very frustrating trying to migrate > to Jrun 4.0. > > >Thye added some version dependency and I cant not use the JRun 4.0 JDBC > > >libraries with SP1. Now we cannot even finish migration > efforts and wait > > >till SP1 release. > > > > > >Ravi > > > > > >-----Original Message----- > > >From: Ravi Vedire [mailto:RVedire@;unicru.com] > > >Sent: Thursday, October 10, 2002 4:02 PM > > >To: JRun-Talk > > >Subject: RE: JSP compilation error in Jrun 4.0 > > > > > > > > >Thanks Eric, > > > > > >That was very helpful. The problem I was trying to solve was > > getting impeded > > >by a bug in JSP compiler in JRun 4.0. And as you mentioned it > > looks like it > > >is fixed in JRun 4 SP1. After installing SP1 the it did not take > > me long to > > >figure out the cause for the original issue and fix it. > > > > > >Any idea when SP1 will be officially released? > > > > > >Thanks, > > >Ravi > > > > > >-----Original Message----- > > >From: Eric Anderson [mailto:eanderson@;macromedia.com] > > >Sent: Thursday, October 10, 2002 10:14 AM > > >To: JRun-Talk > > >Subject: RE: JSP compilation error in Jrun 4.0 > > > > > > > > >Ravi, > > > > > >Have you tried the beta of JRun 4 service pack 1. I set up a > > simple sample > > >of what you are trying to do ( I think ) and it works in JRun 4 sp1. > > > > > >You can get more information on how to get the beta here: > > > > > >http://webforums.macromedia.com/jrun/today.cfm#57 > > > > > >I have included what I did in this email. If it is radically > > different from > > >what you are doing let me know. > > > > > >package com.test; > > > > > >public abstract class Foo { > > > > > > public void test() { > > > > > > } > > > > > >} > > > > > ><%@ page import="com.test.Foo"%> > > ><%! > > > > > >public class Foo2 extends jrun.jsp.runtime.HttpJSPServlet, com.test.Foo > > >{ > > > public void test2(int ifoo ) > > > { > > > ifoo = 0; > > > } > > > > > >} > > >%> > > ><%! > > > > > >public Foo2 test = new Foo2(); > > > > > >%> > > > > > >Eric > > > > > > > > > > > >-----Original Message----- > > >From: Ravi Vedire [mailto:RVedire@;unicru.com] > > >Sent: Thursday, October 10, 2002 11:36 AM > > >To: JRun-Talk > > >Subject: RE: JSP compilation error in Jrun 4.0 > > > > > > > > >After reviewing all the code, the only thing I can attribute the > > >compilation errors to extending a Java class in JSP. > > > > > > > > ><%! > > > > > >public class customSiteLocatorMgr extends com.dpd.wssjsp.SiteLocatorMgr > > >{ > > > public void foo(int ifoo ) > > > { > > > ifoo = 0; > > > } > > > > > >} > > >%> > > ><%! > > > > > >public customSiteLocatorMgr siteLocatorMgr = new > customSiteLocatorMgr(); > > > > > >%> > > > > > >The above strip down version of the code does not give me the > same error, > > >but it also does not work. We get a 500 NULL error. > > > > > >"Extends" -- Directs the translation process to extend the > > generated servlet > > >className. This technique is not to be used lightly as it > > prevents the JSP > > >engine from doing some things on your behalf. Then goes on to > > recommend tag > > >libraries as a better solution. > > > > > > > > >Would some one please enlighten me on the limitations/downside of using > > >extends in JSP. > > > > > >Thanks, > > >Ravi > > > > > > > > >-----Original Message----- > > >From: Baker, Ed [mailto:EBaker@;Kronos.com] > > >Sent: Thursday, October 10, 2002 7:51 AM > > >To: JRun-Talk > > >Subject: RE: JSP compilation error in Jrun 4.0 > > > > > > > > >Ravi, > > > > > >Our error was a simple syntax error (an extra semi-colon). I > forget the > > >error message text but it was a basic syntax error. It's not > related to > > >your error message. > > > > > >-Ed > > > > > >-----Original Message----- > > >From: Ravi Vedire [mailto:RVedire@;unicru.com] > > >Sent: Wednesday, October 09, 2002 7:20 PM > > >To: JRun-Talk > > >Subject: RE: JSP compilation error in Jrun 4.0 > > > > > > > > >Ed, > > > > > >Looks like size is not the issue in my case. After stripping > > down some, the > > >generated java file (in failed compile case) is much smaller > > than the java > > >files generated by the working JSP files. > > > > > >Did you get similar error message for your syntax error? (like the one > > >listed at the bottom of this e-mail). > > > > > >Thanks, > > >Ravi > > > > > > > > >-----Original Message----- > > >From: Baker, Ed [mailto:EBaker@;Kronos.com] > > >Sent: Wednesday, October 09, 2002 1:27 PM > > >To: JRun-Talk > > >Subject: RE: JSP compilation error in Jrun 4.0 > > > > > > > > >We had a compilation error on a JSP file when we switched from > > 3.1 to 4.0. > > >The file had a syntax error which did not fail under 3.1. So 4.0 was > > >correct in reporting the error. I don't know if this will > help you but I > > >thought it worth mentioning. > > > > > >-Ed Baker > > > > > >-----Original Message----- > > >From: Ravi Vedire [mailto:RVedire@;unicru.com] > > >Sent: Wednesday, October 09, 2002 3:04 PM > > >To: JRun-Talk > > >Subject: JSP compilation error in Jrun 4.0 > > > > > > > > >Hi All, > > > > > >We are getting the following JSp compilation error when JRun > 4.0 tries to > > >compiles some of our JSP files. However the same JSP files > work with JRun > > >3.1. > > > > > >On the web I found some references to the size of the JSP and > Java class > > >file size limitations of the JVM, as the cause for this error. > One of the > > >solutions proposed was to re-architect the JSP. > > > > > >Before we go and re-architect all the JSP code, I wanted to find > > out if any > > >one else encountered this issue with JRun 4.0 and what did they > > top resolve > > >it. > > > > > >Thanks a lot in advance > > >Ravi > > > > > >500 (class: jrun__C150__applicant2ejsp13, method: _jspService > signature: > > >(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpS > > ervletRespo > > >nse;)V) Illegal target of jump or branch > > >(class: jrun__C150__applicant2ejsp13, method: _jspService signature: > > >(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpS > > ervletRespo > > >nse;)V) Illegal target of jump or branch > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=8 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=8 Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm
