Foreign jms queue binding problem

          Hi,
          I am on the way to wls7.0 from wls5.1, but I got a probelm when I tried to rebind
          the jms queue to weblogic jndi.
          [javax.naming.ConfigurationException [Root exception is java.rmi.MarshalException:
          failed to marshal rebind(Ljava.lang.String;Ljava.lang.Object;Ljava.util.Hasht
          able;); nested exception is: java.io.NotSerializableException]]
          Can I bind the queue to wls jndi? Anybody has silimar situation?
          Thanks

Hi Jen,
          As TOM said, in your case weblogic interaoperabilty supports only from
          weblogic 5.1 to 6.1, that to specified service packs. you can go through the
          following url
          http://e-docs.bea.com/wls/docs61/interop/interop.html
          So you better go by using message bridges for foreign jms providers. The
          document has how you can configure about JNDI provider either File based Or
          Ldap based.
          Thanks
          Kumar
          "Je" <[email protected]> wrote in message
          news:[email protected]...
          >
          > Thanks, actually I am trying to rebind the jms queue from Fiorano
          > MQ. It works fine in wls5.1. Is there special requirement for jndi for
          wls7.1,
          > does the object needs to be serilizable to be bind into jndi?
          >
          > Tom Barnes <[email protected]> wrote:
          > >
          > >It seems you are trying to access 5.1 JMS from 7.0. WebLogic did not
          > >
          > >support interoperability between versions until 6.1. The classes are
          > >
          > >not compatible. So interop requires a good bit of class-loader magic.
          > >
          > > The only way to interop between JMS 5.1 and 7.0 is to use the
          > >messaging bridge (which does the magic for you).
          > >
          > >FYI: I think that it may be possible to invoke remote 5.1 methods from
          > >
          > >7.0 using the IIOP protocol.
          > >
          > >Tom
          > >
          > >Jen wrote:
          > >> Hi,
          > >> I am on the way to wls7.0 from wls5.1, but I got a probelm when I tried
          > >to rebind
          > >> the jms queue to weblogic jndi.
          > >>
          > >> [javax.naming.ConfigurationException [Root exception is
          java.rmi.MarshalException:
          > >> failed to marshal
          rebind(Ljava.lang.String;Ljava.lang.Object;Ljava.util.Hasht
          > >> able;); nested exception is: java.io.NotSerializableException]]
          > >>
          > >> Can I bind the queue to wls jndi? Anybody has silimar situation?
          > >> Thanks
          > >
          >

Similar Messages

Reading Message from Foreign JMS Queue in SOA Suite 11g.

Hi,
I am trying to read a JMS message that has been put into a JMS Queue on a remote weblogic Server.
The steps that I know is that I need to create a foreign JMS Server and then probably use JMS Adapter to subscribe to the message that is lying in the remote queue.
Has anybody been able to achieve this kind of scenario working for a remote JMS queue? Also, is this supported by JMS Adapter in SOA11g?
Any help will be appreciated.
Regards,
Varun Maheshwari

Hi Atheek1,
Thanks for your reply.
The confusion that is pondering me is that do I need to create a Foreign JMS Server or should I create a JMS adapter and override the properties.
I have tried the steps for creating a Foreign Server from the below link
Unable to access remote JMS Queue through JMS Adapter
But I am not able to find the Foreign Server created and any connection factories and Destinations related to foreign Server in my JMS Destination while configuring JMS Adapter.
I am not sure how to do step2 as entailed by you.
Could you please explain me in little detail on how to do this or redirect me to some blog or forum which will be really helpful.
Cheers,
Varun

WLST offline Foreign JMS creation

I am trying to setup a domain using the WLST, offline, and I need to create a couple of foreign JMS queues but I can not seem to find examples on creating them using the WLST. Is it even possible to do this? If so could someone please show me an example.
Any help would be much appreciated,
Thanks,
PayniePayne

The best way to learn unknown WLST commands is by recording a WLS console session (look for the "record" icon in the upper sniplet) . My recording shows the following commands (see http://e-docs.bea.com/wls/docs103/wlsmbeanref/mbeans/ForeignServerBean.html for complete reference):
startEdit()
cd('/')
cmo.createJMSSystemResource('SystemModule-0')
cd('/SystemResources/SystemModule-0')
set('Targets',jarray.array(, ObjectName))
cd('/JMSSystemResources/SystemModule-0/JMSResource/SystemModule-0')
cmo.createForeignServer('ForeignServer-0')
cd('/JMSSystemResources/SystemModule-0/JMSResource/SystemModule-0/ForeignServers/ForeignServer-0')
cmo.setDefaultTargetingEnabled(true)
cmo.setConnectionURL('some.url')
cmo.setInitialContextFactory('SomeInitialContextFactory')
cmo.createForeignDestination('ForeignDestination-0')
cd('/JMSSystemResources/SystemModule-0/JMSResource/SystemModule-0/ForeignServers/ForeignServer-0/ForeignDestinations/ForeignDestination-0')
cmo.setLocalJNDIName('localQ')
cmo.setRemoteJNDIName('remoteQ')
activate()

Authentication problem w MDB on WL8.1 and JMS Queue on WL6.1

          Hi,
          I'm having problems with a MessageDrivenBean that is deployed on a Weblogic 8.1
          server. It listens to a JMS Queue on a Weblogic 6.1 server.
          I'm getting the following error message upon deployment:
          [java.lang.SecurityException: Authentication for user system denied in realm wl_realm
          I've made sure that both servers are installed with the user "system" and a password
          of "password".
          This worked fine for two WL6.1 servers.
          Here's my ejb-jar.xml:
          <!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>
                      <ejb-name>WebResponseJMSBean</ejb-name>
                      <ejb-class>com.ditech.webresponse.jms.WebResponseJMSBean</ejb-class>
                      <transaction-type>Container</transaction-type>
                      <message-driven-destination>
                          <destination-type>javax.jms.Queue</destination-type>
                      </message-driven-destination>
                  </message-driven>
              </enterprise-beans>
              <assembly-descriptor>
                  <container-transaction>
                      <description>Transaction attributes for 'WebResponseJMSBean' methods</description>
                      <method>
                          <ejb-name>WebResponseJMSBean</ejb-name>
                          <method-name>*</method-name>
                      </method>
                      <trans-attribute>NotSupported</trans-attribute>
                  </container-transaction>
              </assembly-descriptor>
          </ejb-jar>
          Here's my weblogic-ejb-jar.xml:
          <?xml version="1.0"?>
          <!DOCTYPE weblogic-ejb-jar PUBLIC
          '-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN'
          'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
          <weblogic-ejb-jar>
              <weblogic-enterprise-bean>
                  <ejb-name>WebResponseJMSBean</ejb-name>
                  <message-driven-descriptor>
                      <destination-jndi-name>com.ditech.jms.CowResponseQueue</destination-jndi-name>
                      <provider-url>t3://localhost:7003</provider-url>
                      <connection-factory-jndi-name>com.ptp.jms.AppOnlineConnectionFactory</connection-factory-jndi-name>
                  </message-driven-descriptor>
                  <jndi-name>ejb/WebResponseJMSBean</jndi-name>
              </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          Can anyone give me any suggestions?
          Thanks in advance,
          -Ben


          We are facing a similar issue, between MDB's and JMS Queues on 2 separated WebLogic
          8.1 domains. What I will test next week are:
          1. In the domain where my MDB's are deployed, configure Foreign JMS Servers/Connection
          Factories/Queues, for which passwords can be specified (not possible in weblogic-ejb-jar.xml)
          2. If No.1 does not work, I will add CredentialGenerated="false" in <SecurityConfiguration>
          in config.xml in both domains
          3. If No. 2 still does not work, I will specify run-as principal and security-role
          in my MDB DD files, and specify CredentialMapping via the WebLogic admin console.
          Maybe you can try the same?
          Eric Ma
          "B Liu" <[email protected]> wrote:
          >
          >Hi,
          >
          >I'm having problems with a MessageDrivenBean that is deployed on a Weblogic
          >8.1
          >server. It listens to a JMS Queue on a Weblogic 6.1 server.
          >
          >I'm getting the following error message upon deployment:
          >
          >[java.lang.SecurityException: Authentication for user system denied in
          >realm wl_realm
          >
          >I've made sure that both servers are installed with the user "system"
          >and a password
          >of "password".
          >
          >This worked fine for two WL6.1 servers.
          >
          >Here's my ejb-jar.xml:
          >
          ><!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>
          >
          >            <ejb-name>WebResponseJMSBean</ejb-name>
          >            <ejb-class>com.ditech.webresponse.jms.WebResponseJMSBean</ejb-class>
          >            <transaction-type>Container</transaction-type>
          >            <message-driven-destination>
          >                <destination-type>javax.jms.Queue</destination-type>
          >            </message-driven-destination>
          >
          >        </message-driven>
          >
          >    </enterprise-beans>
          >
          >    <assembly-descriptor>
          >
          >        <container-transaction>
          >
          >            <description>Transaction attributes for 'WebResponseJMSBean'
          >methods</description>
          >            <method>
          >                <ejb-name>WebResponseJMSBean</ejb-name>
          >                <method-name>*</method-name>
          >            </method>
          >            <trans-attribute>NotSupported</trans-attribute>
          >
          >        </container-transaction>
          >
          >    </assembly-descriptor>
          >
          ></ejb-jar>
          >
          >Here's my weblogic-ejb-jar.xml:
          >
          ><?xml version="1.0"?>
          >
          >
          >
          ><!DOCTYPE weblogic-ejb-jar PUBLIC
          >
          >'-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN'
          >
          >'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
          >
          >
          ><weblogic-ejb-jar>
          >
          >    <weblogic-enterprise-bean>
          >
          >        <ejb-name>WebResponseJMSBean</ejb-name>
          >
          >        <message-driven-descriptor>
          >
          >            <destination-jndi-name>com.ditech.jms.CowResponseQueue</destination-jndi-name>
          >            <provider-url>t3://localhost:7003</provider-url>
          >            <connection-factory-jndi-name>com.ptp.jms.AppOnlineConnectionFactory</connection-factory-jndi-name>
          >        </message-driven-descriptor>
          >
          >        <jndi-name>ejb/WebResponseJMSBean</jndi-name>
          >
          >    </weblogic-enterprise-bean>
          >
          ></weblogic-ejb-jar>
          >
          >
          >Can anyone give me any suggestions?
          >
          >Thanks in advance,
          >-Ben
          >

Problem connecting weblogic OSB with IBM websphere via foreign JMS

Hi All,
I am trying to setup Foreign JMS. My configuration doesn’t work.
Could you please let me know if I am missing anything .
All my configuration details are done as specified in this link http://www.oracle.com/technology/products/integration/service-bus/docs/osb-websphere-whitepaper.pdf
Here is what I did.
In OSB sbconsole
OSB business Service ENDPoint URL jms://webspherehost:9082/sampleQueuemanager/sampleQueue
In websphere
Created a queue connection factory and a queue from the webspehere administrator console.
Modified JSMAdmin.config to enable the following…/Java/bin/JMSAdmin.config.
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
PROVIDER_URL=file:/C:/JNDI-Directory
Ran JSMAdmin.bat to bind the JNDI
def qcf(sampleQueuemanager) qmanager(QMGR) HOSTNAME(webspherehost) PORT(1327) TRANSPORT(CLIENT)
def Q(sampleQueue) queue(sampleQueue) qmanager(QMGR) PERSISTENCE(PERS)
InitCtx> dis ctx
JMSADM4089 InitCtx
.bindings java.io.File
bck_.bindings java.io.File
a sampleQueuemanager com.ibm.mq.jms.MQQueueConnectionFactory
a sampleQueue com.ibm.mq.jms.MQQueue
4 Object(s)
0 Context(s)
4 Binding(s), 2 Administered
In weblogic admin console
Created foreign JMS, destination and connection factory as mentioned in the following link.
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/ConsoleHelp/taskhelp/jms_modules/foreign_servers/CreateForeignConnectionFactories.html
When I execute business service from OSB sbconsole, this is what I get.
+The invocation resulted in an error: [JMSPool:169803]JNDI lookup of the JMS connection factory sampleQueuemanager failed: javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: HTTP/1.1 400 Bad Request]].+
Thanks
siva

Little confusing. Are we not supposed to use osb host name and port along with foreign connection factory created in weblogic for OSB BS?.
You said: jms://webspherehost:9082/sampleQueuemanager/sampleQueue
We have to jms://osbhost:port/ForeignQueueManagerInWeblogic/ForeignQueueInWeblogic
Manoj

OC4J 9.0.4: Problem receiving message from JMS queue

I've created an application which puts XML files in a JMS queue and try to get it out again. The enqueing (sending) is no problem, but when I dequeue from the same queue I receive nothing and if I don't specify a wait time the programs hangs.
If I create a QueueBrowser I can see there are messages in the queue.
Can someone tell me what I do wrong?
Here is the code of my dequeue action:
public String dequeue(int qName) throws RbsSysException
        final String method = "dequeue(int qName)";
        _log.debug(method);
        QueueConnection queueConnection = null;
        try
            queueConnection = _queueConnectionFactory.createQueueConnection();
            QueueSession queueSession = queueConnection.createQueueSession(false,
                    Session.AUTO_ACKNOWLEDGE);
            QueueReceiver queueRcv = queueSession.createReceiver(getQueue(qName));
            _log.debug("queue = "+ queueRcv.getQueue().getQueueName());
            // Due to bug 3376983 in OC4J We cannot use TextMessage if it exceeds
            // 64 kb. Therefore use ObjectMessage.
            Message msg = queueRcv.receiveNoWait();
            _log.debug("msg = " + msg);
            ObjectMessage objMsg = (ObjectMessage)msg;
            //ObjectMessage objMsg = (ObjectMessage) queueRcv.receiveNoWait();
            _log.debug("objMsg = " + objMsg);
            if (objMsg != null)
                return (String) objMsg.getObject();
            else
                return null;
        catch (JMSException je)
            throw new RbsSysException(je);
        finally
            if (queueConnection != null)
                try
                    queueConnection.close();
                catch (Exception any)
                    _log.error("Error while closing QueueConnection: ", any);
    }

Did you implement javax.jms.MessageListener and the method onMessage(Message)?
If you use onMessage() as wel as receive (or receiveNoWait() or receive(long)), the onMessage() can be called, while the main thread is blocking on a synchronous receive, so make sure you use only one of the two methods: onMessage() or receive.
Receive() blocks your thread until a message is published. So your program 'hangs' by design. Usually this is used when your program is waiting for a particular message. Otherwise use onMessage().
ReceiveNoWait() checks if something is in the queue at that very moment, so if nothing is there (yet), the main thread continues.
Hope this helps,
Lonneke

JMS queue problem integrating with TIBCO

Hi all!
We have several communication channels between XI 3.0 (SP21) and TIBCO via JMS queues. All of them are working fine except one. This problem only happens in development and quality systems with SP21, production has SP17 and doesn't have this error on the same communication channel.
We are getting the following error in communication channel details...
27-03-2008 16:32:21   XI message ID corresponding to the JMS message ID 'ID:EMS-QUALITY.14C46ECF3303EC:61' has the value 'null', with the ID: prefix removed+
27-03-2008 16:32:21   XI message ID corresponding to JMS message with ID 'ID:EMS-QUALITY.14C46ECF3303EC:61' will be created with same value as JMSCorrelationID with value 'null'+
27-03-2008 16:32:20   Error while processing message 'null'; detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Error in converting Binary message <?xml version="1.0" encoding="UTF-8"?> <ns0:MT_PedCarga_GE xmlns:ns0="http://pt.galp.is-oil.ec">    <Partner>        <ZIDIF>62</ZIDIF>    </Partner>    <Controle>        <Nr_Envio>29183049</Nr_Envio>        <Dt_envio>20080229</Dt_envio>        <Tipo_Carga>CPAT</Tipo_Carga>        <Operador>230</Operador>    </Controle>    <PedCarga>        <FRETE>            <Tipo_Registo>N</Tipo_Registo>            <Inst_Carreg>ES41</Inst_Carreg>            <Data_Execucao>20080228</Data_Execucao>            <Resp_Transporte>13</Resp_Transporte>            <Transporte>          </Transporte>            <Transportador>1700</Transportador>            <Ref_Externa_head>2008022931859</Ref_Externa_head>            <Gera_Docs>X</Gera_Docs>            <Imprim_Docs>X</Imprim_Docs>            <Imprim_Ordem_Carreg>X</Imprim_Ordem_Carreg>            <Confirm_Autom>X</Confirm_Autom>            <Operador>230</Operador>        </FRETE>        <ENTREGA>            <Tipo_Destinatario>1</Tipo_Destinatario>            <Local_Entrega>14018</Local_Entrega>            <Cod_Produto>GOA []</Cod_Produto>            <Quantidade>05100</Quantidade>            <Ref_Externa_Item>01737307470601</Ref_Externa_Item>            <Regime_Fiscal>N</Regime_Fiscal>        </ENTREGA>        <ENTREGA>            <Tipo_Destinatario>1</Tipo_Destinatario>            <Local_Entrega>14018</Local_Entrega>            <Cod_Produto>GOC []</Cod_Produto>            <Quantidade>13300</Quantidade>            <Ref_Externa_Item>02737307470602</Ref_Externa_Item>            <Regime_Fiscal>R</Regime_Fiscal>        </ENTREGA>    </PedCarga> </ns0:MT_PedCarga_GE> to XI message for message: null: InvalidParamException: Invalid message id: com.sap.guid.GUIDFormatException+
Any clues?
Regards,
Fernando Figueiredo

We changed the conversation ID from Message ID to Correlation ID.

JMS Queue servicing algorithm problems

I'm using WLS 5.1, and have run into a problem with the way that WLS
          services JMS queues.
          I have two queues (Q1 and Q2, created in that order), each of which is
          serviced by a session pool.
          The problem is that as long as there are messages pending in Q1, there will
          be no messages serviced from Q2. The message listeners for Q2 don't get any
          work until Q1 is completely empty. If Q1 happens to get a big chunk of
          messages dumped into it, then all work on Q2 grinds to a halt until the
          first queue is cleared up.
          If I reverse the creation order, then the same problem occurs the other way
          around.
          Are there any patches or workarounds for this? I would have expected a more
          balanced approach to servicing the queues.
          -Chris Solar, MetaSolv Software.


Known problem with 5.1. No good 5.1 work arounds. Use 6.x or 7.x,
          preferably 7.x.
          _sjz.
          "Chris Solar" <[email protected]> wrote in message
          news:[email protected]..
          > I'm using WLS 5.1, and have run into a problem with the way that WLS
          > services JMS queues.
          >
          > I have two queues (Q1 and Q2, created in that order), each of which is
          > serviced by a session pool.
          >
          > The problem is that as long as there are messages pending in Q1, there
          will
          > be no messages serviced from Q2. The message listeners for Q2 don't get
          any
          > work until Q1 is completely empty. If Q1 happens to get a big chunk of
          > messages dumped into it, then all work on Q2 grinds to a halt until the
          > first queue is cleared up.
          >
          > If I reverse the creation order, then the same problem occurs the other
          way
          > around.
          >
          > Are there any patches or workarounds for this? I would have expected a
          more
          > balanced approach to servicing the queues.
          >
          > -Chris Solar, MetaSolv Software.
          >
          >

Jms queue problem in 11g

exception trace is comming, while running the project in weblogic, in the project iam using jms queue, i configured the jms server and jms module and connection factory but it is showing these exception
[The selected operation process could not be invoked.
An exception occured while invoking the webservice operation. Please see logs for more details.
oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: InvalidSecurity : error in processing the WS-Security security header]
can any one please, provide the suggestions

i got the solution for my problem, i just need to add owsm policies to my processs

OSB 10.3 JMS queue problem: JMSCorrelationID is null

Hi everybody,
I am new to OSB/ALSB, and need some help regarding JMS message handling. I am trying to put some input data into a JMS queue( say, reqQueue) and to get the response from another JMS queue(say resQueue). My architecture is:
OSB proxy service->OSB business service->JMS queue(reqQueue)->BPEL process(through JMS adapter) ->JMS queue(resQueue)->OSB business service->OSB proxy service.
I have used JMSCorrelationID for response correlation. but my problem is that when I am trying to test the service from proxy service, I am getting the JMSCorrelationId as null in BPEL process as well as in the weblogic server JMS log, and as I am getting the CorrelationId as null, I am unable to correlate the response, so I am not getting any response.
This is urgent, please help me as soon as possible as possible.
Thanks in advance.
Joy

Sovled it..
OSB 10.3 JMS queue problem: JMSCorrelationID is null

Dead message queue - DLQ for foreign JMS providers

Is there a way to configure Error-queue or 'Dead message/letter queue' in MDB listening to foreign JMS provider like JBoss? (Automatic routing of failed messages to error-queue after specified retries to preserve JMS messages)
          I did all the docs from BEA and it doesn't cover this DLQ for foreign JMS providers :). For Weblogic JMS service, DLQ can be configured in the config.xml. But for <ForeignJMSServer> there is no way to configure dead-queue.
          Could some please validate this before I start coding this piece in the application instead of appserver configuration.
          JMS provider is Tibco and JMS destinations are pre-defined and can't/doesn't need to be created
          Thanks in advance.

Interesting idea! But no, there's no facility for redirecting failed foreign provider messages to a DLQ. This is a feature normally supplied by the foreign provider itself.
          Some foreign providers, in addition to WebLogic 9.0 JMS, provide a "redelivery count" property in the message. If the foreign provider provides no automatic DLQ capability, you might be able to leverage this property to have your MDB application code automatically forward messages with high redelivery counts to the DLQ.
          Tom

JMS queue hes been binding during server startup but not looking up

Hi,
I have created a queue connection factory as jms/AlertACF and destination resources as jms/AlertQueue with properties
key : imqDestinationName
value : AlertQueue
and
Physical destination as AlertQueue.
I have applied all the changes to the server instance and restrated the server instance. In the log file the startup message like
[08/Aug/2006:11:58:05] INFO ( 5768): JMS5015: Install JMS resources ...
[08/Aug/2006:11:58:06] INFO ( 5768): JMS5002: Binding [< JMS Destination: jms/AlertQueue, javax.jms.Queue, [ imqDestinationName=AlertQueue ] >]
[08/Aug/2006:11:58:06] INFO ( 5768): JMS5002: Binding [< JMS Connection Factory: jms/AlertACF, javax.jms.QueueConnectionFactory, No properties >]along with few other messages about ejb's uploaded successfully...
Now, when I run my test case to test the JMS service, i am getting
[08/Aug/2006:12:03:39] INFO ( 5768): CORE3282: stdout: javax.naming.NameNotFoundException: jms/AlertQueue.........
can anybody help me out in this.......
Thank you very much
Regards,
Mike

Hi,
I have created a queue connection factory as jms/AlertACF and destination resources as jms/AlertQueue with properties
key : imqDestinationName
value : AlertQueue
and
Physical destination as AlertQueue.
I have applied all the changes to the server instance and restrated the server instance. In the log file the startup message like
[08/Aug/2006:11:58:05] INFO ( 5768): JMS5015: Install JMS resources ...
[08/Aug/2006:11:58:06] INFO ( 5768): JMS5002: Binding [< JMS Destination: jms/AlertQueue, javax.jms.Queue, [ imqDestinationName=AlertQueue ] >]
[08/Aug/2006:11:58:06] INFO ( 5768): JMS5002: Binding [< JMS Connection Factory: jms/AlertACF, javax.jms.QueueConnectionFactory, No properties >]along with few other messages about ejb's uploaded successfully...
Now, when I run my test case to test the JMS service, i am getting
[08/Aug/2006:12:03:39] INFO ( 5768): CORE3282: stdout: javax.naming.NameNotFoundException: jms/AlertQueue.........
can anybody help me out in this.......
Thank you very much
Regards,
Mike

MDB problem with Foreign JMS MQ

Hi,
I have MDB 2.1 and i am trying to deploy in weblogic 10.2 app server. Below is my ejb-jar.xml and weblogic.jar xml config. I have a foreign JMS configured and i have destination and connection factory configured too. I was able to post a message to the queue successfully, but my MDB is not getting executed I am getting below exception during the startup of application. I can see other EJBs in the JNDI but not my MDBs. Please advice and your help is very much appreciated.
Warning Message:
<Jun 1, 2010 10:24:04 AM CDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: IFIPNCDistributorMDB is unable to connect to the JMS destination: jms/MyQueue. The Error was:
Can not get distribute destination information. The destination JNDI name is jms/MyQueue, the provider URL is file:/C:/JNDI-Directory>
weblogic-ejb-jar.xml
<weblogic-enterprise-bean>
<ejb-name>MDB</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>4</max-beans-in-free-pool>
<initial-beans-in-free-pool>4</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>jms/IFIPNCQueue</destination-jndi-name>
<initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
<provider-url>file:/C:/JNDI-Directory</provider-url>
<connection-factory-jndi-name>jms/MyQCF</connection-factory-jndi-name>
</message-driven-descriptor>
<reference-descriptor>
<resource-description>
<res-ref-name>MyQCF</res-ref-name>
<jndi-name>jms/MyQCF</jndi-name>
</resource-description>
<resource-description>
<res-ref-name>MyQueue</res-ref-name>
<jndi-name>jms/MyQueue</jndi-name>
</resource-description>
</reference-descriptor>
<jndi-name>MDB</jndi-name>
</weblogic-enterprise-bean>
ejb-jar.xml
<message-driven id="MDB">
               <ejb-name>MDB</ejb-name>
               <ejb-class>com.IFIPNCDistributorMDB</ejb-class>
               <transaction-type>Bean</transaction-type>
               <message-driven-destination>
                    <destination-type>javax.jms.Queue</destination-type>
               </message-driven-destination>
               <resource-ref>
          <res-ref-name>jms/QCF</res-ref-name>
          <res-type>javax.jms.QueueConnectionFactory</res-type>
          <res-auth>Application</res-auth>
          <res-sharing-scope>Unshareable</res-sharing-scope>
     </resource-ref>
     <resource-ref>
          <res-ref-name>jms/MyQueue</res-ref-name>
          <res-type>javax.jms.Queue</res-type>
          <res-auth>Application</res-auth>
          <res-sharing-scope>Unshareable</res-sharing-scope>
          </resource-ref>
          </message-driven>
Thank You,
VJ

Can you setup as in this example:
Foreign JMS_
<foreign-server name=”ForeignServer”>
<default-targeting-enabled>true</default-targeting-enabled>
<foreign-destination name=”A”>
<local-jndi-name>A</local-jndi-name>
<remote-jndi-name>queue/A</remote-jndi-name>
</foreign-destination>
<foreign-connection-factory name=”FConf”>
<local-jndi-name>FConf</local-jndi-name>
<remote-jndi-name>ConnectionFactory</remote-jndi-name>
<username>esbuser</username>
<password-encrypted>{3DES}90sIZwo6Llr9r73p+VXkvQ==</password-encrypted>
</foreign-connection-factory>
<initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
<connection-url>file:/C:/JNDI-Directory</connection-url>
</foreign-server>
weblogic-ejb-jar.xml_
<?xml version=’1.0′ encoding=’UTF-8′?>
<web:weblogic-ejb-jar xmlns:web=”http://www.bea.com/ns/weblogic/weblogic-ejb-jar”>
<web:weblogic-enterprise-bean>
<web:ejb-name>RequestEJB-2518965873970113789–2352f820.127bd3f293c.-7fdb</web:ejb-name>
<web:message-driven-descriptor>
<web:pool>
<web:max-beans-in-free-pool>1000</web:max-beans-in-free-pool>
<web:initial-beans-in-free-pool>1</web:initial-beans-in-free-pool>
</web:pool>
<web:destination-jndi-name>A</web:destination-jndi-name>
<web:connection-factory-jndi-name>FConf</web:connection-factory-jndi-name>
</web:message-driven-descriptor>
<web:transaction-descriptor>
<web:trans-timeout-seconds>600</web:trans-timeout-seconds>
</web:transaction-descriptor>
<web:resource-description>
<web:res-ref-name>jms/ConnectionFactory</web:res-ref-name>
<web:jndi-name>FConf</web:jndi-name>
</web:resource-description>
<web:resource-description>
<web:res-ref-name>jms/QueueName</web:res-ref-name>
<web:jndi-name>A</web:jndi-name>
</web:resource-description>
</web:weblogic-enterprise-bean>
</web:weblogic-ejb-jar>
Note, local JNDI names in the foreign jms server should be used for destination-jndi and conection-factory-jndi. No need to specify provider URL in deployment descriptors. Instead it is specified at the foreign jms setup.
Also you should use the same resource-reference names in both ejb-jar & weblogic-ejb-jar.xml's., In above example resource-reference section of ejb-jar should look like:
<resource-ref>
<res-ref-name>jms/ConnectionFactory</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Application</res-auth>
<res-sharing-scope>Unshareable</res-sharing-scope>
</resource-ref>
<resource-ref>
<res-ref-name>jms/QueueName</res-ref-name>
<res-type>javax.jms.Queue</res-type>
<res-auth>Application</res-auth>
<res-sharing-scope>Unshareable</res-sharing-scope>
</resource-ref>

Using a foreign WLS JMS queue (no bridge)

          Hi,
          We have a configuration from which we communicate from WLS 7 to a foreign MQ via
          JMS. This works well and we have loaded the foreign MQ jms objects into WLS JNDI
          using a statup class (as the whitepaper available describes) and we look them
          up successfully.
          However, we now have a siutation where we briefly need to switch our application
          to point to a WLS JMS queue on another remote WLS server. Is there an easy way
          to load foreign (maybe remote would be a better word in this case) WLS JMS QCF's
          and destinations into my local WLS JNDI so that I can treat them the same way
          as my MQ objects?
          I can't seem to find any information on how to do this as all information seems
          to point towards the messaging bridge (we can't use this as the bridge changes
          the message JMSMessageID and screws our correlation mechanism up).
          I know we could just look the foreign objects up by using the JNDI environment
          of the remote WLS machine but this would mean changing code and this I can't to
          do (as all our code uses the local default WLS JNDI).
          Any ideas would be gratefully received.
          Cheers,
          Jay.


WLS JMS and MQ JMS handle their JNDI objects a little differently, so I can
          see how this can be confusing. An MQ JMS "ConnectionFactory" or
          "Destination" object is like a little configuration file that tells you
          where the queue manager or queue is, so you can serialize it and look it up
          later and use it to find the queue manager.
          A WLS JMS ConnectionFactory or Destination object is a reference to an
          object on a running server. So, you connect to the server and look them up,
          and then you can use it for messaging. You don't have to store these objects
          in a separate place, like MQ makes you do. But it means that the WLS JNDI
          objects have to be looked up from a running server, and if the server
          restarts, you have to look them up again.
          Doing what you're asking is definitely trickier in 7.0. One thing you could
          do is, again using a servlet or an EJB, connect to the remote JMS cluster
          and look up the objects at the time you want to make the switch. (If the
          remote cluster is down, you'll have to retry from time to time.) If the
          remote cluster is down, you won't be able to look up those objects, but then
          again, if it were down you wouldn't be able to send messages there anyway.
          Using 8.1 would be less complicated, but this method should also work.
          greg
          "Jay Green" <[email protected]> wrote in message
          news:[email protected]...
          >
          > Thanks Greg. When I was searching the BEA website I read about the
          facility in
          > 8.1. Unfortunatley, as you point out, it doesn't help me much with WLS
          7.0.
          >
          > My first thought was to copy my exisiting MQ startup class but I couldn't
          work
          > out how to do this for the remote WLS jms objects as the standard jms
          classes
          > (for QCF etc) don't have methods that allow me to define the foreign WLS
          jms
          > host IP address etc. I checked the WLS 7 API and the jms package didn't
          seem
          > to offer anything to help me do this (as IBM do for MQ). Any ideas?
          >
          > Apologies if I'm being a bit slow here!
          >
          > "Greg Brail" <[email protected]> wrote:
          > >WLS 8.1 includes a feature called "Foreign JMS Providers" that lets you
          > >configure (using the console or config.xml) a link between a JMS JNDI
          > >object
          > >in your WLS servers' tree, and a JNDI object in another provider -- which
          > >could be WLS JMS, or a foreign vendor.
          > >
          > >Using this feature, your application could just look up the local JNDI
          > >objects in the local WLS tree, and then the server in turn performs the
          > >lookup from the actual JNDI provider using the parameters you put in
          > >the
          > >console (or config.xml). So, when you make a change in the console, new
          > >JNDI
          > >lookups will go to the new place.
          > >
          > >Unfortunately, this doesn't help you with 7.0. You could always
          > >programmitically update the local JNDI tree the way you're doing in your
          > >startup class, but instead do it from a servlet or an EJB.
          > >
          > > greg
          > >
          > >"Jay Green" <[email protected]> wrote in message
          > >news:[email protected]...
          > >>
          > >> Hi,
          > >>
          > >> We have a configuration from which we communicate from WLS 7 to a
          foreign
          > >MQ via
          > >> JMS. This works well and we have loaded the foreign MQ jms objects
          > >into
          > >WLS JNDI
          > >> using a statup class (as the whitepaper available describes) and we
          > >look
          > >them
          > >> up successfully.
          > >>
          > >> However, we now have a siutation where we briefly need to switch our
          > >application
          > >> to point to a WLS JMS queue on another remote WLS server. Is there
          > >an easy
          > >way
          > >> to load foreign (maybe remote would be a better word in this case)
          > >WLS JMS
          > >QCF's
          > >> and destinations into my local WLS JNDI so that I can treat them the
          > >same
          > >way
          > >> as my MQ objects?
          > >> I can't seem to find any information on how to do this as all
          information
          > >seems
          > >> to point towards the messaging bridge (we can't use this as the bridge
          > >changes
          > >> the message JMSMessageID and screws our correlation mechanism up).
          > >>
          > >> I know we could just look the foreign objects up by using the JNDI
          > >environment
          > >> of the remote WLS machine but this would mean changing code and this
          > >I
          > >can't to
          > >> do (as all our code uses the local default WLS JNDI).
          > >>
          > >> Any ideas would be gratefully received.
          > >>
          > >> Cheers,
          > >>
          > >> Jay.
          > >
          > >
          >

Problem Connecting to JMS queue with C sharp client

Hi there,
I am trying to connect to a JMS queue using a C# client but i have a problem trying to connect. The problem comes in when i run the C# script a dialog box appears requesting a T3TransportFactory.cs which i do not have on the client. and when i close it i get an exception on
IContext context = ContextFactory.CreateContext(paramMap);
Exception - Failed to connect using URL <t3://10.103.130.18:7001>
StackTrace - at WebLogic.Messaging.Physical.T3TransportFactory.CreateT3Transport(IDictionary`2 paramMap) in c:\weblogic\dev\src1032\modules\weblogic-jms-dotnetclient\jmsimpl\src\WebLogic\Messaging\Physical\T3TransportFactory.cs:line 226
at WebLogic.Messaging.Physical.ContextPhysical.CreateContext(IDictionary`2 paramMap) in c:\weblogic\dev\src1032\modules\weblogic-jms-dotnetclient\jmsimpl\src\WebLogic\Messaging\Physical\ContextPhysical.cs:line 83
at WebLogic.Messaging.Context.CreateContext(IDictionary`2 paramMap) in c:\weblogic\dev\src1032\modules\weblogic-jms-dotnetclient\jmsimpl\src\WebLogic\Messaging\Context.cs:line 56
The stacktrace indicates that it is looking for a T3TransportFactory.cs file in that particular path on the client (This is my speculation) but this directory path does not exist on the client machine with the c# code.
I got a WebLogic.Messaging.dll referenced in my c# project and the ip/port numbers are correct (we know this cause we tried a java client that connected successfully)
Can anyone assist me on this issue?

The issue might be the dll file you are referring to. Did you use the dll from the weblogic installation folder (BEA_HOME/modules/com.bea.weblogic.jms.dotnetclient_1.X.X.X).
Refer - http://docs.oracle.com/cd/E15051_01/wls/docs103/jms_dotnet/install.html#wp1075258
Hope this helps.
Thanks,
Patrick

Foreign jms queue binding problem

Similar Messages

Maybe you are looking for