Unable to get distributed destination in cluster

[Cross post with interest.jms]
          Hi,
          I'm working with Weblogic 8.1.2 on Windows. Up until now I've always worked with a single server on which I have configured a JMS server and a number of queues. My clients get references to the queues using the createQueue() method. I now need to test in a clustered environment and my clients are no longer able to create queues; my clients gets a "Invalid destination name" each time.
          I've created a simple cluster with 2 servers and one distributed connection. Each server in the cluster has a uniquely named JMS server. I created a distributed connection called C1_DIST_SECURITY_PERSISTENCE and then created the members automatically for the cluster. My understanding from what I've read is that is the client should no longer need to name the JMS server when calling createQueue, instead the distributed destination name should be sufficient. So, my client calls
          session.createQueue("C1_DIST_SECURITY_PERSISTENCE")
          Everytime it does this it gets the exception: weblogic.jms.common.JMSException: Invalid destination name: C1_DIST_SECURITY_PERSISTENCE
          As an aside I modified my code to try explicitly looking up one of the destination members. In this case a totally different exception occurs:
          eblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Environment not found on thread ] at weblogic.jndi.internal.NamingNodeReplicaHandler.<init>(NamingNodeReplicaHandler.java:150) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
          Any help here greatly appreciated.
          Thanks,
          Aoife

Hi Gsrc,
This is my code in the PR.
public void processRequest(OAPageContext pageContext, OAWebBean webBean)
super.processRequest(pageContext, webBean);
String itemNum=pageContext.getParameter("itemNum");
System.out.println("item nnum "+itemNum);
i am getting a null value in the print stmt.
Thanks.
Message was edited by:
SRK84

Similar Messages

  • How do you get distributed destinations to work ?

              Hi all,
              I'm trying to getting to work Distributed JMS Destinations. But
              still without success. This is the sitation:
              Node1---->JMS Server1------>Queue1 [Distributed destination1]
              Node2---->JMS Server2------>Queue2 [Distributed destination1]
              I have a cluster with 2 Nodes.
              I have created 2 JMS Servers each one targetted on one Node.
              Then I have created 2 Queues and added them to a Distributed Destination as member.
              Now I start the QueueSender (pointing to the Distributed Destination's JNDI)
              I start 2 QueueReceivers (pointing to the JNDI of the 2 Queues).
              The problem is that when one of the two nodes, let's say Node1, fails
              messages aren't dispatched to the JMS Server2.
              So I wonder: Is it possible that if one of the 2 JMS Server fails
              the message is redirected to the other JMS Server ?
              Thanks a lot
              Francesco
              

    Receivers only load-balance once - when
              they are first created. The JMS Performance
              Guide explores the implications of this.
              Keep in mind that the distributed destination
              feature was optimized for the case where
              receivers (generally MDBs) run on the same
              servers as the distributed destination
              instances, which simply load balances each
              receiver to its local destination instance.
              Otherwise, if the receivers
              are not co-located with distributed destination
              instances, load-balancing
              configuration requires special care to prevent
              physical destinations from not getting served
              by receivers.
              One solution for the latter problem, as you
              already wrote below, is to receive directly from the
              physical destinations - which removes the
              load balancing decision all-together.
              Francesco wrote:
              > Hi,
              > thanks a lot for your clean answers.
              > Ps has anybody got an answer about my last question (That is, should I lookup
              > the JNDI
              > of the single Queue or of the Distributed Destination in order to get distributed
              > destination to work ?)
              > Thanks a lot
              > Francesco
              >
              > Tom Barnes <[email protected].bea.com>
              > wrote:
              >
              >>It is normal for a sender to get an exception
              >>when its connection's host server goes down.
              >>The client connection's host server does
              >>not change for the life of the connection,
              >>and does not automatically fail-over.
              >>Even when the client's connection host stays up
              >>but the JMSServer hosting the current
              >>distributed destination instance goes down, the sender
              >>may still get an exception. Such an exception
              >>can indicate that there is ambiguity as to
              >>whether or not the JMS server received the
              >>message from the send().
              >>
              >>The standard way to handle
              >>such exceptions is to re-establish the connection,
              >>session, and producer on the client (usually
              >>using the exact same code that initialized
              >>these resources to start with.)
              >>
              >>In addition, it is highly recommended
              >>for the client to register exception listeners
              >>on both the connection and on the WLSession.
              >>
              >>Tom
              >>
              >>Francesco wrote:
              >>
              >>
              >>>"Barry Myles" <[email protected]> wrote:
              >>>
              >>>
              >>>>Hi Francesco
              >>>>
              >>>>Try creating a connection factory that has Load balanced ticked and
              >>
              >>server
              >>
              >>>>affinity
              >>>>unticked
              >>>>
              >>>>now make sure that the distributed destinations load balancing property
              >>>>is set
              >>>>to Round Robin
              >>>>
              >>>>
              >>>>
              >>>>>I start 2 QueueReceivers (pointing to the JNDI of the 2 Queues).
              >>>>
              >>>>Also when the QueueRecievers are running do you see one consumer attached
              >>>>to each
              >>>>physical queue?
              >>>>
              >>>>HTH
              >>>>
              >>>>
              >>>>"Francesco" <[email protected]> wrote:
              >>>>
              >>>>
              >>>>>Hi all,
              >>>>>I'm trying to getting to work Distributed JMS Destinations. But
              >>>>>still without success. This is the sitation:
              >>>>>
              >>>>>Node1---->JMS Server1------>Queue1 [Distributed destination1]
              >>>>>Node2---->JMS Server2------>Queue2 [Distributed destination1]
              >>>>>
              >>>>>I have a cluster with 2 Nodes.
              >>>>>I have created 2 JMS Servers each one targetted on one Node.
              >>>>>Then I have created 2 Queues and added them to a Distributed Destination
              >>>>>as member.
              >>>>>
              >>>>>Now I start the QueueSender (pointing to the Distributed Destination's
              >>>>>JNDI)
              >>>>>I start 2 QueueReceivers (pointing to the JNDI of the 2 Queues).
              >>>>>
              >>>>>The problem is that when one of the two nodes, let's say Node1, fails
              >>>>>messages aren't dispatched to the JMS Server2.
              >>>>>
              >>>>>So I wonder: Is it possible that if one of the 2 JMS Server fails
              >>>>>the message is redirected to the other JMS Server ?
              >>>>>Thanks a lot
              >>>>>Francesco
              >>>>
              >>>Hi Barry,
              >>>I have tried to modify the connection factory as you said but
              >>>I'm still stuck. Basically when I shut down one of the two Nodes, the
              >>
              >>Sender
              >>
              >>>receives an exception "IllegalStateException: Producer is closed".
              >>>
              >>>Could you tell me if it's basically correct that :
              >>>
              >>>Sender----->looks up the Distributed Queue
              >>>Receivers---->look up the single Queues (which belong to the Distr.
              >>
              >>Queue)
              >>
              >>>Thanks again
              >>>Francesco
              >>
              >
              

  • Unable to get the file system information for: \\****servername\E$\; error = 64 Unable to distribute content to DP

    One of our DPs has stopped loading content. 
    I've research for quite a bit and cannot find a clear cut reason to this.  This server only has a DP role, I verified sharing permissions, all looked good. This DP has been running just fine for the last year or so and all sudden it will no longer load
    packages.  The disk drive is still present I can still reach the hidden share \\servername.com\E$
    Verified that the SMSSIG$ folder is there and the last entry is from 4/23/2015 
    SCCM 2012 R2 
    OS 2008 R2 Standard
    Any help is greatly appreciated!
    Here's a snipit from the distmgr.log
    Start updating the package on server ["Display=\\*****.com\"]MSWNET:["SMS_SITE=1AB"]\\*****.com\...
    Attempting to add or update a package on a distribution point.
    Will wait for 1 threads to end.
    Thread Handle = 0000000000001E48
    STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=***.com SITE=1AB PID=2472 TID=8252 GMTDATE=Thu Apr 30 19:12:01.972 2015 ISTR0="SYSMGMT Source" ISTR1="["Display=\\*****.com\"]MSWNET:["SMS_SITE=1AB"]\\*****.com\"
    ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="CAS00087" AID1=404 AVAL1="["Display=\\*****.com\"]MSWNET:["SMS_SITE=1AB"]\\*****.com\"
    SMS_DISTRIBUTION_MANAGER 4/30/2015 2:12:01 PM
    8252 (0x203C)
    The current user context will be used for connecting to ["Display=\\*****.com\"]MSWNET:["SMS_SITE=1AB"]\\*****.com\.
    Successfully made a network connection to \\*****.com\ADMIN$.
    Ignoring drive \\*****.com\C$\.  File \\*****.com\C$\NO_SMS_ON_DRIVE.SMS exists.
    Unable to get the file system information for: \\*****.com\E$\; error = 64.
    Failed to find a valid drive on the distribution point ["Display=\\*****.com\"]MSWNET:["SMS_SITE=1AB"]\\*****.com\
    Cannot find or create the signature share.
    STATMSG: ID=2324 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=sccmprdpr1sec2.mmm.com SITE=1AB PID=2472 TID=8252 GMTDATE=Thu Apr 30 19:12:55.206 2015 ISTR0="["Display=\\*****.com\"]MSWNET:["SMS_SITE=1AB"]\\*****.com\"
    ISTR1="CAS00087" ISTR2="" ISTR3="30" ISTR4="94" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="CAS00087" AID1=404 AVAL1="["Display=\\*****.com\"]MSWNET:["SMS_SITE=1AB"]\\*****.com\"
    Error occurred. Performing error cleanup prior to returning.
    Cancelling network connection to \\*****.com\ADMIN$.

    Error 64 is being returned which is simply "the network name is no longer available".
    There can be a number of reasons for this from SMB compatibility issues (2003 servers wont support SMB2), to the expected and actual computer name of the boxes don't match (tries to authenticate with server.tld.com when the actual name is srv-01.tld.com and
    you just put a C-name in). I'd start from the top:  Try opening said share from the Primary Site server as that's the box doing the work.  Verify the IP and computer name is legit and that no one has played ACL games between the two systems (remember
    RPC only initiates/listens on port 135 but established connections are up in the dynamic port range).
    At the end of the day it's an issues "underneath" SCCM, and not an SCCM problem specifically. 

  • Distributed destination javax.naming.NameNotFoundException

    Hi, I have a JMS client (java application) that is trying to publish a message to a JMS queue. This queue is a distributed destination that resides on a cluster with 2 servers.
              When I try to lookup the queue name with
              Queue queue_final = (Queue) ctx.lookup(queueName);
              I get the following exception,
              'LAPPLoanStatusJMSExcep' Resolved [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'LAPPLoanStatusJMSExcep' Resolved ]; remaining name
              I can see this queue name under Distributed destinations and under the 2 servers.

    Did you manage to resolve this issue. I appear to be running into the same problem. It only occurs when i am trying to get hold of the queue. I have no problems when i am looking up the connection factory.
              regards
              kodjo

  • Distributed Destination Failover not working

              I'm using WebLogic 7 SP1 on Windows 2000. I've configured a
              distributed queue that has two member. The two members are
              running in two WebLogic instances in a Cluster configuration
              (call them Server1 and Server2). My client posts messages to the
              distributed queue and it seems the messages seem to be
              distributed between Server1 and Server2 (as expected). Although,
              when I kill Server1, the client complains that it can't connect
              to the queue on Server1 and never recovers. I would have
              expected to see (at most) one exception and then the next
              request to use Server2's queue. The client gets the following
              exception:
              weblogic.jms.dispatcher.DispatcherException: Dispatcher not found in jndi: Server1,
              javax.naming.NameNotFoundException: Unable to resolve 'weblogic.jms.S:Server1'
              Resolved: 'weblogic.jms' Unresolved:'S:Server1' ; remaining name 'S:Server1'
                   at weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:323)
                   at weblogic.jms.dispatcher.DispatcherManager.findOrCreate(DispatcherManager.java:413)
                   at weblogic.jms.frontend.FEProducer.<init>(FEProducer.java:87)
                   at weblogic.jms.frontend.FESession$2.run(FESession.java:607)
                   at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:785)
                   at weblogic.jms.frontend.FESession.producerCreate(FESession.java:604)
                   at weblogic.jms.frontend.FESession.invoke(FESession.java:2246)
                   at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:552)
                   at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:275)
                   at weblogic.jms.client.JMSSession.createProducer(JMSSession.java:1461)
                   at weblogic.jms.client.JMSSession.createSender(JMSSession.java:1312)
              Should I have some kind of recovery logic on my client to make
              this stuff work?
              Bob.
              

    Hi,
                   I hit the same problem, were you able to fix it ? if so how ?
              Tom Barnes wrote:
              > Hi Bob,
              >
              > If you haven't already, see if the connection factory you use has
              > "ServerAffinityEnabled" set to false (the default is true) and
              > "LoadBalancingEnabled" set to true. That said, I think you may be
              > seeing a known bug - so I suggesting contacting customer support.
              >
              > Tom
              >
              > Bob S wrote:
              >
              >> Tom,
              >>
              >> I don't really have a problem with getting an exception for the
              >> request that was in progress when the server failed. I would
              >> expect, though, the next request to succeed.
              >> The problem is that even when I restart my client process it
              >> still tries to go to the same destination (weird). It seems
              >> that the Distributed Destination exception handling logic only
              >> removes the failed entry when it receives a certain type of
              >> exception. I'm suspecting this because (just 5 minutes ago)
              >> I got the distributed destination to recover from the failure.
              >> The exception that I got this time was the following:
              >>
              >> weblogic.jms.common.JMSException: Failed to send message because
              >> destination MyQueue_JMSServer1
              >> is not avaiable (shutdown, suspended or deleted).
              >>
              >> Start server side stack trace:
              >> weblogic.jms.common.JMSException: Failed to send message because
              >> destination MyQueue_JMSServer1
              >> is not avaiable (shutdown, suspended or deleted).
              >> at
              >> weblogic.jms.backend.BEDestination.checkShutdownOrSuspendedNeedLock(BEDestination.java:1102)
              >>
              >> at weblogic.jms.backend.BEDestination.send(BEDestination.java:2782)
              >> at weblogic.jms.backend.BEDestination.invoke(BEDestination.java:3810)
              >> at
              >> weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:552)
              >>
              >> at
              >> weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:152)
              >>
              >> at
              >> weblogic.jms.dispatcher.DispatcherImpl.dispatchAsyncTranFuture(DispatcherImpl.java:425)
              >>
              >> at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
              >> Source)
              >> at
              >> weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
              >> at
              >> weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
              >> at
              >> weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:785)
              >>
              >> at
              >> weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
              >>
              >> at
              >> weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
              >>
              >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
              >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
              >> End server side stack trace
              >>
              >> In this (rare) case, my system recovered beautifully!
              >>
              >> Bob.
              >>
              >> Tom Barnes <[email protected]> wrote:
              >>
              >>> Hi Bob,
              >>>
              >>> The particular exception you are seeing seems like it could use
              >>> some enhancement - it should be wrapped in a "friendlier" exception
              >>> such as "remote server XXX unavailable". I
              >>> recommend filing a case with customer support.
              >>>
              >>> That said, a producer sending to a distributed destination needs
              >>> to be able to handle send failures. WebLogic
              >>> will automatically retry sends in cases where there is no ambiguity,
              >>> but
              >>> when it can't determine the nature of the failure (eg it can't
              >>> determine whether or not the message made it to a JMS server) it
              >>> throws the exception back to the client to let the client
              >>> decide what it wants to do - eg commit/don't commit, reconnect
              >>> and resend, reconnect and don't resend.
              >>>
              >>> Tom
              >>> Bob S wrote:
              >>>
              >>>> I'm using WebLogic 7 SP1 on Windows 2000. I've configured a
              >>>> distributed queue that has two member. The two members are
              >>>> running in two WebLogic instances in a Cluster configuration
              >>>> (call them Server1 and Server2). My client posts messages to the
              >>>> distributed queue and it seems the messages seem to be
              >>>> distributed between Server1 and Server2 (as expected). Although,
              >>>> when I kill Server1, the client complains that it can't connect
              >>>> to the queue on Server1 and never recovers. I would have
              >>>> expected to see (at most) one exception and then the next
              >>>> request to use Server2's queue. The client gets the following
              >>>> exception:
              >>>>
              >>>> weblogic.jms.dispatcher.DispatcherException: Dispatcher not found in
              >>>
              >>>
              >>> jndi: Server1,
              >>>
              >>>> javax.naming.NameNotFoundException: Unable to resolve
              >>>> 'weblogic.jms.S:Server1'
              >>>> Resolved: 'weblogic.jms' Unresolved:'S:Server1' ; remaining name
              >>>> 'S:Server1'
              >>>> at
              >>>> weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:323)
              >>>>
              >>>> at
              >>>> weblogic.jms.dispatcher.DispatcherManager.findOrCreate(DispatcherManager.java:413)
              >>>>
              >>>> at weblogic.jms.frontend.FEProducer.<init>(FEProducer.java:87)
              >>>> at weblogic.jms.frontend.FESession$2.run(FESession.java:607)
              >>>> at
              >>>> weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:785)
              >>>>
              >>>> at
              >>>> weblogic.jms.frontend.FESession.producerCreate(FESession.java:604)
              >>>> at weblogic.jms.frontend.FESession.invoke(FESession.java:2246)
              >>>> at
              >>>> weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:552)
              >>>>
              >>>> at
              >>>> weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:275)
              >>>>
              >>>> at
              >>>> weblogic.jms.client.JMSSession.createProducer(JMSSession.java:1461)
              >>>> at
              >>>> weblogic.jms.client.JMSSession.createSender(JMSSession.java:1312)
              >>>>
              >>>> Should I have some kind of recovery logic on my client to make
              >>>> this stuff work?
              >>>>
              >>>> Bob.
              >>>
              >>>
              >>
              >
              

  • WebLogic 10.3 jms Uniform Distributed Destination

    We are running WL Server 10.3 on Suse 11.0. I have created a Cluster, Servers, JMS Servers, Connection Factory and a Distributed Destination. On the Connection Factory, I have the "Server Affinity" checkbox unchecked. Server/Cluster all look good. I am using the jmsfullclient.jar for the test.
    When attempting to access the distributed destination, I get the following error on the second message. If I were to turn on "Session Affinity" in the Cluster, the problem does not arise but I lose the value of the distributed destination. Any suggestions and assistance would be appreciated.:
    weblogic.jms.common.JMSException: No failover destination.
         at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
         at weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1275)
         at weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:783)
         at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:541)
         at weblogic.jms.client.JMSProducer.sendWithListener(JMSProducer.java:394)
         at weblogic.jms.client.JMSProducer.send(JMSProducer.java:384)
         at weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:970)
         at com.overstock.util.Example.main(Example.java:44)
    Caused by: weblogic.jms.common.JMSException: No failover destination.
         at weblogic.jms.frontend.FEProducer.pickNextDestination(FEProducer.java:750)
         at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:1092)
         at weblogic.jms.frontend.FEProducer.send(FEProducer.java:1399)
         at weblogic.jms.frontend.FEProducer.invoke(FEProducer.java:1460)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
         at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:276)
         at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:141)
         at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
         at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: weblogic.messaging.dispatcher.DispatcherException: could not find Server null
         at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:176)
         at weblogic.messaging.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherManager.java:58)
         at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreate(JMSDispatcherManager.java:219)
         at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreateChecked(JMSDispatcherManager.java:230)
         at weblogic.jms.frontend.FEProducer.findDispatcher(FEProducer.java:825)
         at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:995)
         ... 9 more
    Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:null'. Resolved 'weblogic.messaging.dispatcher'; remaining name 'S:null'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:172)
         ... 14 more
    My client code is extremely basic and is the following:
    public class Example {
    public static void main(String args[]) {
    String providerUrl = "t3://localhost:7003,localhost:7005";
    Hashtable<String, String> ht = new Hashtable<String, String>();
    ht.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    ht.put(Context.PROVIDER_URL, providerUrl);
    InitialContext ctx = null;
    try {
    ctx = new InitialContext(ht);
    ConnectionFactory connFactory = (ConnectionFactory) ctx
    .lookup("connectionfactory");
    Destination dest = (Destination) ctx.lookup("distributedqueue");
    Connection conn = null;
    Session session = null;
    MessageProducer p = null;
    try {
    conn = connFactory.createConnection();
    conn.start();
    System.out.println("Thread:" + Thread.currentThread().getId() + " got a connection "
    + conn.hashCode());
    session = conn.createSession(false, Session.AUTO_ACKNOWLEDGE);
    p = session.createProducer(dest);
    System.out.println("Thread:" + Thread.currentThread().getId() + " started a connection");
    for (int i = 0; i < 1000; i++) {
    p.send(session.createTextMessage());
    System.out.println("FinishedRunning:" + Thread.currentThread().getId());
    catch (JMSException e) {
    e.printStackTrace();
    finally {
    if (p != null) {
    try {
    p.close();
    catch (JMSException e) {
    e.printStackTrace();
    if (session != null) {
    try {
    session.close();
    catch (JMSException e) {
    e.printStackTrace();
    if (conn != null) {
    try {
    conn.close();
    catch (JMSException e) {
    e.printStackTrace();
    catch (Exception e) {
    e.printStackTrace();
    Edited by: svachary on Jan 8, 2009 1:01 PM

    Hi,
    I would suggest you to go through these 2 links which you give all the details about UDD
    Topic:Steps to Configure Uniform Distributed Queue (UDQ) on Weblogic Server
    http://middlewaremagic.com/weblogic/?p=3747
    Topic:JMS Demo using WebLogic Uniform Distributed Queue (UDQ)
    http://middlewaremagic.com/weblogic/?page_id=1976
    Tips to solve UDQ issues
    - Make sure the Server Affinity Enabled parameter should be un-checked (disable) which under the [ Connection factory –> Configuration (tab) –> Load Balance (sub-tab)]
    - Disable the Server Affinity Enabled parameter for the connection factory whish is been used by your UDQ.
    - All the managed servers are in the same cluster.
    - If the managed serves are in different boxes make sure the listing address is given correctly which is under [ Machine –> Configuration (tab) –> Node Manager (sub-tab) ]
    - Test if you are able to PING the servers on different boxes and make sure that there is no network issues and you are able to communicate with the servers.
    Hope this helps you.
    Regards,
    Ravish Mody
    http://middlewaremagic.com/weblogic/
    Come, Join Us and Experience The Magic…

  • Error occurred while forwarding a message for distributed destination

    Is there a change in the way that Uniform Distributed Destinations are handled in the cluster after weblogic9.2?
    I am using oracle weblogic 10.3.0.1 in production mode. I have two managed servers, each managed server has a JMS Server.
    I create a Uniform distributed Topic on the System module, and publish a message to it.
    I can see the message in the topic on the first JMSServer but the following error happens and the message never makes it to the second JMSServer
    <Sep 24, 2009 2:00:45 PM GMT+00:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <Sep 24, 2009 2:00:45 PM GMT+00:00> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
    <Sep 24, 2009 2:00:45 PM GMT+00:00> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on IP:PORT for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
    <Sep 24, 2009 2:00:45 PM GMT+00:00> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "ManSvr1" for domain "Domain" running in Production Mode>
    <Sep 24, 2009 2:00:46 PM GMT+00:00> <Notice> <Cluster> <BEA-000102> <Joining cluster Clus on mip:mport>
    <Sep 24, 2009 2:00:47 PM GMT+00:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Sep 24, 2009 2:00:47 PM GMT+00:00> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Sep 24, 2009 2:09:52 PM GMT+00:00> <Warning> <JMS> <BEA-040498> <An error occurred while forwarding a message for distributed destination member JMSSystemResource!JMSServer2@example: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Could not establish a connection with 8935413426058515615S:fqhn:[-1,-1,sslport,sslport,-1,-1,-1]:Domain:ManSvr2, java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):fqhn:nonsslport:null:-1'; No available router to destination; nested exception is:
         java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):fqhn:nonsslport:null:-1'; No available router to destination; nested exception is:
         java.rmi.ConnectException: Could not establish a connection with 8935413426058515615S:fqhn:[-1,-1,sslport,sslport,-1,-1,-1]:Domain:ManSvr2, java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):fqhn:nonsslport:null:-1'; No available router to destination; nested exception is:

    I specified the cluster address, but still get the following errors after a message is published to the topic. Are there other configuration items that can be checked?
    <Sep 29, 2009 9:51:49 AM GMT+00:00> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Sep 29, 2009 9:52:01 AM GMT+00:00> <Notice> <Server> <BEA-002613> <Channel "DefaultAdministration" is now listening on 10.241.134.92:7018
    for protocols admin, CLUSTER-BROADCAST-SECURE, ldaps, https.>
    <Sep 29, 2009 9:53:26 AM GMT+00:00> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 10.241.134.92:7019 for
    protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
    <Sep 29, 2009 9:53:26 AM GMT+00:00> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "ClusManSv
    r2" for domain "domain" running in Production Mode>
    <Sep 29, 2009 9:53:26 AM GMT+00:00> <Notice> <Cluster> <BEA-000102> <Joining cluster Clus on 224.0.0.10:7390>
    <Sep 29, 2009 9:53:27 AM GMT+00:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Sep 29, 2009 9:53:27 AM GMT+00:00> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Sep 29, 2009 9:56:14 AM GMT+00:00> <Warning> <JMS> <BEA-040498> <An error occurred while forwarding a message for distributed destinati
    on member SOAFJMSSystemResource!SOAFJMSServer1@EventingAdminTopic: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteExc
    eption: Could not establish a connection with 5660061832836428941S:managedServer.net:[-1,-1,7017,7017,-1,-1,-1]:testnn
    2092.net:domain:ClusManSvr1, java.rmi.ConnectException: No known valid port for: 'Def
    ault[t3]:t3(t3):managedServer.net:7018:null:-1'; No available router to destination; nested exception is:
    java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No ava
    ilable router to destination; nested exception is:
    java.rmi.ConnectException: Could not establish a connection with 5660061832836428941S:managedServer.net:[-1,-1,1
    1217,7017,-1,-1,-1]:managedServer.net:domain:ClusManSvr1, java.rmi.ConnectException: No
    known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No available router to destination; nested
    exception is:
    java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No ava
    ilable router to destination
    weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Could not establish a connection with 5660061832836428941S:
    managedServer.net:[-1,-1,7017,7017,-1,-1,-1]:managedServer.net:domain:
    ClusManSvr1, java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; N
    o available router to destination; nested exception is:
    java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No ava
    ilable router to destination; nested exception is:
    java.rmi.ConnectException: Could not establish a connection with 5660061832836428941S:managedServer.net:[-1,-1,1
    1217,7017,-1,-1,-1]:managedServer.net:domain:ClusManSvr1, java.rmi.ConnectException: No
    known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No available router to destination; nested
    exception is:
    java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No ava
    ilable router to destination
    at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchAsync(DispatcherWrapperState.java:158)
    at weblogic.jms.dispatcher.DispatcherAdapter.dispatchAsync(DispatcherAdapter.java:84)
    at weblogic.jms.backend.BEForwardingConsumer$1.run(BEForwardingConsumer.java:503)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.jms.backend.BEForwardingConsumer.processMessages(BEForwardingConsumer.java:499)
    Truncated. see log file for complete stacktrace
    java.rmi.RemoteException: Could not establish a connection with 5660061832836428941S:managedServer.net:[-1,-1,7017,701
    7,-1,-1,-1]:managedServer.net:domain:ClusManSvr1, java.rmi.ConnectException: No known v

  • Federated Portal Network - Unexpected Error - Unable to get IView

    Hallo.
    I have this problem: I have two portal federated.
    When I create an iView BI7.0 from the consumer portal , that points to the producer portal , when I execute it I obtain the error :
    500 Internal Server Error
      BEx Web Application
    Failed to process request; contact your system administrator
    Error Summary
    Exception occured while processing the current request; this exception cannot be handled by the application or framework
    If the information on this page does not help you locate and correct the cause of the problem, contact your system administrator
    To facilitate analysis of the problem, keep a copy of this error page Hint: Most Web browsers allow you to select all content, and copy and paste it into an empty document (such as in an email or simple text file)
    Root Cause
    The initial exception that caused the request to fail was:
    Unexpected error - Unable to get IView: fpn:consumer_ABC/pcd:portal_content/com.abc.AbcFolder/zcitbi70/worksetBI70/Prova/sottoprova/BI7ReportProgetti:lQ9fUQ0dfID4PPyUU4cpZg%3D%3D:1:
    Note that I am able to see the iview, role etc from consumer to producer, so the Federated Portal Network seems to work.
    What could I do ?
    Thanks for your help
    Mario

    Hi Experts,
    I am getting below error in logs. Some of the reports working and some of the are not working. I can see below error in BW system logs. Any inputs to solve this issue is much appreciated.
    java.io.IOException: Cannot establish connection with any of the profiles.
    ID 011006:Rmi_P4 Dispatcher: Can't open socket
    Error while processing the request in a BI application; see SAP Notes 937697 and 948490
    Exception caught: com.sapportals.portal.prt.runtime.PortalRuntimeException: Unexpected error - Unable to get IView: fpn:PP2_IS_CONSUMER_FOR_PB1/pcd:portal_content/com.sw1.intranet.staff/com.sw1.intranet.staff.bi/com.sw1.intranet.staff.bi.roles/com.sw1.intranet.staff.bi.hr.roles.headcount_reports/com.sw1.intranet.staff.srm.worksets.reports/com.sw1.intranet.staff.bi.hr.parentws.headcount_reports/com.sw1.intranet.staff.bi.hr.ws.headcount_reports/com.sw1.intranet.staff.bi.hr.iviews.headcount:hNsfu%2FSQ7LTdTmfpBwd7qQ%3D%3D:1:
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Unexpected error - Unable to get IView: fpn:PP2_IS_CONSUMER_FOR_PB1/pcd:portal_content/com.sw1.intranet.staff/com.sw1.intranet.staff.bi/com.sw1.intranet.staff.bi.roles/com.sw1.intranet.staff.bi.hr.roles.headcount_reports/com.sw1.intranet.staff.srm.worksets.reports/com.sw1.intranet.staff.bi.hr.parentws.headcount_reports/com.sw1.intranet.staff.bi.hr.ws.headcount_reports/com.sw1.intranet.staff.bi.hr.iviews.headcount:hNsfu%2FSQ7LTdTmfpBwd7qQ%3D%3D:1:
         at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1960)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:234)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
         at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
         at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._createRequestParameters(BIRuntimeService.java:397)
         at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.createRequestParameters(BIRuntimeService.java:379)
         at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._handleRequest(BIRuntimeService.java:303)
         at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:250)
         at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:24)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
         at java.security.AccessController.doPrivileged(AccessController.java:246)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.portal.fpn.exception.base.unchecked.FpnCommunicationException: Could not retrieve the bean / access service to connect with consumer 'PP2_IS_CONSUMER_FOR_PB1'
         at com.sap.portal.fpn.entrypoint.FederatedPersistanceUtils.getAccessServiceByConsumerName(FederatedPersistanceUtils.java:169)
         at com.sap.portal.fpn.entrypoint.RuntimeFederatedPersistance.retrieveDLRemoteState(RuntimeFederatedPersistance.java:92)
         at com.sap.portal.fpn.FpnRuntimeService.bringRemoteState(FpnRuntimeService.java:134)
         at com.sap.portal.fpn.FpnRuntimeService.doFpnLookup(FpnRuntimeService.java:97)
         at com.sap.portal.fpnprovider.fpn.GenericContext.lookup(GenericContext.java:49)
         at javax.naming.InitialContext.lookup(InitialContext.java:361)
         at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1919)
         ... 40 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances
         Nested exceptions are:
         com.sap.engine.services.rmi_p4.exception.P4BaseIOException: Cannot open connection on host: and port:
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:455)
         at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:65)
         at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:46)
         at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:675)
         at com.sapportals.portal.prt.jndisupport.NamingManager.getInitialContext(NamingManager.java:50)
         at com.sapportals.portal.prt.jndisupport.InitialContext.getDefaultInitCtx(InitialContext.java:39)
         at javax.naming.InitialContext.init(InitialContext.java:233)
         at javax.naming.InitialContext.<init>(InitialContext.java:209)
         at com.sapportals.portal.prt.jndisupport.InitialContext.<init>(InitialContext.java:24)
         at com.sap.portal.fpn.entrypoint.FederatedPersistanceUtils.getAccessServiceByConsumerName(FederatedPersistanceUtils.java:159)
         ... 46 more
    Caused by: com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances
         Nested exceptions are:
         com.sap.engine.services.rmi_p4.exception.P4BaseIOException: Cannot open connection on host: and port:
         at com.sap.engine.interfaces.cross.Destination.getNextAvailableBroker(Destination.java:55)
         at com.sap.engine.interfaces.cross.Destination.getRemoteBroker(Destination.java:35)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:340)
         ... 56 more

  • Unexpected error - Unable to get IView

    Hi,
    I have configured FPN with EP and BI, both are on same SP level.The connection and the producer registration is successful.The producer contents can be navigated in Consumer and am able to copy and paste the producer content in the consumer.But when i preview the content it shows error "Unexpected error - Unable to get IView".
    Regards,
    Adity.

    The error i get in default trace is :
    #1.#000D60F4797A0074000008D70007A25E0004765974FE319B#1256026493825#com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService#sap.com/irj#com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService#TCSADITY#35321##n/a##06dc0750bd5011de9049000d60f4797a#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#/Applications/BI#Plain###Exception caught: com.sapportals.portal.prt.runtime.PortalRuntimeException:
    Unexpected error - Unable to get IView:
    fpn:ddsa/pcd:portal_content/com.pnb.test/gh/iu/com.pnb.test3:pgyy6PHtBJ0B4Z62g5CvLg%3D%3D:1:
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Unexpected error - Unable to get IView: fpn:ddsa/pcd:portal_content/com.pnb.test/gh/iu/com.pnb.test3:pgyy6PHtBJ0B4Z62g5CvLg%3D%3D:1:
            at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1960)
            at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:234)
            at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
            at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
            at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._createRequestParameters(BIRuntimeService.java:428)
            at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.createRequestParameters(BIRuntimeService.java:405)
            at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._handleRequest(BIRuntimeService.java:329)
            at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:276)
            at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:24)
            at com.sapportals.portal.prt.component.AbstractPortalComponent.doPreview(AbstractPortalComponent.java:240)
            at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:168)
            at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
            at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
            at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
            at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
            at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
            at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
            at java.security.AccessController.doPrivileged(AccessController.java:241)
            at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
            at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
            at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
            at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
            at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
            at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
            at java.security.AccessController.doPrivileged(AccessController.java:214)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.portal.fpn.exception.base.unchecked.FpnCommunicationException: Could not retrieve the bean / access service to connect with consumer 'ddsa'
            at com.sap.portal.fpn.entrypoint.FederatedPersistanceUtils.getAccessServiceByConsumerName(FederatedPersistanceUtils.java:169)
            at com.sap.portal.fpn.entrypoint.RuntimeFederatedPersistance.retrieveDLRemoteState(RuntimeFederatedPersistance.java:92)
            at com.sap.portal.fpn.FpnRuntimeService.bringRemoteState(FpnRuntimeService.java:134)
            at com.sap.portal.fpn.FpnRuntimeService.doFpnLookup(FpnRuntimeService.java:97)
            at com.sap.portal.fpnprovider.fpn.GenericContext.lookup(GenericContext.java:49)
            at javax.naming.InitialContext.lookup(InitialContext.java:361)
            at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1919)
            ... 41 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances
            Nested exceptions are:
            com.sap.engine.services.rmi_p4.exception.P4BaseIOException: Cannot make connection.
            at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:455)
            at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:65)
            at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:46)
            at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
            at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:675)
            at com.sapportals.portal.prt.jndisupport.NamingManager.getInitialContext(NamingManager.java:50)
            at com.sapportals.portal.prt.jndisupport.InitialContext.getDefaultInitCtx(InitialContext.java:39)
            at javax.naming.InitialContext.init(InitialContext.java:233)
            at javax.naming.InitialContext.<init>(InitialContext.java:209)
            at com.sapportals.portal.prt.jndisupport.InitialContext.<init>(InitialContext.java:24)
            at com.sap.portal.fpn.entrypoint.FederatedPersistanceUtils.getAccessServiceByConsumerName(FederatedPersistanceUtils.java:159)
            ... 47 more
    Caused by: com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances
            Nested exceptions are:
            com.sap.engine.services.rmi_p4.exception.P4BaseIOException: Cannot make connection.
            at com.sap.engine.interfaces.cross.Destination.getNextAvailableBroker(Destination.java:55)
            at com.sap.engine.interfaces.cross.Destination.getRemoteBroker(Destination.java:35)
            at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:340)
            ... 57 more
    #1.#000D60F4797A0074000008D90007A25E0004765974FE36CD#1256026493826#com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService#sap.com/irj#com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService#TCSADITY#35321##n/a##06dc0750bd5011de9049000d60f4797a#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#/Applications/BI#Plain###Error while processing the request in a BI application; see SAP Notes 937697 and 948490#
    0

  • JMS Distributed Destinations as proxy service endpoints

    We have a cluster of 2 ALSB servers with a proxy service deployed
    listening on a JMS queue which is a distributed destination (DD) on a
    WLS 8.1 system.
    The JMS DD is spread across 4 JMS servers and 4 JVM's.
    When ALSB starts up - we only get consumers on 2 of the 4 DD members,
    which makes sense as a JMS proxy service is essentially an MDB, and this
    is normal MDB/distributed destination behaviour - it will bind to the
    queue member where it first makes the connection to the JVM.
    How do I make sure my messages are consumed from all 4 DD queue members?
    There is a JMS option to forward messages to queues with consumers if no
    consumers exist - is that the way to do it?
    Someone must have come across this before and I'd be grateful for any
    advice.
    Also - how do you reduce the consumers on the JMS queue - seems to
    default to 16. Perhaps you don't.
    Thanks,
    Pete

    Meghan Pietila wrote:
    Update: I see your exchange with Tom over on the JMS forum, Pete. We just switched everything to WLS 9.2, so maybe the ALSB internal extension will work for us. It's not working by default, so possibly it's something that must be activated... I'll follow up with BEA.
    http://forums.bea.com/thread.jspa?threadID=570001317
    I'd still like to hear what you end up working with, if you don't mind sharing once it's running. :)
    MeghanI only have 8.1 as an option - a JMS proxy service is essentially an
    MDB, and if you deploy an MDB in the same way, it will only bind to a
    single destination, so it's actually behaving as I would expect.
    The forward delay on the queue probably won't be an issue for us, as
    we're not talking about high volumes and large messages, but for some
    sites there will be alot of moving around queues, access jms filestore
    etc which you could do without.
    I reckon the trick is (as Tom mentioned) to bind to individual
    distributed queue members from the proxy service somehow.
    I'll let you know what I find out.
    Pete

  • Name of Server using Distributed Destination

              Is there a way to get the name of the server thats consuming my JMS Messages when
              using a Distributed Destination? Basically i have a distributed queue configured
              across two servers in a cluster using Round-robin. I just wanted to see which
              server is being used when i send in my messages.
              Thanks
              Raj
              

    You can verify round-robin behavior by looking
              at the statistics of the distributed
              destination's component physical destinations.
              Raj wrote:
              > Is there a way to get the name of the server thats consuming my JMS Messages when
              > using a Distributed Destination? Basically i have a distributed queue configured
              > across two servers in a cluster using Round-robin. I just wanted to see which
              > server is being used when i send in my messages.
              >
              > Thanks
              > Raj
              

  • Oracle 11i release 2 error "Unable to get the current group"

    Hi oracle gurus,
         I have been trying to install oracle 11g rel 2 on HPUX 11.31 and i am getting the following error
    # more installActions2010-01-06_10-27-37AM.log
    oracle.install.ivw.db.driver.DBInstaller
    -scratchPath
    /u01/tmp/OraInstall2010-01-06_10-27-37AM
    -sourceLoc
    /u01/install/database/install/../stage/products.xml
    -sourceType
    network
    -timestamp
    2010-01-06_10-27-37AM
    INFO: Loading data from: jar:file:/u01/tmp/OraInstall2010-01-06_10-27-37AM/ext/jlib/installcommons_1.0.0b.jar!/oracle/install/driver/oui/resource/ConfigComma
    ndMappings.xml
    INFO: Loading beanstore from jar:file:/u01/tmp/OraInstall2010-01-06_10-27-37AM/ext/jlib/installcommons_1.0.0b.jar!/oracle/install/driver/oui/resource/ConfigC
    ommandMappings.xml
    INFO: Restoring class oracle.install.driver.oui.ConfigCmdMappings from jar:file:/u01/tmp/OraInstall2010-01-06_10-27-37AM/ext/jlib/installcommons_1.0.0b.jar!/
    oracle/install/driver/oui/resource/ConfigCommandMappings.xml
    SEVERE: [FATAL] An internal error occurred within cluster verification framework
    Unable to get the current group.
    Refer associated stacktrace #oracle.install.commons.util.exception.DefaultErrorAdvisor:11
    INFO: Advice is ABORT
    SEVERE: Unconditional Exit
    INFO: Adding ExitStatus FAILURE to the exit status set
    INFO: Finding the most appropriate exit status for the current application
    INFO: Exit Status is -1
    INFO: Shutdown Oracle Database 11g Release 2 Installer
    $
    >>
    # more oraInstall2010-01-06_10-27-37AM.err
    ---# Begin Stacktrace #---------------------------
    ID: oracle.install.commons.util.exception.DefaultErrorAdvisor:11
    oracle.cluster.verification.VerificationException: An internal error occurred within cluster verification framework
    Unable to get the current group
    at oracle.cluster.verification.ClusterVerification.<init>(ClusterVerification.java:200)
    at oracle.cluster.verification.ClusterVerification.getInstance(ClusterVerification.java:294)
    at oracle.install.driver.oui.OUISetupDriver.load(OUISetupDriver.java:407)
    at oracle.install.ivw.db.driver.DBSetupDriver.load(DBSetupDriver.java:161)
    at oracle.install.commons.base.driver.common.Installer.run(Installer.java:216)
    at oracle.install.ivw.db.driver.DBInstaller.run(DBInstaller.java:126)
    at oracle.install.commons.util.Application.startup(Application.java:869)
    at oracle.install.commons.flow.FlowApplication.startup(FlowApplication.java:164)
    at oracle.install.commons.flow.FlowApplication.startup(FlowApplication.java:181)
    at oracle.install.commons.base.driver.common.Installer.startup(Installer.java:265)
    at oracle.install.ivw.db.driver.DBInstaller.startup(DBInstaller.java:114)
    at oracle.install.ivw.db.driver.DBInstaller.main(DBInstaller.java:132)
    ---# End Stacktrace #-----------------------------
    <<
    $ uname -a
    HP-UX rx2600 B.11.31 U ia64 <XXXXXXXX> unlimited-user license
    # swlist | grep -i oe
    HP-Caliper-PERF C.11.31.04 HP Caliper OE Bundle
    HP-WDB-DEBUGGER C.11.31.04 HP DEBUGGER OE Bundle
    HPUX11i-DC-OE B.11.31.0903 HP-UX Data Center Operating Environment
    # swlist | grep -i qpk
    QPKBASE B.11.31.0903.334a Base Quality Pack Bundle for HP-UX 11i v3, March 2009
    # swlist -l product | grep -i c++
    ACXX C.06.20 HP C/aC++ Compiler
    C-ANSI-C C.06.20 HP C/aC++ Compiler
    PHSS_37501 1.0 aC++ Runtime (IA: A.06.16, PA: A.03.76)
    PHSS_39824 1.0 HP C/aC++ Compiler (A.06.23)
    i start the installation as oracle and my group and user id is
    $ id
    uid=109(oracle) gid=102(oinstall) groups=101(dba),104(asmdba)
    Please let me know what else do i need, we might have to use the hardware for testing another application so i am limited in terms of time constraints
    any help is much appreciated, Thank you!!
    Regards,
    Dasjith
    Edited by: user10247524 on Jan 6, 2010 7:52 AM

    Hi Stig Sundqvist
    Where can i find MOS Doc 983713.1 ??You have to login https://support.oracle.com/CSP/ui/flash.html and you have to CSI account. This site is oracle site for tech. documents for can rise SR etc.. for more details please check
    What is CSI:
    Re: Installing Oracle Database 10.2.0.4
    And how do i do to fix this problem ????Login metalink then find upper note and follow document
    Hope it helps
    Regard
    Helios

  • [WLST offline]: Cannot create distributed destination

    We have a small problem with WLST and distributed destinations. I have made the following code:
    readDomain ('< our domain path >/Demo8')
    # Check that the queue exists
    ls ('/JMSServer/cgJMSServer1/JMSQueue')
    create ('myQueue1','JMSDistributedQueue')
    cd ('JMSDistributedQueue')
    cd ('myQueue1')
    set ('JNDIName','myjndi')
    create ('member1','JMSDistributedQueueMember')
    cd ('JMSDistributedQueueMember')
    cd ('member1')
    set ('JMSQueue','queue1')
    cd ('..')
    cd ('..')
    UpdateDomain()
    The problems is, that the command "set ('JMSQueue','queue1')" fails.
    Does anyone have an example of a successful WLST configuration of Distributed Destinations?
    The error message from my script is:
    Error: setJMSQueue() failed.
    Error: set() failed.
    Traceback (innermost last):
    File "scr.py", line 19, in ?
    File "initWls.py", line 46, in set
    com.bea.plateng.domain.script.jython.WLSTException: java.lang.reflect.Invocation
    TargetException
    at com.bea.plateng.domain.script.jython.CommandExceptionHandler.handleEx
    ception(CommandExceptionHandler.java:33)
    Your help will really be appreciated....
    Kind regards,
    Henrik

    The best way to create distributed destinations is to create physical destinations in single server mode and then create more servers and a cluster. wlst offline will automatically create distribued destinations and members. Considering that the recommended JMS architecture is homogeneous, there is little need to do it manually. An example:
    readTemplate('c:/bea813/weblogic81/common/templates/domains/medrec.jar')
    cd('JMSServer/MedRecJMSServer')
    q=create('newQueue', 'JMSQueue')
    q.setJNDIName('newQueue')
    cd('/')
    create('newServer1', 'Server')
    create('newServer2', 'Server')
    create('newCluster', 'Cluster')
    assign('Server', 'newServer1,newServer2', 'Cluster', 'newCluster')
    writeDomain('d:/temp/domains/813/medrec/medrec_0720')
    closeTemplate();

  • ERROR ORA-12203: TNS: unable to connect to destination

    Hello All,
    I have installed Oracle 8i and forms 6i on my computer running on Windows NT 4.0 with service pack 4.0. The order of my installation was Oracle 8i and then Forms 6i. I have also used Net8 Easy Config to configure the tnsnames.ora file. I tested the connection on the Net8 Easy Config wizzard and I got the connection successful message. However I still get the ERROR ORA-12203: TNS: unable to connect to destination message when I tried to connect from forms 6i.
    I have below my tnsnames.ora file:
    # C:\FORMS6I\NET80\ADMIN\TNSNAMES.ORA Configuration File:C:\forms6i\net80\admin\tnsnames.ora
    # Generated by Oracle Net8 Assistant
    LISTENER1 =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = austin)(PORT = 1521))
    (CONNECT_DATA = (SID = SUN))
    Rep60_AUSTIN-Forms6i,Rep60_AUSTIN-Forms6i.world=(ADDRESS=(PROTOCOL=tcp)(HOST=AUSTIN)(PORT=1949))
    I have created database objects, but forms will not connect. What else should do?
    Thanks for your anticipated response.

    Hi
    Your oracle database and forms are installed on different oracle home so when you configurate your sql net that time you are configurating only your oracle database. So for form you must be having different oracle home. you cand change thid from start/oracle inatallation products/home selecter. so change our home and run the form. and if still having problem than check for tnsnames.ora file you must be having two files and both must be having right configuration.
    thanks

  • SPROXY unable to get Interface meta-data from XI Server

    Hi,
    In our SAP R/3 Enterprise system, the transaction SPROXY complains that "No connection to Integration Builder (only local data visible)".  It is unable to get the message interfaces defined in the SAP XI Server.
    Connection to SLD is configured correctly, and transaction SLDCHECK works correctly.
    Where can I configure the SAP R/3 system so that it can retrieve the message interfaces from SAP XI system ?
    thanks,
    Manish

    Hi Manish -
    Did you maintain the RFC destinations LCRSAPRFC and SAPSLDAPI?  And the corresponding J2EE connections?  These must be completed in addition to other possible configurations.
    Please check XI 3.0 Configuration Guide, section 8 (Connecting Business Systems with an Integration Engine to the Central Integration Server).  These have all the necessary steps.
    Regards,
    Jin

Maybe you are looking for