tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <rmannibu...@gmail.com>
Subject Re: Intermittant javax.naming.NamingException: Not remotable
Date Sat, 26 Oct 2013 08:42:43 GMT
Hi Tim

No need to post it 4 times.

If you dont get answers either nobody knows or you didnt give enough
details to ring a bell.

Is it on trunk? Is it with an ear?...
Le 23 oct. 2013 15:16, "Thiago Veronezi" <thiago@veronezi.org> a écrit :

> Hi Tim,
>
> It seems that your first email is missing. I didnt see the moderate email
> for it yet. People can see the full thread here:
>
> http://openejb.979440.n4.nabble.com/Intermittant-javax-naming-NamingException-Not-remotable-tp4665677p4665699.html
>
> []s,
> Thiago.
>
>
>
> On Tue, Oct 22, 2013 at 11:36 AM, ymaraner <tphaley@gmail.com> wrote:
>
> > Nobody else has seen a remotable object JNDI lookup fail with a "Not
> > remotable" error message?
> >
> > I assume that people are assuming that the object is, in fact, not
> > remotable; however, the same remote business interface lookup, called
> from
> > the same code path against the same server with the same deployed
> > applications, succeeds most of the time.
> >
> > It seems to be when the server is extremely loaded, possibly with
> excessive
> > restful web service calls coming in and accessing other EJBs via
> injection,
> > that might trigger this behavior.
> >
> >
> >
> > -----
> > - Tim
> > --
> > View this message in context:
> >
> http://openejb.979440.n4.nabble.com/Intermittant-javax-naming-NamingException-Not-remotable-tp4665677p4665699.html
> > Sent from the OpenEJB User mailing list archive at Nabble.com.
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message