Why do I use local bean interfaces?

When can I use a local bean interface?
Is it when the beans are deployed in the same manufacturers container system or do the beans just have to reside on the same physical machine?

Yes, you should always write local interfaces when
both web and ejb container using the same JVM.
This is incorrect. The EJB Local view (as opposed to the EJB Remote view)
can only be accessed by :
1) an EJB within the same ejb-jar
2) an EJB within a different ejb-jar but packaged within the same .ear
3) a web component(servlet or jsp) in a .war packaged within the same .ear
An ejb or web component in a different application(.ear) cannot portably
access the Local EJB view.
Kenneth Saks
J2EE SDK Team
SUN Microsystems
You can search out about more on local interface for
solving data-aliasing problem.

Similar Messages

Why do we use a home interface in EJB

I am trying to figure out why we need to use a HOME Interface in every EJB that we deploy in a container ? What is the significance ?
Thanks

Some info:
A home interface defines the methods that allow a client to create, find, or remove an enterprise bean. The home interface is EJB's way of creating an object. Home interfaces act as factories to create session beans and entity beans. The home interface defines the bean's life cycle methods, One of two interfaces for an enterprise bean. The home interface defines zero or more methods for creating and removing an enterprise bean. For session beans, the home interface defines create and remove methods, while for entity beans, the home interface defines create, finder, and remove methods.
You may want to also look up:
http://java.sun.com/j2ee/learning/tutorial/
http://java.sun.com/developer/onlineTraining/J2EE/Intro2/j2ee.html

Why use Java Beans?

Why should we use java beans?
Everybody says it is used to set the properties. What does this mean?
Can anyone give me a realtime scenario of the problems it can solve?
How does Spring framework utilize beans to solve problems? i.e wiring beans, declaring them in context file.

shalearns wrote:
Why should we use java beans?[http://java.sun.com/docs/books/tutorial/javabeans/index.html]
Everybody says it is used to set the properties. What does this mean?[http://java.sun.com/docs/books/tutorial/javabeans/whatis/index.html]
Can anyone give me a realtime scenario of the problems it can solve?[http://java.sun.com/docs/books/tutorial/javabeans/nb/index.html]
How does Spring framework utilize beans to solve problems? i.e wiring beans, declaring them in context file.[http://static.springframework.org/spring/docs/1.2.x/reference/beans.html]
~

CMP Entity beans using local interfaces

Why CMP entity beans with CMR relation ship using local interfaces only?
Why we should not use remote interface to get the CMR field relationship?
Pls give me the solutions

"Local interfaces provide the foundation for container-managed relationships among entity beans and session beans. The bean uses the local interface to maintain its references to other beans. For example, an entity bean uses its local interfaces to maintain relationships to other entity beans. Using local interfaces, beans can also expose their state and use pass-by-reference to pass their state between related bean instances. "
http://java.sun.com/developer/technicalArticles/ebeans/EJB20CMP/

Using local session bean interface from web container using EJB 3.0

Hi,
How can you use a local session bean interface from Java (rather than data controls) in a web container using EJB 3.0?
I can use a remote interface by looking up InitialContext, but I can't find a local interface this way (even from another session EJB). I can use a local interface from an EJB using annotation "EJB", but as I understand, this is not available in the web container.
If I try to add an ejb-jar.xml file, these seems to mess up by project...
Hope you can help.
Roger

The portable way to retrieve an EJB reference in Java EE is to either inject it or look it up via the
component's private naming environment. The simplest way is :
@EJB
private DocumentManager dm;
The global JNDI name is only used as an implementation specific way to uniquely assign an
identifier to a specific Remote EJB. It's best for this not to appear directly in the source code.
There's more on global JNDI names in our EJB FAQ :
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html
The alternative to annotations is to use an ejb-ref to declare the ejb dependency. The ejb-ref
is declared in the standard deployment descriptor corresponding to the component doing the
lookup. Each ejb-ref has an ejb-ref-name, e.g. <ejb-ref-name>DM_ref</ejb-ref-name>
The code looks up the ejb-ref-name relative to the java:comp/env namespace to retrieve the
EJB reference.
DocumentManager dm = (DocumentManager)
new InitialContext().lookup("java:comp/env/DM_ref");

Using local interfaces for EJB (session bean)

Hi,
I�ve a question regarding when to use the Local interfaces(EJBLocal and EJBLocalHome) of a enterprise bean. I understand that calls to enterprise bean can be made locally if the client which is invoking is in the same JVM as that of EJB. I�ve written a web client (servlet) which is packaged in a EAR and this servlet is trying to invoke a session bean which is in a �different� EAR using local interfaces. Both the EARs have been deployed in a single server (websphere 6.0 server). It didn�t work for me this way�..If I package the servlet in the same EAR of session bean then it works fine.
So is this to say that both EARs are not running on the same JVM? Or should it work even if the client and the session bean are in different EARs but in same server?
Can anyone explain me the fundamentals behind this.
Thanks in advance

Local access is only portable within the same .ear. For example, the Java EE SDK and SUN's
application servers have never supported local EJB access from a web/EJB component in a different
.ear. One issue is that local access requires that both the caller and target EJB have the same
classloader. By definition, different Java EE applications have distinct classloaders. In addition,
in Java EE 5 persistence context propagation does not span applications, so it wouldn't work in the
local case.
--ken

No performance gain when using local interfaces

Hello,
I'm doing some tests to compare performances between remote ejb interfaces and local ejb interfaces.
I have two stateless session beans EJB1 and EJB2, EJB1 calls a method on EJB2, this method receives one object as the only parameter and returns it immediately. The parameter is a big object (~700ko). My test consists simply of making 1000 calls from EJB1 to EJB2, one time with remote interfaces, one time with local interface. For both tests, the EJBs run in the same container, same VM.
The results show absolutely no differences between the remote and the local interface !
As I found these results a bit surprising, I changed the serialization method of my parameter object this way:
private void writeObject(java.io.ObjectOutputStream out) throws IOException {
System.out.println("writeObject(MyBigObject)");
out.defaultWriteObject();
just to check if my object is serialized when using remote interface. And the response is no.
So question is: is there an "undocumented optimization" of the stub/skel generated by weblogic which make local calls when calling a remote method inside the same VM ?
Some precisions:
- I'am using weblogic 8.1sp2
- When calling remotely my EJB2 from an external batch (running in a separate VM), I see the message "writeObject(MyBigObject)" so the serialization is done in this case.

<Fr?d?ric Chopard> wrote in message news:[email protected]..
So question is: is there an "undocumented optimization" of the stub/skel generated by weblogic which make local calls when callinga remote method inside the same VM ?
>
Some precisions:
- I'am using weblogic 8.1sp2
- When calling remotely my EJB2 from an external batch (running in a separate VM), I see the message "writeObject(MyBigObject)" sothe serialization is done in this case.
WebLogic 5.x, 6.x and 7.x do call by reference for co-located EJBs by default. 8.1 has this behavior turned off by default. You may
experience call-by-reference optimization in 8.1 only if it has been turned on explicitly in the deployment descriptor.
Hope this helps.
Regards,
Slava Imeshev

How to use local interface in my easy code ?

hi everybody
I work on an ejb project. My code is like that to test remote interface (and it works) :
public class TestStudent {
   Properties properties;
   public TestStudent() {
      properties = new Properties();
      properties.put("java.naming.factory.initial",
      "org.jnp.interfaces.NamingContextFactory");
      properties.put("java.naming.factory.url.pkgs",
      "org.jboss.naming:org.jnp.interfaces");
      properties.put("java.naming.provider.url", "jnp://localhost:1099");
      properties.put("jnp.disableDiscovery", "true");
   public static void main(String[] args) {
      TestStudent beanStudent = new TestStudent();
      beanStudent.createBean();
   public void createBean() throws EJBException {
      try {
         InitialContext context = new InitialContext(properties);
         Object object = context.lookup(StudentHome.JNDI_NAME);
         StudentHome studentHome = (StudentHome) PortableRemoteObject.narrow(object,StudentHome.class);
         Student student = studentHome.create();
         student.setName("pirlouit");
         System.out.println(student.getId());
         System.out.println(student.getName());
      } catch (NamingException e) {
         throw new EJBException(e);
      } catch (RemoteException e) {
         throw new EJBException(e);
      } catch (CreateException e) {
         throw new EJBException(e);
}Then I do quite the same thing to test local interface like in the following code but it doen't work :
public class TestStudent {
   Properties properties;
   public TestStudent() {
      properties = new Properties();
      properties.put("java.naming.factory.initial",
      "org.jnp.interfaces.NamingContextFactory");
      properties.put("java.naming.factory.url.pkgs",
      "org.jboss.naming:org.jnp.interfaces");
      properties.put("java.naming.provider.url", "jnp://localhost:1099");
      properties.put("jnp.disableDiscovery", "true");
   public static void main(String[] args) {
      TestStudent beanStudent = new TestStudent();
      beanStudent.createBean();
   public void createBean() throws EJBException {
      try {
         InitialContext context = new InitialContext(properties);
         Object object = context.lookup(StudentLocalHome.JNDI_NAME);
         StudentLocalHome studentLocalHome = (StudentLocalHome)object;
         System.out.println("studentLocalHome is null ? "+studentHome.equals(null));
         StudentLocal student = studentLocalHome.create();
         student.setName("pirlouit");
         System.out.println(student.getId());
         System.out.println(student.getName());
      } catch (NamingException e) {
         throw new EJBException(e);
      } /*catch (RemoteException e) {
         throw new EJBException(e);
      }*/ catch (CreateException e) {
         throw new EJBException(e);
}The print of "student local home is null ?" give me 'true' which is not the answer I want ... so here is the problem. How can I get my entity bean using local interface ?
For the moment 've got the exception (which appears on instruction "StudentLocal student = studentLocalHome.create();") :
Exception in thread "main" java.lang.NullPointerException
     at org.jboss.ejb.plugins.local.LocalHomeProxy.invoke(LocalHomeProxy.java:118)
     at $Proxy0.create(Unknown Source)Please help !! Thank you very much !

Write a JSP to test Local Interface. You cannot call Local Interface from a remote JVM.
Jay
http://www.javarss.com - Java News from around the world.
Visit JavaRSS.com and add above signature to your messages. Thanks!

Configure webapp to use local or remote interface based on environment

Hi,
I have the following problem I am trying to solve (app server is Weblogic 10g by the way).
I have a webapp (war-project) and an ear project containing stateless session beans.
In our development environment I would like to deploy the war and ear separately, because that is easier for development (war-project can then be deployed as a directory, so changes to jsp's and such have immediate effect).
Deploying the war and ear separately means that the war-project can only call the session beans through their remote interfaces. For development this is not a problem.
In a production environment however we would like to package the war INSIDE the ear, so that the webapp can use the local interfaces to call the session beans, as this will improve performance.
So I am looking for a solution where I can configure the way beans are called. Local if the war is inside the ear, remote if the war is separate from the ear. I was thinking along the lines of packaging a properties file with the war that determines the mode (local or remote). Or maybe packaging a different deployment descriptor, if that is a possibility.
This is what I have so far:
Business Interface_
package be.cegeka.test.ejb3.service;
public interface TestService {
     public void doSomething();
Remote Interface_
package be.cegeka.test.ejb3.service;
public interface TestServiceRemote extends TestService {
Local Interface_
package be.cegeka.test.ejb3.service;
public interface TestServiceLocal extends TestService {
Bean implementation_
package be.cegeka.test.ejb3.service;
import javax.ejb.Local;
import javax.ejb.Remote;
import javax.ejb.Stateless;
@Stateless(mappedName="ejb/TestService")
@Local(TestServiceLocal.class)
@Remote(TestServiceRemote.class)
public class TestServiceBean implements TestService {
     @Override
     public void doSomething() {
          System.out.println("I'm doing something");
     @Override
     public void doSomethingLocal() {
          System.out.println("I'm doing something local");
JSF backing bean_
package be.cegeka.test.ui;
public class MyWebAppBackingBean {
     @EJB(mappedName="ejb/TestService", beanInterface=TestServiceRemote.class)
     private TestService testService;
     public String doSmth() {
          testService.doSomething();
          return "success";
}The part that I would like to be configurable is the "+beanInterface=TestServiceRemote.class+" part in the JSF backing bean. Depending on the environment (development vs. production), this should be "+beanInterface=TestServiceRemote.class+" for development and "+beanInterface=TestServiceLocal.class+" for production.
Is something like this possible?
I would like to avoid having to fill my web.xml with ejb-refs and having to do the JNDI-lookups myself if at all possible, to keep things as easy and clean as possible.
Any ideas are welcome!
Steven

Hey Manish,
comments inline.
"manish kumar" <[email protected]> wrote in message
news:1794338.1102557677925.JavaMail.root@jserv5...
So If they are supposed to be in the same JVM -
then
1. the cluster of 3 weblogic servers are three JVMs. So does that meanLOCAL INTERFACES CAN'T BE USED IN CLUSTERED ENVIORONMENT ?
Sure they can, but the calling component in an enterprise app will not call
an intance of the local bean on another node in the cluster. It will make a
by-reference call to the local component in the same EAR. Local interfaces
are not Remote, so they cannot be used with by-value RMI semantics.
>
2. ARE YOU SURE ABOUT THIS FACT THAT THAT LOCAL INTERFACES CAN BE USEDONLY INSIDE THE SAME APPLICATION, I THOUGHT IT CAN BE USED AS LONG AS CLINET
IS IN THE SAME JVM?
PLEASE CONFIRM.........!!!!!!!!!!!!!Dead sure:
http://e-docs.bea.com/wls/docs81/programming/classloading.html#1073506
http://e-docs.bea.com/wls/docs81/ejb/understanding.html#1126831
http://e-docs.bea.com/wls/docs61/ejb/cmp.html#1085452
http://www.theserverside.com/discussions/thread.tss?thread_id=14628
Also, search the ejb newsgroups. I know Rob Woollen has addressed this in
here somewhere. And, if Rob says it's so, trust me, it's so.
Bill

What is the significance of Marker interface? Why are we using, even though

What is the significance of Marker interface? Why are we using, even though it has no method?

Well, what's the significance of an interface? They can define a set of methods a class may implement but the class could equally well implement these methods without the interface so why having interfaces at all?
The answer is that the most important aspect of an interface is that it constitutes a type (you can declare variables of it). And it's a type regardless of how many methods it defines, including none. So the reason for having a marker interface is that you're interested solely in the type aspect of interfaces.

Using Captivate with a localized user interface

Summary:
I'm working on an Adobe Captivate 2 project describing an
application that has been created in several languages.
I'm trying to follow the Captivate 2 help topic "Using Adobe
Captivate with a localized user interface", to create localized
movies for each language, but it does not work as described in the
help topic.
Can anyone help me with this problem, see below "What went
wrong?"
Steps to reproduce:
According to the help topic:
1. Record a source langauge file from the application (in my
case swedish).
2. Export the text captions to a Word document "Export
project captions and closed captions", and translate the text (into
english).
3. Record a new language file from the application, without
any automatically included objects.
4. Import all objects "Import slides/objects from other Adobe
Captivate projects>Objects only" from the source language file
created in step 1.
5. Import the the caption text "Import project captions and
closed captions" from the translated file in step 2.
What went wrong?:
Step 5 does not work, I cannot "Import project captions and
closed captions" into the new language file, the menu text is grey.
Product version:
Product: Adobe Captivate 2
Version: 2.0.0 Build 1177
Platform information:
Hardware: Qbic pc x86
OS Version: XP Professional
RAM: 1014 MB
Color Depth: ?
Display Card: Intel(R) 82865G Graphics Controller
Resolution: 1280 x 1024

Hi TekEl and welcome to our community
For what it's worth, here is how I might try it.
1. Record a project using either language.
2. Perform a "Save As" to a different name.
3. From the new project, export the Captions.
4. Localize as necessary.
5. Import the revised captions into the new project.
I think the trick here is to ensure that you only attempt to
import into the project that created the export.
Cheers... Rick

ClassCastException by using Local Interface of EJB in other, but local EAR

Hi,
I get a ClassCastException if I try to cast the EJSWrapper-Class returned from local EJB Lookup to the interface it implements.
The environment I use is WSADIE 5.1.1 with integrated Testenvironment.
I have defined two EARs. One with a Web-Application and one wich contains the EJB to call from the WebApp. Both run in the same appserver instance wich means both run in the same JVM and i should be able to use Local Interface of the EJB.
The EJB should use Libraries from the Server Environment while the WebApp uses newer Libs than the Server Environment offers(eg axis-rpc,wsdl4j,saaj). The Classloader-Policy of the EAR with the WebApp is set to PARENT_LAST while the Classloader-Policy of the EAR with the EJB is set to PARENT_FIRST.
I do a Lookup by using an EJB-Local-Reference. The returned object is an EJSLocalStatelessHome-Object, wich implements my LocalEJBInterface. But if i try to cast to Object to this interface a ClassCastException occurs.
The Classes of the EJB are packaged as follows:
EJBName.jar contains the EJB-Impl class, the Serverside Implementations for RMI/IIOP interaction an EJSWrapper classes. This jar is packaged with the EJB-EAR.
EJBClient.jar contains the Local- and Remote-Interface classes and the Stub-classes for EJBHome and EJB-Implementation. This jar is packaged wich both EARs, because of the interfaces, wich are needed in both projects.
The Classloader of the EAR with the WebApp has no access the jar with the EJB-Impl, the generated Ties- and EJSWrapperclasses because it is located in only the EJB-EAR. But the interface-class is contained in the WebApp-EAR as described above.
The exact Exception is as follows:
java.lang.ClassCastException: com/ibm/wsrf/EJSLocalStatelessBPEAdapterHome_c2546ef5 incompatible with com/ibm/wsrf/BPEAdapterLocalHome
java.lang.Throwable.<init>(Throwable.java)
java.lang.Throwable.<init>(Throwable.java)
java.lang.ClassCastException.<init>(ClassCastException.java:53)
org.tempuri.ResourceDiscoveryService.DiscoverySoapHttpBindingImpl.getResourceEPR(DiscoverySoapHttpBindingImpl.java)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java)
... The EJSLocalStatelessBPEAdapterHome_c2546ef5 implements the BPEAdapterLocalHome interface.
Please, can anyone give me a hint how to solve this problem?
Thanks in advance, Michael

Problem solved!
The different EAR contained each an own copy of the jar with the local and remote interfaces of the EJB. The Problem is caused by the separate classloaders of the EARs in an application server. Each EAR Classloader loads his own version of the interface classes. Is the same class loaded by different classloaders, the JVM handles this classes as different classes. An example if you create an instance of a class in one classloader and try to reference the created instance by the same class from another classloader, the association will fail, because of different classloaders in the same JVM.
The solution in an application server where you have deployed two projects and want to use local interfaces is, store the interfaces(and only the interfaces) in an directory, where it is found by the parent classloader of the EAR classloaders. Remove the Jar with the interface from the EARs. The EAR Classloaders will then search in the their parent classloader for the interfaces. The interfaces will be loaded by the parent classloader and will recognized as compatible by the JVM.
Greetings, hope this helps help others!
Michael

How to read a local file from Forms10g using PJC/Bean

I'm trying to read a file on the client machine using a Bean.
The code in the Bean is:
File fp = new File(mFileName);
printToConsole( "AFTER creating a File object " );
if (fp.exists())
I get the message after creating File object. But at the next statement - fp.exists() - the Forms session terminates giving a FRM-92100 - Your connection to the server was interrupted.
Any ideas?
Thanks in advance for your help.
Amit

Frank, Thank you for your response on signing the jar. That was exactly what I was missing. After signing the jar, I am able to do client level operations.
Grant, Thank you for asking about WebUtil. To give you a background as to what we are trying to do - to integrate our Forms 10g application with another software - in this case a client-server app. We want to send a message from this app. to our Forms10g app.(a pre-defined Form in the app.) which would initiate certain Forms navigation based on the message. In essence, Forms needs to be "listening" to this app. (in a non-blocking mode, the Forms app. should not be "locked-out" while listening for a message)
The only way I could think of was to write a Bean (modified version of Frank's Dispatch Event sample on his blog) which would spawn a thread and listen for a message from the other app. For our prototype, I started off with watching for a file on the client machine. The final goal is to listen for a message on MQ. This will facilitate us to integrate our Forms10g app. with any other app.
Regarding WebUtil, I did not find a way to do the listening/polling in a non-blocking way. Maybe I must have missed the obvious - Frank can very well attest to that.
Any feedback is most welcome.
Thanks.
Amit

Local bean access via JNDI returns a proxy object?

Hi,
I am using JBoss, and trying to access a local bean from another bean. One would think simple enough no, with the following code adequate:
Context initialContext = new InitialContext();
CartHome cartHome = (CartHome) initialContext.lookup(“java:comp/env/ejb/cart”);Which returns the home interface, right, but no in fact a $Proxy77 is returned. Can anyone tell me why this is? Or a solution please.
Thanks in advance.
Mike

Thanks, it works. But do you think calling the executeQuery from a backing bean is against any ADF related coding standards? Should that call be only in Application Module? Please comment.

Error during processing local bean: localejbs/RfcAFBean

Hi everybody
we currently trying to perform a RFC Call to our developpment system. The scenario is a simple File to RFC Scenario and it worked until yesterday. Since today the Messages stuck in the RFC receiver Adapter with the following errors in the audit log:
MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
Exception caught by adapter framework: Exception thrown in method process. The transaction is marked for rollback.
Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception thrown in method process. The transaction is marked for rollback.: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback..
The deffaultTrace.trc show the following entries. Looks like an error in localejbs/RfcAFBean:
RfcFunctionName:ZPSCD_INTERFACE_XXXXX
Date : 07/13/2007
Time : 9:32:39:301
Message :
[EXCEPTION]
com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:118)
     at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:264)
     at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
     at com.sap.aii.af.listener.AFWListenerBean.onMessage(AFWListenerBean.java:267)
     at com.sap.aii.af.listener.AFWListenerLocalObjectImpl0_0.onMessage(AFWListenerLocalObjectImpl0_0.java:103)
     at com.sap.aii.af.ra.ms.impl.ServicesImpl.deliver(ServicesImpl.java:306)
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1034)
     at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(ReceiveConsumer.java:392)
     at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.onMessage(ReceiveConsumer.java:86)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:848)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.NoSuchMethodError: com.sap.aii.af.rfc.core.config.RfcConfigManager.isPPActive(Lcom/sap/aii/af/service/cpa/Channel;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Z
     at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.isPPActive(RfcAFBean.java:385)
     at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.process(RfcAFBean.java:240)
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:103)
     ... 14 more
Severity : Error
Category :
Location : com.sap.engine.services.ejb
Application : sap.com/com.sap.aii.adapter.rfc.app
Thread : SAPEngine_Application_Thread[impl:3]_44
Datasource : 312846850:/usr/sap/XDS/DVEBMGS31/j2ee/cluster/server0/log/defaultTrace.trc
Message ID : 0003BA5D1D27006D000002BF0000653B000435201DA336D6
Source Name : com.sap.engine.services.ejb
Argument Objs : com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:118)
     at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:264)
     at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
     at com.sap.aii.af.listener.AFWListenerBean.onMessage(AFWListenerBean.java:267)
     at com.sap.aii.af.listener.AFWListenerLocalObjectImpl0_0.onMessage(AFWListenerLocalObjectImpl0_0.java:103)
     at com.sap.aii.af.ra.ms.impl.ServicesImpl.deliver(ServicesImpl.java:306)
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1034)
     at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(ReceiveConsumer.java:392)
     at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.onMessage(ReceiveConsumer.java:86)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:848)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.NoSuchMethodError: com.sap.aii.af.rfc.core.config.RfcConfigManager.isPPActive(Lcom/sap/aii/af/service/cpa/Channel;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Z
     at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.isPPActive(RfcAFBean.java:385)
     at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.process(RfcAFBean.java:240)
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:103)
     ... 14 more
Arguments : com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:118)
     at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:264)
     at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
     at com.sap.aii.af.listener.AFWListenerBean.onMessage(AFWListenerBean.java:267)
     at com.sap.aii.af.listener.AFWListenerLocalObjectImpl0_0.onMessage(AFWListenerLocalObjectImpl0_0.java:103)
     at com.sap.aii.af.ra.ms.impl.ServicesImpl.deliver(ServicesImpl.java:306)
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1034)
     at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(ReceiveConsumer.java:392)
     at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.onMessage(ReceiveConsumer.java:86)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:848)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.NoSuchMethodError: com.sap.aii.af.rfc.core.config.RfcConfigManager.isPPActive(Lcom/sap/aii/af/service/cpa/Channel;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Z
     at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.isPPActive(RfcAFBean.java:385)
     at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.process(RfcAFBean.java:240)
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:103)
     ... 14 more
Dsr Component :
Dsr Transaction : 3bdbc330311311dcb33b0003ba5d1d27
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives :
Resource Bundlename :
Session : 0
Source : com.sap.engine.services.ejb
ThreadObject : SAPEngine_Application_Thread[impl:3]_44
Transaction : SAP J2EE Engine JTA Transaction : [12ffffffa5ffffffaa200435f]
User : J2EE_GUEST
Date : 07/13/2007
Time : 9:32:39:304
Message : Error during processing local bean: localejbs/RfcAFBean
Severity : Error
Category :
Location : com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(String , ModuleData)
Application : sap.com/com.sap.aii.af.app
Thread : SAPEngine_Application_Thread[impl:3]_44
Datasource : 312846850:/usr/sap/XDS/DVEBMGS31/j2ee/cluster/server0/log/defaultTrace.trc
Message ID : 0003BA5D1D27006D000002C00000653B000435201DA33A4D
Source Name : com.sap.aii.af.mp.ejb.ModuleProcessorBean
Argument Objs :
Arguments :
Dsr Component :
Dsr Transaction : 3bdbc330311311dcb33b0003ba5d1d27
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives :
Resource Bundlename :
Session : 0
Source : com.sap.aii.af.mp.ejb.ModuleProcessorBean
ThreadObject : SAPEngine_Application_Thread[impl:3]_44
Transaction : SAP J2EE Engine JTA Transaction : [12ffffffa5ffffffaa200435f]
User : J2EE_GUEST
Date : 07/13/2007
Time : 9:32:39:306
Message : Rolling back transaction for message 38d82020-3113-11dc-c07b-0003ba5d1d27(INBOUND) due to: Exception thrown in method process. The transaction is marked for rollback.
Severity : Error
Category :
Location : com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(QueueMessage, MessageController, Services)
Application :
Thread : SAPEngine_Application_Thread[impl:3]_44
Datasource : 312846850:/usr/sap/XDS/DVEBMGS31/j2ee/cluster/server0/log/defaultTrace.trc
Message ID : 0003BA5D1D27006D000002C10000653B000435201DA341C8
Source Name : com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer
Argument Objs : 38d82020-3113-11dc-c07b-0003ba5d1d27(INBOUND),Exception thrown in method process. The transaction is marked for rollback.,
Arguments : 38d82020-3113-11dc-c07b-0003ba5d1d27(INBOUND),Exception thrown in method process. The transaction is marked for rollback.,
Dsr Component :
Dsr Transaction : 3bdbc330311311dcb33b0003ba5d1d27
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives :
Resource Bundlename :
Session : 0
Source : com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer
ThreadObject : SAPEngine_Application_Thread[impl:3]_44
Transaction : SAP J2EE Engine JTA Transaction : [12ffffffa5ffffffaa200435f]
User : J2EE_GUEST
It looks like the JCO Bean has an error. Any Ideas
Regards Oliver

Hi Bhavesh
I found some more interesting log entries and it seems to be a user password problem:
Retries exceded, set message 38f10280-3388-11dc-9c91-0003ba5d1d27(INBOUND) to status NON_DELIVERED.
Name or password is incorrect (repeat logon)
JCoClient connection missingHost:xdsci_XDS_31|AdapterType:MessagingSystem|Sender::FileServer|Receiver::PSCD_CDD|Interface:ZPSCD_INTERFACE_DECLAR_TVA:urn:sap-com:document:sap:rfc:functions|MsgID:38f10280-3388-11dc-9c91-0003ba5d1d27
Is this the user/password of the channel or is it service user for the JCO?
Regards Oliver

Why do I use local bean interfaces?

Similar Messages

Maybe you are looking for