javax.servlet.ServletException: One of the fields (projectId, issuetype, summary) is not present or of the wrong type I read the other issues "CVS Import broken", which helped me to get a bit ahead. Still this is blocking any progress moving to JIRA. The Map passed contains (type information in [Brackets]): assignee=reck [String] reporter=reck [String] projectId=10000 [Long] issueType=1 [String] summary=BSIfcAdapter shall use OT-BS for nameserver resolving [String] description=OTBS.1 [String] priority=4 [String] I tried using a String for projectId and Long for issueType, with no success. Therefore the Exception is misleading. Catching the exception in the JSP and printing it there I get:

Atlassian JIRA | Christoph Reck | 1 decade ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    Using the import_csv.jsp throws the following: javax.servlet.ServletException: One of the fields (projectId, issuetype, summary) is not present or of the wrong type I read the other issues "CVS Import broken", which helped me to get a bit ahead. Still this is blocking any progress moving to JIRA. The Map passed contains (type information in [Brackets]): assignee=reck [String] reporter=reck [String] projectId=10000 [Long] issueType=1 [String] summary=BSIfcAdapter shall use OT-BS for nameserver resolving [String] description=OTBS.1 [String] priority=4 [String] I tried using a String for projectId and Long for issueType, with no success. Therefore the Exception is misleading. Catching the exception in the JSP and printing it there I get: at com.atlassian.jira.issue.IssueUtils.createIssue(IssueUtils.java:94) at com.atlassian.jira.issue.IssueUtils.createIssue(IssueUtils.java:80) at org.apache.jsp.import_csv_jsp._jspService(import_csv_jsp.java:239) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:204) ... Please help me out with knowledge of what the source code expects. THX, Christoph

    Atlassian JIRA | 1 decade ago | Christoph Reck
    javax.servlet.ServletException: One of the fields (projectId, issuetype, summary) is not present or of the wrong type I read the other issues "CVS Import broken", which helped me to get a bit ahead. Still this is blocking any progress moving to JIRA. The Map passed contains (type information in [Brackets]): assignee=reck [String] reporter=reck [String] projectId=10000 [Long] issueType=1 [String] summary=BSIfcAdapter shall use OT-BS for nameserver resolving [String] description=OTBS.1 [String] priority=4 [String] I tried using a String for projectId and Long for issueType, with no success. Therefore the Exception is misleading. Catching the exception in the JSP and printing it there I get:
  2. 0

    javax.servlet.ServletException deployin portlet

    Stack Overflow | 1 year ago | Iñigo Boyano Ferrer
    javax.servlet.ServletException: Could not complete render request: View is null 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) 12:36:11,791 ERROR [http-localhost/127.0.0.1:8080-4][render_portlet_jsp:132] null 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) javax.portlet.PortletException 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at com.liferay.portlet.InvokerPortletImpl.invoke(InvokerPortletImpl.java:614) 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at com.liferay.portlet.InvokerPortletImpl.invokeRender(InvokerPortletImpl.java:677) 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at com.liferay.portlet.InvokerPortletImpl.render(InvokerPortletImpl.java:379) 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at org.apache.jsp.html.portal.render_005fportlet_jsp._jspService(render_005fportlet_jsp.java:1201) 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
  3. 0

    Connecting from JBoss 4.2 to JBoss 7.1

    codegur.com | 1 year ago
    javax.servlet.ServletException: Could not complete render request: View is null 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) 12:36:11,791 ERROR [http-localhost/127.0.0.1:8080-4][render_portlet_jsp:132] null 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) javax.portlet.PortletException 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at com.liferay.portlet.InvokerPortletImpl.invoke(InvokerPortletImpl.java:614) 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at com.liferay.portlet.InvokerPortletImpl.invokeRender(InvokerPortletImpl.java:677) 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at com.liferay.portlet.InvokerPortletImpl.render(InvokerPortletImpl.java:379) 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at org.apache.jsp.html.portal.render_005fportlet_jsp._jspService(render_005fportlet_jsp.java:1201) 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Build Best Practices to avoid Classloader leaks - OutOfMemoryError: PermGen space

    codegur.com | 1 year ago
    javax.servlet.ServletException: Could not complete render request: View is null 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) 12:36:11,791 ERROR [http-localhost/127.0.0.1:8080-4][render_portlet_jsp:132] null 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) javax.portlet.PortletException 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at com.liferay.portlet.InvokerPortletImpl.invoke(InvokerPortletImpl.java:614) 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at com.liferay.portlet.InvokerPortletImpl.invokeRender(InvokerPortletImpl.java:677) 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at com.liferay.portlet.InvokerPortletImpl.render(InvokerPortletImpl.java:379) 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at org.apache.jsp.html.portal.render_005fportlet_jsp._jspService(render_005fportlet_jsp.java:1201) 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) 12:36:11,791 INFO [stdout] (http-localhost/127.0.0.1:8080-4) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
  6. 0

    ApplicationDispatcher[] Servlet.service() jasper exception and 404 error

    Apache Bugzilla | 1 decade ago | t_santosh_k
    javax.servlet.ServletException: /ehs/environmental/kalamazoo.jsp

    Root Cause Analysis

    1. javax.servlet.ServletException

      One of the fields (projectId, issuetype, summary) is not present or of the wrong type I read the other issues "CVS Import broken", which helped me to get a bit ahead. Still this is blocking any progress moving to JIRA. The Map passed contains (type information in [Brackets]): assignee=reck [String] reporter=reck [String] projectId=10000 [Long] issueType=1 [String] summary=BSIfcAdapter shall use OT-BS for nameserver resolving [String] description=OTBS.1 [String] priority=4 [String] I tried using a String for projectId and Long for issueType, with no success. Therefore the Exception is misleading. Catching the exception in the JSP and printing it there I get:

      at com.atlassian.jira.issue.IssueUtils.createIssue()
    2. com.atlassian.jira
      IssueUtils.createIssue
      1. com.atlassian.jira.issue.IssueUtils.createIssue(IssueUtils.java:94)
      2. com.atlassian.jira.issue.IssueUtils.createIssue(IssueUtils.java:80)
      2 frames
    3. org.apache.jsp
      import_csv_jsp._jspService
      1. org.apache.jsp.import_csv_jsp._jspService(import_csv_jsp.java:239)
      1 frame
    4. GWT dev
      HttpJspBase.service
      1. org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
      1 frame
    5. JavaServlet
      HttpServlet.service
      1. javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
      1 frame
    6. GWT dev
      JspServletWrapper.service
      1. org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:204)
      1 frame