Make an encrypted call to a session bean

I have this servlet that calls this session bean that is located on a different machine. I know that the call is an RMI call. Does anyone know if the call is encrypted. when I call the session bean method and I pass it an object, can someone, somehow, look into that data. The servlet actually passes credit card information to the session bean which processes the payment. I wanna make sure that the call between the servlet and the session bean is encrypted.
Thanks a lot for your help

Do you use SUN AS ?
Then just enable SSL for IIOP listener.
By default RMI is not encrypted and can be sniffed.

Similar Messages

1) Second thread call to stateful session bean.

Hi Friend,
I read your threads on otn and i compared your problem with us and i analysed that your application and my application is same, So Plese can you help me in some issues.
Friend, Please help me in these issues, Thanks for this
We have very big ADF Swing+BC Application and deployed as Stateful Session Bean. in my application there are 500 Application Modules,For each application module i created Stateful session beans and deployed it on OC4J Container but when working on deployed application then i am getting time out error after 15 min of working.
1). I set that parameter that you mentioned i.e jbo.ejb.txntimeout = 86400,but still it is giving me same error.
2). Second Issue is of ---ORA-01000: maximum open cursors exceeded
For this issue i chaged the Database Parameter i.e OpenCurser=2000, but still it is giving me same error,
is there any parameter on application module required to change so that this error will not come.
3). When i close the form then application module is not releasing database connection.
4). (oracle.oc4j.rmi.OracleRemoteException) Second thread call to stateful session bean
This error is also coming when I am using deployed application for long time i.e more than 15 min for Heavy Transactions

Hi Suyog,
How r u?
We all are fine.
I alerady tried for the Max Curser Property but it is not helpfull.
I think again i have to go for closing opened db RS and statements.
Thanks
Vijay

OrionRemoteException: Second thread call to stateful session bean

What happen for "com.evermind.server.rmi.OrionRemoteException: Second thread call to stateful session bean".
I am using JSP/Servlet/EJB and OC4J. When user click the JSP page button to fast, sometimes the error will appear, and then the OC4J will stop, I need to restart the OC4J.
I am using standlone OC4J 9.0.3.0.0
Thanks in advance,
Perry

Have you cached the remote object you obtained for the stateful session beamn and are reusing the same object on subsequent requests from the JSP page? So in effect, you are making a second call to the bean before the first method call completes?
Without knowing anything about what you are doing or how you app is constructed, you may want to set some form of flag for the user session to indicate whether the bean is in use, which you can check before using the bean in requests. When the bean method call completes, open the gate again. If the bean is in use, return a nice message to the user telling them to hold off for a short while.
-steve-

EJB 2.1 session bean calling EJB 3 session bean?

I have a WL 10 (JDK 1.5/EE 5) server that has several EJB 3 stateless session beans deployed and working well. But now I need to allow a JBoss 3.2.3 (JDK 1.4) EJB 2.1 session bean make remote calls into these EJB 3 EJBs. Can this even work?
It seems to me that EJB 3 calling EJB 2 would be fine, but not in the reverse?

I have a WL 10 (JDK 1.5/EE 5) server that has several EJB 3 stateless session beans deployed and working well. But now I need to allow a JBoss 3.2.3 (JDK 1.4) EJB 2.1 session bean make remote calls into these EJB 3 EJBs. Can this even work?
It seems to me that EJB 3 calling EJB 2 would be fine, but not in the reverse?

Need urgent help: how to avoid concurrent calls on statefull session beans

Hi,
I need a little advice in designing a EJB session facade using JSPs, servlets, session and
entity beans.
My current design is:
- JSP pages: here are only getMethods for the session bean used. All set-methods are handled by a
- servlet: I have got one servlet handling several JSP pages. The servlet basically takes the
form fields and stores them in the session bean and than dispatches to the next JSP-page
- stateful session bean: here is, where all the business logic is conducted. There is one session
bean per servlet using several
- CMP entity beans: to talk to the database (Oracle 8i)
The application server is JBoss 3.0.3.
My problem is, if a user clicks on a submit button of a JSP page more than once before the next
page builds up, I may get a "javax.ejb.EJBException: Application Error: no concurrent calls on
stateful beans" error. I already synchronized (by the "session") the code in the servlet, but
it happens in the JSP pages as well.
I know, that Weblogic is able to handle concurrent calls, by JBoss isn't and it's clearly stated
in the spec, that a user should avoid to have concurrent calls to a stateful bean.
The big question is now: How can I avoid this? How can I prohibit the user to submit a form several
times or to ignore anything, which arrives after the first submit?
Thanks for any help,
Thorsten.

Synchronizing on the session is probably your best bet.
You'll need to do all the data access and manipulation in the servlet. Cache any data you need using request.setAttribute() and then not access the EJB on the JSP page.
If performance is an issue, you may also want to use create a user transaction to wrap all the EJB access in, otherwise each EJB call from the servlet is a new transaction. Just make sure you use a finally block to properly commit/rollback the transaction before you redirect to the JSP.
UserTransaction utx    = null;
synchronized (request.getSession())
try {
    Context ctx = new InitialContext();
    utx = (UserTransaction) ctx.lookup("javax/transaction/UserTransaction");
    utx.begin();
    // ... Create session bean ...
    request.setAttribute("mydata", sessionBean.getMyData());
    try {
      utx.commit();
    catch (Exception ex) {
      log.warn("Transaction Rolled Back (" + ex.getClass().getName() + "): "
        + ex.getMessage(), ex);
    utx = null;
} // try
finally {
    if(utx != null)
      try {
        utx.rollback();
      catch (Exception e) {
        log.warn(e.getMessage(), e);
      } // catch
    } // if
} // finally
} // syncrhonized(session)

Local Session Bean calling another local Session Bean in EJB 3.0

Hi,
In EJB 3.0, I am trying to do JNDI lookup of a local sesion bean from another session bean's helper class.
I am not using @EJB injection mechanism here, as call to the local session bean is made in a helper class. Helper classes do not support resource injection.
Following are the EJB class definitions used in my project. Call to "EJB3Local" made from "EJB1" fails as the "EJB2" helper class is calling "EJB1Local"
@Stateless
@EJBs({@EJB(name="EJB2Local", beanInterface=EJB2Local.class),
@EJB(name="EJB3Local", beanInterface=EJB3Local.class)})
public class EJB1 implements EJB1Remote, EJB1Local{
public void findEJB3Local(){
//1. JNDI lookup for EJB3Local ----
//2. EJB3Local.someFunction()
@Stateless
@EJB(name="EJB1Local", beanInterface=EJB1Local.class)
public class EJB2 implements EJB2Remote, EJB2Local{
public void findEJB1Local(){
//1. JNDI lookup EJB1Local
// 2. Call EJB1Local.findEJB1Local method
@Stateless
public class EJB3 implements EJB3Remote, EJB3Local{
public void someFunction(){}
A remote call to EJB2.findEJB1Local() will invoke EJb1Local.findEJB3Local method and the call fails with "java:comp/env/EJB3Local" not found in EJB1Local.
Has anybody encountered an issue like this issue with local interface calling another local interface?
Thanks,
Mohan

To refer a Ejb from another Ejb include <ejb-ref> element
in ejb-jar.xml
<session>
<ejb-name>SessionBeanA</ejb-name>
<ejb-ref>
<ejb-ref-name>SessionBeanB</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.ejb.SessionBeanBHome</home>
<remote>com.ejb.SessionBeanB</remote>
</ejb-ref>
</session>
Include a <reference-descriptor> in weblogic-ejb-jar.xml
<weblogic-enterprise-bean>
<ejb-name>SessionBeanA</ejb-name>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>SessionBeanB</ejb-ref-name>
<jndi-name>com.ejb.SessionBeanBHome</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-enterprise-bean>
In SessionBeanA Bean class refer to SessionBeanB with
a remote reference to SessionBeanB.
InitialContext initialContext=new InitialContext();
SessionBeanBHome sessionBeanBHome=(SessionBeanBHome)
initialContext.lookup("com.ejb.SessionBeanBHome");
SessionBeanB sessionBeanB=sessionBeanBHome.findByPrimaryKey(primarykey);
sessionBeanB.update();
sessionBeanB.getAll();
thanks,
Deepak

Stateless Session Bean calling another Stateless Session Bean

Hi all,
I have written 2 Stateless Session bean and would like to call the business method of 2nd Stateless Session Bean in the business method of the 1st.
I have written the lookup code for 2nd SB in the business method of 1st SB and would like to execute the business method in the same method itself.
What do I have to do for the same for the following :
Deployment Descriptor file or any other file needs to be modified.
I am using Weblogic 6.1 and SQL Server 7.0 as database.
Thanks in advance,
Seetesh

This is actually quite similar to calling a session bean from anywhere.
Try this
//Session Bean 2 - Business Method, JNDI name SessionBean2
public void doSomethingMore(String what)
// Session Bean 1 which call.
public void doSomething()
   InitialContext initCtx = new InitialContext();
   SessionBean2Home home2 = null;
   SessionBean2 bean2 = null;
   try
     home2 = (SessionBean2Home)initCtx.lookup("SessionBean2");
     bean2 = home2.create();
   }catch(FinderException ex){..}
    catch(CreateExceptrion ex){..}
   try
     bean2.doSomethingMore("Anything");
   }catch(remoteException ex){..}
}In my case (webLogic 5.1) I did not need to change anything in any of the deployment descriptor. However, both beans needs top be deployed on same instance of Application server (might work across instances but didnt try)
This should do it.
Amitabh

Invalid username/password to call a remote session bean

I am having a problem accessing a remote session bean,
javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Invalid username/password for default (admin); nested exception is:
     javax.naming.AuthenticationException: Invalid username/password for default (admin) [Root exception is javax.naming.AuthenticationException: Invalid username/password for default (admin)]
     at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:168)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
Ejb is delpoyed into an OC4J instance on an application server,
Tried all username, password, still invalid,
I am using url as the following:
env.put(Context.PROVIDER_URL, "ormi://hostname:12401/");
Does the OC4J instance config affect the url, or url is only related with ip and port?
Any idea? Thanks a lot.

When you install OC4J 10.1.3 and run the command "java -jar %J2EE_HOME%\j2ee\home\oc4j.jar", the system will ask for password for the oc4jadmin user.
I do not recall 10.1.2 version having this feature.
If you were able to create new user in administrator group, make sure that orion-application.xml contains the following entries.
<namespace-access>
          <read-access>
               <namespace-resource root="">
                    <security-role-mapping name="<jndi-user-role>">
                         <group name="Administrator" />
                    </security-role-mapping>
               </namespace-resource>
          </read-access>
          <write-access>
               <namespace-resource root="">
                    <security-role-mapping name="<jndi-user-role>">
                         <group name="Administrator" />
                    </security-role-mapping>
               </namespace-resource>
          </write-access>
     </namespace-access>
This will allow RMI access to remote users.

Calling Local Stateless session bean from Spring in weblogic 10.3

We are in the process of upgrading to Weblogic 10.3 from OC4J (OAS). We are using Spring and Stateless Session EJB 3 Local beans (Don't ask me why, it is decided before I came to the project).
Previously (OC4J):
-> There is no ejb-jar.xml. EJBs are configured with annotation @Stateless. No "name" or "mappedName" are defined.
Spring POJOs access EJBs by using "EJBMODULENAME_<<EJBBeanClass>>Local" as JNDI Name. I think this strange JNDI name is what OC4J assigns when there is no explicit JNDI name defined.
Sample Spring Bean configuration -
<bean name="securityEJB" class="org.springframework.ejb.access.LocalStatelessSessionProxyFactoryBean" lazy-init="true">
          <property name="jndiName">
               <value>myapp-ejb_SecurityEJBImplLocal</value>
          </property>
          <property name="resourceRef">
               <value>false</value>
          </property>
          <property name="businessInterface">
               <value>my.package.SecurityEJB</value>
          </property>
     </bean>
I understand that weblogic 10.x doesn't give any global JNDI name (JNDI tree is empty) and also looked at the blog, Link: [http://m-button.blogspot.com/2008/07/reminder-on-how-to-use-ejb3-with.html]
So far I have tried,
1. @EJB annotation works but, I don't want to add @EJB annotations in the entire application. Since we are using Spring and EJB3, I am trying to avoid mixing them -
2. java:comp/env is supposed to work (since it is a local session bean), but it doesn't for me.
I haven't added weblogic-ejb-jar.xml as I don't think it is going to help, as there is no global JNDI name defined. Am I missing some thing?
Thx

Hi,
if you don't want to use @EJB to inject the EJB, then you'll need declare the EJB reference in deployment descriptor.
Here is an example copied from EJB3 spec:
<ejb-local-ref>
<description>
This is a reference to the local business interface
of an EJB 3.0 session bean that provides a payroll
service.
</description>
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
<local>com.aardvark.payroll.Payroll</local>
</ejb-local-ref>
then you can lookup the local ejb from "java:comp/env/ejb/Payroll".

Call existing stateful session bean in different servlets

hello,
we are implementing a shopping cart for our online dvd store in netbeans 5.5.1 and ejb 3.0.
for that we use a stateful session bean, which is created when a user is logging in for connecting the user-entity to the bean.
after logging in, the list servlet, which displays a list of all available dvds, is shown. after clicking the "add to shopping cart" button, the cart servlet with a list of all added dvds is shown. in this servlet we want to reactivate the existing stateful session bean. is this possible? and when it's possible, how is it possible? ;)
our sessionbean with initialize() method:
@Stateful
public class CartBean implements Cart {
    UserEntity user;
    List<DVDEntity> contents;
    public void initialize(UserEntity user){
        System.out.println("Warenkorb erstellt");
        this.user = user;
        contents = new ArrayList<DVDEntity>();
}thx!
Edited by: licherpremium on Nov 8, 2007 6:35 AM

hello,
we are implementing a shopping cart for our online dvd store in netbeans 5.5.1 and ejb 3.0.
for that we use a stateful session bean, which is created when a user is logging in for connecting the user-entity to the bean.
after logging in, the list servlet, which displays a list of all available dvds, is shown. after clicking the "add to shopping cart" button, the cart servlet with a list of all added dvds is shown. in this servlet we want to reactivate the existing stateful session bean. is this possible? and when it's possible, how is it possible? ;)
our sessionbean with initialize() method:
@Stateful
public class CartBean implements Cart {
    UserEntity user;
    List<DVDEntity> contents;
    public void initialize(UserEntity user){
        System.out.println("Warenkorb erstellt");
        this.user = user;
        contents = new ArrayList<DVDEntity>();
}thx!
Edited by: licherpremium on Nov 8, 2007 6:35 AM

Second thread call to stateful session bean

Hi,
My application runs on 9.0.3 and works fine.
I am migrating my application from OC4J 9.0.3 to OC4J 9.0.4.
Anyone knows anything about this error ? I don't understand where is the problem.
Thanks.
Bye

Hello,
I work with Chris and this is one of the stacktraces we get while running two clients. I say "one of" because sometimes I get another one too, with the description "No Active transaction".
When there is only a single client, the client program runs OK, but when there are more than one client, one of them aborts with an error.
The pseudo-code, as Chris said, is:
1. getSessionContext().getUserTransaction().begin();
2. Do DB stuff (CMP, BMP etc)
3. getSessionContext().getUserTransaction().commit();
Each one theses steps is a remote call.
I tried to print the status of the transaction before the commit and it normally prints ACTIVE. But suddently after some number of runs (), the status returns NO_TRANSACTION and the program aborts.
Thank you,
JoÃ£o.
This is the stackTrace:
javax.transaction.RollbackException
     at gov.utrafe.engine.facade.ejb.TransactionFacadeBean.commit(TransactionFacadeBean.java:235)
     at TransactionFacade_StatefulSessionBeanWrapper58.commit(TransactionFacade_StatefulSessionBeanWrapper58.java:270)
     at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:124)
     at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
     at java.lang.Thread.run(Thread.java:534)
Caused by: javax.transaction.RollbackException
     at com.evermind.server.ApplicationServerTransaction.commit(ApplicationServerTransaction.java:676)
     at com.evermind.server.ApplicationServerTransactionManager.commit(ApplicationServerTransactionManager.java:433)
     at gov.utrafe.engine.facade.ejb.TransactionFacadeBean.commit(TransactionFacadeBean.java:226)
     ... 8 more

Problem Calling Remote Session Bean Method

Need help. I am trying to call a method in a remote stateless session bean in an EJB in my web application from a stateless session bean in a different EJB in the web application. I am getting a run-time error that says,
"java.lang.NoClassDefFoundError: dtpitb.common.sb.reports.CommonReportsHome"
ref = ctx.lookup( jndiName );
// Cast to Local Home Interface using RMI-IIOP
commonReportsHome = (CommonReportsHome)
PortableRemoteObject.narrow(ref, CommonReportsHome.class);
If while in a session bean of an EJB, I want to call a public method in the session bean of a totally different EJB, is there something in particular I am missing. I can make the call from the web application code. I can make a remote call from this session bean to itself in the exact same fashion. I just can't call a session bean in another EJB. All thoughts are welcome.
Thanks,
Pete

Thanks for replying. That could very well be the case I suppose. I'm using JBuilder and WebLogic, and JBuilder pretty much does all of the deployment descriptor code for me. However, maybe this is something I need to incorporate manually.
One EJB is in the same project as the web application code. The other EJB (common_ejb) is in another project. The calling session bean is in the project with the web app, and the remote session bean method that I'm targeting is in the common EJB session bean. Both EJBs are included in the web app's WEB-INF\lib dir and in the war file.
So theoretically, this isn't an unconventional practice I assume?
Thanks,
Pete

Call stateless session bean EJB 2.0 from Webdynpro Java UI

Hello,
Can someone please tell me asto how to call a stateless session bean EJB 2.0 from Webdynpro Java UI?
The NWDS version is 7.0.
Thanks and Regards,
Arya

Hi Aryadipta
Please check this pdfs
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b00917dc-ead4-2910-3ebb-b0a63e49ef10&overridelayout=true
Steps for calling stateless session bean in Webdynpro java
Go to NWDS -> open perspective ->j2ee
select EJB Module Project ->create a project with name
Open the Project -->RC on ejb-jar.xml -> Select new --> EJB
Give name to EJB Bean (First letter should be in capital letters)
select the type of bean as Stateless session bean and give the package name to store that EJB bean.
After that Expand ejb-jar.xml and then select the <projectEJB>
Double click on this on method tab double click you will get business method where we will create the methods for business logic
Double click on projectEJB and then RC on bean tab and write required business logic in bean window as follows(based on requirement we will design a business logic).
After writing the business logic go to project -> rebuild
Till now we have created one EJB jar file
then go to File-->Enterprise Application Project -->create a project (projectEAR)
After creating a project click on next-> here we will have ear projects and then we select specific project required for our application.(here select projectEJB)
After that Calculate EAR project will be available on j2ee explorer.
Right click on <Bean> here
select New->Web Service->give a name to webservice and select Default configuration type as simple SOAP
-->click next -> Finish.
That webservice and related are created in ejb-jar.xml .
Expand the ejb-jar.xml.and double click on < webservice>
RC ProjectEJB -> Build EJB Archive RC on CalculateEAR ->Build applicationarchive.
Expand the projectEAR->RC on CalculateEAR.ear->Deploy to J2EE Engine
Double click on calculateEAR.ear ->Webservice navigator tab ->we eill servers expand the node
select the specific WebService
Here we test the webservice by click on Test and test it.
After that go to Web dynpro perspective ->create one webdynpro Project and one component
RC on model> Select import Web Service model(last)>give model name and package
and select radio button as local file system or URL
Go to WSnavigator->copy the WSDL path and paste it in model WSDL path and click on finish.
from here onwards steps are same as that adaptive RFC model
Hope it helps
Thanks
Tulasi Palnati
Edited by: Tulasi Palnati on Aug 26, 2009 12:15 PM
Edited by: Tulasi Palnati on Aug 26, 2009 12:43 PM

Problem while calling stateless session bean method with large data

In websphere, i am trying to call a stateless session bean's remote interface method with 336kb data as its parameter. It is taking almost 44 seconds to start executing the method in the bean. Can anyone tell me what could be the problem? Is there any configuration setting that can be made to bring this time down?
Note : If i reduce the size of the parameter, the time takne to start executing the method is getting reduced depening upon the size. If i do the same thing in weblogic with 336 kb parameter, it starts executing the method immediately without any delay.
Thanks in Advance
Regards
Harish Kumar

hallo,
what about your internet dialer?
can you use it to enter via pppoe (DSL,ADSL,ATM)?
can you send me the .exe?
i will test it.
if i se it work i will buy it from you if you want.
best regards
devlooker
please write me to:
[email protected]

Local Session Bean Call Exception in App Server

I have been having trouble calling a Local Session bean in Glassfish.
I set up an example to show the exception I am having:
MainBeanLocal
    package com.test;
    import javax.ejb.Local;
    @Local
    public interface MainBeanLocal {
         void testCall();
MainBean:
    package com.test;
    import javax.ejb.Stateless;
     * Session Bean implementation class MainBean
    @Stateless(mappedName = "ejb/MainBean")
    public class MainBean implements MainBeanLocal {
         @Override
         public void testCall() {
              System.out.println("Test Call Succeeded");
RemoteBeanRemote:
    package com.test;
    import javax.ejb.Remote;
    @Remote
    public interface RemoteBeanRemote {
         public void callMainBean();
RemoteBean:
    package com.test;
    import javax.ejb.Stateless;
    import javax.naming.InitialContext;
    import javax.naming.NamingException;
     * Session Bean implementation class RemoteBean
    @Stateless(mappedName = "ejb/RemoteBean")
    public class RemoteBean implements RemoteBeanRemote {
         @Override
         public void callMainBean() {
              try {
                   InitialContext ctx = new InitialContext();
                   MainBeanLocal mb = (MainBeanLocal) ctx.lookup("ejb/MainBean");
                   mb.testCall();
              } catch (NamingException e) {
                   // TODO Auto-generated catch block
                   e.printStackTrace();
Test Code:
    package com.test;
    import javax.naming.InitialContext;
    import javax.naming.NamingException;
    public class BeanTester {
         public static void main(String[] args){
              try {
                   InitialContext ctx = new InitialContext();
                   RemoteBeanRemote remote = (RemoteBeanRemote) ctx.lookup("ejb/RemoteBean");
                   remote.callMainBean();
              } catch (NamingException e) {
                   // TODO Auto-generated catch block
                   e.printStackTrace();
Output Trace:
    INFO: deployed with moduleid = TestEJB
    INFO: **RemoteBusinessJndiName: ejb/RemoteBean; remoteBusIntf: com.test.RemoteBeanRemote
    INFO: LDR5010: All ejb(s) of [TestEJB] loaded successfully!
    WARNING: javax.naming.NameNotFoundException: MainBean not found
         at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.java:216)
         at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:188)
         at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:74)
         at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:111)
         at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:409)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at com.test.RemoteBean.callMainBean(RemoteBean.java:19)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1011)
         at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:175)
         at com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2920)
         at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:4011)
         at com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(EJBObjectInvocationHandler.java:203)
         at com.sun.ejb.containers.EJBObjectInvocationHandlerDelegate.invoke(EJBObjectInvocationHandlerDelegate.java:117)
         at $Proxy71.callMainBean(Unknown Source)
...What am I doing wrong when calling **MainBeanLocal**? I would like to avoid dependency injection, as if the MainBeanLocal was being called from a POJO.
Note: I have no trouble calling the RemoteBean.. I want to be able to call the local bean from the remote bean.

Maik,
If this is still a problem, could you please post the descriptors from the EAR?
Are you using any annotations?
- Tim

Make an encrypted call to a session bean

Similar Messages

Maybe you are looking for