7 Replies Latest reply: Aug 29, 2012 5:40 AM by Ikhan RSS

    error occurred while forwarding a message for distributed destination

    724741
      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:
        • 1. Re: error occurred while forwarding a message for distributed destination
          641965
          Judging from the following:

          <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: 'Defaultt3:t3(t3):fqhn:nonsslport:null:-1'; No available router to destination; nested exception is:
          java.rmi.ConnectException: No known valid port for: 'Defaultt3:t3(t3):fqhn:nonsslport:null:-1'; No available router to destination; nested exception is

          I believe you have set up something wrong, either in Cluster configuration or the managed server. In place of sslport, nonsslport etc, I think you should have real values. These look like dummy values. Also, check fqhn, this seems like a dummy value as well.

          In Cluster, have you configured the t3 cluster address properly?
          • 2. Re: error occurred while forwarding a message for distributed destination
            724741
            dvm, Mea Culpa, I should have noted that the host names and ports were sanitized out.

            Thanks for pointing out the cluster address.
            I will configure the cluster address appropriately.
            The cluster had been configured with the "Number of Servers in Cluster Address" property but no cluster address explicitly.
            • 3. Re: error occurred while forwarding a message for distributed destination
              724741
              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
              • 4. Re: error occurred while forwarding a message for distributed destination
                724741
                ensure the default-protocol is set correctly
                • 5. Re: error occurred while forwarding a message for distributed destination
                  user12951153
                  Hello,

                  What exactly is the solution of the problem?

                  I have the same problem in WLS 10.3.0. My standalone client calls an ejb via two-way t3s. The ejb sends a message to a distributed topic, but during the distribution of message between topics the error below occurs. When the standalone client calls the ejb via t3 then the error does not occur.

                  Thank you.

                  <05.08.2010 11.02 Uhr CEST> <Warning> <JMS> <BEA-040498> <An error occurred while forwarding a message for distributed de
                  stination member JMSModule!JMS_Server_2@HelloTopic: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteExc
                  eption: Could not establish a connection with -1214476631860181442S:10.77.53.71:[7007,7007,-1,-1,-1,-1,-1]:oracle_case_do
                  main:ManagedServer_2, java.rmi.ConnectException: No known valid port for: 'DefaultSecure[t3s]:t3s(t3s):null:7005:10.77.53
                  .71:-1'; No available router to destination; nested exception is:
                  java.rmi.ConnectException: No known valid port for: 'DefaultSecure[t3s]:t3s(t3s):null:7005:10.77.53.71:-1'; No av
                  ailable router to destination; nested exception is:
                  java.rmi.ConnectException: Could not establish a connection with -1214476631860181442S:10.77.53.71:[7007,7007,-1,
                  -1,-1,-1,-1]:oracle_case_domain:ManagedServer_2, java.rmi.ConnectException: No known valid port for: 'DefaultSecure[t3s]:
                  t3s(t3s):null:7005:10.77.53.71:-1'; No available router to destination; nested exception is:
                  java.rmi.ConnectException: No known valid port for: 'DefaultSecure[t3s]:t3s(t3s):null:7005:10.77.53.71:-1'; No av
                  ailable router to destination
                  weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Could not establish a connection with -12144
                  76631860181442S:10.77.53.71:[7007,7007,-1,-1,-1,-1,-1]:oracle_case_domain:ManagedServer_2, java.rmi.ConnectException: No
                  known valid port for: 'DefaultSecure[t3s]:t3s(t3s):null:7005:10.77.53.71:-1'; No available router to destination; nested
                  exception is:
                  java.rmi.ConnectException: No known valid port for: 'DefaultSecure[t3s]:t3s(t3s):null:7005:10.77.53.71:-1'; No av
                  ailable router to destination; nested exception is:
                  java.rmi.ConnectException: Could not establish a connection with -1214476631860181442S:10.77.53.71:[7007,7007,-1,
                  -1,-1,-1,-1]:oracle_case_domain:ManagedServer_2, java.rmi.ConnectException: No known valid port for: 'DefaultSecure[t3s]:
                  t3s(t3s):null:7005:10.77.53.71:-1'; No available router to destination; nested exception is:
                  java.rmi.ConnectException: No known valid port for: 'DefaultSecure[t3s]:t3s(t3s):null:7005:10.77.53.71:-1'; No av
                  ailable 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
                  • 6. Re: error occurred while forwarding a message for distributed destination
                    user10429365
                    Did we get solution to this problem. We are also facing same issue.
                    • 7. Re: error occurred while forwarding a message for distributed destination
                      Ikhan
                      did any one get solution to this problem? , i am also facing the same issue.