WLI 10g3 JMS Event Generator for Foreign Queues

Hi,
Our requirement is to listen to messages on a remote destination on another weblogic instance (8.1).
One option we are trying is create a foreign JMS Module on local server (10g3) to connect to the remote destination
and use JMS Event Generator to poll for messages on the local Foreign JMS Module and fetch the message and publish this
message into a message channel.
This works fine when I have a local JMS Queue and JMS Event Generator tries to listen to it.
But while trying to use JMS Event Generator against foreign JMS module we are getting stuck with error failed to establish JMS Session :
<Jul 8, 2009 12:26:29 PM IST> <Warning> <EJB> <BEA-010096> <The Message-Driven EJB: foreignGenEventName is unable to connect to the JMS destination or bind to JCA resource adapter: test.mydestination. Connection failed after 64 attempts. The MDB will attempt to reconnect/rebind every 10 seconds. This log message will repeat every 600 seconds until the condition clears.>
<Jul 8, 2009 12:26:29 PM IST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: foreignGenEventName is unable to connect to the JMS destination: test.mydestination. The Error was:
weblogic.jms.common.JMSException: Error creating session
Nested exception: weblogic.jms.common.JMSException: Error creating session
Nested exception: weblogic.jms.common.JMSException: Error creating session
Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server AdminServer
Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:AdminServer'. Resolved 'weblogic.messaging.dispatcher'; remaining name 'S:AdminServer'>
Any pointers to a possible issue will eb really helpful.
Thanks,
CA

Varun,
Thanks for your inputs. Regarding the possibility of misconfiguring the ForeignJMSServer , we are able to view the remote destinationname (also the jndi binding name) in the jndi tree of the local server console, which in my opinion translates to a valid configuration.
Can anyone let me know if this issue is fixed in 10.3 as there is a CR raised in the 10.0 version as well for this?
CR332983
CR326377  It was not possible to deploy an MDB while connecting to a foreign JMS provider through WLS foreign server resources configured in a JMS module.
Thanks,
CA
Edited by: user1549937 on Jul 9, 2009 4:26 AM

Similar Messages

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

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

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

  • Using a Foreign JMS Destination as a JMS Event Generator Subscription

    NOTE THIS IS BUMPED UP FROM ROBERT NORTON'S POST. I am having the same
    problem here. From the wliconsole, the only queues listed to have events
    generated from are local ones.
    Hello,
    I'm trying to create a workflow that is started by a JMS message queue
    event.
    I'm trying to use the WLIJMSEventGenTool in WebLogic 8.1 to listen to a
    queue
    on a remote WebLogic 8.1 installation, publish the incoming messages to
    a channel,
    then initiate a workflow by subscribing to that channel. Here's a copy
    of my configuration
    file for the tool:
    <message-broker-jms-event-generator-def
    source-jndi-name="SearchInputQueue"> <channel
    name="/srm/sInput/sInput" /> </message-broker-jms-event-generator-def >
    I tried to tackle this by configuring a foreign JMS Server, Connection
    Factory,
    and Destination using the Weblogic Admin Console. Below are the
    parameters I used
    to define the remote connection
    Foreign JMS Server:
    jndi initial context factory: weblogic.jndi.WLInitialContextFactory jndi
    connection
    url: //OPER1090:7001
    Foreign connection factory:
    local jndi name: FtsFactory remote jndi name:
    weblogic.jws.jms.QueueConnectionFactory
    (Are username and password required?)
    Foreign JMS Destination:
    local jndi name: SearchInputQueue remote jndi name:
    InternalSearchInputQueue
    After I try to deploy my generated JMS Event jar, I receive the
    following error:
    <Jun 6, 2003 10:31:50 AM EDT> <Warning> <EJB> <BEA-010061> <The
    Message-Driven
    E JB: SearchInputQueue-UnorderedMessageListener is unable to connect to
    the JMS
    de stination: SearchInputQueue. The Error was: [EJB:011010]The JMS
    destination
    with the JNDI name: SearchInputQueue could not b e found. Please ensure
    that the
    JNDI name in the weblogic-ejb-jar.xml is correct , and the JMS
    destination has
    been deployed.>
    I'm pretty sure the problem is simply that my syntax is off somewhere in
    my configuration.
    I found the existing BEA documentation to be a bit too generic,
    containing no
    specific examples of the proper syntax to use for this task. Can anyone
    offer
    any advice or better, a working example? Any BEA reps out there?

    NOTE THIS IS BUMPED UP FROM ROBERT NORTON'S POST. I am having the same
    problem here. From the wliconsole, the only queues listed to have events
    generated from are local ones.
    Hello,
    I'm trying to create a workflow that is started by a JMS message queue
    event.
    I'm trying to use the WLIJMSEventGenTool in WebLogic 8.1 to listen to a
    queue
    on a remote WebLogic 8.1 installation, publish the incoming messages to
    a channel,
    then initiate a workflow by subscribing to that channel. Here's a copy
    of my configuration
    file for the tool:
    <message-broker-jms-event-generator-def
    source-jndi-name="SearchInputQueue"> <channel
    name="/srm/sInput/sInput" /> </message-broker-jms-event-generator-def >
    I tried to tackle this by configuring a foreign JMS Server, Connection
    Factory,
    and Destination using the Weblogic Admin Console. Below are the
    parameters I used
    to define the remote connection
    Foreign JMS Server:
    jndi initial context factory: weblogic.jndi.WLInitialContextFactory jndi
    connection
    url: //OPER1090:7001
    Foreign connection factory:
    local jndi name: FtsFactory remote jndi name:
    weblogic.jws.jms.QueueConnectionFactory
    (Are username and password required?)
    Foreign JMS Destination:
    local jndi name: SearchInputQueue remote jndi name:
    InternalSearchInputQueue
    After I try to deploy my generated JMS Event jar, I receive the
    following error:
    <Jun 6, 2003 10:31:50 AM EDT> <Warning> <EJB> <BEA-010061> <The
    Message-Driven
    E JB: SearchInputQueue-UnorderedMessageListener is unable to connect to
    the JMS
    de stination: SearchInputQueue. The Error was: [EJB:011010]The JMS
    destination
    with the JNDI name: SearchInputQueue could not b e found. Please ensure
    that the
    JNDI name in the weblogic-ejb-jar.xml is correct , and the JMS
    destination has
    been deployed.>
    I'm pretty sure the problem is simply that my syntax is off somewhere in
    my configuration.
    I found the existing BEA documentation to be a bit too generic,
    containing no
    specific examples of the proper syntax to use for this task. Can anyone
    offer
    any advice or better, a working example? Any BEA reps out there?

  • Using JMS Event Generator w/ remote WebLogic 8.1 queue

    Hello,
    I'm trying to create a workflow that is started by a JMS message queue event.
    I'm trying to use the WLIJMSEventGenTool in WebLogic 8.1 to listen to a queue
    on a remote WebLogic 8.1 installation, publish the incoming messages to a channel,
    then initiate a workflow by subscribing to that channel. Here's a copy of my configuration
    file for the tool:
    <message-broker-jms-event-generator-def source-jndi-name="SearchInputQueue"> <channel
    name="/srm/sInput/sInput" /> </message-broker-jms-event-generator-def >
    I tried to tackle this by configuring a foreign JMS Server, Connection Factory,
    and Destination using the Weblogic Admin Console. Below are the parameters I used
    to define the remote connection
    Foreign JMS Server:
    jndi initial context factory: weblogic.jndi.WLInitialContextFactory jndi connection
    url: //OPER1090:7001
    Foreign connection factory:
    local jndi name: FtsFactory remote jndi name: weblogic.jws.jms.QueueConnectionFactory
    (Are username and password required?)
    Foreign JMS Destination:
    local jndi name: SearchInputQueue remote jndi name: InternalSearchInputQueue
    After I try to deploy my generated JMS Event jar, I receive the following error:
    <Jun 6, 2003 10:31:50 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
    E JB: SearchInputQueue-UnorderedMessageListener is unable to connect to the JMS
    de stination: SearchInputQueue. The Error was: [EJB:011010]The JMS destination
    with the JNDI name: SearchInputQueue could not b e found. Please ensure that the
    JNDI name in the weblogic-ejb-jar.xml is correct , and the JMS destination has
    been deployed.>
    I'm pretty sure the problem is simply that my syntax is off somewhere in my configuration.
    I found the existing BEA documentation to be a bit too generic, containing no
    specific examples of the proper syntax to use for this task. Can anyone offer
    any advice or better, a working example? Any BEA reps out there?

    Hello,
    I'm trying to create a workflow that is started by a JMS message queue event.
    I'm trying to use the WLIJMSEventGenTool in WebLogic 8.1 to listen to a queue
    on a remote WebLogic 8.1 installation, publish the incoming messages to a channel,
    then initiate a workflow by subscribing to that channel. Here's a copy of my configuration
    file for the tool:
    <message-broker-jms-event-generator-def source-jndi-name="SearchInputQueue"> <channel
    name="/srm/sInput/sInput" /> </message-broker-jms-event-generator-def >
    I tried to tackle this by configuring a foreign JMS Server, Connection Factory,
    and Destination using the Weblogic Admin Console. Below are the parameters I used
    to define the remote connection
    Foreign JMS Server:
    jndi initial context factory: weblogic.jndi.WLInitialContextFactory jndi connection
    url: //OPER1090:7001
    Foreign connection factory:
    local jndi name: FtsFactory remote jndi name: weblogic.jws.jms.QueueConnectionFactory
    (Are username and password required?)
    Foreign JMS Destination:
    local jndi name: SearchInputQueue remote jndi name: InternalSearchInputQueue
    After I try to deploy my generated JMS Event jar, I receive the following error:
    <Jun 6, 2003 10:31:50 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
    E JB: SearchInputQueue-UnorderedMessageListener is unable to connect to the JMS
    de stination: SearchInputQueue. The Error was: [EJB:011010]The JMS destination
    with the JNDI name: SearchInputQueue could not b e found. Please ensure that the
    JNDI name in the weblogic-ejb-jar.xml is correct , and the JMS destination has
    been deployed.>
    I'm pretty sure the problem is simply that my syntax is off somewhere in my configuration.
    I found the existing BEA documentation to be a bit too generic, containing no
    specific examples of the proper syntax to use for this task. Can anyone offer
    any advice or better, a working example? Any BEA reps out there?

  • JMS event generator only gets non-transactional queue msg

    Hi,
    I have created a JMS event generator to listen to a particular queue. It seems to work perfectly fine if, when posting a message to the queue that the JMS EG is listening to, the queue created is a non-transactional queue, i.e. queueConnection.createQueueSession(false, ...).
    However if I created a transactional queue to post message to the JMS EG, i.e. queueConnection.createQueueSession(true, ...), then the JMS EG can't seem to see the message. I checked in the WLI Admin console, JMS EG section, and there are no messages read by the particular JMS EG after I have posted the msg to the queue.
    My question is: is there a known limitation on the JMS EG that it can only read from a non-transactional JMS queue, or is this a bug? (I am using weblogic 8.1 sp2).
    Thanks
    Regards,
    xlfhk

    Hi,
    sorry, just discovered it's my mistake. Instead of using the transaction created when calling queueConnection.createQueueSession(true, ...), and committing that, I created a JTA transaction artificially wrapping the entire chunk of code.
    As a result, I ended up with a pair of transactions that are nested (I think ...), and the external transaction's commit was called when the nested JMS transaction hasn't been committed yet. As a result, no commit ever took place (I think again ...).
    I have now tried calling queueSession.commit() after sending the message. It seems to work fine. Thanks for the help.
    Regards,
    xlfhk.

  • 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.

  • JMS event generator accepts messages, but won't push out to channels

    I am monitoring the JMS event generator through the WLIconsole, and I can see the
    messages coming in. I have a channel rule defined for this particular event generator
    - it just allows everything through (by leaving the name and value fields blank).
    I can see that there is a channel listed under the channel count.
    However, when I go under the Message Broker window, and check the channel, there
    are zero subscribers. This is probably why the messages that are going into
    the generator aren't being recieved by anyone.
    I'm trying to use this channel to kick off a workflow - so the event choice start
    node is set to listen to a channel, but I don't think it actually subscribes to
    the channel - if it did, why wouldn't it be listed under the WLI console as a
    subscriber? How do I get the start node to listen to the channel? How do I get
    the messages from the event generator into the channel?

    Hello MS, Question:  Do any of the LED lights on the keyboard turn on when the computer doesn’t boot?  Here’s an HP troubleshooting document for notebooks that won’t start, along with some info about LED error codes: http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&docname=c01732674 If that doesn’t help, it is probably a hardware issue. Since you've only had the notebook for 10 months it’s probably still under warranty. You can contact HP: http://www8.hp.com/us/en/contact-hp/ww-contact-us.html Please let me know if any of these suggestions helped.  If not, I will try to investigate further. TobindoHP Representative 

  • Suspending JMS event generator

    Hi,
    How do I suspend a jms event dynamically?
    I know that this can be done with WLI Admin Console but is there another way to do this without user intervention?
    Help appreciated.

    Hello,
    event generators are in most cases EJBs (the HTTP event generator may be the only exeption).
    Suspending is actually equal to undeploying.
    I do not know, if you can use the event generator MBeans, but you can always use the weblogic.Admin command to undeploy/redeploy a JMS event generator.
    -Kai

  • JMS event generator extract custom jms property

    [cross posted from integration.interest - this seems the correct place to post]
    Hi, I was looking for a way to enable a workflow/process to extact a custom jms property that is send with a jms message to the jms event generator.
    So the client inserts name/value pair inside the jms message, the event generator picks up the message and starts a workflow. How can I extract that custom name/value pair once inside the workflow/process ?
    TIA

    Hey can u tell me the solution for this problem.....I am also facing similar problems......Help is appericiated....

  • Automatic Generation of JMS event generator using WLST script

    is there any way to create and deploy JMS event generator using WLST script. i am using weblogic server 10.3.1

    You could see this informantion here:
    http://docs.oracle.com/cd/E14981_01/wli/docs1031/deploy/cluster.html#wp1519038

  • JMS Event Generator

    Hi,
    I have created a durable topic and an event generator to listen this topic.
    I got functionality to suspend this topic to start execution of some process and then resume back when it process finished.
    Meanwhile other application keep on publishing messages to the topic and it is expected that when event generator is running is should pick up the message from the topic.
    But it is not happening it does pick any subsequent message published to topic but not picking up old message.
    Can any body what is wrong happening?
    Regards,
    Jugal

    You cannot. The message broker puts the message into the dispatcher queue of the process web application, so it is a JMS message, but the workflow receives it as xml, string or rawData object.
    What do you want to achieve ? Only MB client is a JPD and there is no (obvious) use for JMS messages.
    -Kai

  • WLI FTP File Event Generator

    Hi,
    I'm using a FTP file event Generator from my local machine (Windows) to an AIX machine and I've got this java exception:
    2007-05-29 15:28:06,781 ERROR (InternalLogger.java:65) - Unexpected error when parsing file
    Throwable: java.util.NoSuchElementException: Unix-List: Invalid Number Format
    Stack Trace:
    java.util.NoSuchElementException: Unix-List: Invalid Number Format
    at com.bea.control.FtpFile.parseUnixListLine(FtpFile.java:189)
    at com.bea.control.FtpFile.<init>(FtpFile.java:35)
    at com.bea.control.FtpClient.parseFileNames(FtpClient.java:379)
    at com.bea.control.FtpClient.getFiles(FtpClient.java:328)
    at com.bea.control.FileResource.ftpGetFiles(FileResource.java:1393)
    - My Event configuration:
    FTP Local Directory: /dir/local/
    Directory: /dir/fileDir/{myFile}
    Archive Directory: /dir/archive/
    Error Directory: /dir/error/
    FYI It works fine when I'm using disk file event generator with the same test file.
    Some ideas ?
    Thx,
    Vincent
    Edited by VincentLacaes at 05/29/2007 9:14 AM

    Hi
    This is a problem in WLI 8.1 SP4, and is fixed with a patch.
    Please talk to any BEA Customer support Engineer, and ask for patch from CR213993.
    Thanks
    Ashok

  • Problem with creation of the jms event generator

    hi,
    I have set up a weblogic workshop instance on one of my machines. It has a queue call OUT.QUEUE. The application writes message to this queue. I have set up an integration instance on another machine. I have created a Foreign JMS server to point to the first machine. I have also configured a queue which points to the one on the first machine. However when my integration server starts up, I keep getting the error.
    [EJB:010196]'weblogic.jms.common.JMSException: Error creating session' Linked exception = 'weblogic.jms.dispatcher.DispatcherException: could not find JMS Server portalServer'
    weblogic.jms.common.JMSException: Error creating session
         at weblogic.jms.frontend.FESession.setUpBackEndSession(Lweblogic/jms/dispatcher/DispatcherId;)Lweblogic/jms/common/Sequencer;(FESession.java:809)
         at weblogic.jms.frontend.FESession.consumerCreate(Lweblogic/jms/frontend/FEConsumerCreateRequest;)I(FESession.java:1049)
         at weblogic.jms.frontend.FESession.invoke(Lweblogic/jms/dispatcher/Request;)I(FESession.java:2573)
         at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine()Lweblogic/jms/dispatcher/Response;(Request.java:643)
         at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(Lweblogic/jms/dispatcher/Request;)Lweblogic/jms/dispatcher/Response;(DispatcherImpl.java:179)
         at weblogic.jms.client.JMSSession.consumerCreate(Ljava/lang/String;Lweblogic/jms/common/DestinationImpl;Ljava/lang/String;ZI)Lweblogic/jms/frontend/FEConsumerCreateResponse;(JMSSession.java:1860)
         at weblogic.jms.client.JMSSession.createConsumer(Ljavax/jms/Destination;Ljava/lang/String;ZLjava/lang/String;B)Ljavax/jms/MessageConsumer;(JMSSession.java:1691)
         at weblogic.jms.client.JMSSession.createReceiver(Ljavax/jms/Queue;Ljava/lang/String;)Ljavax/jms/QueueReceiver;(JMSSession.java:1530)
         at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(Ljavax/jms/Destination;Ljava/lang/String;III)V(JMSConnectionPoller.java:1767)
         at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection()V(JMSConnectionPoller.java:2119)
         at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS()V(JMSConnectionPoller.java:1192)
         at weblogic.ejb20.internal.JMSConnectionPoller.trigger(Lweblogic/time/common/Schedulable;)V(JMSConnectionPoller.java:984)
         at weblogic.time.common.internal.ScheduledTrigger.run()Ljava/lang/Object;(ScheduledTrigger.java:243)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(SecurityManager.java:121)
         at weblogic.time.common.internal.ScheduledTrigger.executeLocally()V(ScheduledTrigger.java:229)
         at weblogic.time.common.internal.ScheduledTrigger.execute(Lweblogic/kernel/ExecuteThread;)V(ScheduledTrigger.java:223)
         at weblogic.time.server.ScheduledTrigger.execute(Lweblogic/kernel/ExecuteThread;)V(ScheduledTrigger.java:50)
         at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(ExecuteThread.java:224)
         at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)
         at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)
    Caused by: weblogic.jms.dispatcher.DispatcherException: could not find JMS Server portalServer
         at weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(Lweblogic/jms/dispatcher/DispatcherId;)Lweblogic/jms/dispatcher/Dispatcher;(DispatcherManager.java:318)
         at weblogic.jms.dispatcher.DispatcherManager.dispatcherFindOrCreate(Lweblogic/jms/dispatcher/DispatcherId;)Lweblogic/jms/dispatcher/Dispatcher;(DispatcherManager.java:368)
         at weblogic.jms.frontend.FESession.setUpBackEndSession(Lweblogic/jms/dispatcher/DispatcherId;)Lweblogic/jms/common/Sequencer;(FESession.java:807)
         ... 20 more
    Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.jms.S:portalServer' Resolved weblogic.jms; remaining name 'S:portalServer'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(Ljava/lang/String;Ljava/lang/String;Ljava/util/Hashtable;)Ljavax/naming/NameNotFoundException;(BasicNamingNode.java:924)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(Ljava/lang/String;Ljava/util/Hashtable;Ljava/lang/String;)Ljava/lang/Object;(BasicNamingNode.java:230)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(Ljava/lang/String;Ljava/util/Hashtable;Ljava/lang/String;)Ljava/lang/Object;(ServerNamingNode.java:154)
         at weblogic.jndi.internal.BasicNamingNode.lookup(Ljava/lang/String;Ljava/util/Hashtable;)Ljava/lang/Object;(BasicNamingNode.java:188)
         at weblogic.jndi.internal.BasicNamingNode.lookup(Ljava/lang/String;Ljava/util/Hashtable;)Ljava/lang/Object;(BasicNamingNode.java:196)
         at weblogic.jndi.internal.BasicNamingNode.lookup(Ljava/lang/String;Ljava/util/Hashtable;)Ljava/lang/Object;(BasicNamingNode.java:196)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(Ljavax/naming/Name;Ljava/lang/String;)Ljava/lang/Object;(WLEventContextImpl.java:256)
         at weblogic.jndi.internal.WLContextImpl.lookup(Ljava/lang/String;)Ljava/lang/Object;(WLContextImpl.java:363)
         at javax.naming.InitialContext.lookup(Ljava/lang/String;)Ljava/lang/Object;(InitialContext.java:347)
         at weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(Lweblogic/jms/dispatcher/DispatcherId;)Lweblogic/jms/dispatcher/Dispatcher;(DispatcherManager.java:314)
         ... 22 more
    Any ideas?

    Hi experts/Sriram...
    Thanks for the reply.
    The -
    >showing the line....
            QS80_TAB-DEDMT=QS80_TAB-DEDMT+S80-DEDMT
    Where should we change to get rid of this runtime error.
    Here in my quality everthing is fine and we have uploaded patches in quality upto recent one sp80.But in prod. the patchlevel is sp71.Will it be the reason.
    Please advice me on this as i have to complete the issue of F16.
    Thanks and Regards,
    V Sai.

  • Multiple validate events generated for a new matrix

    I have added a new tab to the item master form which has a matrix grid on it.
    This works fine until I attempt to move to the previous or next record whilst the new tab is visible.
    What happens then is that every column on every line of the matrix causes a validate event to be triggered, it even triggers the event for hidden columns.
    This is really affecting my form and I cannot understand why so many events are generated, does anyone have any odeas?
    I am not sure if it is relevant but I have noticed that when moving through the data a click event is generated on item 41 within the item master form but i am not certain what this item is - could it be the "Move data" button from the toolbar?
    Gordon Wood

    Hi ...
    I would try putting a BubbleEvent = False at a certain point in the event to cancel further execution.
    You could also use the iteration of If pval.InnerEvent = True to catch and further execution, like this
          CASE et_Validate
                   If pval.InnerEvent = True Then BubbleEvent = False
    hope it helps

  • WLS 7.0.4 - JMS connection Factory for RMI queues - server affinity issues help pls

    We are using WLS 7.0.4 - One of JMS connection factory setting in admin
    console we selected "Server Affinity" options.
    We see this messages appear in Weblogic log file,
    ####<Apr 24, 2006 1:56:53 AM EDT> <Error> <Cluster>
    <liberatenode4.dc2.adelphia.com> <node4_svr> <ExecuteThrea
    d: '4' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
    <000123> <Conflict start: You tried to bi
    nd an object under the name sbetrmi2 in the JNDI tree. The object you have
    bound from liberatenode2.dc2.adelp
    hia.com is non clusterable and you have tried to bind more than once from
    two or more servers. Such objects ca
    n only deployed from one server.>
    and then,
    ####<Apr 24, 2006 1:58:12 AM EDT> <Error> <Cluster>
    <liberatenode5.dc2.adelphia.com> <node5_svr> <ExecuteThrea
    d: '7' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
    <000125> <Conflict Resolved: sbetrmi2 for
    the object from liberatenode5.dc2.adelphia.com under the bind name sbetrmi2
    in the JNDI tree.>
    Should we use 'load balancing option' instead of 'server affinity' ?
    Any thuoghts?
    Thanks in adv.
    Vijay

    Test Reply
              <Vijay Kumar> wrote in message news:[email protected]..
              > <b>WLS 7.0.4 - JMS Connection Factory - Server Affinity - issues in log
              > file</b>
              >
              > We are using WLS 7.0.4 - One of JMS connection factory setting in admin
              > console we selected "Server Affinity" options.
              >
              > We see this messages appear in Weblogic log file,
              > ####<Apr 24, 2006 1:56:53 AM EDT> <Error> <Cluster>
              > <liberatenode4.dc2.adelphia.com> <node4_svr> <ExecuteThrea
              > d: '4' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
              > <000123> <Conflict start: You tried to bi
              > nd an object under the name sbetrmi2 in the JNDI tree. The object you have
              > bound from liberatenode2.dc2.adelp
              > hia.com is non clusterable and you have tried to bind more than once from
              > two or more servers. Such objects ca
              > n only deployed from one server.>
              >
              > and then,
              > ####<Apr 24, 2006 1:58:12 AM EDT> <Error> <Cluster>
              > <liberatenode5.dc2.adelphia.com> <node5_svr> <ExecuteThrea
              > d: '7' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
              > <000125> <Conflict Resolved: sbetrmi2 for
              > the object from liberatenode5.dc2.adelphia.com under the bind name
              > sbetrmi2 in the JNDI tree.>
              >
              >
              > Should we use 'load balancing option' instead of 'server affinity' ?
              >
              > Any thuoghts?
              >
              > Thanks in adv.
              > Vijay

Maybe you are looking for