PeopleSoft Connector IT Resource setup

Hello,
I am setting the PeopleSoft Connector up in OIM and ran into some incomplete documentation from Oracle. I am following the installation guide named "Oracle® Identity Manager
Connector Guide for PeopleSoft Employee Reconciliation
Release 9.1.1
E11205-06"
In chapter 2, section 2.2.1.3 Configuring the IT Resource, the guide only shows 2 parameters (Configuration Lookup and IsActive).
The PSFT connector in design console shows more parameters to set. Some of them already have some default values. Some of them have blank and they are:
Admin
AdminCredentials
Jar File Location
Jolt Url
Native connection pool class definition
What are these parameters and what to set them to? Do I need to change any of the default values that are already set?
Thanks
Khanh

I got the log to work properly. I just went back to the People connector installation guide and followed the instructions from there.
Now, I have another question:
I am running the Peoplesoft HRMS Trusted Reconciliation and successfully brought in some users.
I would like to show the user middle name in OIM. For this I did the following set up in the design console:
1. In the RO Peoplesoft HRMS, Reconciliation Fields, I added the "Middle Name" field
2. In the Lookup.PSFT.HRMS.PersonBasicSync.AttributeMapping. I added Code Key = Middle Name and Decode = MIDDLE_NAME~NAMES~NAME_TYPE=PRI~EFFDT (I just set it up the same way that the OOTB first name and last name)
3. In the Lookup.PSFT.HRMS.PersonBasicSyn.Recon, I added Code Key = Middle Name and Decode = Middle Name
I ran a limited reconciliation for a few users. They showed up in OIM without the middle name. In the reconciliation manager, I can see the Middle Name as part of the Reconciliation Data. But the middle name does not show up in the USR form.
What am I missing?
Thanks
Khanh

Similar Messages

  • PeopleSoft connector failing after upgrade

    Has anyone heard of the Peoplesoft connector failing to connect after a PeopleTools upgrade? We have 9.1.1.5 of the Peoplesoft User Management Connector installed. Prior to the upgrade of PeopleTools, it was on version 8.50.09 and we were able to connector and provision users. After the upgrade to PeopleTools 8.50.16, we cannot connect. Below is a piece of the log file where we are getting this error:
    DEBUG,18 Apr 2011 11:03:33,015,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader:findClass - Data: loading class - Value: oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager
    DEBUG,18 Apr 2011 11:03:33,026,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader/findClass entered.
    DEBUG,18 Apr 2011 11:03:33,026,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader:findClass - Data: loading class - Value: psft.pt8.joa.API
    DEBUG,18 Apr 2011 11:03:33,027,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : getConnectionWithTimeout:: STARTED
    DEBUG,18 Apr 2011 11:03:33,027,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader/findClass entered.
    DEBUG,18 Apr 2011 11:16:09,519,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader/findClass entered.
    DEBUG,18 Apr 2011 11:16:09,519,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader:findClass - Data: loading class - Value: bea.jolt.JoltVersionException
    DEBUG,18 Apr 2011 11:16:09,522,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader/findClass entered.
    DEBUG,18 Apr 2011 11:16:09,523,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader:findClass - Data: loading class - Value: psft.pt8.joa.PSMessage
    ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],====================================================
    ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : getConnectionWithTimeout : Unable to connect to Application Server. Try :: 1
    ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],====================================================
    ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],====================================================
    ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : getConnectionWithTimeout : Previously created Session Destroyed : 1
    ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],====================================================
    DEBUG,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : getConnectionWithTimeout:: FINISHED
    INFO,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : connect : Connect = false
    ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],====================================================
    ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : connect : Maximum Retries Reached. exiting........
    ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],====================================================
    DEBUG,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : closeSession:: STARTED
    DEBUG,18 Apr 2011 11:16:09,525,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : closeSession : Session Closed : true
    DEBUG,18 Apr 2011 11:16:09,525,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : closeSession:: FINISHED
    ERROR,18 Apr 2011 11:16:09,530,[PSFTUM],====================================================
    ERROR,18 Apr 2011 11:16:09,530,[PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProvisionManager : createUser : Connection Failed
    ERROR,18 Apr 2011 11:16:09,530,[PSFTUM],====================================================
    DEBUG,18 Apr 2011 11:16:09,530,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/setAdpRetVal entered.
    DEBUG,18 Apr 2011 11:16:09,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getRetValString entered.
    DEBUG,18 Apr 2011 11:16:09,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getRetValString - Data: class - Value: java.lang.String
    DEBUG,18 Apr 2011 11:16:09,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getRetValString - Data: poRetVal.toString() - Value: PSFT.CONNECTION_ERROR
    DEBUG,18 Apr 2011 11:16:09,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getRetValString - Data: Returning:sRetVal - Value: PSFT.CONNECTION_ERROR
    DEBUG,18 Apr 2011 11:16:09,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getRetValString left.
    DEBUG,18 Apr 2011 11:16:09,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/setAdpRetVal - Data: Setting Adapter Return Value to PSFT.CONNECTION_ERROR - Value:
    DEBUG,18 Apr 2011 11:16:09,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/setAdpRetVal left.
    OIM: 9.1.0.2
    Any ideas?

    You will have to use the new psjoa jar. See the connector documentation for compatible psjoa jar.

  • PeopleSoft Connector 11.x transfrom

    Hi All,
    Anyone experienced the problem below?
    I wrote a custom transfom that implemented PeopleSoft Connector transform. The code work fine with Full Sync via XML file but did not work at all for the Basic Sync via Web Service. The error get from diagnosticlog is as below, not much to tell what wrong.
    Error> <ORACLE.IAM.CONNECTORS.PSFT> <BEA-000000> <com.example.transform: transformSingleMultivaluedData
    <Error> <ORACLE.IAM.CONNECTORS.PSFT> <BEA-000000> <oracle.iam.connectors.psft.common.handler.impl.PSFTPersonSyncReconMessageHandlerImpl: handleMessage: com.example.transform>
    Note: This is peoplesoft connector 11.x not 9.x. PeopleSoftOIMListener deployed according document (via command line)
    Thanks
    Edited by: dvt7288 on Jan 15, 2013 10:31 AM

    Hi,
    I don't have enough time to investigate the issue so I fixed the issue by using look up instead of transform. Basically, create a look up and treat it as the switch case. Once case matched just give it a decode value to what we want.
    I hope this help.

  • OIM 11g - PeopleSoft connector - Future Dated Recon Events

    Hi OIM Experts,
    I am having a problem, processing the future dated events using OIM peoplesoft connector.
    All the current dated, events are getting linked and processed.
    The future dated events in OIM are in deferred state as expected. But after running the "Run Future Dated Reconciliation Events " , the event is not linked to any user, but state changes to data received.
    The user exists in OIM.
    Any ideas on how to resolve this.
    Regards
    Vicky

    Hi Suren,
    1311 - Cause: Status of the batch is not 'Completed'.
    1311 - Event id, when i try to Re-Evaluate event.
    Regards
    Vicky
    Edited by: vicky on Jan 27, 2011 6:27 PM

  • Jakarta Tomcat Connectors (JK) + OC4J setup questions

    hi
    i'd like to use Apache 2.0 for dispatching requests to OC4J. i've been doing some experimenting and i was able to setup Apache and Jakarta Tomcat Connectors (JK) v1.2 to route requests to OC4J. this seems to be working fine in my development environment but how well supported or reliable is this setup?
    the requests are now being dispatched to JDeveloper 10.1.3 embedded OC4J instance. the only way i managed to do this was by modifying the embedded-oc4j/config/default-web-site.xml file and changing the web-site element protocol attribute value to "ajp13". this setup has the drawback that now direct http connections don't work anymore. is there a way to have both ajp13 and http connectors working simultaneously in the embedded OC4J?

    Sure there is. Add another web site configuration file, say, myHttp-web-site.xml, which is a copy > of the original default-web-site.xml with http protocol and a different port.
    ..after retrying this it seems to be working now. thanks.
    Can you share how you use the Jakarta Tomcat Connectors v1.2 here?sure, here you go:
    build JK
    # download JK v1.2.15 from http://tomcat.apache.org/download-connectors.cgi
    tar zxf jakarta-tomcat-connectors-1.2.15-src.tar.gz
    cd jakarta-tomcat-connectors-1.2.15-src/jk/native
    ./configure --with-apxs=/foo/bar/apache2055/bin/apxs
    make
    make install
    Configure Apache + JK
    # add the following lines to Apache httpd.conf
    LoadModule jk_module modules/mod_jk.so
    JkWorkersFile conf/workers.properties
    JkMount /<myctxroot>/* oc4j
    JkLogFile logs/mod_jk.log
    JkLogLevel debug
    # create conf/workers.properties with the following lines
    worker.list=oc4j
    worker.oc4j.port=8009
    worker.oc4j.host=localhost
    worker.oc4j.type=ajp13
    configure JDev OC4J
    cd $OC4J_HOME/embedded-oc4j/config
    cp default-web-site.xml ajp-web-site.xml
    # modify web-site element protocol attribute value to "ajp13" in ajp-web-site.xml
    # add the following line in embedded-oc4j/config/server.xml
    <web-site default="false" path="./ajp-web-site.xml" />
    # restart OC4J
    # restart Apache

  • OIM PeopleSoft Connector Employee Bulk Reconciliation

    My configuration: OIM9.0.3.1, OIMCP9.0.4.1, Oracle App Server 10.1.3.1
    I can get the PeopleSoft change-based reconciliation to work (with a few tweaks) but I don't know all the steps to configure the OIM server side. The connector doc is not really specifying this.
    Is it that you simply transfer the CSV file from the Peoplesoft server to a directory on the OIM server and that the FolderPath value (in the Recon task definition) will tell OIM to pick it up from there?
    If that's the case, I getting the following error in the OIM log:
    ERROR,06 Sep 2007 01:17:18,928,[ADAPTER.PSFTEMPLOYEE],com.thortech.xl.schedule.hostAccess.ReconcilePSFTHR::execute : java.lang.Exception: Server Name or Properties Not Found
    Has anybody done this before (on any version of OIM and OIMCP)?

    Regarding the second query for the people tools version 8.47. Since the Connector Pack which you are referring is 9.0.3, hence it supports the PT version upto 8.47 only. The latest connector pack is 9.0.4.1 which supports the peopleTool versions upto 8.48. Also the most latest version of PT 8.49 is also under the development phase to be supported by our connector.
    The other query for the support of the connector pack over environment other than windows, we could not find it in document. Can you please mention where in the deployment document you found that it is supported for Windows platform only.

  • What are minimum Admin acct permissions for PeopleSoft connector?

    Hi,
    We're in the process of configuring the OIM Connector 9.1.0 for PeopleSoft, and the documentation on "Creating a Target System Account for Connector Operations" describes creating a Permission List in PeopleSoft that seems to assume the Admin ID for the connector will also be the ID used to login to the PeopleSoft application itself and manage things on that side (I'm a PeopleSoft developer so I have a pretty clear idea that, for example, the connector's account doesn't need to be able to access App Designer, the developer's IDE, just to send transactions).
    We already have other accts that can login to the PeopleSoft side of things and do the necessary configuration and monitoring there, we just want the connector to be able to connect <g>, and then have access to the target component interface... but not a bunch of other privileges (working on the "least amount of access required" principal).
    Has anyone pared down the items in the Permission List defined for use by the connector, and if so what have you determined are the minimum privileges needed to connect and do provisioning?
    Note we will be using the Remote Manager service to implement.
    thanks,
    Anne

    Software Update gave an error I can't reproduce at the moment; but the upshot was that it could not write the package file to the directory. Permissions were drwxr-xr-x. I've solved that by making /Library/Packages writable by any user in group admin. (chown root:admin /Library/Packages; chmod 775 /Library/Packages.) Call me paranoid but I don't want to make that directory world-writable.
    The reason I'm updating in that fashion is that I choose to use the "minimalist approach" to system updates discussed in a MacFixIt article at http://www.macfixit.com/article.php?story=20070427001751397.

  • OIM Peoplesoft connector message for delete

    Can anyone help with the PSFT connector delete message?
    OIm is sent a message which is the same as the message before but this time with the delete flag set.
    So, for example. I added a row to change the position of a user in PSFT and oim receives and process it correctly.
    In PSFT, I now delete the row and a message is generated to OIM and PSFT connector does not process it. Logs show that it set the "ignore flag" to true.
    The two message are the same, except the AUDIT flag. First message has an 'A' and the second message has an 'D'
    What is expected is that OIM should undo the message it received to change the position of the user.
    thx

    Have you managed to solve this, I am also trying to get some information on this as we have workforce sync
    Not sure if we have to setup something like Routing for the WORKFORCE_SYNC Service Operation as shown at http://download.oracle.com/docs/cd/E11223_01/doc.910/e11205/deploy.htm#BIHGBFDI
    I am interested to know if you have got this working already !
    Regards
    Edited by: user12853463 on Jul 7, 2010 5:15 AM

  • Unable to recon using FlatFile - peoplesoft Connector

    Hi I am unable to do BulkUpload using FlatFile. The scheduler Task events are not being logged into log file,hence unable to see the error. I have checked all the configurations, seems to be correct. I am using Peoplesoft ER 9.1.0 and OIM 9.1.0.1 on Linux platform with Weblogic Server 10.3
    I dont know how to get the logging working, I have checked log.properties and enabled everything needed.
    log4j.logger.XELLERATE = DEBUG
    log4j.logger.XELLERATE.SCHEDULER = DEBUG
    log4j.logger.XELLERATE.SCHEDULER.Task = DEBUG
    log4j.logger.OIMCP.PSFTER=DEBUG
    Can anybody help me with recon problem and logging problem

    I had an issue with getting the PSFT flat file connector to work in the past. Since then, I've always gone with either a custom flat file connector or the GTC.

  • Troubleshooting the R/3 Connector framework resource adaptor

    Hello,
    I have opened this topic so I can monitor new questions and possible problems you may have regarding the R/3 connector.
    Best regards,
    Ran

    Hi! I am trying to establish an initial connection to the backend using JCO (please see below). When I do JCO.Client client = poolEntry.getJCOClient(), I get an exception as shown in the trace. Would you happen to have any idea why this is happening?
    Thanks,
    Haseem
    .................CODE FOLLOWS....................
    IJCOClientService clientService = (IJCOClientService)PortalRuntime.getRuntimeResources().getService(IJCOClientService.KEY);
    IJCOClientPoolEntry poolEntry;
    try
    poolEntry = clientService.getJCOClientPoolEntry("SAP_R3_HumanResources", request);
    catch (Exception e)
    logger.severe("ERROR: Exception reaised when calling getJCOClientPoolEntry()"+e.getMessage());
    return;
    JCO.Client client = poolEntry.getJCOClient();
    ................. STACK TRACE FOLLOWS..................
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:858)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:310)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:190)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:209)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:576)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:300)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:190)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:669)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:208)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:532)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
         at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:665)
         at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:312)
         at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
         at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1229)
         at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
         at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: com.sapportals.portal.prt.component.PortalComponentException: Exception during PageProcessorComponent.doContent()
         at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:139)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:300)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:190)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:209)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:576)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:300)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:190)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:669)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:208)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:532)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
         at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:665)
         at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:312)
         at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
         at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1229)
         at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
         at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: java.lang.reflect.InvocationTargetException: java.lang.NoClassDefFoundError
         at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.init(SAPCFConnectorManagedConnection.java:75)
         at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnectionFactory.createManagedConnection(SAPCFConnectorManagedConnectionFactory.java:62)
         at com.inqmy.services.eisconnector.server.ConnectionHashSet.match(ConnectionHashSet.java:250)
         at com.inqmy.services.eisconnector.server.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:138)
         at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorConnectionFactory.getConnectionEx(SAPCFConnectorConnectionFactory.java:136)
         at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:791)
         at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:737)
         at com.bi.hr.selfservices.paycheck.EmailManager$EmailJSPDynPage.initializeSAPConnection(EmailManager.java:219)
         at com.bi.hr.selfservices.paycheck.EmailManager$EmailJSPDynPage.onRejectButtonClicked(EmailManager.java:130)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)
         at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:101)
         at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:135)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:300)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:190)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:209)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:576)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:300)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:190)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:669)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:208)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:532)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
         at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:665)
         at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:312)
         at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
         at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1229)
         at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
         at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    [email protected]5 #

  • Does iPlanet App Server 6.5 provide support for Java Connector Architecture resource adapters? If not will 7.0?

     

    6.5 does not support JCA. 7.0 is announced on 19th June
    when the official statement regarding support for JCA
    will be made.

  • MDB deployement error in Glassfish - "JMS resource not created"

    Hi,
    I'm tring to deploy a J2EE application which has couple of MDBs in Glassfish 2.1. I get the following error when I deploy the EAR file to the app server. I've cofigured JMS resources using admin console but still getting this error. I've no experience of JMS, I'm not sure if I've configured it correctly. Any step-by-step guide with screenshots would be very useful, but can't find any. Please help me if you have any idea what I'm doing wrong. Thanks in advance.
    <br />
    [#|2009-03-05T13:09:10.143+0000|SEVERE|sun-appserver2.1|javax.enterprise.system.container.ejb|_ThreadID=35;_ThreadName=Thread-3757;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : ;_RequestID=075ba53a-1835-482d-9db7-fe79fe1f1eb3;|EJB5090: Exception in creating EJB container <a href="http://forums.sun.com/#" class="jive-link-anchor"></a><br />
    <br />
    [#|2009-03-05T13:09:10.143+0000|SEVERE|sun-appserver2.1|javax.enterprise.system.container.ejb|_ThreadID=35;_ThreadName=Thread-3757;_RequestID=075ba53a-1835-482d-9db7-fe79fe1f1eb3;|appId=cdm moduleName=cdm-ejb_jar ejbName=SupplierEJB|#]<br />
    <br />
    [#|2009-03-05T13:09:10.143+0000|SEVERE|sun-appserver2.1|javax.enterprise.system.core.classloading|_ThreadID=35;_ThreadName=Thread-3757;_RequestID=075ba53a-1835-482d-9db7-fe79fe1f1eb3;|LDR5004: UnExpected error occured while creating ejb container<br />
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : <br />
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1591)<br />
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1421)<br />
    at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)<br />
    at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)<br />
    at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:524)<br />
    at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:527)<br />
    at com.sun.enterprise.server.ApplicationLoader.doLoad(ApplicationLoader.java:191)<br />
    at com.sun.enterprise.server.TomcatApplicationLoader.doLoad(TomcatApplicationLoader.java:126)<br />
    at com.sun.enterprise.server.ExtendedApplicationLoader.doLoad(ExtendedApplicationLoader.java:134)<br />
    at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:238)<br />
    at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)<br />
    at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)<br />
    at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:159)<br />
    at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:538)<br />
    at java.lang.Thread.run(Thread.java:619)<br />

    Hi Nigel,
    Thanks for ur reply. In my ejb-jar.xml I have
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- Copyright (c) 2003 Sun Microsystems, Inc. All rights reserved. -->
    <ejb-jar version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
      <display-name>myJARName</display-name>
    <enterprise-beans>
        <message-driven>
          <display-name>myEJB</display-name>
          <ejb-name>myEJB</ejb-name>
          <ejb-class>com.mycompany.app.mdb.MyMessageBean</ejb-class>
          <messaging-type>javax.jms.MessageListener</messaging-type>
          <transaction-type>Container</transaction-type>
          <message-destination-type>javax.jms.Queue</message-destination-type>
           <message-destination-link>MyQueue</message-destination-link>
           <activation-config>
               <activation-config-property>
                   <activation-config-property-name>destinationType</activation-config-property-name>
                   <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
               </activation-config-property>
          </activation-config>
    .......So I've created JMS resource with same JNDI name and Physical destination name (both are MyQueue). I don't see any different JNDI name in ejb-jar.xml. Is it nor right?

  • Message driven bean: resource not created

    Hi,
    I'm having trouble deploying a simple test app that I've created (in App Server Platform Edition 8.0). It contains a servlet, that posts messages to a queue, and which appears to work fine. There is also a message-driven bean that receives these messages, but it will not deploy as is. I would be grateful for any assistance in working out why. Apologies if I'm missing something obvious, but the technology is quite new to me.
    I get the following error in the server log -
    [#|2004-07-14T14:03:49.640+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.container.ejb|_ThreadID=12;|EJB5090: Exception in creating EJB container [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : joeMDB]|#]
    [#|2004-07-14T14:03:49.656+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.container.ejb|_ThreadID=12;|appId=mdbtest moduleName=ejb-jar-ic_jar ejbName=joeMDB|#]
    [#|2004-07-14T14:03:49.656+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=12;|LDR5004: UnExpected error occured while creating ejb container
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : joeMDB
         at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:296)
         at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:232)
         at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:139)
         at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:189)
    - which I can't find referenced in any other forum post. The relevant deployment descriptors are as follows -
    ejb-jar.xml -
    <?xml version="1.0" encoding="UTF-8"?>
    <ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
    <display-name>mdbJar</display-name>
    <enterprise-beans>
    <message-driven>
    <ejb-name>joeMDB</ejb-name>
    <ejb-class>joeMDB</ejb-class>
    <messaging-type>javax.jms.MessageListener</messaging-type>
    <transaction-type>Container</transaction-type>
    <message-destination-type>javax.jms.Queue</message-destination-type>
    <message-destination-link>jms/JoeDestQueue</message-destination-link>
    <message-destination-ref>
    <message-destination-ref-name>jmsJoeDestQueue</message-destination-ref-name>
    <message-destination-type>javax.jms.Queue</message-destination-type>
    <message-destination-usage>Consumes</message-destination-usage>
    <message-destination-link>jms/JoeDestQueue</message-destination-link>
    </message-destination-ref>
    </message-driven>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>joeMDB</ejb-name>
    <method-name>onMessage</method-name>
    <method-params>
    <method-param>javax.jms.Message</method-param>
    </method-params>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <message-destination>
    <message-destination-name>jms/JoeDestQueue</message-destination-name>
    </message-destination>
    </assembly-descriptor>
    </ejb-jar>
    sun-ejb-jar.xml -
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 8.0 EJB 2.1//EN" "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_2_1-0.dtd">
    <sun-ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee">
    <enterprise-beans>
    <unique-id>0</unique-id>
    <ejb>
    <ejb-name>joeMDB</ejb-name>
    <jndi-name>joeMDB</jndi-name>
    <pass-by-reference>false</pass-by-reference>
    <mdb-connection-factory>
    <jndi-name>jms/joeFactory</jndi-name>
    </mdb-connection-factory>
    <jms-max-messages-load>1</jms-max-messages-load>
    <is-read-only-bean>false</is-read-only-bean>
    <refresh-period-in-seconds>-1</refresh-period-in-seconds>
    <cmt-timeout-in-seconds>0</cmt-timeout-in-seconds>
    <gen-classes/>
    <bean-pool>
    <steady-pool-size>-1</steady-pool-size>
    <resize-quantity>-1</resize-quantity>
    <max-pool-size>-1</max-pool-size>
    <pool-idle-timeout-in-seconds>-1</pool-idle-timeout-in-seconds>
    <max-wait-time-in-millis>-1</max-wait-time-in-millis>
    </bean-pool>
    </ejb>
    <message-destination>
    <message-destination-name>jms/JoeDestQueue</message-destination-name>
    <jndi-name>jms/JoeDestQueue</jndi-name>
    </message-destination>
    </enterprise-beans>
    </sun-ejb-jar>
    Thanks,
    Joe

    Hi, Joe,
    The message says that
    JMS resource not created : joeMDB
    The command to add the missing Queue:
    asadmin create-jms-resource user admin restype javax.jms.Queue JoeDestQueue
    Please note:
    in your sun-ejb-jar.xml, the real JNDI name for the Queue is JoeDestQueue.
    Double check the namings for the Queue in both ejb-jar.xml and sun-ejb-jar.xml.
    You only need two names for one Queue: one is for JNDI, one is for reference.
    _Dianne                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Message Driven Bean Deployment for a JCA based inbound Connector in SAILFIN

    This post is partly related to my previous post regarding message driven bean deployment issue in SAILFIN b12 application server. I have made another post to put my question to a more specific title with some additions. I am developing a JCA based resource adapter (i.e. connector). The inbound module of the connector listens on a specific port for incoming messages from a server (EIS). The port property and the endpoint interface (custom made message driven bean interface, that is InboundListener) has been specified in the connector's deployment descriptor. When a message reaches, the connector delivers it to the a message driven bean whose code is indicated in the following:
    package com....;
    import com....ra.facade.InboundListener;
    import javax.ejb.ActivationConfigProperty;
    import javax.ejb.MessageDriven;
    import javax.jms.Message;
    import javax.jms.MessageListener;
    import java.util.logging.*;
    * Entity class InboundMessageReceiverMDB
    * @author efikayd
    @MessageDriven(
    mappedName = "InboundMessageReceiverMDB",
    messageListenerInterface = com......ra.facade.InboundListener.class,
    activationConfig = {
    @ActivationConfigProperty(
    propertyName = "listenerPort", propertyValue = "12345"),
    @ActivationConfigProperty(
    propertyName="ConnectionFactoryJndiName", propertyValue="RAjms/MyQCF"),
    @ActivationConfigProperty(
    propertyName="DestinationName", propertyValue="MyQueue"),
    @ActivationConfigProperty(
    propertyName="DestinationType", propertyValue="javax.jms.Queue")
    public class InboundMessageReceiverMDB implements InboundListener, MessageListener {
    private static final Logger logger = Logger.getLogger("com.xyz.inbound.InboundMessageReceiverMDB");
    /** Creates a new instance of InboundMessageReceiverMDB */
    public InboundMessageReceiverMDB() {
    public void onMessage(Message message) {
    public void receiveMessage(String message) {
    logger.log(Level.SEVERE, "CLASS: " + getClass().getName() + "METHOD: receiveMessage() ==> Message received...: " + message);
    The listener interface is the following:
    package com...ra.facade;
    public interface InboundListener{
    public void receiveMessage(String message);
    I have set the JMS resource and the queue properties on the admin console of the SAILFIN instance that is locally installed on my Linux machine (Suse 9 - kernel number: 2.6.5-7.244) in the following manner:
    ConnectionFactory:
    JNDI Name: RAjms/MyQCF
    Pool Name: RAjms/MyQCF
    Type: javax.jms.ConnectionFactory
    Status: enabled
    Property1 ==> Name: DestinationType Value: javax.jms.Queue
    Property2 ==> Name: DestinationName Value: MyQueue
    Destination (i.e. queue):
    JNDIName: MyQueue
    Physical Destination Name: MyQueue
    status: enabled
    Property1 ==> Name: DestinationType Value:javax.jms.Queue
    Property2 ==> Name: DestinationName Value:MyQueue
    When I first written this message driven bean, it was not implementing the MessageListener interface. It was only implementing my own InboundListener interface. I did this because JCA specification says that the endpoint (i.e. message driven bean ) is not supposed to make use of JMS and its MessageListener interface. It says it can support custom message listener interface so to say. Then I got the exceptions that are same as the exceptions stated below. So, I made the bean implement the JMS MessageListener interface in addtion to my InboundListener interface assuming that exceptions result from not including the JMS MessageListener interface. Then I generated the necessary JMS resources with configuration settings stated above in the application server. However, I am still getting the same exceptions (see below) and nothing has changed. Do you think the above configuration for the JMS resource is fine and appropriate to the activation configuration specifications in my message driven bean code? Am I missing something on this configuration? Below, I have indicated the message that I got on the linux terminal when I attempt to deploy the message driven bean and the related server log. Thank you very much in advance for your help.
    Kind regards,
    faydemir
    PS: The 'restart' command in the following linux terminal outcome basically makes a call to a bash script which deploys the message driven bean to the SAILFIN application server. The resource adapter instance is already deployed on the application server before attempting to deploy the message driven bean. I am sure that the resource adapter successfully receives the messages from the EIS but it cannot deliver them to the endpoint (i.e.the message driven bean) since the bean is unable to be deployed correctly. I am using Netbeans IDE 5.5.1
    WHILE DEPLOYING:
    ws2089 [11:29am] [home/efikayd/bin] -> ./restart
    Command deploy executed successfully with following warning messages: Error occurred during application loading phase. The application will not run properly. Please fix your application and redeploy.
    WARNING: com.sun.enterprise.deployment.backend.IASDeploymentException: Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details.
    ws2089 [11:29am] [home/efikayd/bin] ->
    SERVER LOG:
    [#|2008-01-03T11:29:00.542+0100|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Application server startup complete.|#]
    [#|2008-01-03T11:29:09.482+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;/tmp/s1astempdomain1server-1825660455/InboundReceiverMDBModule.jar;|ADM1006:Uploading the file to:[/tmp/s1astempdomain1server-1825660455/InboundReceiverMDBModule.jar]|#]
    [#|2008-01-03T11:29:12.399+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=18;_ThreadName=Thread-32;|deployed with moduleid = InboundReceiverMDBModule|#]
    [#|2008-01-03T11:29:12.739+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;InboundMessageReceiverMDB;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|MDB00017: [InboundMessageReceiverMDB]: Exception in creating message-driven bean container: [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB]|#]
    [#|2008-01-03T11:29:12.739+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|com.sun.enterprise.connectors.ConnectorRuntimeException
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
    at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
    at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
    at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
    at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
    at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
    at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
    at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
    at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
    at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
    at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
    at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
    at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
    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.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
    at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
    at $Proxy1.invoke(Unknown Source)
    at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
    at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
    at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:69)
    at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:155)
    at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:122)
    at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:193)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
    at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:271)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
    |#]
    [#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|EJB5090: Exception in creating EJB container [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB]|#]
    [#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|appId=InboundReceiverMDBModule moduleName=_home_efikayd_SAILFINB12_sailfin_domains_domain1_applications_j2ee-modules_InboundReceiverMDBModule ejbName=InboundMessageReceiverMDB|#]
    [#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.core.classloading|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|LDR5004: UnExpected error occured while creating ejb container
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
    at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
    at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
    at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
    at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
    at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
    at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
    at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
    at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
    at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
    at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
    at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
    at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
    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.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
    at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
    at $Proxy1.invoke(Unknown Source)
    at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
    at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
    at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:69)
    at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:155)
    at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:122)
    at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:193)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
    at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:271)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
    |#]
    [#|2008-01-03T11:29:12.745+0100|WARNING|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|CORE5020: Error while loading ejb module|#]
    [#|2008-01-03T11:29:12.747+0100|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details. ;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|ADM1075:Error on listening event:[Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details. ]|#]

    This post is partly related to my previous post regarding message driven bean deployment issue in SAILFIN b12 application server. I have made another post to put my question to a more specific title with some additions. I am developing a JCA based resource adapter (i.e. connector). The inbound module of the connector listens on a specific port for incoming messages from a server (EIS). The port property and the endpoint interface (custom made message driven bean interface, that is InboundListener) has been specified in the connector's deployment descriptor. When a message reaches, the connector delivers it to the a message driven bean whose code is indicated in the following:
    package com....;
    import com....ra.facade.InboundListener;
    import javax.ejb.ActivationConfigProperty;
    import javax.ejb.MessageDriven;
    import javax.jms.Message;
    import javax.jms.MessageListener;
    import java.util.logging.*;
    * Entity class InboundMessageReceiverMDB
    * @author efikayd
    @MessageDriven(
    mappedName = "InboundMessageReceiverMDB",
    messageListenerInterface = com......ra.facade.InboundListener.class,
    activationConfig = {
    @ActivationConfigProperty(
    propertyName = "listenerPort", propertyValue = "12345"),
    @ActivationConfigProperty(
    propertyName="ConnectionFactoryJndiName", propertyValue="RAjms/MyQCF"),
    @ActivationConfigProperty(
    propertyName="DestinationName", propertyValue="MyQueue"),
    @ActivationConfigProperty(
    propertyName="DestinationType", propertyValue="javax.jms.Queue")
    public class InboundMessageReceiverMDB implements InboundListener, MessageListener {
    private static final Logger logger = Logger.getLogger("com.xyz.inbound.InboundMessageReceiverMDB");
    /** Creates a new instance of InboundMessageReceiverMDB */
    public InboundMessageReceiverMDB() {
    public void onMessage(Message message) {
    public void receiveMessage(String message) {
    logger.log(Level.SEVERE, "CLASS: " + getClass().getName() + "METHOD: receiveMessage() ==> Message received...: " + message);
    The listener interface is the following:
    package com...ra.facade;
    public interface InboundListener{
    public void receiveMessage(String message);
    I have set the JMS resource and the queue properties on the admin console of the SAILFIN instance that is locally installed on my Linux machine (Suse 9 - kernel number: 2.6.5-7.244) in the following manner:
    ConnectionFactory:
    JNDI Name: RAjms/MyQCF
    Pool Name: RAjms/MyQCF
    Type: javax.jms.ConnectionFactory
    Status: enabled
    Property1 ==> Name: DestinationType Value: javax.jms.Queue
    Property2 ==> Name: DestinationName Value: MyQueue
    Destination (i.e. queue):
    JNDIName: MyQueue
    Physical Destination Name: MyQueue
    status: enabled
    Property1 ==> Name: DestinationType Value:javax.jms.Queue
    Property2 ==> Name: DestinationName Value:MyQueue
    When I first written this message driven bean, it was not implementing the MessageListener interface. It was only implementing my own InboundListener interface. I did this because JCA specification says that the endpoint (i.e. message driven bean ) is not supposed to make use of JMS and its MessageListener interface. It says it can support custom message listener interface so to say. Then I got the exceptions that are same as the exceptions stated below. So, I made the bean implement the JMS MessageListener interface in addtion to my InboundListener interface assuming that exceptions result from not including the JMS MessageListener interface. Then I generated the necessary JMS resources with configuration settings stated above in the application server. However, I am still getting the same exceptions (see below) and nothing has changed. Do you think the above configuration for the JMS resource is fine and appropriate to the activation configuration specifications in my message driven bean code? Am I missing something on this configuration? Below, I have indicated the message that I got on the linux terminal when I attempt to deploy the message driven bean and the related server log. Thank you very much in advance for your help.
    Kind regards,
    faydemir
    PS: The 'restart' command in the following linux terminal outcome basically makes a call to a bash script which deploys the message driven bean to the SAILFIN application server. The resource adapter instance is already deployed on the application server before attempting to deploy the message driven bean. I am sure that the resource adapter successfully receives the messages from the EIS but it cannot deliver them to the endpoint (i.e.the message driven bean) since the bean is unable to be deployed correctly. I am using Netbeans IDE 5.5.1
    WHILE DEPLOYING:
    ws2089 [11:29am] [home/efikayd/bin] -> ./restart
    Command deploy executed successfully with following warning messages: Error occurred during application loading phase. The application will not run properly. Please fix your application and redeploy.
    WARNING: com.sun.enterprise.deployment.backend.IASDeploymentException: Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details.
    ws2089 [11:29am] [home/efikayd/bin] ->
    SERVER LOG:
    [#|2008-01-03T11:29:00.542+0100|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Application server startup complete.|#]
    [#|2008-01-03T11:29:09.482+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;/tmp/s1astempdomain1server-1825660455/InboundReceiverMDBModule.jar;|ADM1006:Uploading the file to:[/tmp/s1astempdomain1server-1825660455/InboundReceiverMDBModule.jar]|#]
    [#|2008-01-03T11:29:12.399+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=18;_ThreadName=Thread-32;|deployed with moduleid = InboundReceiverMDBModule|#]
    [#|2008-01-03T11:29:12.739+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;InboundMessageReceiverMDB;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|MDB00017: [InboundMessageReceiverMDB]: Exception in creating message-driven bean container: [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB]|#]
    [#|2008-01-03T11:29:12.739+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|com.sun.enterprise.connectors.ConnectorRuntimeException
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
    at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
    at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
    at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
    at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
    at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
    at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
    at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
    at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
    at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
    at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
    at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
    at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
    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.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
    at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
    at $Proxy1.invoke(Unknown Source)
    at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
    at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
    at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:69)
    at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:155)
    at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:122)
    at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:193)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
    at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:271)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
    |#]
    [#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|EJB5090: Exception in creating EJB container [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB]|#]
    [#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|appId=InboundReceiverMDBModule moduleName=_home_efikayd_SAILFINB12_sailfin_domains_domain1_applications_j2ee-modules_InboundReceiverMDBModule ejbName=InboundMessageReceiverMDB|#]
    [#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.core.classloading|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|LDR5004: UnExpected error occured while creating ejb container
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
    at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
    at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
    at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
    at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
    at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
    at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
    at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
    at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
    at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
    at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
    at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
    at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
    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.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
    at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
    at $Proxy1.invoke(Unknown Source)
    at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
    at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
    at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:69)
    at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:155)
    at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:122)
    at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:193)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
    at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
    at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:271)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
    at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
    |#]
    [#|2008-01-03T11:29:12.745+0100|WARNING|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|CORE5020: Error while loading ejb module|#]
    [#|2008-01-03T11:29:12.747+0100|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details. ;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|ADM1075:Error on listening event:[Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details. ]|#]

  • PeopleSoft HRMS and campus 9.0 db creation please help

    hi friends,
    [This all were install on windows server 2003 enterprise edition ]
    I have install
    1. oracle 10g
    2. weblogic 9.2
    3. tuxedo 9.0
    4. peopleTool 8.49 (7 cds all)
    5.PeopleSoft Enterprise Human Resources Management System and Campus Solutions 9.0 (CD)
    After this i started to create the database part for PS
    after Configuration Manager and using SignOn of DATAMover
    thier i select File > database setup
    here was two options to select
    PeopleSoft HRCS database - US English
    PeopleTool system database - US English
    here selecting demo radio button i select PeopleSoft HRCS database - US English
    got one script to run, executed it and after hours it was successfully completed
    FRom dos prompt [this i got from DataBase part III ]
    url : http://gasparotto.blogspot.com/2008/01/on-peoplesoft-road-peoplesoft-database_7562.html
    C:\PTv849\bin\client\winx86> psae -CD orcl -CT ORACLE -CO PS -CP PS -R INSTALL -A I VERSION
    Message Set Number: 0
    Message Number: 0
    Message Reason: The database is at release 8.48. The PeopleTools being run req
    uire databases at release 8.49. (0,0)
    Error in sign on
    i got this error ..
    please let me know if i done a mistake while db creation.
    is their need to select PEOPLETOOL system database or by select HRMS it will install both the peopletool + peoplesoft db.
    please friend tell te the steps to create Database for 8.49 version + peoplesoft 9.0 HRMS and campus solution..
    Thanks and regards
    Shrikant S
    u can send mail too on [email protected]...
    Edited by: user11084225 on Jun 5, 2009 9:25 PM

    user11084225 wrote:
    Message Reason: The database is at release 8.48. The PeopleTools being run req
    uire databases at release 8.49. (0,0)Very similar issue in [your other thread|http://forums.oracle.com/forums/thread.jspa?messageID=3521167] .
    It seems you missed the part II (upgrade to the latest Peopletools release) on my blog.
    Nicolas.

Maybe you are looking for