[JBoss-dev] JBoss3/Jetty4: Optimized call had serialized argument;....

2001-11-19 Thread Julian Gosnell


I have now plumbed in, thanks to David Jencks, a working copy of jetty4
(Servlet2.3, JSP 1.2).

I am running the WebIntegrationUnitTestCase from the testsuite and all
is going well.

A quick question:

Is this exception something someone is aware of - or is it more likely
that I have made a mistake?

I figure optimised calls are made if the current thread's
ContextClassLoader is correctly set - so they either happen or don't -
howcome then we are in an inconsistant state here, where we prepare to
make a serialised call and then it turns out to be optimised ?

Thanks for your time,


Jules


[01:10:08,484,Default] StatelessSessionBean2.ejbCreate() called
[01:10:08,497,Default] StatelessSessionBean2.noop,
test.wasSerialized=true, optimized=true
[01:10:08,510,StatelessSessionContainer] invoke returned an exception
java.rmi.ServerException: Optimized call had serialized argument; nested
exception is:
 javax.ejb.EJBException: Optimized call had serialized argument
javax.ejb.EJBException: Optimized call had serialized argument
 at
org.jboss.test.web.ejb.StatelessSessionBean2.noop(StatelessSessionBean2.java:77)

 at java.lang.reflect.Method.invoke(Native Method)
 at
org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:569)

 at
org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:67)

 at
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:98)

 at
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:156)

 at
org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:65)
 at
org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:131)

 at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166)

 at
org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.java:280)

 at org.jboss.ejb.Container.invoke(Container.java:528)
 at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)

 at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)

 at
org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerInvoker.java:411)

 at
org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerInvoker.java:493)

 at
org.jboss.ejb.plugins.jrmp.interfaces.GenericProxy.invokeContainer(GenericProxy.java:346)

 at
org.jboss.ejb.plugins.jrmp.interfaces.StatelessSessionProxy.invoke(StatelessSessionProxy.java:123)

 at $Proxy95.noop(Unknown Source)
 at
org.jboss.test.web.servlets.EJBOnStartupServlet.processRequest(EJBOnStartupServlet.java:84)

 at
org.jboss.test.web.servlets.EJBOnStartupServlet.doGet(EJBOnStartupServlet.java:104)

 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:289)
 at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:526)

 at org.mortbay.http.HttpContext.handle(HttpContext.java:1132)
 at org.mortbay.http.HttpContext.handle(HttpContext.java:1086)
 at org.mortbay.http.HttpServer.service(HttpServer.java:723)
 at org.mortbay.http.HttpConnection.service(HttpConnection.java:745)
 at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:918)
 at org.mortbay.http.HttpConnection.handle(HttpConnection.java:760)
 at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:138)

 at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287)
 at org.mortbay.util.ThreadPool$JobRunner.run(ThreadPool.java:715)
 at java.lang.Thread.run(Thread.java:484)
[01:10:08,597,Jetty] WARNING: GET /jbosstest/EJBOnStartupServlet
HTTP/1.1
java.rmi.ServerException: Optimized call had serialized argument; nested
exception is:
 javax.ejb.EJBException: Optimized call had serialized argument
javax.ejb.EJBException: Optimized call had serialized argument
 no stack trace available

[01:10:08,617,Jetty] ENCServlet: init





_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] JBoss3/Jetty4: Optimized call had serialized argument;....

2001-11-19 Thread Scott M Stark


This means the class loader is not set correctly or that the class loader
is more nested than the check performed by the JRMPContainerInvoker
is making can handle. This is the check that Marc mentioned earlier that he
was going to remove. When this is done this test will either succeed or
fail with a ClassCastException.

- Original Message -
From: Julian Gosnell [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, November 19, 2001 5:17 PM
Subject: [JBoss-dev] JBoss3/Jetty4: Optimized call had serialized
argument;



 I have now plumbed in, thanks to David Jencks, a working copy of jetty4
 (Servlet2.3, JSP 1.2).

 I am running the WebIntegrationUnitTestCase from the testsuite and all
 is going well.

 A quick question:

 Is this exception something someone is aware of - or is it more likely
 that I have made a mistake?

 I figure optimised calls are made if the current thread's
 ContextClassLoader is correctly set - so they either happen or don't -
 howcome then we are in an inconsistant state here, where we prepare to
 make a serialised call and then it turns out to be optimised ?

 Thanks for your time,


 Jules


 [01:10:08,484,Default] StatelessSessionBean2.ejbCreate() called
 [01:10:08,497,Default] StatelessSessionBean2.noop,
 test.wasSerialized=true, optimized=true
 [01:10:08,510,StatelessSessionContainer] invoke returned an exception
 java.rmi.ServerException: Optimized call had serialized argument; nested
 exception is:
  javax.ejb.EJBException: Optimized call had serialized argument
 javax.ejb.EJBException: Optimized call had serialized argument
  at

org.jboss.test.web.ejb.StatelessSessionBean2.noop(StatelessSessionBean2.java
:77)

  at java.lang.reflect.Method.invoke(Native Method)
  at

org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(Stateles
sSessionContainer.java:569)

  at

org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSe
ssionInstanceInterceptor.java:67)

  at

org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor
.java:98)

  at

org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.
java:156)

  at
 org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:65)
  at

org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:13
1)

  at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166)

  at

org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.jav
a:280)

  at org.jboss.ejb.Container.invoke(Container.java:528)
  at
 com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)

  at
 com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)

  at

org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerI
nvoker.java:411)

  at

org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerI
nvoker.java:493)

  at

org.jboss.ejb.plugins.jrmp.interfaces.GenericProxy.invokeContainer(GenericPr
oxy.java:346)

  at

org.jboss.ejb.plugins.jrmp.interfaces.StatelessSessionProxy.invoke(Stateless
SessionProxy.java:123)

  at $Proxy95.noop(Unknown Source)
  at

org.jboss.test.web.servlets.EJBOnStartupServlet.processRequest(EJBOnStartupS
ervlet.java:84)

  at

org.jboss.test.web.servlets.EJBOnStartupServlet.doGet(EJBOnStartupServlet.ja
va:104)

  at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
  at
 org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:289)
  at
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:526)

  at org.mortbay.http.HttpContext.handle(HttpContext.java:1132)
  at org.mortbay.http.HttpContext.handle(HttpContext.java:1086)
  at org.mortbay.http.HttpServer.service(HttpServer.java:723)
  at org.mortbay.http.HttpConnection.service(HttpConnection.java:745)
  at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:918)
  at org.mortbay.http.HttpConnection.handle(HttpConnection.java:760)
  at
 org.mortbay.http.SocketListener.handleConnection(SocketListener.java:138)

  at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287)
  at org.mortbay.util.ThreadPool$JobRunner.run(ThreadPool.java:715)
  at java.lang.Thread.run(Thread.java:484)
 [01:10:08,597,Jetty] WARNING: GET /jbosstest/EJBOnStartupServlet
 HTTP/1.1
 java.rmi.ServerException: Optimized call had serialized argument; nested
 exception is:
  javax.ejb.EJBException: Optimized call had serialized argument
 javax.ejb.EJBException: Optimized call had serialized argument
  no stack trace available

 [01:10:08,617,Jetty] ENCServlet: init





 _
 Do You Yahoo!?
 Get your free @yahoo.com address at http://mail.yahoo.com


 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] JBoss3/Jetty4: Optimized call had serialized argument;....

2001-11-19 Thread marc fleury

|This means the class loader is not set correctly or that the class loader
|is more nested than the check performed by the JRMPContainerInvoker
|is making can handle. This is the check that Marc mentioned earlier that he
|was going to remove. When this is done this test will either succeed or
|fail with a ClassCastException.

right,

marcf

|
|- Original Message -
|From: Julian Gosnell [EMAIL PROTECTED]
|To: [EMAIL PROTECTED]
|Sent: Monday, November 19, 2001 5:17 PM
|Subject: [JBoss-dev] JBoss3/Jetty4: Optimized call had serialized
|argument;
|
|
|
| I have now plumbed in, thanks to David Jencks, a working copy of jetty4
| (Servlet2.3, JSP 1.2).
|
| I am running the WebIntegrationUnitTestCase from the testsuite and all
| is going well.
|
| A quick question:
|
| Is this exception something someone is aware of - or is it more likely
| that I have made a mistake?
|
| I figure optimised calls are made if the current thread's
| ContextClassLoader is correctly set - so they either happen or don't -
| howcome then we are in an inconsistant state here, where we prepare to
| make a serialised call and then it turns out to be optimised ?
|
| Thanks for your time,
|
|
| Jules
|
|
| [01:10:08,484,Default] StatelessSessionBean2.ejbCreate() called
| [01:10:08,497,Default] StatelessSessionBean2.noop,
| test.wasSerialized=true, optimized=true
| [01:10:08,510,StatelessSessionContainer] invoke returned an exception
| java.rmi.ServerException: Optimized call had serialized argument; nested
| exception is:
|  javax.ejb.EJBException: Optimized call had serialized argument
| javax.ejb.EJBException: Optimized call had serialized argument
|  at
|
|org.jboss.test.web.ejb.StatelessSessionBean2.noop(StatelessSessionB
|ean2.java
|:77)
|
|  at java.lang.reflect.Method.invoke(Native Method)
|  at
|
|org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke
|(Stateles
|sSessionContainer.java:569)
|
|  at
|
|org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(St
|atelessSe
|ssionInstanceInterceptor.java:67)
|
|  at
|
|org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxIn
|terceptor
|.java:98)
|
|  at
|
|org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterc
|eptorCMT.
|java:156)
|
|  at
| org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:65)
|  at
|
|org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityIntercepto
|r.java:13
|1)
|
|  at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166)
|
|  at
|
|org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionCont
|ainer.jav
|a:280)
|
|  at org.jboss.ejb.Container.invoke(Container.java:528)
|  at
| com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
|
|  at
| com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
|
|  at
|
|org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPC
|ontainerI
|nvoker.java:411)
|
|  at
|
|org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPC
|ontainerI
|nvoker.java:493)
|
|  at
|
|org.jboss.ejb.plugins.jrmp.interfaces.GenericProxy.invokeContainer(
|GenericPr
|oxy.java:346)
|
|  at
|
|org.jboss.ejb.plugins.jrmp.interfaces.StatelessSessionProxy.invoke(
|Stateless
|SessionProxy.java:123)
|
|  at $Proxy95.noop(Unknown Source)
|  at
|
|org.jboss.test.web.servlets.EJBOnStartupServlet.processRequest(EJBO
|nStartupS
|ervlet.java:84)
|
|  at
|
|org.jboss.test.web.servlets.EJBOnStartupServlet.doGet(EJBOnStartupS
|ervlet.ja
|va:104)
|
|  at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
|  at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
|  at
| org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:289)
|  at
| org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:526)
|
|  at org.mortbay.http.HttpContext.handle(HttpContext.java:1132)
|  at org.mortbay.http.HttpContext.handle(HttpContext.java:1086)
|  at org.mortbay.http.HttpServer.service(HttpServer.java:723)
|  at org.mortbay.http.HttpConnection.service(HttpConnection.java:745)
|  at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:918)
|  at org.mortbay.http.HttpConnection.handle(HttpConnection.java:760)
|  at
| org.mortbay.http.SocketListener.handleConnection(SocketListener.java:138)
|
|  at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287)
|  at org.mortbay.util.ThreadPool$JobRunner.run(ThreadPool.java:715)
|  at java.lang.Thread.run(Thread.java:484)
| [01:10:08,597,Jetty] WARNING: GET /jbosstest/EJBOnStartupServlet
| HTTP/1.1
| java.rmi.ServerException: Optimized call had serialized argument; nested
| exception is:
|  javax.ejb.EJBException: Optimized call had serialized argument
| javax.ejb.EJBException: Optimized call had serialized argument
|  no stack trace available
|
| [01:10:08,617,Jetty] ENCServlet: init
|
|
|
|
|
| _
| Do You Yahoo!?
| Get your free @yahoo.com address at http://mail.yahoo.com