Wls7 GA bridge deletes durable subscriptions on source destination when stopped

          The bridge (with durability enabled) seems to delete its durable subscriptions
          from the source destination when it is stopped in any of the following 3 ways:
          (1) uncheck the "started" box & apply
          (2) untarget the bridge from the server
          (3) gracefully shutdown the server hosting the bridge
          ..whereas if I kill the server the bridge is on, the durable subcription on the
          source destination remains.
          For me the behaviour in (1) (2) & (3) is unwanted: I want the durable subscription
          to remain, so that when I start the bridge again it can pick up messages stored
          for it. Is there some reason you have implemented it this way? Is there a config.xml
          attribute I can set to inhibit this behaviour? Or is there a patch for it?
          In my case the bridge is running on a standalone admin server, with a local target
          destination; the source destination is on a remote wls7 managed server instance.
          I can send you config.xmls for everything but I don't want to post them here.
          We're using lots of bridges to simplify our JMS topology.
          (I'll raise a case for this too, I just wanted to log it here.)
          Regards,
          Jeremy.

It is not the intended behavior and looks like a new bug introduced in 7.0.
          I have filed an internal change request for this (CR082386).
          Thanks,
          Dongbo
          "Jeremy Watson" <[email protected]> wrote in message
          news:[email protected]...
          >
          > The bridge (with durability enabled) seems to delete its durable
          subscriptions
          > from the source destination when it is stopped in any of the following 3
          ways:
          > (1) uncheck the "started" box & apply
          > (2) untarget the bridge from the server
          > (3) gracefully shutdown the server hosting the bridge
          >
          > ..whereas if I kill the server the bridge is on, the durable subcription
          on the
          > source destination remains.
          >
          > For me the behaviour in (1) (2) & (3) is unwanted: I want the durable
          subscription
          > to remain, so that when I start the bridge again it can pick up messages
          stored
          > for it. Is there some reason you have implemented it this way? Is there
          a config.xml
          > attribute I can set to inhibit this behaviour? Or is there a patch for
          it?
          >
          > In my case the bridge is running on a standalone admin server, with a
          local target
          > destination; the source destination is on a remote wls7 managed server
          instance.
          > I can send you config.xmls for everything but I don't want to post them
          here.
          > We're using lots of bridges to simplify our JMS topology.
          >
          > (I'll raise a case for this too, I just wanted to log it here.)
          >
          > Regards,
          > Jeremy.

Similar Messages

Durable subscriptions

I am using code similar to this:
aq.connection = topicConnectionFactory.createTopicConnection( "aquser", "aquser");
aq.session = aq.connection.createTopicSession( true,Session.CLIENT_ACKNOWLEDGE);
It works no problem when sending and receiving messages from a queue (Point to Point). It works when publishing a message to a topic, but when trying to creat a durable subscription, it throws a ora-24047 error (invalid agent name, should be type NAME and not string). I am using strings similar to the above example.
This doesn't make sense as PTP works and publishing messages work using strings as the agent name, and not the NAME object.
What could be causing a Durable Subscription to be rejected when using the agent name in string format?

That specific error goes away when there are no special characters such as underscores in the name, and everything is uppercase.

Weblogic 9.2 distributed source destination problem.

(Tom, posting this here as you monitor this one). Answering your query as well.
We are using Weblogic 9.2 and have configured a Messaging Bridge (to connect to Weblogic 8.1). We have a distribted queue defined and 2 managed servers. jms-xa-rar deployed correctly and passes the test.
In the Source Bridge Desitination, the ConnectionURL is given as "t3://ms1:54032,ms2:54034"
Initially bridge as not started and both managed servers were shutdown. Then we brought up the 2 managed servers one by one, found that one member of source destination on ms2 had a consumer while destination member on ms1 had no consumers. Instead when turning on debug for MessagingBridge, found these exceptions.
<29-Mar-2010 17:07:23 o'clock BST> <Warning> <Connector> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3://ms1:54032,ms2:54034, user name = null) ">
<29-Mar-2010 17:07:23 o'clock BST> <Info> <MessagingBridge> <BEA-200042> <Bridge com.bridge.somename failed to connect to the source destination and will try again in 60 seconds. This could be a temporary condition unless the messages repeat several times. (javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3://ms1:54032,ms2:54034, user name = null))>
The whole setup works with just one managed server given in ConnectionURL i.e. "t3://ms1:54032"
Why is it unable to find initial context when we give a cluster JNDI for ConnectionURL in source bridge destination?
1) With ONLY ms1 as the connection url for source bridge destination, it works fine and I can see 2 consumers on the member ms1 destination (no consumers on ms2 as expected)
2) With ONLY ms2 as the connection url for source bridge destination, it works only with MS2. I can see 1 consumer on member destination ms2. Nothing shows up on ms1. when starting ms1, it did show some messages given below. I could not see JMS Server recognizing ms1 as Active Destination either even though server started up.
3) With ms1 and ms2 in connection url, one seems to connect correctly at times but never both (never gotten consumers listed on both managed servers).
<31-Mar-2010 07:05:34 o'clock BST> <Info> <MessagingBridge> <BEA-200021> <Bridge "com.somebridge"
failed to get one of the adapters from JNDI (javax.naming.NameNotFoundException: Unable to resolve
'eis.jms.WLSConnectionFactoryJNDIXA'. Resolved 'eis.jms'; remaining name 'WLSConnectionFactoryJNDIXA').
javax.naming.NameNotFoundException: Unable to resolve 'eis.jms.WLSConnectionFactoryJNDIXA'. Resolved 'eis.jms'; remaining
name 'WLSConnectionFactoryJNDIXA'
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:171)
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.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:362)
at weblogic.jms.bridge.internal.MessagingBridge.startInternal(MessagingBridge.java:562)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1030)
at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>
<31-Mar-2010 07:16:28 o'clock BST> <Info> <MessagingBridge> <BEA-200033> <Bridge "com.somebridge"
is obtaining connections to the two adapters.>
<31-Mar-2010 07:16:28 o'clock BST> <Info> <Common> <BEA-000628> <Created "1" resources for pool
"eis/jms/WLSConnectionFactoryJNDIXA", out of which "1" are available and "0" are unavailable.>
<31-Mar-2010 07:16:28 o'clock BST> <Info> <Common> <BEA-000628> <Created "1" resources for pool
"eis/jms/WLSConnectionFactoryJNDIXA", out of which "1" are available and "0" are unavailable.>
<31-Mar-2010 07:12:13 o'clock BST> <Debug> <JMSBackEnd> <000000> <Starting block
ing receive for consumer>
<31-Mar-2010 07:12:13 o'clock BST> <Debug> <JMSBackEnd> <000000> <Blocking recei
ve request: state = 101>
<31-Mar-2010 07:12:13 o'clock BST> <Debug> <JMSBackEnd> <000000> <Associating me
ssage with transaction>

Tom,
Please find responses to your queries below
Can you help me understand your topology?
-- Is the bridge running on the same server/cluster as its source destination? Its target destination? Neither?
Bridge is running on same cluster as the source destination, there are 2 managed servers in cluster.
-- If neither, is it running on 8.1 or 9.1?
Bridge running on Weblogic 9.2.2.
-- Is the source destination distributed? Is it on 8.1 or 9.1?
source = Weblogic 9.2.2, yes source destination is a distributed queue (uniform distributed with member allocated evenly)
-- Is the target destination distributed? Is it on 8.1 or 9.1?
target destination is 8.1 and is distributed target as well. This is on a remote machine.
-- What is the bridge's URL for the source destination?
http://ms1:50128,ms2:50130 (I may not be able to provide details on actual IP or DNS, apologies)
-- What is the bridge's URL for the target destination?
http://r1:40888,r2:40890
More inputs
The connection factory on the message producer side i.e my end is Server Affinity while the connection factory on target side is Load Balanced
JMSBackendDebug on, I can actually see that 2 consumers are being created on each ms
Managed Server 1
<01-Apr-2010 11:32:06 o'clock BST> <Debug> <JMSBackEnd> <000000> <New consumer for jms_module!jms.server.ms1@queue_name>
<01-Apr-2010 11:32:06 o'clock BST> <Debug> <JMSBackEnd> <000000> <Calling out to DDMember: jms_module!jms.server.ms1@queue_name, hash: 335836273, dispId: managed1_server, backEndId: <6772957712843200991.10>:managed1_server, destinationId: <6772957712843200991.12>, remoteSecurityMode: 11>
<01-Apr-2010 11:32:06 o'clock BST> <Debug> <JMSBackEnd> <000000> <Created a new consumer with ID <6772957712843200991.16> on queue jms_module!jms.server.ms1@queue_name>
<01-Apr-2010 11:32:06 o'clock BST> <Debug> <JMSBackEnd> <000000> <Back from DDMember: jms_module!jms.server.ms1@queue_name, hash: 335836273, dispId: managed1_server, backEndId: <6772957712843200991.10>:managed1_server, destinationId: <6772957712843200991.12>, remoteSecurityMode: 11>
<01-Apr-2010 11:32:06 o'clock BST> <Debug> <JMSBackEnd> <000000> <Calling out to DDHandler: queue_name, hash: 29969233, dd: jms_module!queue_name>
<01-Apr-2010 11:32:06 o'clock BST> <Debug> <JMSBackEnd> <000000> <Calling out to FEDDHandler: queue_name, hash: 23986467>
<01-Apr-2010 11:32:06 o'clock BST> <Debug> <JMSBackEnd> <000000> <Back from FEDDHandler: queue_name, hash: 23986467>
<01-Apr-2010 11:32:06 o'clock BST> <Debug> <JMSBackEnd> <000000> <Calling out to QueueForwardingManager: jms_module!jms.server.ms1@queue_name within jms_module!queue_name, hash: 25321487>
Managed Server 2
<01-Apr-2010 11:32:06 o'clock BST> <Debug> <JMSBackEnd> <000000> <New consumer for jms_module!jms.server.ms2@queue_name>
<01-Apr-2010 11:32:06 o'clock BST> <Debug> <JMSBackEnd> <000000> <Calling out to DDMember: jms_module!jms.server.ms2@queue_name, hash: -112860366, dispId: managed2_server, backEndId: <4215229783845568768.10>:managed2_server, destinationId: <4215229783845568768.12>, remoteSecurityMode: 11>
<01-Apr-2010 11:32:06 o'clock BST> <Debug> <JMSBackEnd> <000000> <Created a new consumer with ID <4215229783845568768.16> on queue jms_module!jms.server.ms2@queue_name>
<01-Apr-2010 11:32:06 o'clock BST> <Debug> <JMSBackEnd> <000000> <Back from DDMember: jms_module!jms.server.ms2@queue_name, hash: -112860366, dispId: managed2_server, backEndId: <4215229783845568768.10>:managed2_server, destinationId: <4215229783845568768.12>, remoteSecurityMode: 11>
<01-Apr-2010 11:32:06 o'clock BST> <Debug> <JMSBackEnd> <000000> <Calling out to DDMember: jms_module!jms.server.ms1@queue_name, hash: 335836273, dispId: managed1_server, backEndId: <6772957712843200991.10>:managed1_server, destinationId: <6772957712843200991.12>, remoteSecurityMode: 11>
<01-Apr-2010 11:32:06 o'clock BST> <Debug> <JMSBackEnd> <000000> <Back from DDMember: jms_module!jms.server.ms1@queue_name, hash: 335836273, dispId: managed1_server, backEndId: <6772957712843200991.10>:managed1_server, destinationId: <6772957712843200991.12>, remoteSecurityMode: 11>
<01-Apr-2010 11:32:06 o'clock BST> <Debug> <JMSBackEnd> <000000> <Calling out to DDHandler: jms_module!queue_name, hash: 24464810, dd: jms_module!queue_name>
<01-Apr-2010 11:32:06 o'clock BST> <Debug> <JMSBackEnd> <000000> <Calling out to FEDDHandler: jms_module!queue_name, hash: 10346403>
Edited by: user9521457 on Apr 1, 2010 3:49 AM

Alert subscription data source module encountered errors while running

Hello All,
After I configured subscriptions with many monitors, error alerts appear at SCOM(scom 2012 r2) console in active alert page.
I googled it and found some topics at TechNet but I could not figure it out. Alert description is shown below
Alert subscription data source module encountered errors while running: Alert subscription data source module was unable to find alerts that match the subscription because of database errors.
The following error(s) were encountered:
Exception Message: The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.
One or more workflows were affected by this.
Workflow name: Subscriptioneaa7b044_b3c1_4198_be71_ffaaf66a163f
Instance name: Alert Notification Subscription Server
Instance ID: {E07E3FAB-53BC-BC14-1634-5A6E949F9230}
Management group: STS
Any idea?
Thanks

As I understand, this issue occurs and remains after I configure a subscription with too many rules and/or monitors( i.e al available rule and/or monitor of a management pack).
After I had deleted those subscription with many rule/monitor, this issue was resolved.
Any idea?

AQ JMS: non-durable subscriptions not cleaned up

Whenever I create a non-durable subscription I see a TSUB_... subscription in the AQ$ tables. This subscription does not disappear when the client terminates abnormally.
This can be very annoying because these queues fill up quickly and deleting a big subscription locks the queue for a substantial amount of time.
Is there something I missed - should the QMN take care of these orphaned subscriptions ?

We are having exactly the same problem...

My JMS 2 wish list - Part 4, durable subscriptions

I attended the JavaOne 2010 session on future JMS evolutions. During the session I described some current limitations or issues I'd like to be solved in a portable way. I've been adviced to share the issues to get feedback from the community. I will post each issue in a dedicated thread.
Issue 4 - How durable are durable topic subscriptions?
Non durable subscribers receive topic messages only if they are active at the time when the message is received and processed by the JMS engine. Durable subscribers are more complicated, they receive messages if the durable subscription is active when the message is received and processed by the JMS engine.
How do I know when messages are kept or discarded? Simply put, what is the lifecycle of the subscription?
When using synchronous receptions or message listeners, the durable subscription lifecycle is managed by the developper using Session:createDurableSubscriber and Session:unsubscribe.
When using MDB, the durable subscription lifecycle is unspecified and is application server dependant.
With JBoss 4.2, the subscription lifecyle is the same than the MDB. This means that if the application is redeployed (for example copy the new .ear over the old one in the deploy folder), there is a time frame when the subscription in non existent, so messages are lost.
WebLogic 10 also seems to associate the subscription lifecycle to the MDB. WebLogic 10 offers a flag, "durable-subscription-deletion", to allow or not the durable subscription deletion when the MDB is undeployed or removed. True means that when the application is redeployed the subscription is deleted and messages are lost. When false is used (it is the default value) the subscription remains even when the MDB is undeployed. I hope this does not mean that if we permanently undeploy the application, the subscription will stay and messages will continue to stack.
With WebSphere 6 the situation is different. The subscription is not associated to the MDB but to an activation spec that is an administred object. The MDB is merely a client of the activation spec. This way messages are kept as long as the activation spec is active, regardless of application starts/stops/redeploys/etc. Messages are not lost.
We need a portable way to use durable topics subscriptions.

gimbal2 wrote:
A portable solution would be useful.You could already do it now by leveraging the Timer functionality that has been part of the EJB spec since JEE 1.4. In stead of sending the message directly, let the timer do it after the delay you specify. That would make it portable with current tech.
I can't be sure what other implications that might have though, such as in the area of performance and resource usage - I can imagine you wouldn't want to use a timer when you need to send large volumes of messages.In the original requirement, the message is put in the queue immediately by a call to queuesender.send(message) and there's a delivery in delay to a consumer.
Whereas in this solution, the delay is in the message delivery to the queue itself.
IMHO there's a subtle but important difference here.What would for example happen if posting the message to the queue is in the scope of a distributed JTA transaction? You can definitely include the timer call to be in the scope of the transaction, but now you will have to account for the fact and there may be an error when the message is delivered which has to be handled explicitly. In the original scenario the tx would automatically rollback.
cheers,
ram.

Regarding destroying durable subscription using JMX

Hi,
I have web based application in which i m using JMS. For JMS, i am using ActiveMQ as a Message Broker.Here, i want to delete Durable topics using JMX remote connection to my broker,where activeMQ should not be stopped. I can delete durable topics but how to remove subscription of that topic that i dont know and because of subscription
when i restart my standalone component it gives an error such as
'mail_topic is already connected because of that subscription".
Here, whenever i try to destroyDurableSubscriber it gives error such as
Durable consumer is in use.
How to overcome to this problem,please tell me,
Thanks in advance.

What is the MQ version shown at beginning of the broker log ? Could you please give more description of your application and what the subscriber clients do ?

How can I delete an ODBC data source after 10g client has been uninstalled?

I uninstalled the 10g client and now when I attempt to delete the ODBC data source, I get an error: "The setup routines for the Oracle in Oraclient10g_home2 ODBC driver could not be found. Please reinstall the driver. I re-installed the client and I get the same error, but I had to specify a new home. I still get the error. Anyone have an answer or a workaround to deleting the ODBC entry so that I can re-create with the same name later under the 9i client?

I have the same problem... and nobody gots the point:
1st. the ODBC and the client/home exists on the machine...
2nd. the client/home is unistalled and so...
3rd. tada! Now we have a impossible-to-unistall ODBC entry!
That is happening on a Windows, at last to me...
Please, help us if someone knows how to remove this ODBC entry... if know how to DO the stuff (permissions, system, all that things is answered above).
Best regards,
Bruno Araujo

InvalidClientIdException while creating Durable subscription in weblogic

Hi,
We have scenario to create a durable subscription for an MDB. Here application in weblogic is a subscriber to a Topic present on the Progress Sonic. For integrating to independent platforms we are using Foreign Server mechanism under JMS Modules.
For creating durable subscription, we have changed the MDB code . Below is the MDB code,
package com.test;
import java.util.Enumeration;
import javax.annotation.Resource;
import javax.annotation.Resources;
import javax.ejb.MessageDriven;
import javax.ejb.TransactionAttribute;
import javax.ejb.TransactionAttributeType;
import javax.ejb.TransactionManagement;
import javax.ejb.TransactionManagementType;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;
import javax.ejb.ActivationConfigProperty;
* Message-Driven Bean implementation class for: TestMDB
@MessageDriven(description = "mdb for Airline Schedule Change MDB",
name = "AirlineScheduleMDB",
activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType",
propertyValue = "javax.jms.Topic"),
@ActivationConfigProperty(propertyName = "subscriptionDurability",
propertyValue = "Durable")
@TransactionManagement(value = TransactionManagementType.CONTAINER)
@Resources( { @Resource(name = "ConnectionFactoryRef",
mappedName = "TopicConnectionFactory",
type = javax.jms.ConnectionFactory.class) })
public class TestMDB implements MessageListener {
* @see MessageListener#onMessage(Message)
@TransactionAttribute(value = TransactionAttributeType.NOT_SUPPORTED)
public void onMessage(Message message) {
System.out.println("Inside message : ");
try {
Enumeration<Object> messageProperty = message.getPropertyNames();
System.out.println("The request : "+message);
if(message != null){
System.out.println("TestMDB : onMessage : Start");
}else{
System.out.println("Received Input message is empty");
} catch (Exception e) {
System.out.println("Exception Occurred in TestMDB : ");
e.printStackTrace();
System.out.println("TestMDB : onMessage : End.Time taken is :");
Also the following change was included in the weblogic-ejb-jar.xml.
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar
xmlns="http://www.bea.com/ns/weblogic/90"
xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>TestMDB</ejb-name>
<message-driven-descriptor>
<pool>
<initial-beans-in-free-pool>1</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>DurableJNDI</destination-jndi-name>
<connection-factory-jndi-name>TopicConnectionFactory</connection-factory-jndi-name>
<jms-polling-interval-seconds>30</jms-polling-interval-seconds>
<generate-unique-jms-client-id>true</generate-unique-jms-client-id>
<jms-client-id>DurableTest</jms-client-id>
</message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Exception we got :
<03-Apr-2012 18:11:02 o'clock UTC> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: TestMDB is unable to connect to the JMS destination: DurableJNDI. The Error was:
javax.jms.InvalidClientIDException: Invalid client id: DurableTest_drdevwls_TestDomain-wls1_CLEARCF.jarTestMDB
Weblogic is automatically creating a unique id based on the combination of Adminserver/Managedserver/Projectname etc.
However the id created by weblogic seems to have a dot(.) which as per Sonic spec is an invalid character.
eg:- DurableTest_test_domain_AdminServer_CLEARCF.jarTestMDB
Hence we changed the parameter to false and provided our own value.
<generate-unique-jms-client-id>false</generate-unique-jms-client-id>
<jms-client-id>DurableTest</jms-client-id>
At this point of time we were able to see that MDB have created a Durable subscription successfully and it worked as expected.
However when we tried to scale this change to multiple managed servers, there were errors thrown from sonic side.
javax.jms.JMSException: [129] progress.message.client.EUserAlreadyConnected: Administrator/$DURABLE$DurableTest$DurableTest
So we cannot have same clientid for multiple clients(managed server). We arent sure how to proceed with this.
We need to find a way to remove the dot from the dynamic id weblogic creates.
Any help on this is highly appreciated.

Hi Tom,
We have found the solution to this problem and thanks for your suggestion that has partially helped us in solving the problem.
As you have suggested we have defined client-id on the connection factory however we will be having only connection factory instead of multiple with different client-ID's.
Along with the client-id configured at the connection factory level we are now setting the attributes generate-unique-client-id as true at the weblogic end.
By doing this way, I assume that weblogic while making the durable subscription connection is passing the uniquely generated client ID (which has dots '.' included in it ) as subscription name and client-id will be same, that is defined on the connection factory.
A question may arise that - 'why is sonic accepting subscription name with dots but not the client-id ?' - When observed from the sonic end the dots in the subscription name are replaced by '@@@' .
Sonic need to answer the question of why the dots are being replaced for subscription name but not for client-id.
Regards,
Bharat K

BDC for ME01 to delete vendors in the source list

Hi ABAP'ers,
I am trying to write a BDC program to delete a particular vendor from ME01 TCODE. My program runs well till deletion after i delete a record it is showing a pop up to confirm and on clicking yes the vendor is deleted. But the source list is not getting saved, or in other words the BDC flow stops after deletion, though i have handled save ok code in my BDC internal table. is there a solution for this.
thanx $ regrds
thrinath k

Run in mode 'E' and fix whatever you have missed on your BDC.

Do I really need two connection pools when using two durable subscriptions?

I have a Spring daemon which takes messages from two different topics and stores them in a database.
What irritates me is that I can't get it to work with a single connection pool. I get a message that I can't create durable subscriptions without a unique client id on the connection. It's not enough that the client id be set on the listener container, I have to set it on the underlying ConnectionFactory. I though this was some kind of glitch with openMQ but activeMQ gives me exactly the same behaviour.
This is the important part of the config
    <bean id="realCon" class="org.apache.activemq.ActiveMQConnectionFactory" p:brokerURL="discovery:(multicast://default?group=live)"
    p:clientID="DB_RECORD_CLIENT"/>
    <bean id="realCon2" class="org.apache.activemq.ActiveMQConnectionFactory" p:brokerURL="discovery:(multicast://default?group=live)"
    p:clientID="DB_LOG_CLIENT"/>
    <bean id="jmsConnectionFactory" class="org.springframework.jms.connection.CachingConnectionFactory"
    p:targetConnectionFactory-ref="realCon"/>
    <bean id="jmsConnectionFactory2" class="org.springframework.jms.connection.CachingConnectionFactory"
    p:targetConnectionFactory-ref="realCon2"/>
    <bean id="ocsMessageListener" class="com.cc.mer.ordercatcher.MessageReceived"/>
    <bean id="logMessageListener" class="com.cc.mer.ordercatcher.LogMessageReceived"/>
    <jms:listener-container
        connection-factory="jmsConnectionFactory"
        destination-type="durableTopic"
        transaction-manager="transactionManager"
        acknowledge="transacted"
        >
        <jms:listener ref="ocsMessageListener" destination="OCS_RELAYED"
                      subscription="ocs.db.recording" />
    </jms:listener-container>
    <jms:listener-container
        connection-factory="jmsConnectionFactory2"
        destination-type="durableTopic"
        transaction-manager="transactionManager"
        acknowledge="transacted"
        >
        <jms:listener ref="logMessageListener" destination="OCS_LOG"
                      subscription="ocs.log.recording" />
    </jms:listener-container>

Thank you all for your replies.
Yesterday, I went back to BestBuy and returned the Gigabit Ethernet Switch and exchanged it for a Belkin Share Max N300 router. I chose this one because I want to use the router in WIRED mode and this had a 10/100/1000Mbps Gigabit Ethernet capability. Most other routers that I looked at only had 10/100Mbps. I also liked that it had two USB ports.
I had to call Belkin tech support because the installer from the included CD would not install the software. Nor would the installer that I downloaded from their web site. I ended up actually having to be taken to the IP address' web site and from there I was able to configure everything.
Although it took me a few hours to get all my other wireless devices onto my wireless network (I have a couple of Airport Express(es) for running "Airplay," and a wifi dongle on my TV), things now seem to be working fine.

Durable Subscription with MDB in Weblogic 7.0

Hi,
          I am using WLS 7.0 as the JMS Provider and as the EJB Container(no
          clustering). My question is do I need MDB with durable subscription. I
          cannot think of a instance when the container will be down but JMS
          provider is still running if I am using WLS as both container and JMS
          provider.
          One instance i can think of is if the MDB is not deployed (upon a new
          release of our application, for some strange reason) but rest of the
          application is deployed then the producers will produce messages for
          the off-line subscriber.
          If I assume that the above is not likely to happen, can you think of
          any compelling reason for me to use MDB with durable subcription .
          Thanks for your input.
          ssahu


1) The MDB should only specify "durable" if it is receiving from a
          topic. Durable does not apply to queues.
          2) If messages are non-persistent, then you likely don't need durable.
          As these messages don't survive the shutdown...
          3) Making it durable helps with race-conditions during shutdown or
          startup where messages are sent but the MDB isn't up. It also helps
          with the condition where shutdown occurs before the MDB finishes
          processing all of its messages. (So Durable ensures that the
          MDB does not miss a message. It may even help in the non-persistent
          case if is possible that the MDB is temporarily undeployed (by you)
          while the server is up.
          [email protected] wrote:
          > Hi,
          > I am using WLS 7.0 as the JMS Provider and as the EJB Container(no
          > clustering). My question is do I need MDB with durable subscription. I
          > cannot think of a instance when the container will be down but JMS
          > provider is still running if I am using WLS as both container and JMS
          > provider.
          > One instance i can think of is if the MDB is not deployed (upon a new
          > release of our application, for some strange reason) but rest of the
          > application is deployed then the producers will produce messages for
          > the off-line subscriber.
          >
          > If I assume that the above is not likely to happen, can you think of
          > any compelling reason for me to use MDB with durable subcription .
          >
          > Thanks for your input.
          >
          > ssahu

Alert subscription data source module encountered errors while running: Alert subscription data source module was unable to find alerts that match the subscription because of database errors.

Hi, We recently started getting these errors a couple times a day. There are 12 of them in total. We also have exactly 12 subscriptions. Does this indicate some db issue causing all of these
to fail?
Alert subscription data source module encountered errors while running: Alert subscription data source module was unable to find alerts that match the subscription because of database errors.
The following error(s) were encountered:
Exception Message: ExecuteScalar requires an open and available Connection. The connection's current state is closed.
One or more workflows were affected by this.
Workflow name: Subscription8b108a3e_4e3d_4fd0_b67e_cbfc21cd10b8
Instance name: Alert Notification Subscription Server
Instance ID: {E07E3FAB-53BC-BC14-1634-5A6E949F9230}
Management group: A Company Management Group
Thanks Lance

Hi,
Do you have hotfixes applied?
http://blogs.technet.com/kevinholman/archive/2009/01/27/which-hotfixes-should-i-apply.aspx
Also, I found a relevant thread for your reference.
Alert subscription data source module encountered errors while running</u1:p>
http://social.technet.microsoft.com/Forums/systemcenter/en-US/50557249-7f97-4b67-9729-f7088202385b/alert-subscription-data-source-module-encountered-errors-while-running?forum=operationsmanagergeneral</u1:p>
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Bridge cc expand to dual monitor mode when copying or deleting photos?

why does bridge cc expand to dual monitor mode when copying or deleting photos?

You say your running 10.5.6? Why haven't you updated to 10.5.8?
FWIW, I never had color issues under 10.5.X, however I have since upgrade to 10.6.
See the thread I started in which Adobe responded:
http://forums.adobe.com/thread/483359

Bridge Deleting Folders on Our Server

Twice now here at work,
2 different people were trying to make a shortcut in their 'favorites' panel in Bridge,
and the folder itself has disappeared COMPLETELY...
luckily our server is backed up nightly,
so not much was lost (except that morning's work), but still, how is this happening?
In the first instance,
the person was dragging the folder from a 'finder' window into 'favorites' and it just disappeared,
the second instance was being done directly in Bridge and the same thing happened...
This is more than a little scary, and have never had this problem before and now it's happened twice in a month...
We're all on iMacs (10.6 and up) and using CS 5....
H E L P!
Thanks

Bridge seems to literally be deleting the folder from our server somehow when trying to make a shortcut in the favorites panel...
First of all, Bridge is not designed to work over a network configuration, nor does Adobe support this use. Creating a favorite of a folder is nothing else then creating an alias for this folder so their should be no reason to delete it at all.
But all things that you change in Bridge are user related and the info is stored somewhere in the user library (not everything is easy to find but if you preview a file the cache for it builds in the Cache folder which is by default in the user library in the user account itself. If you work on other accounts over a network their might get confusion of which info to store where. I find it hard to believe Bridge deletes folders completely by creating an alias but I also have no experience with network environment.
So if you would like to use a Digital Asset Management and you want to use Bridge for it you should threat it with great care and much discipline for all users.
Check this blog, this guy did achieve a network based environment.
But to be honest, you better look for a dedicated network DAM application that is designed for this task. And if you need the powers of Bridge you best do so in user based situations.

Wls7 GA bridge deletes durable subscriptions on source destination when stopped

Similar Messages

Maybe you are looking for