Need JMS topics tutorial

Hi
I need to create a WebLogic JMS topic and read messages from it. Need a step-by-step tutorial, searched the web, no help. If any one knows a good tutorial on this, pl let me know. Even a tutorial on JMS Queues would help.
thanks
a s

Here are the steps for you. If you need anymore help let me know.
Configure a JMS server.
2.1 AdminServer and dizzy1 are running.
2.2 Navigate to dizzyworld Services Messaging JMS Servers. Lock the
console.
2.3 Click New under the JMS Servers table and specify the following properties:
Name: dizzyworldJMSServer
Persistent Store: (none)
2.4 Click Next and target the JMS server to dizzy1 Managed Server. Click Finish.
2.5 Activate your changes.
Configure a JMS module and add a queue and a topic to the JMS module.
3.1 Navigate to dizzyworld Services Messaging JMS Modules. Lock the
console, if necessary.
3.2 Click New under the JMS Modules table and specify the following properties:
Name: dizzyworldModule
Descriptor File Name: dizzyworldModule
3.3 Click Next and target the module to the dizzy1 Managed Server. Click Next and
select the following:
Would you like to add resources to this JMS system module?
3.4 Click Finish.
3.5 In the Settings for dizzyworldModule page, click the Subdeployments tab. Under the
Subdeployments table, click New to create a subdeployment with the following
specifications:
Subdeployment Name: dizzy1SubDeployment
Click Next.
3.6 In the Targets page, select the dizzyworldJMSServer as the target under the
JMS Servers table. Click Finish.
3.7 Click the Configuration tab.
3.8 In the Settings for dizzyworldModule page under the Summary of Resources table,
click New to configure a new JMS queue for the JMS module.
3.9 In the Create a New JMS System Module Resource page under the heading of
Choose the type of resource you want to create, select Queue.
3.10 Click Next.
3.11 In the JMS Destination Properties, specify the following parameters:
Name: dizzyworldQueue
JNDI Name: dizzyworldQueue
Template: None
3.12 Click Next.
3.13 Click Advanced Targeting. Select dizzy1SubDeployment from the
subdeployments list. Click Finish.
3.14 In the Settings for dizzyworldModule page under the Summary of Resources table,
click New to configure a new JMS topic for the JMS module.
Contents Page 70 of 143
mhtml:file://C:\Documents and Settings\RTiwari\Desktop\Weblogic_9.2_LAB.mht 11/3/2008
3.15 In the Create a New JMS System Module Resource page under the heading of
Choose the type of resource you want to create, select Topic.
3.16 Click Next.
3.17 In the JMS Destination Properties, specify the following parameters:
Name: dizzyworldTopic
JNDI Name: dizzyworldTopic
Template: None
3.18 Click Next.
3.19 Click Advanced Targeting. Select dizzy1SubDeployment from the
subdeployments list. Click Finish.
3.20 Activate the changes.
You should be able to see JNDI entries on the dizzy1 managed server called
dizzyworldQueue and dizzyworldTopic.
Thanks
Togotutor
<b><a class="jive-link-external" href="http://www.togotutor.com">http://www.togotutor.com</a> (Learn Programming and Administration for Free)</b>

Similar Messages

  • Tom !!! Help needed in JMS Topic Lookup Cluster DOMAIN

    Hi Tom,
              We have a clustered domain with 2 managed servers and our application is an Applet-Servlet based application.We user JMS Topic for some of online blotters.
              And on looking up we get the following error,
              weblogic.jms.common.JMSException: <055053> <java.rmi.RemoteException: CORBA INTERNAL 1398079712 Maybe; nested exception is: org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 224 completed: Maybe >      
              weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:272)at weblogic.jms.client.JMSConnectionFactory.createConnectionInternal(JMSConnectionFactory.java:299)at weblogic.jms.client.JMSConnectionFactory.createTopicConnection(JMSConnectionFactory.java:198)at
              Pls note while looking up for the Initial context since it is a cluster environment, we look up using comma separated Ipaddresses.
              Pls note, we use JRE 1.4.2_13 for the applet to launch,.
              Earlier also for JMS failover i sought your help and your suggestions have really invaluable.
              Request you to provide me some more suggestions on this issue as well.
              Regards
              Suresh

    The exception is thrown by the JVM's built in Sun IIOP (CORBA) libraries. I don't know the cause, but a google search for "SUN minor code: 224 completed: Maybe" yields a single hit that might help. See the July 23/24 posts for "Re: iiop: error with bidirectional connections" in the weblogic rmi-iiop newsgroup:
              http://forums.bea.com/thread.jspa?threadID=300001651
              Tom

  • JMS Topic Sample Needed

    Hi,
    Can someone point me to a doc which explains how to develope a sample JMS application using standalone oc4j.
    And also what are the properties that are used to create the InitialContext for the oc4j JMS Directory service.
    i. e
    Properties env = new Properties( );
    env.put(Context.SECURITY_PRINCIPAL, "");
    env.put(Context.SECURITY_CREDENTIALS, "");
    env.put(Context.INITIAL_CONTEXT_FACTORY,"");
    env.put(Context.PROVIDER_URL,"");
    InitialContext jndi = new InitialContext(env);
    It will be of great help if u can share a sample for the above.
    Thx,
    Siddhardha.

    Ashique wrote:
              > I belive JMS Topic supports multiple publishers, subscribers
              > for the same topic right?
              Yes.
              > I am sure about the multiple subsicriber part because
              > I have done it before (with one publisher). However, I am changing my
              > design to have multiple publishers now as well. Is this possible?
              >
              Yes.
              >
              > Thanks
              

  • JMS Topic - Deliver to only one Durable Subscriber

    Hi,
    Is it possible to put a message onto a topic but only have it delivered to a single durable subscriber?
    I realise this breaks the rules of what a topic is but this is for a scenario where a single subscriber has errored when processing the original message from the topic. I am putting a user interaction process to recover it and if the user selects ‘resubmit’ I want to put the message back on the topic but only deliver it to the one subscriber that failed to process the message.
    My ways to achieve this (in order of preference) would be.
    1.     JMS Adapter
    2.     Writing Java to use JMS API
    If neither of these are possible than:
    3.     Create a System Resubmit queue and have every composite look for message on the resubmit queue (with their client ID) as well as the normal topic they use
    Of course I would like to avoid 3 as it introduces a complication into every process we create that takes messages from a JMS Topic.
    Thanks for your help.
    Robert

    I could suggest a (dirty) trick:
    all subscribers subscribe to the topic using a filter (message selector, http://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html#bncer)
    SUBSCRIBER1 uses:
    destination = ALL OR SUBSCRIBER1
    SUBSCRIBER2 uses:
    destination = ALL OR SUBSCRIBER2
    etc
    The first message has the property destination set to ALL, so all subscribers will process it.
    The resubmitted message will have destination = SUBSCRIBER<N>, where N is the failed subscriber

  • Invoke Error while inserting consumed JMS Topic msg in table thru DBadapter

    Hi All,
    To brief abt my requirement, I am integrating Peoplesoft HRMS module with Oracle SOA i.e.,
    +
    1. PS HRMS module will publish a JMS msg into a JMS Topic
    2. I will consume the same msg using JMS adapter consume operation in my SOA project
    3. The Payload(msg) is coming into RECEIVE activity and thru ASSIGN activity invoking the DB adapter to insert the msg into a table.
    4. INVOKE activity is throwing the below error(along with the error, able to see the payload in INVOKE activity )
    <part name="summary"> +
    <summary>*Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert' failed due to: Mapping Not Found Exception. The mapping [EMPLID] for descriptor [class insert.Employee] could not be found. The input xml record had an element [Employee/EMPLID]. Most likely the wrong xml input variable (not matching the expected xsd) was passed to this invoke. Make sure that the input xml is valid relative to the xsd and that the mapping exists in the Mappings.xml. If an old version of the descriptor without this mapping has been loaded by the database adapter, you may need to bounce the app server. If the same descriptor is described in two separate Mappings.xml files, make sure both versions include this attribute/mapping. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. *</summary>
    </part>
    Please, provide some suggestions.
    Regards,
    Satya

    Hi Satya,
    Try replacing the Assign activity with a Transform acitivity.
    Also please check the schema that comes of the DB adapter is having the similar sort of definition that you are getting in your input.
    What I mean is to check for length of fields, type of the fields etc.
    Thanks,
    Deepak.
    Edited by: DeepakDabbiru on Oct 23, 2012 3:29 AM

  • Jms adapter not polling messages from jms topic

    Hi
    We have a jms adapter configured in BPEL process which need to poll messages from JMS topic.Unfortunately its not polling message from JMS Topic if we add Message Selector and Durable Subscriber properties in jca file.Please find jca file content below
    <adapter-config name="SyncCustomerPartyListCDHJMSConsumer" adapter="JMS Adapter" wsdlLocation="oramds:/apps/AIAMetaData/AIAComponents/ApplicationConnectorServiceLibrary/CDH/V1/ProviderABCS/SyncCustomerPartyListCDHProvABCSImpl.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
      <connection-factory location="eis/jms/aia/syncCustomerParty_cf" UIJmsProvider="WLSJMS" UIConnectionName="Dev"/>
      <endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
        <activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
          <!--property name="DurableSubscriber" value="XYZ"/-->
          <property name="PayloadType" value="TextMessage"/>
          <!--property name="MessageSelector" value="Target in ('XYZ')"/-->
          <property name="UseMessageListener" value="true"/>
          <property name="DestinationName" value="jms/aia/Topic.jms.COMMON.CustomerParty.PUBLISH"/>
        </activation-spec>
      </endpoint-activation>
    </adapter-config>
    If we remove Durable subscriber and message selector properties,its able to poll messages.
    Any pointer will help
    thanks in advance
    Baji

    After changing below property in jca file.JMS adapter is able to poll messages from JMS Topic.
    <property name="UseMessageListener" value="false"/>
    But if i un comment below line and deploy my code again, it stop pulling the messages from topic.
    <property name="DurableSubscriber" value="XYZ"/>
    If i bounce the server after above change and deployment ,it will start polling the message.I am not sure why i need to restart my server after adding above property.
    Thanks
    Baji

  • Error in Applet reading a JMS topic

    I have an applet trying to read a JMS topic. It connects fine, but as
              soon as a message is written into the topic (that the applet is
              subscribed to), I get the following error on the server:
              <Apr 26, 2002 2:46:39 PM PDT> <Error> <RJVM> <Unsolicited error
              response for: '-1'>
              The applet shows the following stacktrace:
              <Apr 26, 2002 2:40:26 PM PDT> <Warning> <Dispatcher> <Error thrown by
              rmi server: 'weblogic.rmi.internal.BasicServerRef@101 - jvmid:
              '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,7001,7002,7002,7001,7002,-1]:mydomain:myserver',
              oid: '257', implementation:
              'weblogic.jms.dispatcher.DispatcherImpl@2c3327''
              weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
              generate the Skeleton on the server for:
              weblogic.jms.dispatcher.DispatcherImpl_WLSkel ]
                   at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDescriptor.java:296)
                   at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescriptor.java:309)
                   at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
                   at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
                   at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              <Apr 26, 2002 2:40:39 PM PDT> <Warning> <Dispatcher> <Error thrown by
              rmi server: 'weblogic.rmi.internal.BasicServerRef@2 - jvmid:
              '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,7001,7002,7002,7001,7002,-1]:mydomain:myserver',
              oid: '2', implementation:
              'weblogic.rmi.internal.dgc.DGCServerImpl@4d7745''
              weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
              generate the Skeleton on the server for:
              weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel ]
                   at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDescriptor.java:296)
                   at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescriptor.java:309)
                   at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
                   at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
                   at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                   at weblogic.kernel.Kernel.execute(Kernel.java:235)
                   at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:169)
                   at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:195)
                   at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:642)
                   at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
                   at weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.java:42)
                   at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
                   at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
                   at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:319)
                   at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
                   at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              <Apr 26, 2002 2:41:39 PM PDT> <Warning> <Dispatcher> <Error thrown by
              rmi server: 'weblogic.rmi.internal.BasicServerRef@2 - jvmid:
              '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,7001,7002,7002,7001,7002,-1]:mydomain:myserver',
              oid: '2', implementation:
              'weblogic.rmi.internal.dgc.DGCServerImpl@4d7745''
              weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
              generate the Skeleton on the server for:
              weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel ]
                   at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDescriptor.java:296)
                   at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescriptor.java:309)
                   at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
                   at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
                   at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                   at weblogic.kernel.Kernel.execute(Kernel.java:235)
                   at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:169)
                   at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:195)
                   at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:642)
                   at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
                   at weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.java:42)
                   at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
                   at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
                   at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:319)
                   at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
                   at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              Thanks in advance for suggestions/help.
              Raj
              

    Is it with 7.0 GA or beta?
              Do you know whether the classpath servlet is open or not?
              Can you run this url from a browser and update this issue please.
              http://host:port/bea_wls_internal/classes/weblogic/jms/dispatcher/Dispatcher
              Impl_WLSkel.class
              You should get a downloaded file to be saved. Otherwise your server need to
              open the classpathservlet.
              use -Dweblogic.servlet.ClasspathServlet.disableStrictCheck=true to open the
              classpath servlet.
              Attach the applet code, so that it will help us to nail down the issue.
              Cheers,
              ..maruthi
              "theist" <[email protected]> wrote in message
              news:[email protected]...
              > I have an applet trying to read a JMS topic. It connects fine, but as
              > soon as a message is written into the topic (that the applet is
              > subscribed to), I get the following error on the server:
              >
              > <Apr 26, 2002 2:46:39 PM PDT> <Error> <RJVM> <Unsolicited error
              > response for: '-1'>
              >
              >
              > The applet shows the following stacktrace:
              >
              > <Apr 26, 2002 2:40:26 PM PDT> <Warning> <Dispatcher> <Error thrown by
              > rmi server: 'weblogic.rmi.internal.BasicServerRef@101 - jvmid:
              >
              '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,
              7001,7002,7002,7001,7002,-1]:mydomain:myserver',
              > oid: '257', implementation:
              > 'weblogic.jms.dispatcher.DispatcherImpl@2c3327''
              > weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
              > generate the Skeleton on the server for:
              > weblogic.jms.dispatcher.DispatcherImpl_WLSkel ]
              > at
              weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDe
              scriptor.java:296)
              > at
              weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescrip
              tor.java:309)
              > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
              > at
              weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
              > at
              weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
              2)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > >
              > <Apr 26, 2002 2:40:39 PM PDT> <Warning> <Dispatcher> <Error thrown by
              > rmi server: 'weblogic.rmi.internal.BasicServerRef@2 - jvmid:
              >
              '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,
              7001,7002,7002,7001,7002,-1]:mydomain:myserver',
              > oid: '2', implementation:
              > 'weblogic.rmi.internal.dgc.DGCServerImpl@4d7745''
              > weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
              > generate the Skeleton on the server for:
              > weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel ]
              > at
              weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDe
              scriptor.java:296)
              > at
              weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescrip
              tor.java:309)
              > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
              > at
              weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
              > at
              weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
              2)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.Kernel.execute(Kernel.java:235)
              > at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:169)
              > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:195)
              > at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:642)
              > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
              > at
              weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.jav
              a:42)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at
              weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:319)
              > at
              weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
              > at
              weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > >
              > <Apr 26, 2002 2:41:39 PM PDT> <Warning> <Dispatcher> <Error thrown by
              > rmi server: 'weblogic.rmi.internal.BasicServerRef@2 - jvmid:
              >
              '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,
              7001,7002,7002,7001,7002,-1]:mydomain:myserver',
              > oid: '2', implementation:
              > 'weblogic.rmi.internal.dgc.DGCServerImpl@4d7745''
              > weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
              > generate the Skeleton on the server for:
              > weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel ]
              > at
              weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDe
              scriptor.java:296)
              > at
              weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescrip
              tor.java:309)
              > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
              > at
              weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
              > at
              weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
              2)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.Kernel.execute(Kernel.java:235)
              > at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:169)
              > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:195)
              > at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:642)
              > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
              > at
              weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.jav
              a:42)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at
              weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:319)
              > at
              weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
              > at
              weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > >
              >
              >
              > Thanks in advance for suggestions/help.
              > Raj
              

  • Flex with JMS Topic/Queue for Asynchronous messaging

    I have been working on Flex and JMS integration using Data
    Services for Asynchronous messaging. I am able to do this
    successfuly. Now I am in need to do the same without using the Data
    Services piece.
    For doing this I have done the following ......
    I have created a JMS Webservice in the Oracle JDeveloper 10G
    along with Webservice Client.I am able to Listen to JMS Topic/Queue
    ( this has been created in the Oracle AS ) using this Webservice
    and receive the messages from this JMS Topic/Queue
    Asynchronously.....
    But If I need to use the Flex Client , I am not able to
    Communicate with this Webservice to listen to the JMS Topic/Queue.
    Did any one in this forum tried to communicate with JMS
    Topic/Queue without using Flex Data Service.If so please share your
    inputs.

    Here is my confusion (I'm using J2EESDK1.3).
    On a local server I did the following
    j2eeadmin -addJmsFactory jms/RemoteTCF topic -props url=corbaname:iiop:mars#mars
    In the app client running on the local server I had the code
    ic = new InitialContext();
    // JNDI lookup. The resource factory ref points to the
    // Remote Connection Factory I registered
    tcf = (TopicConnectionFactory)ic.lookup("java:comp/env/jms/TopicConnectionFactory");
    // The env ref points to jms/Topic of the local server
    pTopic = (Topic)ic.lookup("java:comp/env/jms/PTopic");
    So I'm assuming that I'm using a connection factory that connect to mars and a Topic on the local box.
    On remote server mars, I deployed a MDB which use
    jms/TopicConnectionFactory and jms/Topic. But I'm thinking this jms/Topic and the one I used on the local box are not the same one. Right? Then how could the app client and the MDB share messages?
    Some of my explanation I don't if it makes sense or not.
    ConnectionFactory is a way to tell what kind of connection it could generate (Queue, Topic, Durable etc) and Where the connection would go to (local or remote).'
    As for as destination, I'm not sure. How could two server share one Topic?

  • Can JMS topics and queues be clustered in a WLS 7.0 Cluster?

    We are installing a weblogic 7.0 cluster with 1 admin server and 2 managed
              node servers. Two nodes have been clustered. We are at the point where we
              need to configure JMS. Has any one implemented JMS in WLS 7 clustered
              environment? What are the things to watch out when clustering JMS? Can JMS
              topics and queues be clustered?
              TIA for any helpful hints and comments.
              Regards
              

    "Karim Ali" <[email protected]> wrote:
              >> Has any one implemented JMS in WLS 7 clustered
              >> environment?
              I'm currently working on a project with WLS 7 here at work, involving
              the implementation of BEA's JMS Cluster. So far, I really haven't had
              many hiccups.
              "Karim Ali" <[email protected]> wrote:
              >> What are the things to watch out when clustering JMS?
              At least in WLS 7, the biggest thing that stands out is the lack of
              automatic failover. Also, Message Paging -- make sure you configure
              paging high/low thresholds. Or, if you don't wish for it to occur but
              can't stop the server (very common these days with SLAs), set that
              byte/message high threshold to a very large number (correct me if I'm
              wrong, but I believe BEA recommends 2^63 -1).
              "Karim Ali" <[email protected]> wrote:
              >> Can JMS topics and queues be clustered?
              Well, since Topics and Queues are extensions of the
              javax.jms.Destination interface, the answer is: Yes!
              (SIDE NOTE: most people usually refer to them as a [JMS] "destination"
              -- it avoids a lot of conceptual baggage and plus, less typing!)
              You'll probably want to see this section of BEA's e-docs:
              http://edocs.bea.com/wls/docs70/adminguide/jms.html#config_distributed_destinations
              later,
              Brian J. Mitchell
              BEA Systems Administrator
              TRX
              Atlanta, GA
              email: [email protected]
              office: 404-327-7238
              mobile: 678-283-6530
              

  • Newbie question about JMS topic and OSB

    So here is what I want to achieve:
    I want to "front" a JMS topic on WLS using OSB 10g. I want the users (producers and subscribers) to be access the topic via proxy services. The way I picture this is that a producer will invoke a proxy to publish a message. The subscriber will (asynchronously) invoke another proxy to pickup the message.
    Is this possible and how do I go about doing this?
    thanks
    Edited by: user10341230 on Apr 28, 2010 8:49 AM

    Hi there,
    user10341230 wrote:
    I want to "front" a JMS topic on WLS using OSB 10g. I want the users (producers and subscribers) to be access the topic via proxy services. > it's not really clear what you want to achieve here.
    you say
    user10341230 wrote:
    The way I picture this is that a producer will invoke a proxy to publish a message.you need a proxy with whatever inbound protocol you like (http, file, mail...), which through a jms business service push the message to the Topic.
    you say
    user10341230 wrote:
    The subscriber will (asynchronously) invoke another proxy to pickup the messagethe subscriber can be either asyncrhnous, in which case you need a proxy service with inbound protocol jms. or as you probably need a synchronous one
    in which case you need another proxy with whatever inbound protocol you like whch once called in its pipeline calls some pojo class to read from this topic synchrnously (you need a durable subsciber).
    Regards,
    Tony
    ps: have a look http://download-llnw.oracle.com/docs/cd/E11035_01/wls100/jms/design_best_practices.html#wp1058694

  • JMS Topic Load Balancing on Cluster

    Folks
    How do we load balance JMS Topic on a cluster.
    We have a 2 App Server configuration to a single cluster.
    If we have Topic A on both OC4J instances 1,2 - and we send a message to 1 - only clients connected to 1 get the message.
    What do we need to do to setup JMS clustering so that the messages sent to Topic A can be handled by both OC4J instances.

    Hi Ravi,
    Check this forum:
    /thread/24959 [original link is broken]
    Load Balancing for J2EE Web Applications
    http://help.sap.com/saphelp_nw04/helpdata/en/ce/4522d557b26942b202e05ff9ee1f3a/frameset.htm
    SAP Web Dispatcher - Load balancing EP6.0 SP2
    /thread/19304 [original link is broken]
    Reward points if this helps
    Regards
    Pragathi.

  • Receive asynchronous message from JMS  topic over web service

    Hi,
    I have a JMS topic and I want to expose it as a web service so that clients can
    make durable subcription to the topic and receive messages asynchronously. What
    is the best way of doing this ? Is there a portable (to other containers) way
    of do this ? If not, is there a web logic specific way of doing this ?
    Thanks,
    Siva

    So you expect clients to be receiving SOAP messages over HTTP? In this
    case, the clients are really servers that are capable of servicing SOAP
    requests, correct? And how about the senders: are they also using
    SOAP/HTTP to send messages that are delivered to the receivers?
    It should be possible to write this yourself using JMS not as the
    transport, but as a mechanism for distributing the message to a set of
    clients. You'll need to implement a Web Service for publishing to a
    topic, an operation for registering an end point to recieve messages,
    and an MDB (or other form of JMS subscriber) executing on the server to
    relay the message to the end point.
    Siva wrote:
    Hi,
    I have a JMS topic and I want to expose it as a web service so that clients can
    make durable subcription to the topic and receive messages asynchronously. What
    is the best way of doing this ? Is there a portable (to other containers) way
    of do this ? If not, is there a web logic specific way of doing this ?
    Thanks,
    Siva

  • How to subscribe to a JMS topic with a selector

    I'd like to receive messages on a JMS topic satifying a selector.
    I'm trying examples\webservices\message. The ConsumerClient
    receives messages on "examples.soap.msgService.MsgSend". But if
    I want to sepcify a selector, how do I do it? Thanks!
    Kevin

    I think Mediator by default participates in a same transaction and if the webservice calls fails, it would rollback the message to queue.
    I would suggest you to setup fault policy in mediator for the webservice invoke and catch the fault and do the retries or human intervention depends on your need.
    Also, my personal suggestion is to use BPEL in place of ESB in this scenario as you have more persistence and fault handling capabilities in BPEL over ESB.

  • Concurrent nodes reading from JMS topic (cluster environment)

    Hi.
    Need some help on this:
    Concurrent nodes reading from JMS topic (cluster environment)
    Thanks
    Denis

    After some thinking, I noted the following:
    1 - It's correct that only one node subscribes to a topic at a time. Otherwise, the same message would be processed by the nodes many times.
    2 - In order to solve the load balancing problem, I think that the Topic should be changed by a Queue. This way, each BPEL process from the node would poll for a message, and as soon as the message arrives, only one BPEL node gets the message and take if off the Queue.
    The legacy JMS provider I mentioned in the post above is actually the Retek Integration Bus (RIB). I'm integrating Retek apps with E-Business Suite.
    I'll try to configure the RIB to provide both a Topic (for the existing application consumers) and a Queue (an exclusive channel for BPEL)
    Do you guys have already tried to do an integration like this??
    Thanks
    Denis

  • Messages posted to JMS Topic from OSB disappear even when not subscribed

    Hi,
    We are using an OSB service to publish xml messages to a weblogic JMS Topic. Message is persistent. There are no consumers for the Topic. There is no expiration limit set.
    We are able to see the message from OSB reach the Topic. It stays in the Topic for a few seconds and then disappears.
    The State of the message shows up as "send transaction" on the Topic in the weblogic console. And it shows up as Message Pending instead of Message Current.
    Is there a way to ensure that the message stays in the Topic till it is consumed by a subscriber?
    Thanks,
    Senthil

    Hi Senthil,
    The topic persists messages only for subscribers, if there is no subscribers, then it is not necessary to persist the message.
    This is the same case for you as well, as there are no subscribers the message gets deleted.
    So first you need to have atleast one subscriber first (A dummy proxy that is reading from the topic) and then post to the topic (through your OSB service or hermes jms tool, etc .. ) . Then if you try to go and check the topic you will be able to see the message.
    Hope this information helps.
    Thanks,
    Patrick
    Edited by: Patrick Taylor on May 13, 2011 2:40 PM

Maybe you are looking for

  • What is the best program to create a price list in?

    What is the best program to design a price list please.

  • Wow crashes randomly.

    Hey everyone, I'm trying to figure this one out. For no reason at all, WoW will just randomly crash. I'm running Arch 64bit on a T61p with a Nvidia graphics card. I'm using WINE to run WoW. I was able to snag a strace of when it crashed. I'm hoping s

  • Enterprise Portal Install

    Can someone send me the link to download EP 6.0 software and install guide. I have checked under My application component >EP but don't find any doc or software to download from there . when i went to https://websmp106.sap-ag.de/ep60  it forward me t

  • Os X 10.6 Snow Leopard question

    So i just bought the 2.53ghz macbook pro and i am curious when they release the 10.6 Snow leopard will this be a free upgrade or do you have to pay for this upgrade? Do they Tend to charge for their larger software updates?

  • SAP TM / Business object creation

    Hi, this my first posting, so please excuse that I am still searching for the right place to put my message ... I hope this is the right group. I have some questions concerning SAP Transportation management; I haven't seen a special group for that, s