Re: Lookup for an EJB on a JBoss AS 7 from an Axis2 Webservice runs into a javax.naming.NameNotFoundException

 Am Freitag, den 02.08.2013, 05:01 +0200 schrieb "robertlazarski ." 
 <[email protected]>:
> On Fri, Aug 2, 2013 at 2:50 AM, Jörg <[email protected]> wrote:
>> Hello,
>> first of all I'm new on this mailing list but I'm working for 
>> several years
>> with Axis2.
>> But now after reading some books and articles I've a problem with 
>> the
>> collaboration of Axis2 and JBoss AS7.
>> Our situation: we run a bunch of Webservices based on Tomcat 
>> 7.0.22/Axis2
>> 1.5.4. Now for one web service
>> the business logic has changed and the service has to connect to an 
>> remote
>> ejb running on a JBoss AS 7.1.1.
>> The code:
>> very simple: first of all I created a little standalone client for 
>> this
>> remote ejb and everything works fine.
>> Then I placed the code in the webservice, and the jndi lookup 
>> failed.
>>
>> The code:
> <snip>
>
>> The error:
>> when doIt() is called, it goes to context.lookup() and then throws 
>> the
>> exception:
>> javax.naming.NameNotFoundException: Name ejb:app-ejb is not bound in 
>> this
>> Context
>> On the other side I find in the JBoss log:
>> 09:51:55,663 ERROR [org.jboss.remoting.remote.connection] (Remoting
>> "localhost" read-1) JBREM000200: Remote connection failed:
>> java.io.IOException: Received an invalid message length of 
>> -2140864253
>> So something goes to the JBoss but nothing what he expects.
>> Since this code runs in a standalone program it seems that the Axis2 
>> System
>> changes the protocol message. Maybe I've to do some configuration 
>> stuff?
>> Does anyone has experience in this area? So I will be grateful for 
>> some
>> hints.
>>
>> Best wishes
>>
>> Jörg
>>
>>
>>
>>
>>
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
> I use axis2 1.6.1 with JBoss AS 7.1.0 with no issues though I do not 
> use EJB.
>
> Are you using Spring with axis2 inside the aar? There are some known
> issues with jndi , not sure if it matches your problem, see the docs:
>
> http://axis.apache.org/axis2/java/core/docs/spring.html#a263
>
> Also, your are using a really old version of axis2. I'd try upgrading
> to see if that helps.
>
> Lastly, read this if you haven't already:
>
> http://axis.apache.org/axis2/java/core/docs/ejb-provider.html
>


 Hello,

 thank you much for your answer. Very good idea: an upgrade to axis2 
 1.6.2. solved my problem.

 Best wishes

 Jörg