Doubt on using DB as JMS resource provider

Hi
I am trying to use Oracle DB as JMS resource provider. I am trying to create required tables like following.
connect as sysdba/pwd
CREATE USER TUSER IDENTIFIED BY tiger
GRANT CONNECT, RESOURCE,AQ_ADMINISTRATOR_ROLE TO TUSER
GRANT EXECUTE ON SYS.DBMS_AQ TO TUSER // Hanging
In line 3 it never completes. Looks like some lock is there on that table, But I am not able to understand what lock.
Can anybody explain me what could be wrong. (I am not DBA. Just trying to learn JMS using DB as resource provider. I am using the DB which comes with Infra)
Thanks
Ratheesh

Which database version is this? The hang is likely caused by a lock held on the dbms_aq package. For example, when a session is blocked inside dbms_aq package wating for messages to be delivered, it is not possble to grant/revoke execute permissions on that package to a different db user.
You could try bouncing the db to see if you still see the hang.
Hope this helps,
-Frances

Similar Messages

Error initializing the Oracle JMS Resource provider for Topics

Getting this error when starting OC4J 9.0.3 standlone on Windows2000.
Resource provider config'd as
<resource-provider class="oracle.jms.OjmsContext" name="ojms">
<description> OJMS/AQ </description>
<property name="datasource" value="jdbc/ProlianceDS"></property>
</resource-provider>
Datasource config'd as
 <data-source
 class="com.evermind.sql.OrionCMTDataSource"
 name="ProlianceDS"
 location="jdbc/ProlianceDS"
 xa-location="jdbc/xa/ProlianceDS"
 ejb-location="jdbc/ProlianceDS"
 connection-driver="oracle.jdbc.driver.OracleDriver"
 username="proliance"
 password="******"
 url="jdbc:oracle:thin:@aps67.ere.com:1538:ifstst"
 inactivity-timeout="30"
 />
ejb-jar config'd as
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<message-driven>
<description>Proliance Message Driven Bean</description>
<display-name>ProlianceMDB</display-name>
<ejb-name>ProlianceMDB</ejb-name>
<ejb-class>com.lendlease.bll.ProlianceMDB</ejb-class>
<transaction-type>Container</transaction-type>
<message-selector>
<method>
<ejb-name>ProlianceMDB</ejb-name>
<method-name>onMessage</method-name>
</method>
</message-selector>
<message-driven-destination>
<destination-type>javax.jms.Topic</destination-type>
<subscription-durability>Durable</subscription-durability>
</message-driven-destination>
<resource-ref>
<res-ref-name>java:comp/resource/ojms/Topics/PROLIANCE.OUT_AQ</res-ref-name>
<res-type>javax.jms.Topic</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-env-ref>
<resource-env-ref-name>java:comp/resource/ojms/TopicConnectionFactories/aqTcf</resource-env-ref-name>
<resource-env-ref-type>javax.jms.TopicConnectionFactory</resource-env-ref-type>
</resource-env-ref>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>ProlianceMDB</ejb-name>
<method-name>onMessage</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
orion-ejb-jar config'd as:
<?xml version = '1.0'?>
<!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" "http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd">
<orion-ejb-jar deployment-time="e7f1ce76f6" deployment-version="1.0.2.2">
<enterprise-beans>
<message-driven-deployment
name="ProlianceMDB"
connection-factory-location="java:comp/resource/ojms/TopicConnectionFactories/aqTcf"
destination-location="java:comp/resource/ojms/Topics/PROLIANCE.OUT_AQ"
subscription-name="PROLIANCE_SUBSCRIBER">
</message-driven-deployment>
</enterprise-beans>
</orion-ejb-jar>
Full startup trace is:
C:\ora\oc4j_9.0.3\j2ee\home>java -Djdbc.connection.debug=true -jar oc4j.jar
Node started with id=-2143203582
Auto-unpacking C:\ora\oc4j_9.0.3\j2ee\home\applications\ProlianceMDB.ear... done.
Auto-unpacking C:\ora\oc4j_9.0.3\j2ee\home\applications\ProlianceMDB\ProlianceMDB.war... done.
Auto-deploying ProlianceMDB (New server version detected)...
Copying default deployment descriptor from archive at C:\ora\oc4j_9.0.3\j2ee\home\applications\ProlianceMDB/ProlianceMDB
.jar/META-INF/orion-ejb-jar.xml to deployment directory C:\ora\oc4j_9.0.3\j2ee\home\application-deployments\ProlianceMDB
\ProlianceMDB.jar...
Auto-deploying ProlianceMDB.jar (New server version detected)... done.
Error initializing the Oracle JMS Resource provider for Topics: Not an OracleConnection
Error deploying file:/C:/ora/oc4j_9.0.3/j2ee/home/applications/ProlianceMDB/ProlianceMDB.jar homes: No javax.jms.Destina
tion found at the specified destination-location (java:comp/resource/ojms/Topics/PROLIANCE.OUT_AQ) for MessageDrivenBean
ProlianceMDB
OrionCMTConnection not closed, check your code!
Logical connection not closed, check your code!
Created at:
java.lang.Throwable: OrionCMTConnection created
at com.evermind.sql.OrionCMTConnection.<init>(OrionCMTConnection.java:42)
at com.evermind.sql.OrionCMTDataSource.getConnection(OrionCMTDataSource.java:82)
at oracle.jms.AQjmsConnection.newDBConnection(AQjmsConnection.java:1681)
at oracle.jms.AQjmsConnection.<init>(AQjmsConnection.java:537)
at oracle.jms.AQjmsTopicConnectionFactory.createTopicConnection(AQjmsTopicConnectionFactory.java:232)
at oracle.jms.OjmsResource.initT(OjmsResource.java:512)
at oracle.jms.OjmsResource.initAQ(OjmsResource.java:411)
at oracle.jms.OjmsResource.init(OjmsResource.java:214)
at oracle.jms.OjmsContextFactory.getObjectInstance(OjmsContextFactory.java:103)
at oracle.jms.OjmsContext.getResource(OjmsContext.java:328)
at com.evermind.server.Application.lookupResource(Application.java:2548)
at com.evermind.server.Application.lookupResource(Application.java:2563)
at com.evermind.server.ApplicationContext.handleResourceLookup(ApplicationContext.java:639)
at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:162)
at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:66)
at com.evermind.server.ejb.MessageDrivenHome.<init>(MessageDrivenHome.java:236)
at com.evermind.server.ejb.EJBPackageDeployment.bindHomes(EJBPackageDeployment.java:304)
at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:595)
at com.evermind.server.Application.postInit(Application.java:431)
at com.evermind.server.Application.setConfig(Application.java:136)
at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1635)
at com.evermind.server.ApplicationServer.initializeApplications(ApplicationServer.java:1585)
at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1240)
at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:93)
at java.lang.Thread.run(Thread.java:484)
Auto-deploying ProlianceMDB Poster (New server version detected)...
Oracle9iAS (9.0.3.0.0) Containers for J2EE initialized
Using native aqapi.jar with OC4J -didn't copy from 9.2.0.2 DB. 9.2.0.2 patchset ran fully, completed fine. What's going wrong?
Brian

Shouldn't I be getting a com.evermind.sql.OrclCMTConnection created instead of a com.evermind.sql.OrionCMTConnection (per the stack trace)? OJMS is complaining that it doesn't have an OracleCOnnection but how do I tell it to use the "OrclCMTConnection" class instead?
Brian

JMS Resource Adapter and JDeveloper 10g

Hello,
I an trying to use the OC4J JMS Resource Adapter for WebSphere MQ with Jdeveloper 10g (OC4J 9.0.4). The program is just a servlet that sends a message to a JMS Queue. My orion-web.xml looks like:
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE orion-web-app PUBLIC "-//Evermind//DTD Orion Web Application 2.3//EN" "http://xmlns.oracle.com/ias/dtds/orion-web.dtd">
<orion-web-app servlet-webdir="/servlet/">
<resource-ref-mapping name="jms/QCF" location="mqjms/MyQCF" />
<resource-env-ref-mapping name="jms/QUEUE1" location="mqjms/MyQ" />
</orion-web-app>
The problem is that when I try to start the server I get the following Jdeveloper error:
java.lang.IllegalArgumentException: Unrecognized parent-elem combination: interface oracle.jdeveloper.xml.oc4j.war.OrionWebApp - resource-env-ref-mapping
 at oracle.javatools.xml.bind.XMLBinding.throwUnrecognizedElem(XMLBinding.java:127)
 at oracle.jdeveloper.xml.j2ee.war.WebAppBinding.elem2intImpl(WebAppBinding.java:637)
 at oracle.javatools.xml.bind.XMLBinding.elem2int(XMLBinding.java:104)â¦.
Any ideas?
Thanks in advance

Did you find a fix for this? I'm experiencing the same problem.

JMS Foreign Provider using XAConnectionFactory for Container Managed Trans

Hello, we've been running some proof of concepts using Weblogic 10.3 with a JMS Foreign Provider attached to MQSeries 7.
We created a very simple MDB to read a message and output it's content.
We created a bindings file with a Connection Factory (without XA)
The question I have is that when I set the Transaction Management to Container and Transaction Attribute to "Required" , does Weblogic automatically look for a XAQueueConnectionFactory? We get the error below:
[EJB:011013]The Message-Driven EJB attempted to connect to the JMS connection factory with the JNDI name: OP_CF. However, the object with the JNDI name: OP_CF is not a JMS connection factory. NestedException Message is :com.ibm.mq.jms.MQQueueConnectionFactory cannot be cast to javax.jms.XAConnectionFactory>
When we set the transacation to Bean Managed or we set to Container Managed but set the attribute to "NotSupported" it works fine.
My goal is to have a MDB that has Container Managed Transactions and "Requires" Attribute, but only particpates in a local transaction and does not need the overhead of XA. It will read from a Foreign MQ manager Queue, process and then write back to the same Foreign MQ manager(different queue), so only one resource (MQ) is used.
If we set the above settings, it seems that a XAConnectionFactory is required. Is that true?

-- If you do not enable the container transaction, then the MDB connection factory does not need to be an XA connection factory.
-- If the application is performing messaging operations, and wants to use locally managed transactions, then you have a variety of options. These are all standard JMS:
* Use an XA connection and XA session. Begin JTA transactions before performing JMS operations, and call commit or rollback on the JTA transaction after performing the JMS operations. For foreign vendors, you must take extra steps to ensure that the vendor enlists with the WebLogic transaction -- typically by using WebLogic resource reference wrappers.
* Use the standard JMS API "transacted session" on a non-XA session -- the transaction will be local to the session (this is extremely similar to JDBC local transactions).
* Use a non-transacted session. Sends will occur immediately. Receive messages will be acknowledged immediately for auto-ack sessions, or will not for non-ack.
-- Note that if a transaction only includes a single operation, there's no need for XA or non-transacted sessions.
-- For more information on transactions and integration, I highly recommend reading our [ Integrating Remote JMS Providers | http://download.oracle.com/docs/cd/E15523_01/web.1111/e13727/interop.htm#JMSPG553 ] FAQ. I also very highly recommend purchasing a copy of [ Professional Oracle WebLogic Server | http://www.amazon.com/Professional-Oracle-WebLogic-Server-Patrick/dp/0470484306/ref=sr_1_1?ie=UTF8&s=books&qid=1252088885&sr=8-1 ], and of course reviewing our [ JMS Information Roadmap | http://download.oracle.com/docs/cd/E15523_01/web.1111/e14529/messaging.htm#sthref23 ].
-- Finally, you may also want to consider replacing some MQ usage with WebLogic JMS. WL JMS is a heavily adopted messaging vendor, and for obvious reasons, tends to integrate especially well with the WebLogic app server.
Hope this helps,
Tom

How to Configure and Use Oracle's JMS Connector with Tibco EMS

Jeff,
I am getting the below exception while try to do the deployment of the sample provided on 'How to Configure and Use Oracle's JMS Connector with Tibco Enterprise for JMS'
While deployment not able to get the 'TibcoJMSReference',
As I understand in the 'orion-application.xml for the below, unable to get the instance. Could you adivce how I can enable the trace more?
<resource-provider class="com.evermind.server.deployment.ContextScanningResourceProvider" name="TibcoJMSReference">
could you help to resolve the issue?
Error
Operation failed with error: No resource named 'TibcoJMSReference/TibcoXACF'found

Hi,
I'm also looking for the same 'Configure and Use Oracle's JMS Connector with Tibco JMS to consume message'. If you have already implemented and working fine, please let me know the steps and some documents.

How to Configure and Use Oracle's JMS Connector with Tibco Enterprise

Following the advice here: http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-connect-to-tibco/doc/how-to-connect-to-tibco.html
I believe I need to provide a username and password for the Tibco JMS provider, and would like to know the correct way. Is this right, in orion-application.xml
 <resource-provider class="com.evermind.server.deployment.ContextScanningResourceProvider" name="TibcoJMSReference">
 <property
 name="java.naming.factory.initial"
 value="com.tibco.tibjms.naming.TibjmsInitialContextFactory">
 </property>
 <property
 name="java.naming.provider.url"
 value="tibjmsnaming://jleinawe-sun:7222">
 </property>
<property name="java.naming.security.principal" value="user" />
<property name="java.naming.security.credentials" value="password" />
 </resource-provider>

This is kind of up to Tibco...
When you add properties to the resource-provider element, you are just adding entries to a Map which gets passed to the initial context factory, which in this case is implemented by Tibco (TibjmsInitialContextFactory), so you may want to check their docs.
It's possible they only use that for username/password for JNDI access purposes and not for JMS. If so, you can explicitly set username/password for outbound connections in the oc4j-ra.xml file, and using ResUser/ResPassword in the MDB's activation-spec to set username/password for inbound connections.
-Jeff

[EJB:010112] - error with WLI8.1 Event Generator for foreign JMS/MQ provider

I'm getting following error in weblogic server log when starting a JMS Event generator
to a foreign JMS(MQ5.3) Queue.
<May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010096> <The Message-Driven
EJ
B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
JMSQueue. Connection failed after 2 attempts. The MDB will attempt to reconnect
every 10 seconds. This log message will repeat every 600 seconds until the condi
tion clears.>
<May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
EJ
B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
JMSQueue. The Error was:
[EJB:010112]The Message Driven Bean 'mqQueueEventGen' is transacted, but the pro
vider defined in the EJB is not transacted. Provider should be transacted if onM
essage method in MDB is transacted.>
My WLI8.1.2 is patched with CR131686_812.zip to support event generator for foreign
JMS destinations. The foreign JMS/MQ provider is configured properly. QueueSend/Receive
were tested fine with JMS java code using local JNDI names of foreign JMS objects.
So we know that foreign Queue is active and accessiable from webLogic.
Anyone run into this? Solution?
Thanks,
Scott

Hi Scott,
I need a transaction from the MDB since I am not using an EJb to pursue the action.
Hence I need to retain the <trans-attribute>Required</trans-attribute> at the
MDB.
Have any answers?
Pradip
"Scott Yen" <[email protected]> wrote:
>
It's resolved.
The MDB automatically created by JMS Event Generator defaults to be deployed
with
“transacted”. That requires the foreign JMS provider to be “XA”.
The deployment descriptor is created as <domain-directory>/WLIJmsEG_<event_gen_name>.jar
e.g. C:\bea812\user_projects\domains\jmsInterop\WLIJmsEG_mqQueueEventGen.jar
Since MQ in the localhost and remote SLUDV18 are not XA-enabled, we had
to manually
change the <container-transaction> section in ejb-jar.xml:
From :
<trans-attribute>Required</trans-attribute>
To:
<trans-attribute>NotSupported</trans-attribute>
"Scott Yen" <[email protected]> wrote:
I'm getting following error in weblogic server log when starting a JMS
Event generator
to a foreign JMS(MQ5.3) Queue.
<May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010096> <The Message-Driven
EJ
B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
JMSQueue. Connection failed after 2 attempts. The MDB will attempt to
reconnect
every 10 seconds. This log message will repeat every 600 seconds until
the condi
tion clears.>
<May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
EJ
B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
JMSQueue. The Error was:
[EJB:010112]The Message Driven Bean 'mqQueueEventGen' is transacted,
but the pro
vider defined in the EJB is not transacted. Provider should be transacted
if onM
essage method in MDB is transacted.>
My WLI8.1.2 is patched with CR131686_812.zip to support event generator
for foreign
JMS destinations. The foreign JMS/MQ provider is configured properly.
QueueSend/Receive
were tested fine with JMS java code using local JNDI names of foreign
JMS objects.
So we know that foreign Queue is active and accessiable from webLogic.
Anyone run into this? Solution?
Thanks,
Scott

How to Use Office 365 api in Provider Hosted App

Hi,
I want to use outlook api in SharePoint Provider Hosted App.
when I use :-
$.ajax({
url: 'https://outlook.office365.com/api/v1.0/me/contacts',
type: 'GET',
beforeSend: function (xhr) {
xhr.setRequestHeader('Authorization', 'Bearer');
Accept: "application/json",
"client-request-id": "9de3d763-a8d9-4433-92f3-096d6be36d86",
success: function () {
alert("Welcome to Outlook ")},
error: function (e) {
alert(' Error121212 :' +e);
Error:-
XMLHttpRequest cannot load https://outlook.office365.com/api/v1.0/me/contacts. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://localhost:44309' is therefore not allowed access. The response had HTTP status code
401.
Please Provide me a good example.
Thanks in Advance

Hi SharePlus,
You probably want to use the Office 365 API's to authenticate and communicate with the API's.
There's several resources available for this:
Ultimate LinkRoll for Getting Started with the Office 365 API's
Download Office 365 API Tools for Visual Studio 2013
Getting Started with O365 Dev - Communicate with Exchange
If you don't want to use the pre-compiled typed objects in the Office 365 API's for communicating with the Mail service (Exchange), you can always just make sure to handle the authentication properly and then construct your queries as raw queries, like Chaks
describes here: http://chakkaradeep.com/index.php/working-with-office365apis-the-raw-version/
Also, as a general rule; When working with anything Office 365, you should always keep an eye out for the example code, articles and news published from the Office 365 Patterns & Practices team here: https://github.com/OfficeDev/PnP
I hope this will guide you in the right direction :-)
Tobias Zimmergren
Microsoft MCP, MCTS, MCT, MVP (SharePoint)
Blog: www.zimmergren.net
Twitter: twitter.com/zimmergren
Corporate site: www.tozit.com

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.
 
[#|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> 
 
[#|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|#] 
 
[#|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 
com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : 
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1591) 
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1421) 
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:524) 
at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:527) 
at com.sun.enterprise.server.ApplicationLoader.doLoad(ApplicationLoader.java:191) 
at com.sun.enterprise.server.TomcatApplicationLoader.doLoad(TomcatApplicationLoader.java:126) 
at com.sun.enterprise.server.ExtendedApplicationLoader.doLoad(ExtendedApplicationLoader.java:134) 
at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:238) 
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.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:159) 
at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:538) 
at java.lang.Thread.run(Thread.java:619) 

Hi Nigel,
Thanks for ur reply. In my ejb-jar.xml I have
<?xml version="1.0" encoding="UTF-8"?>

<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?

AQ resource provider in Weblogic 10.3

Hello,
Can you plz tell me how to create Resource Provider in WL Admin console to Oracle DB Q (AQ) ?
Thanks

Have a look at this link, there is also a great how to link with examples.
http://biemond.blogspot.com/2008/11/using-aq-in-weblogic-103.html
cheers
James

Add a resource provider to application.xml

I am trying to setup Oracle AQ integration to BAM
This requires adding the following resource provider to the file application.xml
<resource-provider name="BAMTTT" class="oracle.jms.OjmsContext">
<description>BAM for Generic</description>
<property name="datasource" value="jdbc/OracleTTTDS"/>
</resource-provider>
It seems to give an error if I add it to either the beginning or end of this file.
What is the proper way to add this resource to application.xml?

As long as I add this text before the last line it works ok.

Lookup JMS resource from server level failed, but other level will success

I have a jms resource in websphere the full jndi is
cell/nodes/sampleNode/servers/sampleServer/jms/foundation/SimpleQueue.TCFIf I use
Context jndiContext = (Context)jndiInitialContext.lookup("cell/nodes/sampleNode/servers/sampleServer/jms/foundation/SimpleQueue.TCF");No problem
but if use
Context jndiContext = (Context)jndiInitialContext.lookup("cell/nodes/sampleNode/servers/sampleServer");
(TopicConnectionFactory)jndiContext.lookup("jms/foundation/SimpleQueue.TCF");This will fail with exception
0000000a W UOW=3-fc00fc-21429626:localhost source=com.ibm.ws.naming.util.Helpers org=IBM prod=WebSphere component=Application Server thread=[P=500142:O=0:CT]
          NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow:
Context implementation: com.ibm.ws.naming.jndicos.CNContextImpl
Context method: lookupExt
Target name: jms/foundation/SimpleQueue.TCF
Other data: ""
Exception stack trace: javax.naming.NamingException: Error during resolve [Root exception is org.omg.CORBA.INTERNAL: initial and forwarded IOR inaccessible vmcid: IBM minor code: 58C completed: No]
        at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1939)
        at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1862)
        at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1552)
        at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1354)
        at Main.main(Main.java:98)
Caused by: org.omg.CORBA.INTERNAL: initial and forwarded IOR inaccessible vmcid: IBM minor code: 58C completed: No
        at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:1213)
        at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.java:1320)
        at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:1109)Even I change the lookup level to other like
Context jndiContext = (Context)jndiInitialContext.lookup("cell/nodes/sampleNode/servers");
(TopicConnectionFactory)jndiContext.lookup("sampleServer/jms/foundation/SimpleQueue.TCF");It will success, only from server level, exception happened.
Any idea?
Thank you.

I haven't tried this before, but I think you need to tell Apache to tunnel t3 and/or iiop explicitly in the config:
http://e-docs.bea.com/wls/docs103/plugins/apache.html#wp124662
Which client jar are you using? The thin client or the wlfullclient.jar/weblogic.jar?
If you read this section of the JMS thin client docs, it discusses how thin client t3 urls are transparently switched to iiop and http urls use iiop tunneling:
http://e-docs.bea.com/wls/docs103/client/jms_thin_client.html#wp1026979

C/C++ using SOAP as JMS Client ?

Did any body tried C/C++ using SOAP as JMS Client?

You can register any compliant JMS provider as a foreign jms provider in weblogic and then can access the JMS administered objects (destination and connection factory) from the local weblogic JNDI tree.
This blog shows how to configure AQJMS as a foreign JMS provider and then configure JMS adapter to access the jms objects.
http://biemond.blogspot.com/2009/07/using-aq-jms-text-message-in-wls-1031.html
You can use the above link as a reference on how to setup. You will have to modify the Initial Context Factory, Provider URL, JNDI Properties, foregin connection factories and foreign detsinations section to suit activeMQ.
Note: Weblogic does not come inbuild with the required jars to connect to ActiveMQ unlike AQJMS, so you need to ensure that the active mq jms client jars are available in the weblogic's classpath.

Howto delete Resource Provider Name for a database persistence provider?

Hi,
I have performed the steps successfully given here: http://mike-lehmann.blogspot.com/2006/09/simple-mdb-with-oracle-database-jms.html
Now, I need to do a clean up for this complete task. I have been able to do so completely sans one problem that if I want to do it again, the Resource Provider Name is visible in EM.
The steps I have taken to to clean the task are:
1. Undeployed the MDB application.
2. Deleted the data source
3. Deleted the connection pool
4. Undeployed the RA (doing so the JMS destination also got deleted)
5. Deleted the JMSUSER schema/user completely.
My environment is RH4 Update 5 + AS 10.1.3.1.0 [J2EE Server+ Web Server] + 10.1.3.3 patch.
Can someone please let me know how to remove the Resource provider name also?
thanks,
Saurabh

In addition to the steps highlighted above, the value for the Resource Provider Name was persisting in the application.xml file. Once it is deleted, OC4J instance restarted, all works fine.
Thanks.

MDB - JMS foreign provider

 Using WLS8.1:
 I'm currently trying to set up a MDB listening directly on a JMS queue, provided
 by Sonic.
 I registered my queue through the Sonic JMS console in the WLS JNDI repository,
 and can browse to the object successfully in the JNDI browser.
 However, when I deploy my MDB, I get an exception:
 <Feb 28, 2004 3:27:09 PM MET> <Warning> <EJB> <BEA-010061> <The Message-Driven
 EJB: SomeMDB is unable to connect to the JMS destination: myforeigndestination.
 The Error was:
 weblogic.jms.common.InvalidDestinationException: Foreign destination, q_external
 weblogic.jms.common.InvalidDestinationException: Foreign destination, q_external
 at weblogic.jms.common.Destination.checkDestinationType(Destination.java:106)
 at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1580)
 at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1484)
 at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1609)
 at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1844)
 at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
 at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
 at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
 at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
 at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 The only way to get it working is setting up an additional internal WL queue,
 connected by a Messaging Bridge, but that's not what I want.
 It seems like weblogic JMS implemenation only accepts weblogic Queue's as valid
 Queue objects.
 Thanks for any pointers.
 Rgrds,
 Klaas van der Ploeg


 Klaas van der Ploeg wrote:
 > Using WLS8.1:
 >
 > I'm currently trying to set up a MDB listening directly on a JMS queue, provided
 > by Sonic.
 >
 > I registered my queue through the Sonic JMS console in the WLS JNDI repository,
 > and can browse to the object successfully in the JNDI browser.
 > However, when I deploy my MDB, I get an exception:
 > <Feb 28, 2004 3:27:09 PM MET> <Warning> <EJB> <BEA-010061> <The Message-Driven
 > EJB: SomeMDB is unable to connect to the JMS destination: myforeigndestination.
 > The Error was:
 > weblogic.jms.common.InvalidDestinationException: Foreign destination, q_external
 > weblogic.jms.common.InvalidDestinationException: Foreign destination, q_external
 > at weblogic.jms.common.Destination.checkDestinationType(Destination.java:106)
 > at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1580)
 > at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1484)
 > at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1609)
 > at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1844)
 > at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
 > at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
 > at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
 > at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 > at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
 > at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
 > at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 >
 >
 > The only way to get it working is setting up an additional internal WL queue,
 > connected by a Messaging Bridge, but that's not what I want.
 >
 >
 > It seems like weblogic JMS implemenation only accepts weblogic Queue's as valid
 > Queue objects.
 Emphatically not true. In pointed fact, WebLogic has gone through
 great pains over the years to ensure integration works with multiple
 JMS vendors - sending out fix requests to them as needed (including
 Sonic).
 Anyhow, you are trying to use a non-WebLogic destination with a
 WebLogic JMS session. No vendor supports this. Instead, you
 must make sure that the MDB creates a Sonic JMS session. So
 configure a foreign connection factory, and configure the
 MDB to refer to this connection factory. You can find
 this information in WebLogic's JMS developer guide.
 This is the first time I've gotten a Sonic question in quite a
 while, but I know that they have step-by-step doc on how to
 integrate their product with WebLogic. You might want to try
 looking there for more help. I don't know if their doc
 leverages 8.1 foreign destination wrapper feature.
 Tom Barnes, BEA
 >
 > Thanks for any pointers.
 >
 > Rgrds,
 > Klaas van der Ploeg

Doubt on using DB as JMS resource provider

Similar Messages

Maybe you are looking for