JMS with Oracle AQ

Can someone help me how JMS can access Oracle AQ messages?
Regards

Hello,
It's not restriction of Oralce AQ.
There is something wrong with IP adress of client.
Read answer for the same question on this forum from Feb 25, 2002 "AQ callback notification in OCI"
I've this problem and they helped me.
Server posts message but client IP adrress was wrong - problem was with OS NET config
Good luck

Similar Messages

  • SOAP over JMS with Oracle tool chain

    Hi,
    is there an easy way to create a webservice with SOAP over JMS for Oracle Application Servers?
    Are there any tutorials, docus or examples?
    Any hint is appreciated....

    I found a first step...:
    In JDeveloper i created a "new..."-> "Webservice->JMS Adapter"
    This created a complete wsdl:
    <definitions
    name="MySOAPoverJMS"
    targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/jms/MySOAPoverJMS/"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/jms/MySOAPoverJMS/"
    xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns:jca="http://xmlns.oracle.com/pcbpel/wsdl/jca/"
    xmlns:pc="http://xmlns.oracle.com/pcbpel/" xmlns:imp1="http://xmlns.oracle.com/pcbpel/adapter/db/DBAPP/ADDEMPLOYEES/"
    xmlns:hdr="http://xmlns.oracle.com/pcbpel/adapter/jms/"
    >
    <import namespace="http://xmlns.oracle.com/pcbpel/adapter/jms/" location="jmsAdapterInboundHeader.wsdl"/>
    <types>
    <schema xmlns="http://www.w3.org/2001/XMLSchema" >
    <import namespace="http://xmlns.oracle.com/pcbpel/adapter/db/DBAPP/ADDEMPLOYEES/" schemaLocation="ADDEMPLOYEES.xsd" />
    </schema>
    </types>
    <message name="InputParameters_msg">
    <part name="InputParameters" element="imp1:InputParameters"/>
    </message>
    <portType name="Consume_Message_ptt">
    <operation name="Consume_Message">
    <input message="tns:InputParameters_msg"/>
    </operation>
    </portType>
    <binding name="Consume_Message_binding" type="tns:Consume_Message_ptt">
    <pc:inbound_binding />
    <operation name="Consume_Message">
    <jca:operation
    ActivationSpec="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec" DestinationName="java:comp/resource/OEMS/Topics/JMSUSER.JMSDEMO_TOPIC"
    UseMessageListener="false"
    PayloadType="TextMessage"
    OpaqueSchema="false" >
    </jca:operation>
    <input>
    <jca:header message="hdr:InboundHeader_msg" part="inboundHeader"/>
    </input>
    </operation>
    </binding>
    <service name="MySOAPoverJMS">
    <port name="Consume_Message_pt" binding="tns:Consume_Message_binding">
    <!--Your runtime connection is declared in
    J2EE_HOME/application-deployments/default/JMSAdapter/oc4j-ra.xml
    These mcf properties here are from your design time connection and
    save you from having to edit that file and restart the application server
    if eis/Jms/OEMS is missing.
    These mcf properties are safe to remove.-->
    <jca:address location="eis/Jms/OEMS" UIConnectionName="OEMS" ManagedConnectionFactory="oracle.tip.adapter.jms.JmsManagedConnectionFactory" mcf.ConnectionFactoryLocation="java:comp/resource/OEMS/TopicConnectionFactories/TCF"
    mcf.IsTopic="true"
    mcf.IsTransacted="true"
    mcf.FactoryProperties=""
    mcf.Username="jmsuser"
    mcf.Password="BE49B84750434652C21A27623F0F412D"
    UIJmsProvider="OJMS" />
    </port>
    </service>
    <plt:partnerLinkType name="Consume_Message_plt" >
    <plt:role name="Consume_Message_role" >
    <plt:portType name="tns:Consume_Message_ptt" />
    </plt:role>
    </plt:partnerLinkType>
    </definitions>
    But this contains no SOAP definition, so that i cannot use this with "new..."->"Webservice->Java Web Service from WSDL" to create the java code...
    Any ideas?

  • Weblogic Connection with Oracle JMS AQ errors

    Hi All,
    I am a newbie with SOA 11g and I am trying to do a simple test case for a use case of connecting Oracle AQ JMS with Weblogic and using it in my SOA 11g process. I am trying to publish something to my queue that I created but I am getting this error in the weblogic / soa log files pasted below :
    The steps I followed exactly are this :
    1) Created a Database Queue called DemoInqueue using the following scripts :
    exec dbms_aqadm.create_queue_table ( queue_table=> 'DemoInQueue', queue_payload_type=> 'SYS.AQ$_JMS_TEXT_MESSAGE', multiple_consumers=> FALSE, compatible=> '8.1');
    COMMIT;
    exec dbms_aqadm.create_queue(queue_name=> 'DemoInQueue', queue_table=> 'DemoInQueue');
    COMMIT;
    exec dbms_aqadm.start_queue('DemoInQueue');
    COMMIT;
    2) Created a Data Source in weblogic server : Called it using the JNDI name : jdbc/oracle/jms Driver Class Name : oracle.jdbc.xa.client.OracleXADataSource (I tested the connection it works fine)
    3) Created a JMS Module (JMSTestModule) and then Created a New Summary of Resource for it ( AQServer) and chose option Foregin Server.
    Under General Tab, I gave "oracle.jms.AQjmsInitialContextFactory" as the JNDI Initial Context Factory and Under JNDI Properties I put in "datasource=jdbc/oracle/jms" as I created the above datasource.
    Under Connection Factores I created a new "ForeignConnectionFactory-0". Under Configuration I gave Local JNDI name as "jms/DemoCF" and remote JNDI Name as "XAQueueConnectionFactory" (I have also tried with
    QAConnectionFactory but no difference )
    Under Destinations I created a new "ForeignDestination-0" with local JNDI name as "jms/DemoInQ" and Remote JNDI Name as "Queues/DemoInQueue" (Because my Queue name is that)....
    4) I restarted the Weblogic Server then went to SOA suite and tried a very simple process Hello world added a JMS adpater....Inside the adpater I selected OEMS (Advanced Queueing), App server my weblogic server,
    operation as ProduceMessage and when I hit Browse I was able to see my AQServer ForeignDestination-0 Queue. I selected it and under destination name it populated "jms/DemoInQ" but under JNDI name it also
    populated "eis/aqjms/Queue" I left that as is and deployed my process and tried invoking it. It failed with the error message below.....I also tried modifying the JNDI name to something else...in Jdev..but the results
    are the same....
    Are these steps correct ? Am I missing something here.?
    I followed all the blogs and forums in this site and I think I did all the steps...but if anyone can help me I would really appreciate it...
    Here is the error stack below :
    <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437281> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "BINDING.JCA-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
    Please examine the log file to determine the problem.
    ">
    ####<Dec 1, 2010 2:07:17 PM EST> <Warning> <Connector> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437296> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "BINDING.JCA-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
    Please examine the log file to determine the problem.
    ">
    SOA LOG.....
    ####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.adapter> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <JCABinding=> [default/HelloWorldComposite!1.0*soa_25f514de-3db3-4bed-9144-44d83dacbe10.Publishmessage]:Produce_Message One-way operation Produce_Message() failed>
    ####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.bpel.engine.ws> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <<WSInvocationManager::invoke> got FabricInvocationException
    oracle.fabric.common.FabricInvocationException: BINDING.JCA-12563
    Exception occured when binding was invoked.
    Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: JCA Binding Component connection issue.
    JCA Binding Component is unable to create an outbound JCA (CCI) connection.
    HelloWorldComposite:Publishmessage [ Produce_Message_ptt::Produce_Message(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
    Please examine the log file to determine the problem.

    Thanks for passing along the link.
    The part about Oracle's documentation not mentioning the JmsAdapter configuration was a real sticking point for me - I was having the same problem as the original poster until I updated that deployment as the link outlined.
    Also, towards the end of that link the author mentions running in to problems getting their composite to successfully bind to the queue definitions that were created in WebLogic.
    I attempted post my solution to this on the original site, but I'm not sure if it got through - so I'll add the details of what worked for me here:
    Connection Factory:
    Local JNDI: aqjms/JMSTest_Connection_Factory
    Remote JNDI: XAQueueConnectionFactory
    Destination:
    Local JNDI: aqjms/JMSTest_Queue
    Remote JNDI: Queues/JMSTest_Queue
    Outbound Connection Pool:
    Name: eis/aqjms/JMSTest_Queue
    Connection Factory: aqjms/JMSTest_Connection_Factory
    JDeveloper Composite:
    Destination Name: aqjms/JMSTest_Queue
    JNDI Name: eis/aqjms/JMSTest_Queue
    Cheers,
    - Nathan

  • Language support in JMS adapter with Oracle JDev 10.1.3.1

    Hi,
    I' using JDeveloper 10.1.3.1 with Oracle SOA Suite - ESB 10.1.3.1 in the following scenario:
    1) Use Database adapter with "on insert" condition to read Student record with Chinese name (Unicode format) - ESB process
    2) Use JMS adapter to push this data into "DemoTopic" as string - ESB process
    3) Use Message Driven Bean's (EJB 3.0) "onMessage" method to fetch the data from JMS topic - J2EE app
    4) Use JDBC executeUpdate to update this Chinese name into another database table - J2EE app
    5) Finally, verify the updated Chinese name in ADF application - J2EE app
    Prerequisites
    1) The database charset on both sides of the flow is UTF8
    2) The ADF application JSF page encoding is UTF8
    3) The SOA Suite is installed on DB repository (UTF8 charset)
    Result
    1) The flow from Step 1-5 works.
    2) But, the println of the JMS message (holding the Chinese name) gives "????" when checked with Wordpad (Unicode readable word processor)
    3) Junk characters are inserted into the database
    Please let me know where I'm going wrong. Also, let me know if I need to configure/set the character encoding in OC4J, or the JMS adapter and how.

    Hi all,
    This is been resolved by using the AL32UTF8 character set in the database. JMS adapter by default supports UTF-8. No setting/configuration needs to be done.

  • Any kind of integration experience with Weblogic JMS and Oracle AQ?

    Hi,
    In my company I work with java developers who believe in some kind of "holly" database independence I don't understand and as a result my life as a database developer is hell on earth.. Yesterday we again started to discuss, this time where to log, they believe database is slow and prefer logging to filesystem, after some hours finally I could convince them for some operational and reporting needs to use the database and will do this in an asyncronous way whiich they won't get slow. After all I believe the reason for a database is data, this is the place where data lives, and with the correct desing and implementation logging to database would perform better.
    I love Oracle features, and know that we paid a lot for this software, so today I started investigating this promised solution. And quickly I found AQ and JMS topics in the documentation :)
    After this introduction here is my problem; my company use BEA Weblogic as application server and the java guys want AQ to automatically (but of course with some delay) take their JMS log requests into database tables. Does any one have similar application experience, or any kind of integration experience with Weblogic JMS and Oracle AQ?
    Any comments, references, documentation, sample code, url will be most welcomed :)
    Thank you very much!
    Tonguc
    [email protected]
    References I found upto now;
    Oracle® Streams Advanced Queuing Java API Reference 10g Release 2 (10.2) http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14291/toc.htm
    (Packages; javax.jms & oracle.jms)
    Oracle® Streams Advanced Queuing User's Guide and Reference 10g Release 2 (10.2) http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14257/toc.htm
    Part IV
    Using Oracle JMS and Oracle Streams AQPart V describes how to use Oracle JMS and Oracle Streams Advanced Queuing (AQ).
    Chapter 11, "Introducing Oracle JMS"
    Chapter 12, "Oracle JMS Basic Operations"
    Chapter 13, "Oracle JMS Point-to-Point"
    Chapter 14, "Oracle JMS Publish/Subscribe"
    Chapter 15, "Oracle JMS Shared Interfaces"
    Chapter 16, "Oracle JMS Types Examples"
    A Sample Code from Otn
    http://www.oracle.com/technology/sample_code/tech/java/web_services/jmsws/NewsQueueEJB.java.html

    I wouldn't go as far to say Oracle AQ is out-dated today. However, it is indeed a proprietary technology that did not found much main-stream adoption in the earlier years after its introduction. The advent of JMS made it somewhat more useful (or should I say intriguing, because more people are trying to tie it together with other J2EE technologies), but the Oracle's JMS wrapper classes in aqapi.jar were not feature complete for a long while, so using it outside Oracle's application server was painful, if not impossible. I do agree that the info at the dev2dev's JMS newsgroup or in this forum is highly fragmented, as neither Oracle nor BEA provides an official solution to integrate AQ with WebLogic, so people like us have to learn the technology through experimentation and in a piecemeal fashion.
    3 years ago I was literally "playing around" - we had a polling mechanism set up to use triggers to write Oracle data changes into an event table, and had a Java-based daemon to scan that table and publish events as JMS messages to the WebLogic JMS server. This continues to work reliably till today, but I was looking for a solution that has few parts - I wanted to hook up my WebLogic MDB directly to AQ as a foreign JMS provider. Although I was able to get it to work (including XA), there were a few hoops I had to jump through, such as decompiling the Oracle AQjms classes to make them bind to the WebLogic JNDI tree.
    One year after that Diptanshu Parui took what I did a giant step further - he extended the Oracle AQjms classes to allow them to be bound to the WebLogic JNDI tree naturally, and he figured out how to use WebLogic JMS messging bridge to re-send single-threaded AQ JMS messages to clustered JMS queues, which allow concurrent message assumption by multiple instances of MDB's. My impression is that he is using that setup in a production environment.
    I am sure you are aware of it but I would like to make it clear - in order to use AQ as a foreign JMS provider to WebLogic-hosted MDB's, you don't need to update your database to Oracle 10g - Oracle 8i is good enough (although I recommend at least 9i Release 2). It is not the database engine, but rather the aqapi.jar JMS wrapper on top of AQ that matters. I do recommend that you use aqapi.jar from Oracle Application Server 10.0.3 or up for better XA support, among other things. Again, you don't have to replace WebLogic with Oracle AS - you only need a single jar file from it and put it in your WebLogic's classpath. However, I don't know what this means from a licensing point of view if you ever go to production - do you have to pay the full price of OracleAS or OC4J just to use the aqapi.jar?
    In the coming days I will test the latest aqapi.jar to see how much progress Oracle has made in terms of making their J2EE products more spec-compliant :-).
    Hope the above gives you a different perspective.
    Eric

  • Petstore 1.3 on Weblogic 7.0 with Oracle 8.1.7

    Hi, I am trying to get petstore 1.3 working on Weblogic7.0
    with Oracle 8.1.7 database on HPUX. I made some modifications
    to the source files and regenerated the EAR files. When I copied
    the four EAR files to the applications sub-directory, two .ear
    files (petstoreadmin.ear & petstore.ear) deployed successfully
    but not the supplier.ear and opc.ear. I got the following messages from deploying
    supplier.ear:
    Any help would be greatly appreciated,
    Min-Shih
    =====================================================
    ####<Nov 7, 2002 5:09:30 PM PST> <Warning> <EJB> <cutst058.cup.hp.com> <examplesServer>
    <ExecuteThread: '9' for
    queue: 'default'> <kernel identity> <> <010061> <The Message-Driven EJB: supplier_OPC_MDB_QUEUE
    is unable to connect to the
    JMS destination: jms/opcApplication/SUPPLIER_PO_MDB_QUEUE. The EJB container will
    automatically attempt to re-establish the connection with the JMS server. This
    warning may occur during WebLogic Cluster start-up if the JMS destination is located
    on another WebLogic Server instance. When the JMS server connection is re-established,
    the Message-Driven EJB will again receive JMS messages.
    The Error was:
    The JMS destination with the JNDI name: jms/opcApplication/SUPPLIER_PO_MDB_QUEUE
    could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml
    is correct, and the JMS destination has been deployed.>
    ####<Nov 7, 2002 5:09:30 PM PST> <Error> <EJB> <cutst058.cup.hp.com> <examplesServer>
    <ExecuteThread: '9' for queue: 'default'> <kernel identity> <> <010072> <Error
    starting EJB Module : supplierEjb.jar
    Exception is :
    Unable to deploy EJB: supplierEjb.jar from supplierEjb.jar:
    weblogic.ejb20.WLDeploymentException: nulljava.lang.reflect.InvocationTargetException:
    javax.ejb.EJBException: Supp
    lier.MsgBean.ejbCreate: naming exceptionjavax.naming.LinkException: [Root exception
    is javax.naming.NameNotFoundEx
    ception: Unable to resolve 'jms.TopicConnectionFactory' Resolved: 'jms' Unresolved:'TopicConnectionFactory'
    ; remai
    ning name 'TopicConnectionFactory']; Link Remaining Name: 'jms/TopicConnectionFactory'

    Hi, I am trying to get petstore 1.3 working on Weblogic7.0
    with Oracle 8.1.7 database on HPUX. I made some modifications
    to the source files and regenerated the EAR files. When I copied
    the four EAR files to the applications sub-directory, two .ear
    files (petstoreadmin.ear & petstore.ear) deployed successfully
    but not the supplier.ear and opc.ear. I got the following messages from deploying
    supplier.ear:
    Any help would be greatly appreciated,
    Min-Shih
    =====================================================
    ####<Nov 7, 2002 5:09:30 PM PST> <Warning> <EJB> <cutst058.cup.hp.com> <examplesServer>
    <ExecuteThread: '9' for
    queue: 'default'> <kernel identity> <> <010061> <The Message-Driven EJB: supplier_OPC_MDB_QUEUE
    is unable to connect to the
    JMS destination: jms/opcApplication/SUPPLIER_PO_MDB_QUEUE. The EJB container will
    automatically attempt to re-establish the connection with the JMS server. This
    warning may occur during WebLogic Cluster start-up if the JMS destination is located
    on another WebLogic Server instance. When the JMS server connection is re-established,
    the Message-Driven EJB will again receive JMS messages.
    The Error was:
    The JMS destination with the JNDI name: jms/opcApplication/SUPPLIER_PO_MDB_QUEUE
    could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml
    is correct, and the JMS destination has been deployed.>
    ####<Nov 7, 2002 5:09:30 PM PST> <Error> <EJB> <cutst058.cup.hp.com> <examplesServer>
    <ExecuteThread: '9' for queue: 'default'> <kernel identity> <> <010072> <Error
    starting EJB Module : supplierEjb.jar
    Exception is :
    Unable to deploy EJB: supplierEjb.jar from supplierEjb.jar:
    weblogic.ejb20.WLDeploymentException: nulljava.lang.reflect.InvocationTargetException:
    javax.ejb.EJBException: Supp
    lier.MsgBean.ejbCreate: naming exceptionjavax.naming.LinkException: [Root exception
    is javax.naming.NameNotFoundEx
    ception: Unable to resolve 'jms.TopicConnectionFactory' Resolved: 'jms' Unresolved:'TopicConnectionFactory'
    ; remai
    ning name 'TopicConnectionFactory']; Link Remaining Name: 'jms/TopicConnectionFactory'

  • Problems setting up Weblogic Server 9.2 with Oracle AQ

    We are in the process of upgrading from WLS81 to WLS92 and I'm currently trying to set up the environment. We have applications communicating with 3 different JMS-servers; Sonic, WMQ and Oracle AQ. For both Sonic and WMQ the connection seem to work fine. We get an active application, and the beans connecting to queues on those servers reports as 'connected'.
              For Oracle AQ I must be doing something wrong, but I can't for the life of me figure out what it is.
              Our setup is as follows:
              We have a domain-scoped startup class that binds the AQ-queues and a custom QueueConnectionFactory to the WL default context. Giving them a name like aqadapter-AQ_ARE_PING.
              We have defined a System Resource, within which we have defined AQ as a Foreign Server. Within this foreign server we have each queue mapped to the queue-names bound through the Startup class. Likewise we have a qcf mapped to the qcf bound through the startup class.
              The application contains message-driven beans which are supposed to be listening to the AQ-queues. In weblogic-ejb-jar.xml each target queue is mapped within each bean to the same name mapped within the Foreign Server element.
              All this results in MDB's that report as 're-connecting' and 'initializing' and the following message in Server1.stdout for each MDB:
              <Mar 28, 2007 4:27:58 PM CEST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ARE_Ping is unable to connect to the JMS destination: AQ_ARE_PING. The Error was:
              javax.jms.InvalidDestinationException: JMS-125: Invalid Queue specified>
              Any ideas what I am doing wrong? It seems to me that all the settings are as similar as the way they are set up on WLS81 as we could get them.
              Anyone reading this that have done this before? Setting up WLS92 or WLS90 to interact with Oracle AQ?
              Regards,
              Frode Laukus
              Edited by laukus at 03/28/2007 7:53 AM

    Hi Frode
              Have you managed to find a solution to this issue?
              We are trying to do something very similar and encountering all sorts of issues.
              Are you using the DIPSStartup classes to register your queues & qcf with the WL JNDI? I haven't managed to get these classes to work with the AQJmsSession in the latest release of the aqapi13.jar files.
              Hopefully we can sort out a workable solution between us :)
              Andy

  • Problem with Oracle XA Datasource

    Hi All,
    I have created a JDBC XA Resource pool for Oracle DB and when i try to run my application, i am getting the below exception. But the same appln runs in NON-XA Datasource.
    <jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="oracle.jdbc.xa.client.OracleXADataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" max-pool-size="32" max-wait-time-in-millis="60000" name="ORA_XAPool" pool-resize-quantity="2" res-type="javax.sql.XADataSource" steady-pool-size="8">
    <property name="URL" value="jdbc:oracle:thin:@192.54.45.245:1521:orcl"/>
    <property name="Password" value="TestDB"/>
    <property name="User" value="TestDB"/>
    <property name="DataSourceName" value="OracleXADataSource"/>
    </jdbc-connection-pool>
    Any idea.... Please help.
    Version: Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs)
    Exception Trace:
    [#|2004-12-08T01:39:12.140-0800|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=12;|RAR5027:Unexpected exception in resource pooling
    java.lang.NullPointerException
         at com.sun.gjc.spi.XAResourceImpl.start(XAResourceImpl.java:162)
         at com.sun.jts.jta.TransactionState.startAssociation(TransactionState.java:238)
         at com.sun.jts.jta.TransactionImpl.enlistResource(TransactionImpl.java:173)
         at com.sun.enterprise.distributedtx.J2EETransaction.enlistResource(J2EETransaction.java:360)
         at com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.enlistResource(J2EETransactionManagerImpl.java:303)
         at com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.enlistResource(J2EETransactionManagerOpt.java:115)
         at com.sun.enterprise.resource.SystemResourceManagerImpl.enlistResource(SystemResourceManagerImpl.java:69)
         at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.java:140)
         at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:205)
         at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:94)
         at com.sun.gjc.spi.DataSource.getConnection(DataSource.java:68)
         at com.sun.jdo.spi.persistence.support.sqlstore.ejb.TransactionHelperImpl.getConnection(TransactionHelperImpl.java:181)
         at com.sun.jdo.spi.persistence.support.sqlstore.ejb.EJBHelper.getConnection(EJBHelper.java:166)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getConnection(SQLPersistenceManagerFactory.java:886)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.initializeSQLStoreManager(SQLPersistenceManagerFactory.java:851)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getFromPool(SQLPersistenceManagerFactory.java:780)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getPersistenceManager(SQLPersistenceManagerFactory.java:667)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:849)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:681)
         at
    #|2004-12-08T01:39:12.296-0800|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb.entity.finder|_ThreadID=12;|JDO74010: Bean 'ItemEnt' method ejbFindAll: problems running JDOQL query.
    com.sun.jdo.api.persistence.support.JDOFatalInternalException: JDO76519: Failed to identify vendor type for the data store.
    NestedException: java.sql.SQLException: Error in allocating a connection. Cause: java.lang.NullPointerException
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.initializeSQLStoreManager(SQLPersistenceManagerFactory.java:864)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getFromPool(SQLPersistenceManagerFactory.java:780)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getPersistenceManager(SQLPersistenceManagerFactory.java:667)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:849)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:681)
         at
    thanks,
    Bobby

    Hi Aditya,
    Thanks for looking at my issue.
    1. Do you always get this NPE or is it an intermittent issue?
    Always i am getting this error, while accesing my sample CMP application.
    2. Did you run the code snippet that I posted yesterday with the jdk bundled with the appserver or some other jdk?
    I ran the code snippet with the jdk bundled with appserver.
    3. Have you run into any more of these NPE issues with other applications and other XA pools?
    When i executed another sample demo CMP application with oracle XA Pool, it works fine.
    4. Are there any other related expceptions in the log before the NPE? Would you please start with an empty server.log, run this application and post the whole log?
    StackTrace:
    Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
    [#|2004-12-20T16:46:48.921+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]
    [#|2004-12-20T16:46:50.343+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
    [#|2004-12-20T16:46:50.562+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
    [#|2004-12-20T16:46:54.062+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
    [#|2004-12-20T16:46:54.062+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
    [#|2004-12-20T16:46:54.078+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
    [#|2004-12-20T16:46:56.890+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
    [#|2004-12-20T16:46:58.437+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
    [#|2004-12-20T16:47:00.593+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
    [#|2004-12-20T16:47:01.390+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
    [#|2004-12-20T16:47:02.531+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
    [#|2004-12-20T16:47:03.234+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
    [#|2004-12-20T16:47:03.234+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
    [#|2004-12-20T16:47:03.500+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [Tester:Tester.war] in virtual server [server] at [Tester]|#]
    [#|2004-12-20T16:47:04.343+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [cmpcustomer] loaded successfully!|#]
    [#|2004-12-20T16:47:04.343+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [cmpcustomer:cmpcustomer.war] in virtual server [server] at [customer]|#]
    [#|2004-12-20T16:47:04.375+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
    [#|2004-12-20T16:47:04.531+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
    [#|2004-12-20T16:47:04.562+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
    [#|2004-12-20T16:47:04.562+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
    [#|2004-12-20T16:47:04.562+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
    [#|2004-12-20T16:47:04.578+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
    [#|2004-12-20T16:47:04.578+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
    [#|2004-12-20T16:47:04.718+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
    [#|2004-12-20T16:47:10.234+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
    [#|2004-12-20T16:47:12.203+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
    [#|2004-12-20T16:47:12.234+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
    [#|2004-12-20T16:47:12.375+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
    [#|2004-12-20T16:47:12.375+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
    [#|2004-12-20T16:47:12.421+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
    [#|2004-12-20T16:47:12.421+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
    [#|2004-12-20T16:47:12.609+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [d:\servers\Sun\AppServer\imq\bin].|#]
    [#|2004-12-20T16:47:12.609+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1103541432609|#]
    [#|2004-12-20T16:47:12.609+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
    [#|2004-12-20T16:47:12.609+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
    [#|2004-12-20T16:47:33.734+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=11;|WebModule[/asadmin]WARNING: No 'dtdURLBase' init parameter defined in Servlet config!|#]
    [#|2004-12-20T16:48:11.453+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=12;|DPL5109: EJBC - START of EJBC for [Sample_CMP]|#]
    [#|2004-12-20T16:48:27.953+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=12;|Processing beans ...|#]
    [#|2004-12-20T16:48:28.281+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=12;|Compiling RMI-IIOP code ...|#]
    [#|2004-12-20T16:48:46.671+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=12;|DPL5110: EJBC - END of EJBC for [Sample_CMP]|#]
    [#|2004-12-20T16:48:48.109+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=12;|Total Deployment Time: 41359 msec, Total EJB Compiler Module Time: 35218 msec, Portion spent EJB Compiling: 85%
    Breakdown of EJBC Module Time: Total Time for EJBC: 35218 msec, CMP Generation: 5047 msec (14%), Java Compilation: 11344 msec (32%), RMI Compilation: 18375 msec (52%), JAX-RPC Generation: 47 msec (0%),
    |#]
    [#|2004-12-20T16:48:48.125+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=12;|deployed with moduleid = Sample_CMP|#]
    [#|2004-12-20T16:48:48.531+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=12;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy Sample_CMP]|#]
    [#|2004-12-20T16:48:54.515+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=12;|LDR5010: All ejb(s) of [Sample_CMP] loaded successfully!|#]
    [#|2004-12-20T16:48:54.546+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=12;|WEB0100: Loading web module [Sample_CMP:employee.war] in virtual server [server] at [Module]|#]
    [#|2004-12-20T16:48:56.000+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=12;|WEB0100: Loading web module [Sample_CMP:web.war] in virtual server [server] at [TestServer]|#]
    [#|2004-12-20T16:48:57.187+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=12;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
    [#|2004-12-20T16:49:43.890+0530|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=13;|RAR5027:Unexpected exception in resource pooling
    java.lang.NullPointerException
         at com.sun.gjc.spi.XAResourceImpl.start(XAResourceImpl.java:162)
         at com.sun.jts.jta.TransactionState.startAssociation(TransactionState.java:238)
         at com.sun.jts.jta.TransactionImpl.enlistResource(TransactionImpl.java:173)
         at com.sun.enterprise.distributedtx.J2EETransaction.enlistResource(J2EETransaction.java:360)
         at com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.enlistResource(J2EETransactionManagerImpl.java:303)
         at com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.enlistResource(J2EETransactionManagerOpt.java:115)
         at com.sun.enterprise.resource.SystemResourceManagerImpl.enlistResource(SystemResourceManagerImpl.java:69)
         at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.java:140)
         at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:205)
         at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:94)
         at com.sun.gjc.spi.DataSource.getConnection(DataSource.java:68)
         at com.sun.jdo.spi.persistence.support.sqlstore.ejb.TransactionHelperImpl.getConnection(TransactionHelperImpl.java:181)
         at com.sun.jdo.spi.persistence.support.sqlstore.ejb.EJBHelper.getConnection(EJBHelper.java:166)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getConnection(SQLPersistenceManagerFactory.java:886)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.initializeSQLStoreManager(SQLPersistenceManagerFactory.java:851)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getFromPool(SQLPersistenceManagerFactory.java:780)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getPersistenceManager(SQLPersistenceManagerFactory.java:667)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:849)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:681)
         at com.test.orders.itement.ejb.ItemEJB1437418622_ConcreteImpl.jdoGetPersistenceManager(ItemEJB1437418622_ConcreteImpl.java:594)
         at com.test.orders.itement.ejb.ItemEJB1437418622_ConcreteImpl.ejbFindAll(ItemEJB1437418622_ConcreteImpl.java:308)
         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:324)
         at com.sun.enterprise.security.SecurityUtil$2.run(SecurityUtil.java:146)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sun.enterprise.security.application.EJBSecurityManager.doAsPrivileged(EJBSecurityManager.java:930)
         at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:151)
         at com.sun.ejb.containers.EJBHomeInvocationHandler.invoke(EJBHomeInvocationHandler.java:179)
         at $Proxy108.findAll(Unknown Source)
         at com.test.orders.itement.ejb._ItemEntHome_Stub.findAll(Unknown Source)
         at com.test.webbeans.ProcessListBean.getItemsList(ProcessListBean.java:166)
         at org.apache.jsp.new_005forder_jsp._jspService(new_005forder_jsp.java:222)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:102)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:282)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:263)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:210)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
         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:324)
         at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
         at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
         at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:236)
         at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
         at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:214)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:168)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:144)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:133)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:539)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
         at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
         at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
         at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:114)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
         at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:936)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:165)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:683)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:604)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:542)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:647)
         at java.lang.Thread.run(Thread.java:534)
    |#]
    [#|2004-12-20T16:49:44.000+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=13;|RAR5117 : Failed to obtain/create connection. Reason : java.lang.NullPointerException|#]
    [#|2004-12-20T16:49:44.000+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=13;|RAR5114 : Error allocating connection : [Error in allocating a connection. Cause: java.lang.NullPointerException]|#]
    [#|2004-12-20T16:49:44.000+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jdo.persistencemanager|_ThreadID=13;|JDO76520: Errors while obtaining information about the database. Got the following exception:
    java.sql.SQLException: Error in allocating a connection. Cause: java.lang.NullPointerException
         at com.sun.gjc.spi.DataSource.getConnection(DataSource.java:72)
         at com.sun.jdo.spi.persistence.support.sqlstore.ejb.TransactionHelperImpl.getConnection(TransactionHelperImpl.java:181)
         at com.sun.jdo.spi.persistence.support.sqlstore.ejb.EJBHelper.getConnection(EJBHelper.java:166)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getConnection(SQLPersistenceManagerFactory.java:886)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.initializeSQLStoreManager(SQLPersistenceManagerFactory.java:851)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getFromPool(SQLPersistenceManagerFactory.java:780)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getPersistenceManager(SQLPersistenceManagerFactory.java:667)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:849)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:681)
         at com.test.orders.itement.ejb.ItemEJB1437418622_ConcreteImpl.jdoGetPersistenceManager(ItemEJB1437418622_ConcreteImpl.java:594)
         at com.test.orders.itement.ejb.ItemEJB1437418622_ConcreteImpl.ejbFindAll(ItemEJB1437418622_ConcreteImpl.java:308)
         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:324)
         at com.sun.enterprise.security.SecurityUtil$2.run(SecurityUtil.java:146)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sun.enterprise.security.application.EJBSecurityManager.doAsPrivileged(EJBSecurityManager.java:930)
         at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:151)
         at com.sun.ejb.containers.EJBHomeInvocationHandler.invoke(EJBHomeInvocationHandler.java:179)
         at $Proxy108.findAll(Unknown Source)
         at com.test.orders.itement.ejb._ItemEntHome_Stub.findAll(Unknown Source)
         at com.test.webbeans.ProcessListBean.getItemsList(ProcessListBean.java:166)
         at org.apache.jsp.new_005forder_jsp._jspService(new_005forder_jsp.java:222)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:102)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:282)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:263)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:210)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
         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:324)
         at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
         at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
         at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:236)
         at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
         at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:214)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:168)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:144)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:133)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:539)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
         at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
         at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
         at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:114)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
         at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:936)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:165)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:683)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:604)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:542)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:647)
         at java.lang.Thread.run(Thread.java:534)
    |#]
    [#|2004-12-20T16:49:44.093+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb.entity.finder|_ThreadID=13;|JDO74010: Bean 'ItemEnt' method ejbFindAll: problems running JDOQL query.
    com.sun.jdo.api.persistence.support.JDOFatalInternalException: JDO76519: Failed to identify vendor type for the data store.
    NestedException: java.sql.SQLException: Error in allocating a connection. Cause: java.lang.NullPointerException
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.initializeSQLStoreManager(SQLPersistenceManagerFactory.java:864)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getFromPool(SQLPersistenceManagerFactory.java:780)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getPersistenceManager(SQLPersistenceManagerFactory.java:667)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:849)
         at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:681)
         at com.test.orders.itement.ejb.ItemEJB1437418622_ConcreteImpl.jdoGetPersistenceManager(ItemEJB1437418622_ConcreteImpl.java:594)
         at com.test.orders.itement.ejb.ItemEJB1437418622_ConcreteImpl.ejbFindAll(ItemEJB1437418622_ConcreteImpl.java:308)
         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:324)
         at com.sun.enterprise.security.SecurityUtil$2.run(SecurityUtil.java:146)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sun.enterprise.security.application.EJBSecurityManager.doAsPrivileged(EJBSecurityManager.java:930)
         at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:151)
         at com.sun.ejb.containers.EJBHomeInvocationHandler.invoke(EJBHomeInvocationHandler.java:179)
         at $Proxy108.findAll(Unknown Source)
         at com.test.orders.itement.ejb._ItemEntHome_Stub.findAll(Unknown Source)
         at com.test.webbeans.ProcessListBean.getItemsList(ProcessListBean.java:166)
         at org.apache.jsp.new_005forder_jsp._jspService(new_005forder_jsp.java:222)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:102)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:282)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:263)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:210)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
         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:324)
         at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
         at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
         at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:236)
         at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
         at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:214)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:168)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:144)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:133)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:539)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
         at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
         at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
         at org.apache.catalina.core.StandardValveContext.invokeNext(

  • Orion JMS Vs Oracle JMS

    Hi
    I am deploying an application with MDB using Oracle JMS( AQ ) and durable subscriptions. Now for configuration of the topics, I have a doubt. In addition to creation of the topics in the db do I have to specify those in jms.xml or it is required only in case of Orion JMS? I am really confused with this, since I am getting a deployment error even though I have configured orion-ejb-jar.xml as per AQ req... Any help pls...
    Thanks in Advance...

    Hi Gilbert,
    I have done the same, but while deploying it gives error 'Syntax error in source' with no other error message. And I have one more doubt. Does AQ work with Oracle 8i databse ?

  • Integrating with Oracle EBS using XMLGateway issues

    Hi all,
    I'm trying to integrating with Oracle EBS using XMLGateway, and I meet some issues. Here are the steps I did.
    1) Update DATA_MAP.xgm file and DATA_TEST.dtd file into XMLGateway repository
    2) Define transactions in EBS client:
    Party Type: Supplier
    Transaction Type: Cat
    Transaction Subtype: Dog
    Transaction Description: test for cat and dog
    Standard Code: OAG
    External Transaction Direction: IN
    External Transaction Type: Cat
    External Transaction Subtype: Dog
    Queue: APPLSYS.ECX_IN_OAG_Q
    3) Define trading partners in EBS client
    Operating Unit: Vision Operations
    Trading Partener Type: Supplier
    Trading Partener name: ****
    Trading Partener site: ****
    Company Admin email: [email protected]
    ... other transaction info defined in step 2)
    4) Send inbound message using OTA send Inbound Page. It succeed.
    a. The return page display status code 1000 with status discription OK.
    b. From the transaction monitor, I can see the inbound message was processed successfully.
    c. From the database, I can see that this inbound message first arrived in ecx_inqueue table, and then moved to ecx_in_oag_q_table. And last disappeared from the ecx_in_oag_q_table. That means XMLGateway process the inbound message in transaction queue successfully.
    5) Send inbound message using SOAPUi. It failed.
    a. The return page display status code 200. That means the inbound message has been sent to inbound message queue successfully.
    b. From transaction monitor, I cannot see this request record.
    c. From the database, I can saw that this inbound message first arrived in wf_ws_jms_in table, then disappeared. It didn't moved to transaction queue which I selected when defined transations, so I guess it wasn't processed by XMLGateway. Using the following SQL, but cannot find error reason.
    select * from ecx_inbound_logs where process_id='******************'
    select * from apps.ecx_error_msgs where error_id='*****'
    I guess the reason is something happend to prevent inbound message to move from inbound message queue to transaction queue. So XMLGateway cannot process this inbound message.
    From XMLGateway user guide, I understand that there are three kinds of inbound queues(ECX_INBOUND which OTA uses, WF_WS_JMS_IN which soap over https uses, WF_JMS_IN which JMS uses), does't mention what are the corresponding transaction queues? Can they share the same transaction queue? Also see from this user guide, ecx_in_oag_q (transaction queue) is only for ecx_inbound queue. But when I try to define a transaction in EBS client, it seems that only ecx_in_oag_q can be chosen. I wondered why my second senarios failed when I used the same transation and trading partner. The message already arrived at wf_ws_jms_in and then disappeared. Is that because I selected the wrong transaction queue when defining transactions? But it was really cannot select any other transaction queues there. Or I missed some steps when using SOAP over HTTP/S?
    Appreciate you can give me some suggestions. Hope to hear your voice. Thanks in advance.

    Hi,
    Regarding the integration what type of integration you want.
    Can you please elaborate?There are some integration tools releases by Oracle for the integration.
    Regards
    Pramod

  • ESB integration with oracle soa

    Hi , Some one could please help me to integrate sonic esb with oracle soa using jms adapter ?

    Hi,
    Have you created a foreign destination?
    A Foreign Destination resource in a JMS module represents either a queue or a topic. It contains the destination JNDI name that is looked up on the foreign JNDI provider and the JNDI name that the destination is mapped to on the local WebLogic Server.
    http://docs.oracle.com/cd/E28280_01/apirefs.1111/e13952/taskhelp/jms_modules/foreign_servers/CreateForeignDestinations.html
    http://docs.oracle.com/cd/E28280_01/web.1111/e13738/advance_config.htm#i1075770
    Cheers,
    Vlad

  • SAP Integration with Oracle AQ

    Hi,
    I'm developing a SAP solution without XI as another Integration system has been proposed.
    The problem is that I would like to communicate SAP with the Integration system through Oracle Advanced Queuing, that is, send  SAP Idocs trough Oracle queues.
    Is SAP compatible with Oracle AQ? Do I need to implement any adaptor like JMS, iWay or similar(I've seen there are a lot developed in the market)?
    Thanks!

    What I told you is different from an RFC (You can also call an RFC as you said). When you create a BAPI it is automatically published as a Web Service. Going to the <u>webservice browser</u> in <u>BSP applications</u>(<u>transaction SE80</u> in your SAP). There you have the WDSL of each BAPI.  This way you don't need XI. The WSDL export all the functionallity of the BAPI and it's the same as execute the BAPI itself.
    If you use XI you can do the same using a SOAP adapter. Even if it is equivalent doing that throw XI have many advantages, above all if you have many aplications to consume.
    Watch here for more info for Enterprise Services:
    <a href="http://help.sap.com/saphelp_autoid2007/helpdata/en/d0/69ef41a0b99d39e10000000a155106/frameset.htm">http://help.sap.com/saphelp_autoid2007/helpdata/en/d0/69ef41a0b99d39e10000000a155106/frameset.htm</a>
    You can search for more information by searching in both SDN and Google for:
    Web Services, Proxy, JDBC Adapter, SOAP adapter, WSDL...
    Regards
    Gonzalo

  • Integrate Web application with Oracle BPM

    Hi,
    Can you guide me in achieving the following scenario:
    1. Integration web application with oracle BPM
    Say, I have a application where I need to trigger an event to call Oracle BPM. For ex: On click of submit button call the Oracle BPM workflow to do some process and then revert back to the same application with an alert or status message. Please let me know the steps to acheive this.
    Thanks
    ST

    Hi,
    I take from this description that you currently have your Web Application and you would possibly like to trigger or create an instance into an OBPM business process. If this is the case, you have several options available here:
    a) Use PAPI (Java API).
    b) Use PAPI-Ws (SOAP API).
    c) Use some sort of communication channel that the process is implemented to listen (for example a JMS Queue or Topic).
    For the first 2, you can try to take a look into the official Documentation page for OBPM through this link: http://download.oracle.com/docs/cd/E13154_01/bpm/docs65/index.html (Check the For Developers section).
    If I have miss interpreted your question, please do not hesitate to provide more details.
    Cheers,
    eduardoc.

  • Error while installing Oracle Apps server 10.1.3 with Oracle DB 11.2.0.2

    Error while installing Oracle Apps server 10.1.3 with Oracle DB 11.2.0.2 residing in the same server and being used by Apps server as it's metadata.
    bash-3.00$ export ORACLE_HOME=/data/ora11g/app/ora11g/product/11.2.0
    bash-3.00$ cd /data/OAS/install/soa_schemas/irca/
    bash-3.00$ ./irca.sh
    Integration Repository Creation Assistant (IRCA) 10.1.3.1.0
    (c) Copyright 2006 Oracle Corporation. All rights reserved.
    ERROR: Cannot find library - /data/ora11g/app/ora11g/product/11.2.0/jdbc/lib/ojdbc14.jar
    Please verify that the ORACLE_HOME is set correctly.
    bash-3.00$

    Hi Craig,
    Database 11gR2 could be used for Installing Application Server 10.1.3.x but with some limitation.
    So please review the note:-887365.1 Oracle Database 11g Release 2 (11.2) Certification for Oracle Application Server 10g (10.1.2, 10.1.3, 10.1.4)
    Section :- Oracle Application Server 10g Release 3 (10.1.3)
    Regards,
    Praaksh.

  • Install Solution Manager in RedHat Enterprise 6 with Oracle 11

    Hello ,
    In the marketplace-PAM,  RedHat Enterprise 6 is not listed as approved for EHP1 Solution Manager 7.0 64 bit (unicode) with Oracle.
    Does anyone have any information on this subject?
    Has anyone installed the Solution Manager 7.0/Oracle with RedHat Enterprise 6?
    tks

    Yes, you are correct. Apart from PAM, following Note confirms this. RHEL 6 is not supported yet for Oracle, is in planning stage.
    Note 1565179 - SAP software and Oracle Linux
    Thanks

Maybe you are looking for

  • Help needed in SRM upgrade to SRM server 5.0

    Experts, My client is on EBP 2.0 and going for an upgrade to SRM Server 5.0 and working on classic scenario and keeping the backend as 4.6C for this phase of the project. Please share any experiences on how to go about the upgrade, any questionaries,

  • Error While Building my First Process with Oracle BPM 11g

    Hi All, I am new to Oralce BPM. While Working through the BPM from http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/obpm/11g/r1/firstProcess/firstprocess_obpm11g.htm Am getting the below error while creating form for the Human interactio

  • Purchase Order deleted by mistake

    Hi all, We have a purchase order that was deleted by accident.  We we wanted to remove one of the line items and it set the whole purchse order for deletion.  Is there a way to undelete a purchase order?  Thanks all for your help and let me know if I

  • Deleting e-mail is slow with IPhone 1 and 2.0 operating system

    Since my IPhone 1 was updated to the 2.0 operating system, when I delete an e-mail from the Inbox, my IPhone will hang up for a few to as many as 30 seconds. During that time I can do nothing else. I am using the "Delete" confirmation as I have in th

  • Where can i get MiniSap?

    Hi guys, Do you know where i can get MiniSap for my own practice and learning purpose? P/S: Sometimes after work, i would like to get access to ABAP Workbench Editor too. Does anyone know what are the tools i can use to practice my ABAP after work? T