0 Replies Latest reply on Feb 11, 2005 11:39 PM by kapil khanna

    Console output breaks after org.omg.CORBA.MARSHAL Exception

    kapil khanna Newbie

      I have a JSP that makes a EJB call to a Weblogic server 8.1 sp3.
      There is a mismatch between the client classes for the EJB on the web application and the ones on the Weblogic 8.1 server.
      I get the following exception on the JSP page, nothing on the console
      javax.servlet.ServletException: java.rmi.MarshalException: CORBA MARSHAL 1398079699 Maybe; nested exception is:
      org.omg.CORBA.MARSHAL: Unable to read value from underlying bridge : Mismatched serialization UIDs : Source (Rep. IDRMI:com.wyndham.features.property.valueobject.PropertyImpl:D4506DE0EBC76C6D:68595C982BBAD313) = 68595C982BBAD313 whereas Target (Rep. ID RMI:com.wyndham.features.property.valueobject.PropertyImpl:DE6345F4203F680C:9BA3A4843264774A) = 9BA3A4843264774A vmcid: SUN minor code: 211 completed: Maybe
      org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:825)
      org.apache.jasper.runtime.PageContextImpl.access$1100(PageContextImpl.java:64)
      org.apache.jasper.runtime.PageContextImpl$12.run(PageContextImpl.java:745)
      java.security.AccessController.doPrivileged(Native Method)
      org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:743)
      org.apache.jsp.testProp_jsp._jspService(testProp_jsp.java:94)
      org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
      javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
      org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
      org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
      org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
      javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
      org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)


      The exception is really not a problem, i know how to fix it. The real issue is more alarming.
      After this exception, any System.out.println() or exception.printStackTraces do not log to the console. Something breaks as far as console logging is concerned when this exception arises. This test case is reproucible every single time.
      Any idea why this is happening?