cancel
Showing results for 
Search instead for 
Did you mean: 

bean not found - Java Server Proxy PI 7.11

Former Member
0 Kudos

Hi guys,

I am trying to generate a Java Server Proxy using PI 7.11.

I've followed the links below:

[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7d4db211-0d01-0010-1e8e-9b07fc2113ab?quicklink=index&overridelayout=true]

[http://wiki.sdn.sap.com/wiki/display/Java/JavaProxyChangesinPI7.1fromPI7.0]

When I try to execute I'm getting the following error:

com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: No remote bean found for reference of class $Proxy3192

That's strange because I've registered my bean with success in browser by using the URL below:

http://hsbbbfpid.bfe.sa.dir.bunge.com:53000/ProxyServer/register?ns=http://www.bunge.com/SAP_to_FAST...

Anyone can help me?

Thanks in advance.,

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Baskar,

Thank you for your reply. I redeployed the ear file and I faced the error again. Assume that I can see my ejb in NWA and he has the values below:

Object Name sap.com/Java_Proxy_BUNGE_EAR/ItfGLOGCarregamentoViagemInb_PortTypeBean

Class Name javax.naming.Reference

Context Name sap.com/Java_Proxy_BUNGE_EAR

Object Value Reference Class Name:

Type: clientAppName

Content: sap.com/Java_Proxy_BUNGE_EAR

Type: interfaceType

Content: remote

Type: home

Content: com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundHome4

Type: ejb-link

Content: ItfGLOGCarregamentoViagemInb_PortTypeBean

Type: remote

Content: com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundRemote4

So, if I have a remote ejb class in my NWA how can I got this error again:

com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: No remote bean found for reference of class $Proxy3266

Another regarding point is that I've received an ear file created in NWDS 7.0 but I've used NWDS 7.11 to deploy it on server.

baskar_gopalakrishnan2
Active Contributor
0 Kudos

>Another regarding point is that I've received an ear file created in NWDS 7.0 but I've used NWDS 7.11 to deploy it on server.

Couple of suggestions:

a) Though java compiler does support backward compatibility, still i see there might be jdk version issues too. PI 7.0 works in Jdk1.4 and PI 7.11 supports only Jdk 1.5 and above. You might want to recompile in netweaver developer studio with the latest jdk and see if the compiling goes without error.

b) if you specify java home in any config file, PLease make sure that you point the right jdk version that supports PI 7.11

Plus it is a better practice if we change jdk version, better to compile with the latest version and see whether build goes fine. Deploying ear file in pi 7.0 and pi 7.11 is different. Make sure using NWA and check whether your java ear file is propery deployed .

Former Member
0 Kudos

Hi,

In addition to the above suggestions chk this also:

http://help.sap.com/saphelp_nw04/helpdata/en/a4/d5b3b0b16843b3867c0245d9847ae5/content.htm

if a server bean is a co-located bean then use the prefix "localejbs/" with your bean name...

Thanks

Amit

Answers (3)

Answers (3)

Former Member
0 Kudos

I've finally got by doing it from the scratch using NWDS 7.1.

Cheers.,

ravi_kanakam
Explorer
0 Kudos

Dear glauco.r.cunha

How did you resolve your issue. I am facing the same issue. Can you please advise me on resolutions. Thanks in advance.

Ravi Kanakam

Former Member
0 Kudos

Thank you for the replies,

I think is better develop the solution again from scratch by using NWDS 7.1. Can someone provide me a step-by-step to develop this in NWDS 7.1, because, it's different from NWDS 7.0.

Assume that I will create an synchronous inbound service interface inside PI 7.1 and I will generate the proxy for it. What's the next if I will use the NWDS 7.1 to accomplish the solution?

Thanks!

baskar_gopalakrishnan2
Active Contributor
0 Kudos

The error message clearly says that the your deployment is not current or updated in the java netweaver stack of 7.11. Please work with BASIS, redeploy the ear file again and make sure the deployment is successful. Check log messages. After deployment successful , try to access and test. Also , if you have multiple versions of ear file deployment in the java netweaver stack, delete those old versions too. Sometime hot deployment did not work too. Refresh cache or restart the server.

Edited by: Baskar Gopal on May 19, 2011 12:31 PM