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?


View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866298#3866298

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866298


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to