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
          >
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         

Similar Messages

  • Compare creation of Datasources and JMS Queues : SAP vs (Weblogic/Websphere

    I am used to creating JDBC Datasources and JMS Queues on Weblogic/Websphere thru their Admin applications.
    Can someone compare/contrast that process to that on SAP's netweaver ( either using NWA or Visual Administrator).
    Thanks

    Hi Parag,
    For the process of creating JDBC datasources and JMS resources @ SAP NetWeaver you can refer to the documents here on SDN and help.sap.com, and compare that process for yourself, thus not being influenced by others' biased or unbiased opinions.
    For NetWeaver 04 and 04s these would be:
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/b0/6e62f30cbe9e44977c78dbdc7a6b27/frameset.htm">JDBC Connector Service</a>
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/22/cf4e71c46cdb4da31153be96c5389f/frameset.htm">JMS Connector Service</a>
    For the <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/javaee5">Java EE 5 Edition</a>:
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7bb9751d-0e01-0010-febd-c3adce2c408c">Working with Database Tables, DataSources and JMS Resources</a>
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/806e75a0-0e01-0010-2587-fc518de8ac1a">Administration Guide</a> -> section "Application Resources Management" (pages 89-104)
    Hope that helps!
    Your feedback/findings are very welcome!
    -Vladimir

  • Are Connection Factory and JMS Queue supposed to be in JNDI tree

    I have created Connection Factory and JMS Queue. I am expecting to find both in JNDI tree. Where, in the http://localhost:7001/console/consolejndi.portal, could I find them? I mean, in which branch of the JNDI tree?

    Hi,
    You should find them following exactly the way you define their JNDI Names... Make sure you are looking into the JNDI tree for the right managed server... Pay attention into the targets of your connection factory and queue...
    For example, a JNDI name jms.myConnectionFactory (or jms/myConnectionFactory) targeted to soa_server1 will appear under soa_server1 / jms / myConnectionFactory ...
    Hope this helps...
    Cheers,
    Vlad

  • Single MDB on a clustered JMS queues(2)

    I have 2 JMS servers in a cluster and each server has a JMS queue, which forms the distributed destination. Now I need a MDB to listen on both these queues. Is it possible?
    Thanks
    -Ankur

    Yes - thats the usual purpose of distributed queues, to allow consumers to consume from the distributed queue (wherever its hosted).
    Though distributed destinations are JMS provider specific so do check your providers documentation on using distributed queues. In some providers, like ActiveMQ, distributed queues look and act just like regular queues so they just work from inside a JMS client or MDB.
    James
    http://logicblaze.com/

  • Configuration for JMS Adapter Sensor action and JMS Queue sensor action..!!

    Hi,
    Id like my BPEL process to send an XML message to JMS on Websphere,I was able to do this through a JMS adapter.But I would more like to add sensors into my process which would really do the same thing - send an XML message to JMS Q.
    Now I understand that there are two ways to do this,JMS Queue and JMS Adapter - thorugh bpel sensor action.
    I am able to use JMS Queue and it works fine , but adds its own xml tags to the message,Is there any way I could send only my xml payload as a message to the queue??
    Also could any1 tell me what is the configuration for JMS Adapter sensor action?
    Any suggestions how do I go about it??

    Hey Anirudh,
    Thanx for the response :-)
    All these hold good when I have an AQ adaptor right,But the thing is I want to send a message to a 'JMS' queue with out actually using an adapter configuration wizard and everythng..So I resolved to JMS queue Sensor action..Heres the xml snippet from the sensorAction.xml files which is generated..
    <actions targetNamespace="http://xmlns.oracle.com/Test_JMS_Logging" xmlns="http://xmlns.oracle.com/bpel/sensor" xmlns:tns="http://xmlns.oracle.com/Test_JMS_Logging" xmlns:pc="http://xmlns.oracle.com/bpel/sensor">
    <action name="JMS_LogEntry" publishName="" publishType="JMSQueue" enabled="true" filter="" publishTarget="jms/L_Queue">
    <property name="JMSConnectionFactory">jms/L_QueueCF</property>
    <sensorName>ActivitySensor_JMS</sensorName>
    </action>
    </actions>
    This works grt and adds messages to the queue..But adds its own header info according to the sensor.xsd loacted at the Oracle_home\bpel\system\xmllib\ folder.
    Right now the XML message added to the Queue is:-
    <actionData xmlns="http://xmlns.oracle.com/bpel/sensor">
    <header>
    <sensor sensorName="ActivitySensor_JMS" classname="oracle.tip.pc.services.reports.dca.agents.BpelActivitySensorAgent" kind="activity" target="AddLEntr
    y" xmlns:pc="http://xmlns.oracle.com/bpel/sensor" xmlns:ns2="http://www.ulrhome.com/2008/10/L_Entry" xmlns:tns="http://xmlns.oracle.com/Test_JMS">
    <activityConfig evalTime="completion">
    <variable outputDataType="string" outputNamespace="http://www.w3.org/2001/XMLSchema" target="$WriteL_Produce_Message_InputVariable/L_Entry/ns2:L_Entry/ns2:LCName"/>
    </activityConfig>
    </sensor>
    <instanceId>950016</instanceId>
    <processName>Test_JMS</processName>
    <processRevision>v2009_04_15__40833</processRevision>
    <domain>default</domain>
    <timestamp>2009-04-15T11:21:23.596-04:00</timestamp>
    <midTierInstance>app01.ulrhome.com:9700</midTierInstance>
    </header>
    <payload>
    <activityData>
    <activityType>scope</activityType>
    <evalPoint>completion</evalPoint>
    <durationInSeconds>0.011</durationInSeconds>
    <duration>PT0.011S</duration>
    </activityData>
    <variableData>
    <dataType>12</dataType>
    <data>
    <ns0:LCName xmlns:ns0="LC_Test1http://www.ulrhome.com/2008/10/L_Entry">LC_Test1</ns0:LCName>
    </data>
    <queryName/>
    <target>$WriteL_Produce_Message_InputVariable/L_Entry/ns2:L_Entry/ns2:LCName</target>
    <updaterName>AddL_Entry</updaterName>
    <updaterType>scope</updaterType>
    </variableData>
    </payload>
    </actionData>
    My requirement is that I need to add a sensor to the BPEL process which posts 'Only my payload message to the JMS queue'..
    What I would want the message in the Queue to be is : -
    <data>
    <ns0:LCName xmlns:ns0="LC_Test1http://www.ulrhome.com/2008/10/L_Entry">LC_Test1</ns0:LCName>
    </data>
    Also while creating a Sensor action I get another option as JMS Adaptor,I am not sure of what value to type in this wizard..Heres what I keyed in..M sure this is not right..Cos it dosnt work :-)
    <action name="SensorAction_JMS" publishName="" publishType="JMSAdapter" enabled="true" filter="" publishTarget="jms/LoggingQueue">
    <property name="JMSConnectionName">Log</property>
    </action>
    </actions>
    Could any 1 tel me what values are the right values..And does JMS Adapter mean that I have to create a JMS Apator in the project and give that connection name as a Value..
    I am not finding sufficiant Documentation for 'JMS Adapter' so M clueless and right now any help will be appriciated :-)
    Regards,
    Akshatha.

  • Problem in configuring my driver for JMS Queues

    Hello,
    I'm working in connecting ODI to Sonic ESB.
    I have added all the drivers needed to ODI/Drivers and I continue to have an error.
    After searching in our ESB Doc i finally found why.
    I have to change a property of my Driver.
    I have tryied to change it in the Property Tab of the JMS Queue Data Server.
    with Key= "My Property Name" and Value= "the new Value needed"
    But there's no change, where can I do this ???
    Thanks for your answer,
    Cordially,
    BM

    In fact I have to change the domain in which I will be connected.
    On Sonic ESB by default it is nammed Domain1 and I want to change this name to SonicTestDomain.
    In java I just have to put :
    prop.put("com.sonicsw.jndi.mfcontext.domain", "SonicTestDomain");
    but in my Topology I'm using the Property Tab and in the first column nammed Key I put
    com.sonicsw.jndi.mfcontext.domain and on the other nammed Value I put SonicTestDomain.
    But when I put Test it always responding me :
    javax.naming.NamingException [Root exception is com.sonicsw.mf.comm.InvokeTimeoutException: Domain1.DIRECTORY SERVICE:ID=DIRECTORY SERVICE - listDirectories()]
    --> with Domain1 so the ghange of the property didn't do nothing.
    If someone can help me...

  • MDB not listening to JMS Queue

    We are using OC4J 10.1.2 We are using JMS for queueing, the Queueing application sucessfully displays the JMS message id, but MDB is NOT listening to the JMS for some reason. We have verified the deployment config files etc. Can amy one help

    1 - It doesn't appear that targets were set for any of the administered WL objects. In WL, most administered objects must have a configured target so that WL knows which servers to run them on.
              2 - There's no need to specify a URL or initial-context-factory in the MDB. In your case, you're referencing JNDI objects on the MDB's local cluster (which, in turn, map to foreign references).
              3 - Note that URL and connection-factory have been re-specified in the foreign JMS server properties, and there 's a mix of delimiters ";" and " ". Normally, no JNDI props are needed except, depending on the use case, for security credentials.

  • Oracle BPM and JMS Queue: How to associate data from Map Messages to Process Data Objects?

    Good Day!
    I'm currently working on a project wherein it tries to get data from a JMSqueue Map Message being populated by CEP.
    After CEP pushes some data in the JMSqueue. I have BPM configured with a JMS adapter to look up whether there are any messages to be processed upon.
    Inside BPM, I want to know how can I correlate the data from the Map Message to my Process Data Object.
    For example, If I have a Map Object wherein it has 3 attributes:
    FirstName:String
    LastName:String
    Age:int
    What is the expression I need to use inside Oracle BPM Data Association screen in order to map the data from the Map Messages into my process data objects?
    Thanks!
    Regards,
    Jeff

    Any ideas? Thanks!

  • MDBs in 9.1 continue to consume JMS queues even after being deleted

    <b>We have an MDB application that reads a batch message off of a JMS queue, archives it in a database, parses the batch message into individual messages and writes them onto other JMS queues to be consumed by another application. Everything was running fine in Weblogic 8.1.5. However, due to problems with XA drivers and the MSDTC(predictable SQL server crashes), we decided to upgrade to Weblogic 9.1 to take advantage of the LLR option.</b>
              <b>First, we had an issue where our MDBs were causing the following exception:</b>
              <i>####<May 26, 2006 7:42:12 PM EDT> <Error> <JMX> <ist-clft2> <wltest1> <ExecuteThread: '1' for queue: 'default'> <<WLS Kernel>> <> <> <1148686932991> <BEA-149500> <An exception occurred while registering the MBean null.
              java.lang.IllegalArgumentException: Registered more than one instance with the same objectName : com.bea:ServerRuntime=wltest1,MessageDrivenEJBRuntime=RhapsodyMDB_DMBModule!JMSServer4@DMB_BEAN_QUEUE,Name=RhapsodyMDB_DMBModule!JMSServer4@DMB_BEAN_QUEUE,ApplicationRuntime=DataBrokerEAR1_2,Type=EJBPoolRuntime,EJBComponentRuntime=DataBrokerEJB new:[email protected] existing weblogic.ejb.container.monitoring.EJBPoolRuntimeMBeanImpl@7db003
                   at weblogic.management.jmx.ObjectNameManagerBase.registerObject(ObjectNameManagerBase.java:146)
                   at weblogic.management.mbeanservers.internal.WLSObjectNameManager.lookupObjectName(WLSObjectNameManager.java:133)
                   at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:86)
                   at weblogic.management.mbeanservers.internal.RuntimeMBeanAgent$1.registered(RuntimeMBeanAgent.java:104)
                   at weblogic.management.provider.internal.RegistrationManagerImpl.invokeRegistrationHandlers(RegistrationManagerImpl.java:205)
                   at weblogic.management.provider.internal.RegistrationManagerImpl.register(RegistrationManagerImpl.java:85)
                   at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:320)
                   at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:257)
                   at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:222)
                   at weblogic.ejb.container.monitoring.EJBPoolRuntimeMBeanImpl.<init>(EJBPoolRuntimeMBeanImpl.java:32)
                   at weblogic.ejb.container.monitoring.MessageDrivenEJBRuntimeMBeanImpl.<init>(MessageDrivenEJBRuntimeMBeanImpl.java:49)
                   at weblogic.ejb.container.manager.MessageDrivenManager.initialize(MessageDrivenManager.java:503)
                   at weblogic.ejb.container.manager.MessageDrivenManager.setup(MessageDrivenManager.java:120)
                   at weblogic.ejb.container.manager.MessageDrivenManager.setup(MessageDrivenManager.java:146)
                   at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManager(MessageDrivenBeanInfoImpl.java:1481)
                   at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createDDMDManagers(MessageDrivenBeanInfoImpl.java:1378)
                   at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.onDDMembershipChange(MessageDrivenBeanInfoImpl.java:1285)
                   at weblogic.jms.common.CDS$DD2Listener.listChange(CDS.java:454)
                   at weblogic.jms.common.CDSServer$DDHandlerChangeListener.statusChangeNotification(CDSServer.java:167)
                   at weblogic.jms.dd.DDHandler.callListener(DDHandler.java:318)
                   at weblogic.jms.dd.DDHandler.callListeners(DDHandler.java:344)
                   at weblogic.jms.dd.DDHandler.run(DDHandler.java:282)
                   at weblogic.jms.common.SerialScheduler.run(SerialScheduler.java:37)
                   at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
              >
              ####<May 26, 2006 7:42:13 PM EDT> <Info> <EJB> <ist-clft2> <wltest1> <ExecuteThread: '1' for queue: 'default'> <<WLS Kernel>> <> <> <1148686933069> <BEA-010060> <The Message-Driven EJB: RhapsodyMDB has connected/reconnected to the JMS destination: weblogic.jms.DMB_BEAN_QUEUE.></i>
              <b>
              Generally this happend after there were cluster communication issues. Multi-cast messages were lost and our MDB reconnects to the JMS queues as indicated by the below log:</b>
              <i>####<May 30, 2006 5:19:06 PM EDT> <Info> <EJB> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '54' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1149023946040> <BEA-010060> <The Message-Driven EJB: DataBrokerMDB has connected/reconnected to the JMS destination: weblogic.jms.PHINMS_DMB_QUEUE.>
              ####<May 30, 2006 5:19:10 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023950228> <BEA-000112> <Removing RAPBEA3S jvmid:720875810499147484S:cmts-rap-bea3:[7005,-1,-1,-1,-1,-1,-1]:DMBstg:RAPBEA3S from cluster view due to timeout.>
              ####<May 30, 2006 5:19:11 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023951009> <BEA-000115> <Lost 2 multicast message(s).>
              ####<May 30, 2006 5:19:11 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023951040> <BEA-000111> <Adding RAPBEA3S with ID 720875810499147484S:cmts-rap-bea3:[7005,-1,-1,-1,-1,-1,-1]:DMBstg:RAPBEA3S to cluster: DMBstg_cluster view.></i>
              <b>
              This would cause the queues to eventually have hundreds of consumers and cause the server to fail.
              Basically, it seems as though the MDBs that are supposed to stop continue and attempt to process, while new threads connect to the JMS queues.
              I tried undeploying our application and deleted it from the configuration. However there were consumers still on the respective queues and when I sent messages, I got an error indicating a "Class Not Found exception" due to the fact that the EJB was undeployed and deleted from the configuration, however the MDB component was not and continued to listen for messages. In 8.1.5, as soon as the application was undeployed, there were zero consumers on the JMS queues.
              I have read the posts about a soon to be released fix that would have the MDBs connect only to the queues locally and not go out the the cluster. Would this fix my issue?
              Is there something in the deployment descriptor to configure that will cause it to disconnect and now spawn so many consumers to the JMS queues?
              Why is it that the number of MDB consumers on the JMS queues stayed static in 8.1.5, but they are erratic in 9.1 even after I set our 9.1 server to use the 8.1.5 execute queue policy. Help would be much appreciated.</b>

    I recommend contacting customer support. There's a known problem with MDBs listening to distributed destinations that are local to the same cluster as the MDB, you're problem may be related (the clue is that the stack trace contains jms.dd.DDHandler.callListeners()). The problem is that the MDB connects to all physical queues in a distributed destination rather than just the local queue.
              Tom

  • WiFi Authentication problem

    I have an iMac, and iPad, a Blackberry (forgive me) and Airport for my WiFi all of my pieces are working fine with my WiFi.  I had guests over the other day and we could not allow my guests iPads or iPhone to sign onto my network.  I bought my dad a generic tablet to use for solving cross words, etc., and I cannot sign into my own network.  No opportunity exists to put in a password because it just reads "Authentication Problem".
    No opportunity exists, therefore, to enter the password.  Signal strength is excellent, Securty is WPA2 PSK, I touch connect and it says Saved Secured with WPA2 and then goes back to "Authentication Problem."
    I've unplugged (and plugged back in) both the Airport / router and Internet Service provider's modem. I've rebooted my iMac and the new generic pad 3 times each. 
    I had 2 networks one for me and one for guests, can't get into either, identical problem. I can see all of the neighbour's networks and they're all locked and say secured with (various WPA/WPA2, etc., just mine says Authentication Problem.  I plugged the tablet into my iMac and it's functioning well.
    I now deleted the guest network and can't open a new network. 
    I've triple checked my passwords, hand written and in the Key Chain.
    I've checked my Apple ID (I'm able to get into this forum).
    Both my iPad (purchased May 2013) and BlackBerry (received free July 2013) signed in without any problems.
    I cannot see why I can't get into my network ~ any ideas?

    Hello,
    Hmmm..."problem"...pretty hard to understand. Can you provide more details? What exactly do you try? What exactly happens at each step of what you try? What is the exact and complete content of any error messages presented?
    Please remember that we can't see you nor your device. We have only your words to help us understand your situation, and such understanding is the natural prerequisite to providing you with any useful guidance.
    Thanks and let us know.
    Occam's Razor nearly always applies when troubleshooting technology issues!
    If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
    Join our BBM Channels
    BSCF General Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • Wifi authentication problem yoga 2 1050F

    Hi,I am a new member and have just upgraded to android 5. Seems a big mistake as cannot connect to internet (no trouble with android 4) Says authentication problem. Have tried cancelling and re-entering password, turning router on and off and factory reset. Nothing. If Lenovo come up with a repair how will I be able to get it into the tablet when I have no internet connection.At the moment I have a tablet that is about as usefull as a roof tile. HELP

    You have been looking everywhere, except this forum. This issue was already addressed in this thread: https://forums.lenovo.com/t5/Android-Yoga-Series-Tablets/Wifi-Won-t-Connect-quot-Authentification-Problem-quot-Yoga/td-p/2105009 Are you using a WEP key encryption? If yes, try switching to WPA/WPA2. Though i have been able to connect without problem with these settings: Have you performed a factory reset after switching from 4.4.2 to 5.0? You could try that, sometimes it fixes so e issues.

  • Using socket and JMS protocol in the same logic for OSB

    Hi frnds,
    In my organization...the only communication protocol used is "socket" protocol. However, I want to use JMS protocol to process incoming messages. Can somebody help me figuring out how to go about it.
    Using some nice OSB blogs, I am able to create the JMS connection factory and JMS queues in weblogic. And that works fine when I select the communication protocol as JMS while creating the BS and PS.
    What should be my message flow when the communication protocol used is "socket" for both BS and PS.
    salil

    Hi,
    Make the BS as JMS and the PS as socket, in the PS's flow do a route for the BS... Then if an external call is made to the PS via socket, it will send a messages to a JMS queue...
    Hope this helps...
    Cheers,
    Vlad

  • MapMessage and JMS Event Generator

    Hello
    I need to set up a WLI JMS event generator that will consume a JMS MapMessage. It appears that the only message types supported by a JMS event generator are xml, rawData, string and none.
    I've already tried each of these and for each I get a message saying "Cannot publish non-TextMessage to channel of type String" or "Cannot publish non-ByteMessage to channel of type ...".
    I have sent MapMessage types using WLI's JMS controls. Is there a way to consume a MapMessage type via an event generator?
    Thanks
    Tom

    Bishu thanks, Channel type is defined as String, Message on JMS queue are of type String. Also can you elaborate on "JMS event generator check the type of message you want to process." that you mentioned. I have not found this option while configuring JMS EG. (We are using ver. 8.1 sp 5)
    This was working fine in local env. But when we configured message bridge between MQ queue and JMS queue, we startted getting error messages. I am trying to find out how does MQ stores messages. Doing integrations with MQ has been real headache for us.

  • Getting events into WLI from  External JMS Queue

    Hi,
    I can't figure out how to get an event into WLI from an external JMS queue.
    I can send an XML message to an external queue but can't figure out how to get
    a message from an external queue into WLI. I have created the MDB using the generator
    program provided and have deployed. How does this MDB now send these messages
    into WLI?
    I have also posted this same question in weblogic.interest.jms newsgroup.
    -- Bill

    Hi Bill.
    Actually this is really simple. Here are the steps:
    Connect your MDB to the external JMS queue by modifying the weblogic-ejb-jar.xml
    The MDB onMessage(Message m) method will receive a message from the external JMS
    queue. It will then use JNDI to bind to the EventQueue of WLI and submit the event
    as XML into that queue.
    Obvously the onMessage() operation must be transacted using container managed
    transactions so the scope will spawn both de-queuing from the external JMS queue
    and enqueing into the WLI Evnet Queue.
    "Bill Ozeroff" <[email protected]> wrote:
    >
    Hi,
    I can't figure out how to get an event into WLI from an external JMS
    queue.
    I can send an XML message to an external queue but can't figure out how
    to get
    a message from an external queue into WLI. I have created the MDB using
    the generator
    program provided and have deployed. How does this MDB now send these
    messages
    into WLI?
    I have also posted this same question in weblogic.interest.jms newsgroup.
    -- Bill

  • IS XI Support BEA Weblogic JMS Queue

    Hi
    I have a scenario where i have to send and recive message from the Weblogic JMS Queue ..
    Is XI support Weblogic JMS Queue ..if it is which tranport protocol i have to use to connect to Weblogic queue
    SV

    Hi
    Thanks Ravi..
    U mean to say i have to use the Transport Protocol
    Access JMS Provider with JNDI
    I have few more questions like ..
    what needs to filled in Connection parameters:
    JNDI Look up name of Queue Connection Factory:
    JNDI Look up name of JMS Queue:
    Name of JNDI Initial Context Factory:
    JNDI Sever Address:
    JNDI Logon User:
    JNDI Logon Password:
    When i selected the Protocol some default Values came in do i have have to change any thing
    JNDI Look up name:
    JNDI Look up name of JMS Queue:
    Name of JNDI Initial Context:
    as u mentioned in Server address i will put : t3://server:XXX
    and i have given the user id and Password ..
    the user id and password is same for both JNDI logon and JMS Queue User..
    SV

Maybe you are looking for

  • How to make space on Hard Drive for videos?

    I recently tried to download the first season on "Lost" on my 60GB video iPod, but I ran into problems when trying to download these b/c of the space needed on my hard drive. Besides the obvious answer, "erase other files on your computer," is there

  • Optional Plugins for CS5

    Has anyone successfully installed the optional plugins in CS5 running in 64bit under Snow Leopard 10.6.3?

  • Validating email address on blackberry curve

    I need help to validate my hotmail address on my blackberry curve.  I cannot access the username to the blackberry device in email setup to even do this.  I need help

  • Attach multiple stylesheets to one tag (body tag)

    Dear People, Hi. This is a first for me since Adobe bought Macromedia, so please be patient................ Anyway. I want to attach multiple stylesheets. What I need to do is to attach the stylesheet to the body tag to make a repeating backgorund he

  • Imovie9 won't load in mp4

    My macbook pro has all of the software updates to-date and suddenly none of my MP4 videos will import to imovie.  Thoughts?