Getting methods out of the application module.

I have now deployed my BC components to the OAS as an EJB and now I am trying to get the method calls working from my applet. The module connection code somewhat confusing because of when I look at the EJB/Client snippet, it returns the remote interface, but I don4t know how to get projectmoduleimpl out what need to be returned. Could you please give me some insight to this issue? Here is the code what I am trying now...
public static ProjectModuleImpl/*Project.common.oas.RemoteProjectModule*/ getGenericAppMod(String platform)
String ejbUrl = "oas://<host>:8889/ProjectOAS/Project/ProjectModule";
// Setup the environment
Hashtable environment = new Hashtable();
// Turn JNDI on to OAS
environment.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "oracle.oas.naming.jndi.RemoteInitCtxFactory");
// Lookup the URL
Project.common.oas.ProjectModuleHome homeInterface = null;
try {
System.out.println("Creating an initial context");
Context ic = new InitialContext(environment);
System.out.println("Looking for the EJB published as 'ProjectOAS/Project/ProjectModule'");
homeInterface = ( Project.common.oas.ProjectModuleHome )javax.rmi.PortableRemoteObject.narrow(ic.lookup(ejbUrl), Project.common.oas.ProjectModuleHome.class);;
catch (CommunicationException e) {
System.out.println("Communication exception! Unable to connect: " + ejbUrl);
e.printStackTrace();
System.exit(1);
catch (NamingException e) {
System.out.println("Naming exception occurred!");
System.out.println("Cause: This may be an unknown URL, or some" +
" classes required by the EJB are missing from your classpath," +
" or your OAS host is short of resources");
System.out.println("Suggestion: Check the components of the URL," +
" and make sure your project includes a library containing the" +
" EJB .jar files generated by the deployment utility.");
e.printStackTrace();
System.exit(1);
// That's it!
try {
System.out.println("Creating a new EJB instance");
Project.common.oas.RemoteProjectModule remoteInterface = homeInterface.create();
Hashtable env = new Hashtable(2);
env.put(Context.INITIAL_CONTEXT_FACTORY, JboContext.JBO_CONTEXT_FACTORY);
env.put(JboContext.DEPLOY_PLATFORM, JboContext.PLATFORM_EJB_OAS);
Context ic = new InitialContext(env);
System.out.println("Initial context done1");
ApplicationModuleHome home1 = (ApplicationModuleHome) ic.lookup("Project.ProjectModule"); //Impl");
System.out.println("home done1");
//Module
ProjectModuleImpl appMod = (ProjectModuleImpl) home1.create();
System.out.println("module done1");
//Module
appMod.getTransaction().connect("jdbc:oracle:thin:<user>/<password>@<host>:1521:<SID>");
System.out.println("connection done1");
return appMod;
catch (Exception e) {
System.out.println("Module failed : " + e.getMessage());
e.printStackTrace();
return null;
}// end getgenericappmod
Thank you in advance!!

Am I to understand that this cannot be done? Please give me some info on this, because the applet works fine in the local mode and frankly, as you might quess, it is of no use if I cannot use the methods from OAS... I am waiting...

Similar Messages

  • Help!! - Unable to use the Application Module Deployed as Corba Object in Oracle 8i

    I have been able to successfully deploy an Application Module in Oracle 8i but i am un able to get a reference to the Application Module from the database the code used by me is -
    package client;
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import java.util.Hashtable;
    import oracle.jbo.*;
    import org.omg.CORBA.*;
    public class Corba8IClient{
    Hashtable env = new Hashtable();
    ApplicationModule appMod = null;
    String theAMDefName = "test/jd/freshJBO.FreshJBOModule";
    public Corba8IClient() {
    System.out.println("Started...");
    // Load the Application Module
    try{
    // Component deployed to Oracle8i CORBA Server.
    // Set up the 8i environment
    System.out.println("Setting up initial Context...");
    env.put(Context.INITIAL_CONTEXT_FACTORY, JboContext.JBO_CONTEXT_FACTORY);
    env.put(JboContext.DEPLOY_PLATFORM, JboContext.PLATFORM_ORACLE8I);
    env.put(Context.SECURITY_PRINCIPAL, "jd");
    env.put(Context.SECURITY_CREDENTIALS, "jd");
    env.put(JboContext.HOST_NAME, "Dev51");
    env.put(JboContext.CONNECTION_PORT, "2481");
    env.put(JboContext.ORACLE_SID, "ORA8I");
    // env.put(JboContext.APPLICATION_PATH, "test/jd/");
    System.out.println("Getting initial Context.");
    Context ic = new InitialContext(env);
    System.out.println("Doing Lookup...");
    ApplicationModuleHome home = (ApplicationModuleHome)ic.lookup(theAMDefName);
    System.out.println("Calling create...");
    // home
    System.out.println("Home Class Name : "+home.getClass().getName());
    oracle.jbo.client.remote.corba.aurora.AuroraApplicationModuleHome am = (oracle.jbo.client.remote.corba.aurora.AuroraApplicationModuleHome)home;
    System.out.println("DefName "+am.getDefName());
    appMod = home.create();
    System.out.println("Setting up connetion from AppMod to database...");
    appMod.getTransaction().connect("jdbc:oracle:thin:jd/jd@dev51:1521:ORA8I");
    }catch(Exception e) {
    e.printStackTrace();
    System.out.println("AppMod full Name "+ appMod.getFullName());
    public ApplicationModule getAppMod(){
    return appMod;
    public static void main(String args[]){
    Corba8IClient c8c = new Corba8IClient();
    after running the output is -
    Started...
    Setting up initial Context...
    Getting initial Context.
    Doing Lookup...
    Diagnostics: Silencing all diagnostic output (use -Djbo.debugoutput=console to see it)
    Calling create...
    Home Class Name : oracle.jbo.client.remote.corba.aurora.AuroraApplicationModuleHome
    DefName null
    oracle.jbo.ApplicationModuleCreateException: JBO-25222: Unable to create application module.
    at oracle.jbo.client.remote.corba.CORBAApplicationModuleHomeImpl.create(CORBAApplicationModuleHomeImpl.java:63)
    at client.Corba8IClient.<init>(Corba8IClient.java:39)
    at client.Corba8IClient.main(Corba8IClient.java:53)
    java.lang.NullPointerException
    at client.Corba8IClient.<init>(Corba8IClient.java:45)
    at client.Corba8IClient.main(Corba8IClient.java:53)
    Corba Object is deployed as -
    ObjectName = /test/jd/freshJBOModule
    Server Class = freshJBO.server.o8.FreshJBOModuleServerO8
    Helper Class = oracle.jbo.common.remote.corba.RemoteApplicationModuleHomeHelper
    The Application Module conatians an entity object and a view object for Dept Table in schema jd(Username -jd, Password -jd).

    Moneesh,
    I believe there is a problem with the way you set the variable theAMDefName. It should be:
    String theAMDefName = freshJBO.FreshJBOModule";
    Then you need to reinstate the line you commented out, to set the application path (but remove the trailing / from the path, as shown):
    env.put(JboContext.APPLICATION_PATH, "test/jd");
    If that doesn't work, and for future reference, I suggest testing your deployed application module from the Business Component Browser (aka the tester) before trying your hand-coded client. Start the tester, select Oracle8i as the middle tier server type, make sure the other information in the connect window is correct, then click Connect.
    Good luck
    Blaise

  • How to get the application module instance in backing bean.

    This is Ramesh, I am new to JDeveloper world.
    In my current application I have change password screen which allows user to change there password.
    Here this is a pop-up page. Here I don't have the view object and pagadef for this changepassword.jspx file.
    My aim is to call the Application Module method which takes the user name, old password and new password.
    In backing bean I am trying to call this method by using
    MyProjAM obj = _binding.getDataControl().getApplicationModule();  //throw null pointer exception.
    _binding is the object of DCBindingContainer. 
    ( I have created the parameter called "binding" as my managed bean property and values as #{binding})
    But the above line is throwing the NullPointerException.
    Could you please help me to come out of this problem.
    Thanks and Regards,
    Ramesh Biradar.

    If your page has no page definition, then #{bindings} will be null during the request for that page.
    If you need your page to invoke a data control method when you press a button, the simplest (and declarative) way is publish your AM method on the AM's client interface, then drop the method as a button from the data control palette onto your page. You don't even need a backing bean to accomplish this.
    That said, you can refer to a data control in a backing bean using the expression #{data.[i]YourAppModuleNameDataControl.dataProvider}
    So, assuming you have a helper method like this:
      public static Object EL(String expression) {
        FacesContext ctx = getFacesContext();
        Application app = ctx.getApplication();
        ValueBinding bind = app.createValueBinding(expression);
        return bind.getValue(ctx);
      }and assuming that your application module is named SRService
    and assuming that you have correctly nominated any Application Module custom methods as being available to clients by selecting them on the "Client Interface" panel of the application module editor, then in a backing bean you can acquire an instance.
    Then, the ADF design time will have automatically generated you a custom AM client interface named SRService and you can reference that service interface in your backing bean by using code like this:
            SRService svc = (SRService)EL("#{data.SRService.dataProvider}");
            svc.yourCustomMethod(your,args);

  • Question about the Application Module in bc4j

    Hi all,
    I've been playing with JDeveloper9i for a little ovar a week only and have been trying to get access to a BC4J View Object in order to execute a runtime specific query on it, by passing 2 user input values to the object, and setting the WHERE clause by a call to the setWhereClause() method on the View Object. The only way i could come across to get hold of the View Object was to create an Application Object (in this case its called Bc4jModule) and then to use a call to a custom method in the Application Module Implementation which i created and set to be a Client Method.
    The code is as follows:
    In the Application Module (Bc4jModuleImpl)
    public int authenticateUser(String strLogin, String strP_Word)
    getUsersView().setWhereClause(" LOGIN='" + strLogin + "' AND P_WORD='" + strP_Word + "'");
    System.out.println(getUsersView().getWhereClause());
    getUsersView().executeQuery();
    return getUsersView().getRowCount();
    In the JClient panel (JButton action):
    Bc4jModule app = (Bc4jModule)panelBinding.getApplicationModule();
    int n = app.authenticateUser(txtUser.getText(), txtPassword.getText());
    System.out.println("Number of rows queried = " + n);
    I would like to know if this is the best way of doing a custom query on the Entity Object or is there some other way that i'm missing?

    The best way would be to:
    [list=1]
    [*]Design a view object in JDeveloper which has bind variables for the parameters you need to pass in at runtime. For example, your WHERE clause for your view object would look like:
    LOGIN = :0 and P_WORD = :1[*]Add an instance of that view object definition to your application module
    [*]Write your custom AppModule method like this:
    public boolean authenticateUser(String strLogin, String strP_Word)
      getUsersView().setWhereClauseParams(new Object[]{strLogin,strP_Word});
      getUsersView().executeQuery();
      return getUsersView().first() != null;
    }[list]

  • Problem releasing the application module after upgrade to 11.1.1.2

    We have recently upgraded from JDeveloper 11.1.1.1 to 11.1.1.2.
    In the "tearDown()" method in our Unit Tests, the Application Module is realeased using:
    private ApplicationModule am;
    Configuration.releaseRootApplicationModule(am, true);
    Alter the upgrade, this produces the following error:
    oracle.jbo.JboException: JBO-33025: Failed to release application module MapServiceGlobal. Cookie handle not found.
    Please Help.
    FYI - this is the code that is used to create the application module:
    Hashtable env = new Hashtable(2);
    env.put(JboContext.INITIAL_CONTEXT_FACTORY,JboContext.JBO_CONTEXT_FACTORY);
    env.put(JboContext.DEPLOY_PLATFORM, JboContext.PLATFORM_LOCAL);
    try
    InitialContext ic = new InitialContext(env);
    ApplicationModuleHome home = (ApplicationModuleHome)ic.lookup(rootAM);
    am = home.create();
    catch (NamingException nex)
    /* Handle the error here if you don't find it */
    throw new NamingException("Application Module naming exception " + rootAM + " : " + nex.getMessage());
    /* Connect the AM to a database connection */
    am.getTransaction().connect(jdbcConnectionURL);
    * Set the bundled exception mode so that exceptions are thrown in the
    * same way as when we're running in the web application.
    am.getTransaction().setBundledExceptionMode(true);
    Thanks,
    -Spiro

    Hi,
    I used OCEP 10.3.0.0 and upgraded the wlevs30 domain to PS6(11.1.1.7.0). and it worked without such error.
    My experience is:
    1) in OCEP 10.3.0.0 it needs not to add the security groups in atnstore.txt
    2) you need to add <scratch-directory/> for Jetty in server's config.xml otherwise you will see the visualizer takes a long time to get up on Windows
    Thanks
    Junger

  • Coding custom business methods in ADF BC Application Module ?

    Dear All,
    Where do i put my custom business methods in ADF BC Application Module ?
    Can anyone point me to a good tutorial which gives a good insight into developing ADF BC Applications ?
    Thanks,
    Raghavendra

    Hi,
    there will be a developer guide out soon. Its written by Steve Muench and provides an indepth walk-through ADF BC.
    To answer your question, custom code is written in Java files on the ApplicationModule, ViewObject and EntityObject level. If you go to the Editor of each of these components there is an option for you to create Impl.java and RowImpl.java files. The first is for generic business logic, the latter for row based logic
    Frank

  • Getting error while importing the application in Oracle Apex

    Hi,
    I am facing an issue while importing an application into my new Oracle Apex installation. Installation was successful with out any issue. I exported an application from my old Apex (version 3.0.0.00.20) and importing the same into new apex (version 3.0.1.00.08). I am getting the following error.
    ============================================================
    The requested URL /pls/apex/wwv_flow.accept was not found on this server.
    ============================================================
    When I click on import in Application Builder page and then browse the required file it gives the progress saying "Importing File" and after some time it displays the above error.
    I tried bouncing the application also and there is not error in alert log.
    Could any one please suggest, if there is some problem here. Or my approach is not correct.
    Thanks in advance.
    Regards,
    Advait Deo

    Osacar, I recommend that you try to import the application into your workspace on apex.oracle.com and see what happens. Also, refine the problem statement as much as you can, e.g., you get this error importing "the application" or when importing "any" application. How big is the file you're trying to import? Where did it come from? Can you upload images?
    Scott

  • Logout has timed out because the application Mail failed to quit.

    Hello world... (Mac world that is)
    The message says more "Logout has timed out because the application Mail failed to quit. To try again, quit Mail and choose Log Out from the Apple menu."
    I tried everything. Still does not let me shut down.
    Other programs will not shut down at this time, including Finder. I also know that the Time Machine icon has been spinning for over an hour. So I imagine we are in a loop of sorts.
    Unfortunately, I have had similar troubles before that I did not record. So I figure I start now and see if somebody out there can help me.
    Peace!
    Chopo

    I'm having the same problem (can't logout, shut down or restart), but the referenced solution doesn't seem to apply. I do not get a "Cannot connect to server" message, I just get a "Logout has timed out" message. It seemed to happen after an automatic software update that was supposed to involve a restart, but it hasn't been able to restart since.
    Can you please clarify, what is meant by "delete the AutoLaunchedApplicationDictionary, which is located under the root node" (with reference to file loginwindow.plist)?
    This is what the loginwindow.plist file looks like now:
    bplist00Ñ!AutoLaunchedApplicationDictionary¢ÒTPathTHide-/Library/Printers/hp/hpio/HPEventHandler.app/Ò _N/Library/Application Support/Hewlett-Packard/Software Update/HP Scheduler.app//27
    I was at the genius bar earlier, and they said I need to 'archive and install' in order to 'reset the OS'... but there's got to be a better answer than that, no? Perhaps this plist thing? I'm surprised that even powering off the imac doesn't reset anything... it just comes back the way it was. I'm supposed to bring the 25 inch imac in to the mac store for surgery (archive and install), but seeing several similar cases on this discussion forum, without archive and install identified as the clear solution, I'm in search of a second opinion... or any suggestion for how to simply make this work the way it was before? Is it 10.5.4 that is causing this? Should I go back to 10.5.3?
    Any suggestions are appreciated. Thank you.

  • JCA - Failed calling get method getThreadSecurity on the ManagedConnectionF

    Hi All,
    This is my first post with the SDN, hope I could see and extend helping hands in form of technology and solutions
    My problem
    =============
    I am new to JCA.I am trying to deploy the helloworldra.ear provided by the IBM site.I deployed the resoource adapter and created a connectionFactory named "HelloWorld"(jndi).I get the below mentioned exception when I do
    ConnectionFactory cxFactory = (ConnectionFactory) context.lookup("java:comp/env/HelloWorld");
    Kindly chek into the exception and provide me with the solution.
    Thanks in Advance
    KABA
    Exceptions Snapshot
    ==================
    [7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O Populating Context
    [7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O #################### JNDI Context Contents ####################
    [7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.websphere.naming.hostname.normalizer ---:-- com.ibm.ws.naming.util.DefaultHostnameNormalizer
    [7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O java.naming.factory.initial ---:-- com.ibm.websphere.naming.WsnInitialContextFactory
    [7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.websphere.naming.name.syntax ---:-- jndi
    [7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.websphere.naming.namespace.connection ---:-- lazy
    [7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.ws.naming.ldap.ldapinitctxfactory ---:-- com.sun.jndi.ldap.LdapCtxFactory
    [7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.websphere.naming.jndicache.cacheobject ---:-- populated
    [7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.websphere.naming.namespaceroot ---:-- defaultroot
    [7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.ws.naming.wsn.factory.initial ---:-- com.ibm.ws.naming.util.WsnInitCtxFactory
    [7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.websphere.naming.jndicache.maxcachelife ---:-- 0
    [7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.websphere.naming.jndicache.maxentrylife ---:-- 0
    [7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.websphere.naming.jndicache.cachename ---:-- providerURL
    [7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O java.naming.provider.url ---:-- corbaloc:rir:/NameServiceServerRoot
    [7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O java.naming.factory.url.pkgs ---:-- com.ibm.ws.runtime:com.ibm.ws.naming
    [7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O #################### JNDI Context Contents END ####################
    [7/7/06 14:38:28:718 EDT] 5a004128 ConnectionFac E J2CA0066E: Failed calling get method getThreadSecurity on the ManagedConnectionFactory class com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource jca/HelloWorld with the value <null>. Exception is java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
         at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.getThreadSecurity(WSManagedConnectionFactoryImpl.java:612)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getThreadSecurity(ConnectionFactoryBuilderImpl.java:2520)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createMCFandPM(ConnectionFactoryBuilderImpl.java:1747)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1188)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
         at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
         at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1762)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1615)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1525)
         at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1225)
         at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
         at javax.naming.InitialContext.lookup(InitialContext.java:359)
         at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:293)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstance(IndirectJndiLookupObjectFactory.java:144)
         at com.ibm.ws.util.ResRefJndiLookupObjectFactory.getObjectInstance(ResRefJndiLookupObjectFactory.java:127)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
         at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
         at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:135)
         at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1227)
         at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1203)
         at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1257)
         at javax.naming.InitialContext.lookup(InitialContext.java:359)
         at com.ibm.ssya.helloworldra.servlets.HelloWorldBean.execute(HelloWorldBean.java:81)
         at org.apache.jsp._HelloWorldResults._jspService(_HelloWorldResults.java:105)
         at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java:89)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:357)
         at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java:675)
         at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:773)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
         at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
         at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
         at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
         at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
         at com.ibm.ssya.helloworldra.servlets.HelloWorldController.dispatch(HelloWorldController.java:101)
         at com.ibm.ssya.helloworldra.servlets.HelloWorldController.performTask(HelloWorldController.java:66)
         at com.ibm.ssya.helloworldra.servlets.HelloWorldController.doPost(HelloWorldController.java:88)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
         at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
         at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
         at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
         at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:201)
         at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
         at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:114)
         at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
         at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
         at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
         at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
         at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:431)
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
    [7/7/06 14:38:28:812 EDT] 5a004128 ConnectionFac E J2CA0009E: An exception occurred while trying to instantiate the ManagedConnectionFactory class com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource jca/HelloWorld : java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
         at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.getThreadSecurity(WSManagedConnectionFactoryImpl.java:612)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getThreadSecurity(ConnectionFactoryBuilderImpl.java:2520)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createMCFandPM(ConnectionFactoryBuilderImpl.java:1747)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1188)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
         at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
         at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1762)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1615)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1525)
         at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1225)
         at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
         at javax.naming.InitialContext.lookup(InitialContext.java:359)
         at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:293)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstance(IndirectJndiLookupObjectFactory.java:144)
         at com.ibm.ws.util.ResRefJndiLookupObjectFactory.getObjectInstance(ResRefJndiLookupObjectFactory.java:127)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
         at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
         at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:135)
         at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1227)
         at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1203)
         at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1257)
         at javax.naming.InitialContext.lookup(InitialContext.java:359)
         at com.ibm.ssya.helloworldra.servlets.HelloWorldBean.execute(HelloWorldBean.java:81)
         at org.apache.jsp._HelloWorldResults._jspService(_HelloWorldResults.java:105)
         at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java:89)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:357)
         at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java:675)
         at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:773)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
         at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
         at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
         at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
         at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
         at com.ibm.ssya.helloworldra.servlets.HelloWorldController.dispatch(HelloWorldController.java:101)
         at com.ibm.ssya.helloworldra.servlets.HelloWorldController.performTask(HelloWorldController.java:66)
         at com.ibm.ssya.helloworldra.servlets.HelloWorldController.doPost(HelloWorldController.java:88)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
         at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
         at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
         at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
         at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:201)
         at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
         at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:114)
         at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
         at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
         at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
         at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
         at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:431)
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
    [7/7/06 14:38:28:859 EDT] 5a004128 Helpers W NMSV0605W: A Reference object looked up from the context "localhost/nodes/localhost/servers/server1" with the name "jca/HelloWorld" was sent to the JNDI Naming Manager and an exception resulted. Reference data follows:
    Reference Factory Class Name: com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl
    Reference Factory Class Location URLs: <null>
    Reference Class Name: HelloWorld
    Type: connectorName
    Content: HelloWorld
    Type: classpath
    Content: C:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1\runtimes\base_v5/lib/rsadapter.rar
    Type: FactoryJndiName
    Content: jca/HelloWorld
    Address Type: dd
    AddressContents: ffffffac ffffffed 0 5 73 72 0 25 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 52 65 73 6f 75 72 63 65 ...
    Address Type: poolProps
    AddressContents: ffffffac ffffffed 0 5 73 72 0 27 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 43 6f 6e 6e 65 63 74 6f ...
    Address Type: configProps
    AddressContents: ffffffac ffffffed 0 5 73 72 0 23 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 43 6f 6e 6e 65 63 74 6f ...
    Address Type: mmProps
    AddressContents: ffffffac ffffffed 0 5 73 72 0 14 6a 61 76 61 2e 75 74 69 6c 2e 50 72 6f 70 65 72 74 69 65 73 39 12 ffffffd0 7a ...
    Address Type: mbeanProps
    AddressContents: ffffffac ffffffed 0 5 73 72 0 1a 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 4d 42 65 61 6e 50 72 6f ...
    Exception data follows:
    java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
         at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.getThreadSecurity(WSManagedConnectionFactoryImpl.java:612)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getThreadSecurity(ConnectionFactoryBuilderImpl.java:2520)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createMCFandPM(ConnectionFactoryBuilderImpl.java:1747)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1188)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
         at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
         at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1762)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1615)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1525)
         at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1225)
         at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
         at javax.naming.InitialContext.lookup(InitialContext.java:359)
         at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:293)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstance(IndirectJndiLookupObjectFactory.java:144)
         at com.ibm.ws.util.ResRefJndiLookupObjectFactory.getObjectInstance(ResRefJndiLookupObjectFactory.java:127)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
         at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
         at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:135)
         at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1227)
         at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1203)
         at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1257)
         at javax.naming.InitialContext.lookup(InitialContext.java:359)
         at com.ibm.ssya.helloworldra.servlets.HelloWorldBean.execute(HelloWorldBean.java:81)
         at org.apache.jsp._HelloWorldResults._jspService(_HelloWorldResults.java:105)
         at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java:89)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:357)
         at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java:675)
         at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:773)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
         at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
         at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
         at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
         at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
         at com.ibm.ssya.helloworldra.servlets.HelloWorldController.dispatch(HelloWorldController.java:101)
         at com.ibm.ssya.helloworldra.servlets.HelloWorldController.performTask(HelloWorldController.java:66)
         at com.ibm.ssya.helloworldra.servlets.HelloWorldController.doPost(HelloWorldController.java:88)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
         at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
         at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
         at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
         at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:201)
         at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
         at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:114)
         at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
         at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
         at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
         at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
         at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:431)
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
    [7/7/06 14:38:28:953 EDT] 5a004128 Helpers W NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow:
    Context implementation: com.ibm.ws.naming.jndicos.CNContextImpl
    Context method: lookup
    Context name: localhost/nodes/localhost/servers/server1
    Target name: jca/HelloWorld
    Other data:
    Exception stack trace: com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. Root exception is java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
         at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.getThreadSecurity(WSManagedConnectionFactoryImpl.java:612)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getThreadSecurity(ConnectionFactoryBuilderImpl.java:2520)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createMCFandPM(ConnectionFactoryBuilderImpl.java:1747)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1188)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
         at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
         at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1762)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1615)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1525)
         at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1225)
         at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
         at javax.naming.InitialContext.lookup(InitialContext.java:359)
         at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:293)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstance(IndirectJndiLookupObjectFactory.java:144)
         at com.ibm.ws.util.ResRefJndiLookupObjectFactory.getObjectInstance(ResRefJndiLookupObjectFactory.java:127)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
         at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
         at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:135)
         at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1227)
         at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1203)
         at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1257)
         at javax.naming.InitialContext.lookup(InitialContext.java:359)
         at com.ibm.ssya.helloworldra.servlets.HelloWorldBean.execute(HelloWorldBean.java:81)
         at org.apache.jsp._HelloWorldResults._jspService(_HelloWorldResults.java:105)
         at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java:89)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:357)
         at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java:675)
         at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:773)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
         at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
         at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
         at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
         at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
         at com.ibm.ssya.helloworldra.servlets.HelloWorldController.dispatch(HelloWorldController.java:101)
         at com.ibm.ssya.helloworldra.servlets.HelloWorldController.performTask(HelloWorldController.java:66)
         at com.ibm.ssya.helloworldra.servlets.HelloWorldController.doPost(HelloWorldController.java:88)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
         at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
         at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
         at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
         at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
         at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
         at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:201)
         at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
         at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:114)
         at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
         at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
         at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
         at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
         at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:431)
         at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
    [7/7/06 14:38:29:031 EDT] 5a004128 ConnectionFac E J2CA0066E: Failed calling get method getThreadSecurity on the ManagedConnectionFactory class com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource jca/HelloWorld with the value <null>. Exception is java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
         at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.getThreadSecurity(WSManagedConnectionFactoryImpl.java:612)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getThreadSecurity(ConnectionFactoryBuilderImpl.java:2520)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createMCFandPM(ConnectionF

    PersianKamran wrote:
    folks.. i am sending my class object on Sockets from client to Server (i am implementing Seriablizable Interface).
    No your aren't.
    You are sending the data in the class.
    That is what serialization does. (And actually not all data can be sent either.)
    When i get the object on server, i am able to print all its fields and methods... But i have one problem. I want to invoke a simple static method that just prints "hello".. The method on client that i am trying to invoke is....You probably either need stop attempting that or re-architect the solution.
    It is possible to send a class (not data) to another computer and that computer runs it. That is how applets work.
    But for that to work you must send the class. And deal with how the VM loads and unloads classes (not data) as well.

  • I am trying to download firefox5 and the download failed, and getting message To close the application -Rundell32.exe and Ox0000142

    Trying to download firefox 5 and the download failed i am getting message to close the application and cod number Ox0000142, is have any way to fix the problem with out removing window 7

    Open the Java pane in System Preferences. A separate application will launch. In the Security tab, check the box marked
    Enable Java content in the browser
    If necessary, adjust the Security Level slider, but if you must reduce the level, do so only temporarily and only if you are absolutely sure of what you're doing. Don't do this to play a game or because a stranger on the Internet asked you to. Java can be dangerous.
    If your browser is Safari, you may also need to make changes to the plugin settings in the Security tab of its preferences window.

  • Problems with the Application Module Pool

    Hello,
    We have an Oracle ADF Application working in a production enviroment. The application module pool seems to work properly during the first days, but after a few days, the application module pool seems not to work properly. We start to get some errors like JBO-30003: the application pool failed to checkout an application module.
    We have included in the application a DumpPoolStatistics servlet, and what we have observed is:
    1. When the application is restarted in the server, the "total number of application modules in the pool" is equal to "maximum number of application modules in the pool".
    2. Several days after, the "total number of application modules in the pool" starts to decrease.
    We don't know why the "total number of application modules in the pool" starts to decrease, but we think this is the reason of the errors. In fact, "total number of application modules in the pool" is lower than the "jbo.ampool.minavailablesize" parameter value.
    The management of the application module pool is not a task of the developer, so we don't undestand where is the problem.
    We have configured the application module with the next parameters:
    <jbo.ampool.initpoolsize>10</jbo.ampool.initpoolsize>
    <jbo.ampool.maxpoolsize>100</jbo.ampool.maxpoolsize>
    <jbo.ampool.minavailablesize>10</jbo.ampool.minavailablesize>
    <jbo.recyclethreshold>15</jbo.recyclethreshold>
    <jbo.ampool.maxinactiveage>600000</jbo.ampool.minavailablesize>
    <jbo.ampool.monitorsleepinterval>600000</jbo.ampool.monitorsleepinterval>
    <jbo.initpoolsize>15</jbo.initpoolsize>
    <jbo.maxpoolsize>30</jbo.maxpoolsize>
    <jbo.poolminavailablesize>15</jbo.poolminavailablesize>
    <jbo.poolmaxavailablesize>25</jbo.poolmaxavailablesize>
    <jbo.poolmonitorsleepinterval>30000</jbo.poolmonitorsleepinterval>
    <jbo.poolmaxinactiveage>30000</jbo.poolmaxinactiveage>
    <jbo.dofailover>true</jbo.dofailover>
    <jbo.ampool.resetnontransactionalstate>true</jbo.ampool.resetnontransactionalstate>
    <jbo.ampool.doampooling>true</jbo.ampool.doampooling>
    We are working with JDeveloper 10.1.3.4.
    Thanks in advance!

    Sorry, you are right, the number of application modules created whe the application starts is given by the jbo.ampool.initpoolsize. But what it is sure is that the "total number of application modules in the pool" starts to decrease. The number of days is not always the same. But we have to restart the application occasionally.
    I think the time parameters are ok, I would like for example 10 minutes for pool resoruce cleanup, and 10 minutes for considering an inactive AM instance in the pool as a candidate for removal during the next resource cleanup.
    <jbo.ampool.monitorsleepinterval>600000</jbo.ampool.monitorsleepinterval> --> 10 minutes
    <jbo.ampool.maxinactiveage>600000</jbo.ampool.minavailablesize> --> 10 minutes
    Is this right?

  • Android Emulator get hangs on starting the application in debug Mode

    I have deployed the application on Android Emulator in debug mode but on starting the app it get hangs. I have set the Java Debugging to true in the cvm.properties file and also started Java debugger from JDev before launching the ADF Mobile app on android emulator. Can any body help me to figure out the problem why the emulator gets hang on starting the application in debug Mode.

    Hi, after setting the debugging = true, you would also need to start the JDeveloper debugger and configure it for remote debugging. Shay has a blog article that should help.
    The emulator is hung while trying to connect to the JDeveloper debugger.
    https://blogs.oracle.com/shay/entry/debugging_adf_mobile_apps_on
    Thanks,
    Joe Huang

  • Howto stop the application module from using a DB

    Hello,
    Maybe and unusual question, but is there a way to stop the application module from connect to a DB? I know its purpose is to do so. But currently we are using ‘stub’ views and entities.
    In the executequery and dodml we wrote our own code to access data from webservices.
    We did this because we are also using JHeadStart which requires BC.
    It all works fine, but the application module needs a valid connection to a DB, although it will never query anything there.
    So is there a method which I can overwrite to make the application module think its connected to the DB but it actually isn’t?
    A second problem is most likely its state table.
    Anton

    Example #96 on my blog does this. It might have some useful clues.

  • Java code common to the applications modules

    I need help to generalise some methods and include them in project.
    I have some Java methods and I need it to be able to include/calll these methods from different application modules.
    I need it accessible to all app modules.
    Is there any way to do it?

    what we do is create a root application module to be the parent of all our app modules. edit that root app module and add your other app modules as nested app modules under the "Application Modules" section. then in your child app module java code you can initialize your root application module by using the getRootApplicationModule() method:
    YourServiceImpl yourServ = (YourServiceImpl)getRootApplicationModule();
    then you have access to all your methods in the master app module. however, to make sure you're accessing your app module in the desired hierarchy, you have to base your jhs app def file on your root app module or use your app module under the desired hierarchy in any of your custom adf pages.
    hope this helps
    paul

  • How to add an error message in the application module?

    Hi,
    I have some code running in the application module. I want to display error messages in the messages section of the screen if an error happens in my code.
    How could I achieve this?
    I am using JDeveloper 10G
    Thanks

    Muhammed,
    Have you tried throwing a JboException in your AM code?
    John

Maybe you are looking for

  • SAP PI conceptual best practice for synchronous scenarios

    Hi, <br /><br />Apologies for the length of this post but I'm sure this is an area most of you have thought about in your journey with SAP PI. <br /><br />We have recently upgraded our SAP PI system from 7.0 to 7.1 and I'd like to document  best prac

  • Gmail won't open in Firefox (and I've already reset it and deleted prefs.js)

    Gmail won't open in Firefox. I get this error: The page isn't redirecting properly Firefox has detected that the server is redirecting the request for this address in a way that will never complete. Steps I've taken: 1) Reset Firefox preferences 2) D

  • Page display in Reader 9.1

    Hi I like to have my pdf files open in Adobe Reader with the window maximised, the bookmarks in the left hand column and the pages displayed to fill the width of the remaining window space. I have tried various settings in Preferences to try and achi

  • Elements 9 and Apple Mac Lion - Exit Code 24 on installation

    When trying to install Elements 9 on a new Apple Mac with Lion Server (10.7) , I get the following error: Exit Code: 24 -------------------------------------- Summary -------------------------------------- - 0 fatal error(s), 19 error(s), 0 warning(s

  • Can anyone demystify the PSE Organizer catalog backup options?

    I need to backup my catalog--preferably just my catalog, not all my pictures (the picture files themselves are already backed up). More accurately, I would like my automated online backup service (Carbonite) to back up my PSE Organizer catalog for me