On Oct 3, 2007, at 3:59 AM, Phillpotts, James wrote:

> Hi all,
>
> I'm trying to port an EJB that we have previously used in weblogic  
> over
> to resin - so far this has been very simple. However, in one of the  
> EJB
> calls, I get a whole lot of hex output, and then an IOException:

Can you try 3.1.2?  I've reported this as a bug, but we have already  
made a good number of IIOP fixes in the 3.1 branch.

-- Scott

>
>
>  00 6e 00 69 00 65 00 4d 00 61 00 72 00 6b 00 65 .n.i.e.M.a.r.k.e
>  00 74 00 74 00 69 00 6e 00 67 00 3d 00 22 00 59 .t.t.i.n.g.=.".Y
>  00 65 00 73 00 22 00 20 00 77 00 61 00 6e 00 74 .e.s.". .w.a.n.t
> [10:42:57.557] java.lang.RuntimeException: java.io.IOException:  
> expected
> Fragment at 0
> [10:42:57.557]  at
> com.caucho.iiop.IiopReader.read_short(IiopReader.java:1346)
> [10:42:57.557]  at
> com.caucho.iiop.IiopReader.read_wstring(IiopReader.java:993)
> [10:42:57.557]  at
> com.caucho.iiop.IiopReader.read_wstring(IiopReader.java:980)
> [10:42:57.557]  at
> com.caucho.iiop.IiopReader.read_value(IiopReader.java:558)
> [10:42:57.557]  at
> com.caucho.iiop.MarshallObject.unmarshall(MarshallObject.java)
> [10:42:57.557]  at
> com.caucho.iiop.SkeletonMethod.service(SkeletonMethod.java:74)
> [10:42:57.557]  at
> com.caucho.iiop.IiopSkeleton.service(IiopSkeleton.java:98)
> [10:42:57.557]  at
> com.caucho.iiop.IiopRequest.handleRequest(IiopRequest.java:205)
> [10:42:57.557]  at
> com.caucho.server.port.TcpConnection.run(TcpConnection.java:514)
> [10:42:57.557]  at
> com.caucho.util.ThreadPool.runTasks(ThreadPool.java:520)
> [10:42:57.557]  at com.caucho.util.ThreadPool.run(ThreadPool.java:442)
> [10:42:57.557]  at java.lang.Thread.run(Thread.java:595)
> java.lang.RuntimeException: unknown type: 7
>         at com.caucho.iiop.IiopReader.readRequest(IiopReader.java:288)
>         at
> com.caucho.iiop.IiopRequest.handleRequest(IiopRequest.java:154)
>         at
> com.caucho.server.port.TcpConnection.run(TcpConnection.java:514)
>         at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:520)
>         at com.caucho.util.ThreadPool.run(ThreadPool.java:442)
>         at java.lang.Thread.run(Thread.java:595)
> [10:42:57.648] IIOP[15] java.lang.RuntimeException: unknown type: 7
> [10:42:57.648] java.lang.RuntimeException: unknown type: 7
> [10:42:57.648]  at
> com.caucho.iiop.IiopReader.readRequest(IiopReader.java:288)
> [10:42:57.648]  at
> com.caucho.iiop.IiopRequest.handleRequest(IiopRequest.java:154)
> [10:42:57.648]  at
> com.caucho.server.port.TcpConnection.run(TcpConnection.java:514)
> [10:42:57.648]  at
> com.caucho.util.ThreadPool.runTasks(ThreadPool.java:520)
> [10:42:57.648]  at com.caucho.util.ThreadPool.run(ThreadPool.java:442)
> [10:42:57.648]  at java.lang.Thread.run(Thread.java:595)
> CHUNKED:
>  00 73 00 4f 00 74 00 68 00 65 00 72 00 4d 00 61 .s.O.t.h.e.r.M.a
>  00 72 00 6b 00 65 00 74 00 74 00 69 00 6e 00 67 .r.k.e.t.t.i.n.g
>
>
> It looks to me like it's having a problem reading a value out of this
> XML request - I can't work out whether it's a problem with our request
> (which always worked in weblogic), or whether it's some  
> configuration I
> need to change to allow it to read more data in at a time, or what.
>
> Any pointers would be very gratefully received.
>
> Cheers,
> James
>
> PS - I'm using Resin v3.0.24
>
>
>
>
> This e-mail and any attachment is for authorised use by the  
> intended recipient(s) only. It may contain proprietary material,  
> confidential information and/or be subject to legal privilege. It  
> should not be copied, disclosed to, retained or used by, any other  
> party. If you are not an intended recipient then please promptly  
> delete this e-mail and any attachment and all copies and inform the  
> sender. Thank you.
>
>
> _______________________________________________
> resin-interest mailing list
> resin-interest@caucho.com
> http://maillist.caucho.com/mailman/listinfo/resin-interest



_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Reply via email to