Distributed destination with MQ as Foreign Provider

Hi
Messages arrive in a set of clustered MQ Series Queues. MDBs process the messages (We use MQ as the Foreign JMS Provider). Can I set up a distributed destination (JMS Queues) in WebLogic and use those clustered MQ queues as the Foreign Provider ? I would like the MQ Series clustering to provide the redundancy/availability of the MQ Series system and the JMS distributed destination to provide high availability for the MDBs that are hosted in a set of clustered WebLogic server instances.
Thanks

Hi          > Messages arrive in a set of clustered MQ Series
          > Queues. MDBs process the messages (We use MQ as the
          > Foreign JMS Provider). Can I set up a distributed
          > destination (JMS Queues) in WebLogic and use those
          > clustered MQ queues as the Foreign Provider ?
          No. WL distributed destinations consist only of a set of physical WL destinations. The WL distributed destination code does not support non-WL destinations.
          > I would
          > like the MQ Series clustering to provide the
          > redundancy/availability of the MQ Series system and
          > the JMS distributed destination to provide high
          > availability for the MDBs that are hosted in a set of
          > clustered WebLogic server instances.
          If MQ Series exposes its distributed destination via the standard JMS API, then the MDBs will automatically run as MQ distributed dest clients. This is a function of MQ, not WL -- WL MDBs simply use the standard JMS API of the vendor's supplied client to get their messages.
          But note that WL MDBs use a single connection per MDB pool/deployment. Some clustering implementations (MQ?) require using multiple connections...
          >
          > Thanks

Similar Messages

Using Messaging Bridge with Distributed Destinations

I'm having some problems using Distributed Destinations with the Messaging Bridge in WLS 7.0sp2. Our configuration consists of the following:
          * WLS Server1:
          * JMS Server1:
          * inbound queue
          * outbound queue
          * JMS Server2:
          * inbound queue
          * outbound queue
          * WLS Server 2:
          * JMS Server3:
          * inbound queue
          * outbound queue
          A distributed destination is configured for the inbound and outbound queues.
          Two messaging queues are configured so that bridge from WLS JMS to Tibco JMS using the distributed destinations.
          Everything is working fine for the inbound, but we have found that the outbound messaging bridge is picking up messages from only one of the two JMS servers on the first WLS instance. When monitoring, it can be seen that there is no consumer registered against the second JMS server.
          Any suggestions?


Hi Rob,
          Consumers on distributed destinations are always pinned
          to a single physical destination on creation. Only
          producers can round-robin each message. When a
          distributed destination is used as a source destination,
          you will need to configure a bridge per distributed
          destination. Alternatively, you can enable
          forwarding between the physical queues, which automatically
          forwards messages from physical queues with
          no consumers to physical queues that have consumers
          (but the extra hop impacts performance). For more information,
          consult the JMS documentation.
          Tom
          Rob McArthur wrote:
          > I'm having some problems using Distributed Destinations with the Messaging Bridge in WLS 7.0sp2. Our configuration consists of the following:
          > * WLS Server1:
          > * JMS Server1:
          > * inbound queue
          > * outbound queue
          > * JMS Server2:
          > * inbound queue
          > * outbound queue
          > * WLS Server 2:
          > * JMS Server3:
          > * inbound queue
          > * outbound queue
          >
          > A distributed destination is configured for the inbound and outbound queues.
          >
          > Two messaging queues are configured so that bridge from WLS JMS to Tibco JMS using the distributed destinations.
          >
          > Everything is working fine for the inbound, but we have found that the outbound messaging bridge is picking up messages from only one of the two JMS servers on the first WLS instance. When monitoring, it can be seen that there is no consumer registered against the second JMS server.
          >
          > Any suggestions?
          >
          >

JMS Foreign Provider using XAConnectionFactory for Container Managed Trans

Hello, we've been running some proof of concepts using Weblogic 10.3 with a JMS Foreign Provider attached to MQSeries 7.
We created a very simple MDB to read a message and output it's content.
We created a bindings file with a Connection Factory (without XA)
The question I have is that when I set the Transaction Management to Container and Transaction Attribute to "Required" , does Weblogic automatically look for a XAQueueConnectionFactory? We get the error below:
[EJB:011013]The Message-Driven EJB attempted to connect to the JMS connection factory with the JNDI name: OP_CF. However, the object with the JNDI name: OP_CF is not a JMS connection factory. NestedException Message is :com.ibm.mq.jms.MQQueueConnectionFactory cannot be cast to javax.jms.XAConnectionFactory>
When we set the transacation to Bean Managed or we set to Container Managed but set the attribute to "NotSupported" it works fine.
My goal is to have a MDB that has Container Managed Transactions and "Requires" Attribute, but only particpates in a local transaction and does not need the overhead of XA. It will read from a Foreign MQ manager Queue, process and then write back to the same Foreign MQ manager(different queue), so only one resource (MQ) is used.
If we set the above settings, it seems that a XAConnectionFactory is required. Is that true?

-- If you do not enable the container transaction, then the MDB connection factory does not need to be an XA connection factory.
-- If the application is performing messaging operations, and wants to use locally managed transactions, then you have a variety of options. These are all standard JMS:
* Use an XA connection and XA session. Begin JTA transactions before performing JMS operations, and call commit or rollback on the JTA transaction after performing the JMS operations. For foreign vendors, you must take extra steps to ensure that the vendor enlists with the WebLogic transaction -- typically by using WebLogic resource reference wrappers.
* Use the standard JMS API "transacted session" on a non-XA session -- the transaction will be local to the session (this is extremely similar to JDBC local transactions).
* Use a non-transacted session. Sends will occur immediately. Receive messages will be acknowledged immediately for auto-ack sessions, or will not for non-ack.
-- Note that if a transaction only includes a single operation, there's no need for XA or non-transacted sessions.
-- For more information on transactions and integration, I highly recommend reading our [ Integrating Remote JMS Providers | http://download.oracle.com/docs/cd/E15523_01/web.1111/e13727/interop.htm#JMSPG553 ] FAQ. I also very highly recommend purchasing a copy of [ Professional Oracle WebLogic Server | http://www.amazon.com/Professional-Oracle-WebLogic-Server-Patrick/dp/0470484306/ref=sr_1_1?ie=UTF8&s=books&qid=1252088885&sr=8-1 ], and of course reviewing our [ JMS Information Roadmap | http://download.oracle.com/docs/cd/E15523_01/web.1111/e14529/messaging.htm#sthref23 ].
-- Finally, you may also want to consider replacing some MQ usage with WebLogic JMS. WL JMS is a heavily adopted messaging vendor, and for obvious reasons, tends to integrate especially well with the WebLogic app server.
Hope this helps,
Tom

JMS Failover with Distributed Destinations in 7.0

          How does JMS failover with distributed destinations in WL 7.0?
          In an environment using file stores for persistent messages, can a working server
          automatically pick up unprocessed and persisted messages from a failed server?
          If so, what's the best way to set this up?
          Or, is this completely manual? In other words, we have to bring up a new server
          pointing to the location of the file store from the failed server?


          It appears that two JMSServers cannot share the same file store and, I'm assuming,
          two file stores cannot be using the same directory for persistence.
          So the HA you're talking about is something like Veritas automatically restarting
          a server (or starting a new one) to process the messages in the persistent queue
          that were unprocessed at the time of failure with the file store residing on some
          sort of HA disk array.
          The key point is that a message once it arrives at a server must be processed
          by that server or, in the case of failure of that server, must be processed by
          a server similarly configured to the one that failed so that it picks up the unprocessed
          messages. The message can't be processed by another server in the cluster.
          Or, is there some trick that could be employed to copy from the file store of
          the failed server and repost the messages to the still operating servers?
          "Zach" <[email protected]> wrote:
          >Unless you have some sort of HA framework/hardware, this is a manual
          >operation. You either point to the existing persistent storage (shared
          >storage or JDBC connection pool), or you move the physical data.
          >
          >_sjz.
          >
          >"Jim Cross" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >>
          >> How does JMS failover with distributed destinations in WL 7.0?
          >>
          >> In an environment using file stores for persistent messages, can a
          >working
          >server
          >> automatically pick up unprocessed and persisted messages from a failed
          >server?
          >> If so, what's the best way to set this up?
          >>
          >> Or, is this completely manual? In other words, we have to bring up
          >a new
          >server
          >> pointing to the location of the file store from the failed server?
          >
          >

Looking up a distributed queue with two persistent stores using two JMS Svr

I am trying to do the following:
1. Setup a distributed queue, i have two servers which are part of the cluster:
Server A: t3://localhost:7003
Server B: t3://localhost:7005
I go in and create two jms servers:
JMS Server JA: Target on Server A
JMS Server JB: Target on Server B
Now as the jms servers need to use a seperate persistent store for each one of them i create two persistent stores.
2. Now from my MDB which is deployed on another server i lookup the queue using
t3://localhost:7003,localhost:7005 as the provider url
My problem is that i always end up listening to the messages on the first jms server and never get to read the messages on jms server JB as i guess i am able to connect to JMS Server JA so i never try and connect to JB? What to do about this?
Edited by: user4828945 on Mar 23, 2009 2:32 PM

Allocation of consumers wouldn't take into account the number of messages on the queue - they'd be allocated randomly. The scenario you're proposing shouldn't happen though - WebLogic Server takes into account whether a member has consumers when sending to a distributed destination, but otherwise, assuming that Queue 1 and Queue 2 both have consumers, then distribution of load will be equal. It's not the amount of consumers that determine how many messages get sent to a distributed destination member - it's whether it has members at all.
Assuming that did occur initially though, you'd expect processing to be a little bit more intensive on the server with the queue holding 30 messages. It would pretty quickly even up though.
From that point forward, it would be somewhere between difficult and impossible to get to the second scenario, where you have an unequal number of messages in each distributed destination member, unless the work being sent with each message to an MDB can vary significantly in how long it would take to process.
Assuming (and it's a big if) you could get to that scenario, then the MDBs wouldn't switch over - they stay connected to a particular distributed destination member. And it's their connection to a member as a consumer that controls how WebLogic Server load balances messages (assuming default configuration) so that's part of what makes it unlikely to get there.
From going back to first principles in the documentation, it seems like your best result would actually be from deploying the MDB to the cluster - that way, there's no remote connections to JMS queues, and you get a pool of MDBs on each server instance.
Ref here: http://e-docs.bea.com/wls/docs81/ejb/message_beans.html

MDB - JMS foreign provider

          Using WLS8.1:
          I'm currently trying to set up a MDB listening directly on a JMS queue, provided
          by Sonic.
          I registered my queue through the Sonic JMS console in the WLS JNDI repository,
          and can browse to the object successfully in the JNDI browser.
          However, when I deploy my MDB, I get an exception:
          <Feb 28, 2004 3:27:09 PM MET> <Warning> <EJB> <BEA-010061> <The Message-Driven
          EJB: SomeMDB is unable to connect to the JMS destination: myforeigndestination.
          The Error was:
          weblogic.jms.common.InvalidDestinationException: Foreign destination, q_external
          weblogic.jms.common.InvalidDestinationException: Foreign destination, q_external
          at weblogic.jms.common.Destination.checkDestinationType(Destination.java:106)
          at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1580)
          at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1484)
          at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1609)
          at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1844)
          at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
          at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
          at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
          at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
          at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
          at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          The only way to get it working is setting up an additional internal WL queue,
          connected by a Messaging Bridge, but that's not what I want.
          It seems like weblogic JMS implemenation only accepts weblogic Queue's as valid
          Queue objects.
          Thanks for any pointers.
          Rgrds,
          Klaas van der Ploeg


          Klaas van der Ploeg wrote:
          > Using WLS8.1:
          >
          > I'm currently trying to set up a MDB listening directly on a JMS queue, provided
          > by Sonic.
          >
          > I registered my queue through the Sonic JMS console in the WLS JNDI repository,
          > and can browse to the object successfully in the JNDI browser.
          > However, when I deploy my MDB, I get an exception:
          > <Feb 28, 2004 3:27:09 PM MET> <Warning> <EJB> <BEA-010061> <The Message-Driven
          > EJB: SomeMDB is unable to connect to the JMS destination: myforeigndestination.
          > The Error was:
          > weblogic.jms.common.InvalidDestinationException: Foreign destination, q_external
          > weblogic.jms.common.InvalidDestinationException: Foreign destination, q_external
          > at weblogic.jms.common.Destination.checkDestinationType(Destination.java:106)
          > at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1580)
          > at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1484)
          > at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1609)
          > at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1844)
          > at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
          > at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
          > at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
          > at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
          > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
          > at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
          > at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
          > at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >
          >
          > The only way to get it working is setting up an additional internal WL queue,
          > connected by a Messaging Bridge, but that's not what I want.
          >
          >
          > It seems like weblogic JMS implemenation only accepts weblogic Queue's as valid
          > Queue objects.
          Emphatically not true. In pointed fact, WebLogic has gone through
          great pains over the years to ensure integration works with multiple
          JMS vendors - sending out fix requests to them as needed (including
          Sonic).
          Anyhow, you are trying to use a non-WebLogic destination with a
          WebLogic JMS session. No vendor supports this. Instead, you
          must make sure that the MDB creates a Sonic JMS session. So
          configure a foreign connection factory, and configure the
          MDB to refer to this connection factory. You can find
          this information in WebLogic's JMS developer guide.
          This is the first time I've gotten a Sonic question in quite a
          while, but I know that they have step-by-step doc on how to
          integrate their product with WebLogic. You might want to try
          looking there for more help. I don't know if their doc
          leverages 8.1 foreign destination wrapper feature.
          Tom Barnes, BEA
          >
          > Thanks for any pointers.
          >
          > Rgrds,
          > Klaas van der Ploeg

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

Fatal error distributing forms with Adobe Acrobat 9 Pro

Fatal error distributing forms with Adobe Acrobat 9 Pro.
I click
"Adobe Acrobat Pro/Formularer/Distribuer formularer/"
("Adobe Acrobat Pro/Forms/Distribute forms/")
and chose a form for distribution and in the picture "Distribute Form" chose
"Automatically download & organize responsees with Acrobat.com".
I then click "Next" and write an email-address to send it to (i.g. to my own)
and then click "Send".
The program quickly writes
"Authenticating email-addresses"
and then gives the following error message
"Borland Database er ikke installeret. Kan ikke indlæse tjenesteudbyder af Corel-adressekartotetek."
("Borland Database is not installed. Can not read load service provider of Corel address directory.")
When I clik "OK" I get the error message
"Adobe Acrobat has encountered a problem and needs to close. We are sorry for the inconvenience."
I have undeleted and reinstalled Adobe Acrobat many times without any effect.
The same procedure has been tried on another computer without any problem.
What is my problem and how do I resolve it ?
Operating System Windows XP
Has worked may times before
Same results with other files
No recent system hardware or software change

This is the image that I have plus....
Reader 9.0 AcroRd32.exe caused Microsoft Visual C++ Runtime Library error
Preinstalled Adobe 9 Standard doesn't work on a new Dell out of the box - why would it?
Need help in creating a batch file that will add and remove some registy keys.
%userprofile%

Get error from SQL AGENT: The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D024

I am running SQL Agent that executes an SSIS process from sql server1. The SSIS process executes its SQL/tables/sp’s against another sql server2.
I get an error after adding data flow tasks with transaction supported within a sequence with transaction required. The error, “The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D024 "The transaction
manager has disabled its support for remote/network transactions"
Prior to adding this sequence everything was working from sql agent, and there were other sequences with oledb destinations.
Everything works when running within SSIS Package.
I see this article on similar issue,
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/0bfa2569-8849-4884-8f68-8edf98a9b4fe/problem-to-execute-a-package-and-tasks-with-a-certain-transactionoption-property-i-need-help?forum=sqlintegrationservices
“I had similar issue and solved by setting the following on both the machines. Allow Remote Clients, Allow Remote Administration,
Allow Inbound Clients, Allow Outbound Clients, and TIP are enabled in Component Services/My Computer/Properties/MSDTC/Security Configuration.”
I don’t want to remove transaction required for the “Remove Duplicates from Staging” sequence.
Anyone seen this?
Greg Hanson

DTC was running on remote computer. The problem was it was no longer accepting transactions from remote servers. This was in SSIS so I had to turn to "Transaction Supported" for all Data Flow Transactions.
Greg Hanson

Error handling message: flex.messaging.MessageException: No destination with id '' is registered with any service

Hi,
We are using both Remoting and HttpService calls for our business application.
We were able to communicate with the LCDS server till this point with whatever default settings provided for AMFChannel configuration in services-config.xml through a flex client. Also we have a clustered environment for this servers which works out fine till now.
Now for performance enhancement improvements, we started using Caching Mechanism for our HttpService urls (through some third party service), which will now be cached on the network instead of accessing every time from our clustered servers. But all our AMF calls through Remoting services are still the same.
So after migrating to this Caching environment, we started encountering intermittent issues where some of our AMF calls were failing with falling exception trace :
16:03:40,576 INFO [STDOUT] [Flex] [ERROR] Error handling message: flex.messaging.MessageException: No destination with id '' is registered with any service.
incomingMessage: Flex Message (flex.messaging.messages.CommandMessage)
operation = invalid.12
clientId = D7855C44-810B-64AB-C176-7C38F83DEB2C
correlationId =
destination =
messageId = 2DA6BDB8-859E-8AE1-03A4-57743DE03188
timestamp = 1247007820561
timeToLive = 0
body = {}
hdr(DSId) = D77C6BD2-3808-1512-3984-CCF397428E35
hdr(DSEndpoint) = my-amf
errorReply: Flex Message (flex.messaging.messages.ErrorMessage)
clientId = D7855C44-810B-64AB-C176-7C38F83DEB2C
correlationId = 2DA6BDB8-859E-8AE1-03A4-57743DE03188
destination =
messageId = D7855C64-3E08-466B-96F8-5BAE7D385129
timestamp = 1247007820574
timeToLive = 0
body = null
code = Server.Processing
message = No destination with id '' is registered with any service.
details = null
rootCause = null
body = null
extendedData = null
So i do not understand, most of the times the AMF calls works correctly and some times it fails with above fail trace.
Any suggestions would be appreciated.
Thanks,
FlexPirate

It might be a bit late but replying for anyone who lands on this page facing this same problem.
The solution for "No destination with id '<my dest id>' is registered with any service" problem is that you have to make sure your destination definition is added in your:
C:\ColdFusion9\wwwroot\WEB-INF\flex\messaging-config.xml
Secondly, If you are deploying it on a ColdFusion Server, then you have to make sure exact same definition is added in Server messaging-config.xml file as well.
This should solve this problem.
While we are at it, wanted to point another possible gotcha.
if your Server is using SSL protocol i.e. it has https:// rather than http://, Then within your <destination> definition block in messaging-config.xml, you have to add appropriate secure channels in <channels> section. You can find all available channel definitions in
C:\ColdFusion9\wwwroot\WEB-INF\flex\services-config.xml

[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();

Distributed destination issue on Web Logic server 8.1

Hi,
I'm using distributed JMS destination (Cluster) of Web Logic server 8.1.
I'm using Oracle B2B to talk to the cluster. Oracle B2B is only creating a consumer on one of the managed servers in this cluster. This is resulting in loss of messages when messages are placed by the WLI on the other managed server.
Further the consumers are created randomly by Oracle B2B.
My question here is whether Web Logic Server 8.1 supports multiple consumers for its clusters?
Please Help!
Thanks in advance.
Warm Regards,
Suhas.

Are your consumers co-located with each managed server or remote?
Let me preface this by this is the way I believe it works...
The reason I ask is that distributed destinations route to one managed server at connect time. So for producers, when 1 message is placed on a distributed destination, it is really routed to only 1 managed server queue. From a remote consumer standpoint, when connecting to a distributed destination to read messages, you are only routed to one of the managed server queues to read from, not the logical superset of all queues in the distributed destination. So you would need to connect to each distributed destination member queue directly to ensure each had consumers. Whereas if your consumers are co-located on the cluster, then they can each connect to the local member queue for that distributed destination and ensure that each member of the distributed destination has consumers.
I'd recommend you note the follow docs:
QueueReceivers
http://edocs.bea.com/wls/docs103/jms/dds.html
When creating a queue receiver, if the supplied queue is a distributed queue, then a single physical queue member is chosen for the receiver at creation time. The created QueueReceiver is pinned to that queue member until the queue receiver loses its access to the queue member. At that point, the consumer will receive a JMSException, as follows:
If the queue receiver is synchronous, then the exception is returned to the user directly.
If the queue receiver is asynchronous, then the exception is delivered inside of a ConsumerClosedException that is delivered to the ExceptionListener defined for the consumer session, if any.
Upon receiving such an exception, an application can close its queue receiver and recreate it. If any other queue members are available within the distributed queue, then the creation will succeed and the new queue receiver will be pinned to one of those queue members. If no other queue member is available, then the application won’t be able to recreate the queue receiver and will have to try again later.
Note: For information on the load-balancing heuristics for distributed queues with zero consumers, see “Configuring Distributed Destination Resources”.
http://edocs.bea.com/wls/docs103/jms_admin/advance_config.html#jms_distributed_destination_config
The producer makes such a decision each time it sends a message. However, there is no compromise of ordering guarantees between a consumer and producer, because consumers are load balanced once, and are then pinned to a single destination member.

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

JMS distributed destination

In Bea's WLS 7.0 JMS: "Looking up Distributed Topics" and "Deploying Message-Drive
Beans on a Distributed Topic" :
http://e-docs.bea.com/wls/docs70/jms/implement.html#1260828
This sound like each message(topic) gets sent to all members of a distributed
topic.
Then in the same doc for LB, a couple paragraphs down we have a conflict explaination:
"In the round-robin algorithm, WebLogic JMS maintains an ordering of physical
destinations within the distributed destination. The messaging load is distributed
across the physical destinations one at a time in the order that they are defined
in the WebLogic Server configuration (config.xml) file. "
If a topcs sent to a distributed topic will be sent to all physical destinations,
why we need LB here. Or the LB is applied to distributed Queue only.
Please comments.
THX.
-John

Rob,
Not a expert I must admit, but the link provided by you states "A distributed destination is a set of destinations (queues or topics) that are accessible as a single, logical destination to a client. A distributed destination has the following characteristics:
It is referenced by its own JNDI name."
You can actually configure JMS adapters using JNDI so I think this should be possible. More info here,
http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm
Do let us know if this helps and works!
Regards
Bhavesh

JMS Distributed Destination Topic - how to avoid MDB to recieve duplicates

HELP!!
          I have spent a lot of time looking for an option to move jms on a cluster, finally I can do this using distributed destination, I have two memmbers(Topic) in the distributed destination topic, but when both of them are active, the Message Driven Bean which is deployed on cluster recieves 2 messages instead of 1, anyone please help me to change this to have only one message instead of 2 !!!!!

Make it a Queue or don't deploy the MDB to the cluster. You are seeing
          expected behavior. I have the same situation with a Topic and I deploy my
          MDB to one node in the cluster and have it configured to consume the local
          physical Topic.
          Bill
          "Manav Sehgal" <[email protected]> wrote in message
          news:18024883.1107530318601.JavaMail.root@jserv5...
          > HELP!!
          > I have spent a lot of time looking for an option to move jms on a
          > cluster, finally I can do this using distributed destination, I have two
          > memmbers(Topic) in the distributed destination topic, but when both of
          > them are active, the Message Driven Bean which is deployed on cluster
          > recieves 2 messages instead of 1, anyone please help me to change this to
          > have only one message instead of 2 !!!!!

Distributed destination with MQ as Foreign Provider

Similar Messages

Maybe you are looking for