Problem not resolved: Java.lang.AbstractMethodError:javax.servlet.jsp.PageContext.getELContext () Ljavax/el/elcontext__js

Source: Internet
Author: User

Changed part of the code, the implementation of a sudden encounter the title exception, baffled, obviously did not move JSP and servlet, how suddenly reported this error ...

There is no solution on the Internet, and there is no relevant information. Later had to manually troubleshoot, access the JSP page alone no problem, once connected to the servlet on the accident, also do not know what is causing this problem. Because the report is El wrong, at first thought it was a jstl version of the problem, but think about just a good, it is not the reason. Later, according to the URL of the access to the page to delete the corresponding code, back to normal. Repeat several times after found the problem of the place, the error is as follows:

Exception

Org.apache.jasper.JasperException:Exception in JSP:/inc/pagination.jsp:5

2: <%@ taglib prefix= "PG" uri= "http ://jsptags.com/tags/navigation/pager "%>
3: <!--bottom section page-->				
4: <div align=center style=" font-size : 16px;padding-top:5px;padding-bottom:8px ">
5:      <pg:pager url=" list.do "	items=" ${requestscope[ ' Pe.pager '].maxelements} "
6: 		          maxpageitems=" ${requestscope[' Pe.pager '].pagesize} "  " >
7: 		<pg:index>
8: 			<pg:first unless= "current" ><a href= "${pageurl}&p=${pagenumber ......
Root cause
Java.lang.ArithmeticException:/By Zero
	com.jsptags.navigation.pager.PagerTag.pageNumber (pagertag.java:334)
	Com.jsptags.navigation.pager.PagerTag.doStartTag (pagertag.java:372)
	org.apache.jsp.list_jsp._ Jspservice (list_jsp.java:626) ...

Appears to be pagination in the JSP fragment, opened a look, this just remembered is modified the servlet mapping path, resulting in the <pg:pager url= "list.do" in the inconsistent, the paging component can not find the servlet

But this is not the real problem, after the change, found that even if the paging code deleted, the problem remains. Finally after the investigation, the error is located in the code used in the <c:forEach> part, as long as not to use will be no problem. Adjusted a night no effect, java.lang.AbstractMethodError like a ghost refused to leave, finally in a rage, a new project to do again, a section of code code from the original project in handcuffs. The use of the TOMCAT6, and finally no problem. Under the tomcat5.5.26, the problem still seems to be the Tomcat version of the problem AH. The real reason is still not found, just under the TOMCAT6 development, all normal.

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.