MDBs in 9.1 continue to consume JMS queues even after being deleted

We have an MDB application that reads a batch message off of a JMS queue, archives it in a database, parses the batch message into individual messages and writes them onto other JMS queues to be consumed by another application. Everything was running fine in Weblogic 8.1.5. However, due to problems with XA drivers and the MSDTC(predictable SQL server crashes), we decided to upgrade to Weblogic 9.1 to take advantage of the LLR option.
 First, we had an issue where our MDBs were causing the following exception:
 ####<May 26, 2006 7:42:12 PM EDT> <Error> <JMX> <ist-clft2> <wltest1> <ExecuteThread: '1' for queue: 'default'> <<WLS Kernel>> <> <> <1148686932991> <BEA-149500> <An exception occurred while registering the MBean null.
 java.lang.IllegalArgumentException: Registered more than one instance with the same objectName : com.bea:ServerRuntime=wltest1,MessageDrivenEJBRuntime=RhapsodyMDB_DMBModule!JMSServer4@DMB_BEAN_QUEUE,Name=RhapsodyMDB_DMBModule!JMSServer4@DMB_BEAN_QUEUE,ApplicationRuntime=DataBrokerEAR1_2,Type=EJBPoolRuntime,EJBComponentRuntime=DataBrokerEJB new:[email protected] existing weblogic.ejb.container.monitoring.EJBPoolRuntimeMBeanImpl@7db003
 at weblogic.management.jmx.ObjectNameManagerBase.registerObject(ObjectNameManagerBase.java:146)
 at weblogic.management.mbeanservers.internal.WLSObjectNameManager.lookupObjectName(WLSObjectNameManager.java:133)
 at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:86)
 at weblogic.management.mbeanservers.internal.RuntimeMBeanAgent$1.registered(RuntimeMBeanAgent.java:104)
 at weblogic.management.provider.internal.RegistrationManagerImpl.invokeRegistrationHandlers(RegistrationManagerImpl.java:205)
 at weblogic.management.provider.internal.RegistrationManagerImpl.register(RegistrationManagerImpl.java:85)
 at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:320)
 at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:257)
 at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:222)
 at weblogic.ejb.container.monitoring.EJBPoolRuntimeMBeanImpl.<init>(EJBPoolRuntimeMBeanImpl.java:32)
 at weblogic.ejb.container.monitoring.MessageDrivenEJBRuntimeMBeanImpl.<init>(MessageDrivenEJBRuntimeMBeanImpl.java:49)
 at weblogic.ejb.container.manager.MessageDrivenManager.initialize(MessageDrivenManager.java:503)
 at weblogic.ejb.container.manager.MessageDrivenManager.setup(MessageDrivenManager.java:120)
 at weblogic.ejb.container.manager.MessageDrivenManager.setup(MessageDrivenManager.java:146)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManager(MessageDrivenBeanInfoImpl.java:1481)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createDDMDManagers(MessageDrivenBeanInfoImpl.java:1378)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.onDDMembershipChange(MessageDrivenBeanInfoImpl.java:1285)
 at weblogic.jms.common.CDS$DD2Listener.listChange(CDS.java:454)
 at weblogic.jms.common.CDSServer$DDHandlerChangeListener.statusChangeNotification(CDSServer.java:167)
 at weblogic.jms.dd.DDHandler.callListener(DDHandler.java:318)
 at weblogic.jms.dd.DDHandler.callListeners(DDHandler.java:344)
 at weblogic.jms.dd.DDHandler.run(DDHandler.java:282)
 at weblogic.jms.common.SerialScheduler.run(SerialScheduler.java:37)
 at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
 >
 ####<May 26, 2006 7:42:13 PM EDT> <Info> <EJB> <ist-clft2> <wltest1> <ExecuteThread: '1' for queue: 'default'> <<WLS Kernel>> <> <> <1148686933069> <BEA-010060> <The Message-Driven EJB: RhapsodyMDB has connected/reconnected to the JMS destination: weblogic.jms.DMB_BEAN_QUEUE.>
 
 Generally this happend after there were cluster communication issues. Multi-cast messages were lost and our MDB reconnects to the JMS queues as indicated by the below log:
 ####<May 30, 2006 5:19:06 PM EDT> <Info> <EJB> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '54' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1149023946040> <BEA-010060> <The Message-Driven EJB: DataBrokerMDB has connected/reconnected to the JMS destination: weblogic.jms.PHINMS_DMB_QUEUE.>
 ####<May 30, 2006 5:19:10 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023950228> <BEA-000112> <Removing RAPBEA3S jvmid:720875810499147484S:cmts-rap-bea3:[7005,-1,-1,-1,-1,-1,-1]:DMBstg:RAPBEA3S from cluster view due to timeout.>
 ####<May 30, 2006 5:19:11 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023951009> <BEA-000115> <Lost 2 multicast message(s).>
 ####<May 30, 2006 5:19:11 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023951040> <BEA-000111> <Adding RAPBEA3S with ID 720875810499147484S:cmts-rap-bea3:[7005,-1,-1,-1,-1,-1,-1]:DMBstg:RAPBEA3S to cluster: DMBstg_cluster view.>
 
 This would cause the queues to eventually have hundreds of consumers and cause the server to fail.
 Basically, it seems as though the MDBs that are supposed to stop continue and attempt to process, while new threads connect to the JMS queues.
 I tried undeploying our application and deleted it from the configuration. However there were consumers still on the respective queues and when I sent messages, I got an error indicating a "Class Not Found exception" due to the fact that the EJB was undeployed and deleted from the configuration, however the MDB component was not and continued to listen for messages. In 8.1.5, as soon as the application was undeployed, there were zero consumers on the JMS queues.
 I have read the posts about a soon to be released fix that would have the MDBs connect only to the queues locally and not go out the the cluster. Would this fix my issue?
 Is there something in the deployment descriptor to configure that will cause it to disconnect and now spawn so many consumers to the JMS queues?
 Why is it that the number of MDB consumers on the JMS queues stayed static in 8.1.5, but they are erratic in 9.1 even after I set our 9.1 server to use the 8.1.5 execute queue policy. Help would be much appreciated.

I recommend contacting customer support. There's a known problem with MDBs listening to distributed destinations that are local to the same cluster as the MDB, you're problem may be related (the clue is that the stack trace contains jms.dd.DDHandler.callListeners()). The problem is that the MDB connects to all physical queues in a distributed destination rather than just the local queue.
Tom

Similar Messages

When I run repair permissions I continue to get this message even after a full reformat and re-install of OS. "Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repai

When I run repair permissions I continue to get this message even after a full reformat and re-install of OS. "Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired."

Doug,
According to Apple, Mac OS X: Disk Utility's Repair Disk Permissions messages that you can safely ignore.

Re: Consuming jms queue synchronously in SOA11g

Hi
I have the below requirement
In Queue total 5 messages are there, in those 3 are with same ID and 2 are with same ID.
My requirement is that for the above 5 messages only two BPEL processes should be created for each ID.
1st BPEL consumes 3 messages
2nd BPEL consumes 2 messages
Please give me idea to do this.
Thanks in Advance
Vamsi..

Hello friend,
So, according to your scenario...you are producing messages into the Queue using JMS Adapter Outbound Operation ( JMS adapter is on the references side)
And as we know, in order to read the message from JMS Queue we use JMS Adapter and that would be inbound operation (JMS adapter is on the services side)
So, when we define a JMS adapter in our composite as consume message operation...then the JMS adapter will be on the services side...then we declare our BPEL interface based on the WSDL of JMS Adapter (Consume operation). SO by default the interface of the BPEL would be one-way i.e., just fire and forget. So, lets say you wrote 10 messages to the Queue. So, the consuming BPEL would take all messages at a time...as you said there would be 10 instances....
So, if you make the interface of the BPEL to synchronous and also you just need to reply back ( any dummy message) to JMS adapter....just keep a reply activity at the end of the BPEL ...so by doing this...unless and until it gets the response from the synchronous BPEL (consuming BPEL), the JMS adapter doesn't give the next message in the Queue to the BPEL...that means at any point of time only one BPEL instance would be running for you which is what we want to achieve...And you can see this clearly in the Queue in the weblogic admin console...This is called throttling the JMS adapter....This works...
And one more important thing to be considered is...taking the synchronous process time out thing...as we know by default the client of the synchronous process cannot wait for more than 45 seconds...may be if you want more time to process ...you can change that in EM console...BPEL properties in SOA administration...
I think it is syncMaxWaitTime..change that may be to 300...
Try this...Hopefully this should work for you..and let us know ...
Hope this helps...
Thanks,
N

Firefox continues to load streaming videos even after the tab is closed

I'm running Windows 7 64-bit, and I've noticed that whenever I go to load a video (from Youtube, for example), and close the tab before the video finishes loading, Firefox would still be downloading that video.
I can tell because my normal ping to a local server is about 50-60ms. Then when I begin loading the video, it'll jump up to about 800+ms. I close the tab, but the ping continues at this rate. If I go to another video, begin loading that, and close it before it finishes in the same fashion, it will stack, and Firefox will be loading two videos at once (my ping will spike to 1600ms).
This is an extremely annoying issue since my internet connection is on the slow side.

SOLVED!
The hidden download was caused by a Firefox extension named GrabPro, included in "Orbit Downloader" boundle.
GrabPro caches all streamed media, providing a way for save it quickly.
You can disable this feature unchecking the "Enable Recorder" option in its configuration dialog.
This sofware was present on all my tested systems.
That was the cause of my confusion.

ICloud continues to show open tabs even after Safari quit

Since OS 10.10, when I close and quit Safari on my iMac or MBP iCloud occasionally continues to show an open tab on the other devices like the iPhone, even for several hours after Safari has been quit on the iMac. This is annoying in that one time I left it, and the iMac restarted because of a kernel panic.
This appears to be an iCloud and Yosemite problem. Furthermore, I have called Apple care twice about this, and they have been unable to find any problem with my computers.
Has anyone else had this problem, and what to do about it.

Try clearing Safari's cache : Settings > Safari > Clear Cache (and Clear History)

New Ipad continues to draw down battery even after cover is closed. Is this normal?

Even though I close the cover and can hear the magnetic switch shut off the Ipad, it continues to draw down my battery, is this normal?
Screen does go blank

I've read different opinions (and personal stories) about whether the battery drains in sleep mode. All I know is that mine does not seem to drain. I was just noticing this last night. Before I went to bed my battery meter read 97%. I simply closed the smart cover to put it in sleep mode (I heard the click). When I opened the cover this morning it was still at 97%. I used it for about 15 minutes and only then did it drop to 96%. I did not turn off any wifi or location settings.
I should disclose that my battery meter was acting weird the other day. After a full charge, it was stuck on 100% during a few hours of light use (internet, email, kindle) before dropping again. Maybe my meter is just screwed up, but it seemed to be back to normal again and draining at a normal rate prior to my observation about it not draining at all during sleep mode.

Why Are Surnames Continually Added Back to Contact Entries After I Delete the Surname?

I have quite a few contacts with just their first name.
The Contacts app on my MacBook Pro continually adds last names -- if I had it in there at one time and since removed it -- back to the contact. Then this syncs over to my iPhone and iPads.
Why does Contacts do this and how can I stop it permanently?

Hello HellBlazerRaiser,
If contacts are reverting back, the next place I would try to fix is at iCloud.com, from there you can edit from the source of the contacts. I have also provided and article that will assist with troubleshooting contacts across multiple devices.
iCloud: Troubleshooting iCloud Contacts
http://support.apple.com/kb/ts3998
Thanks for using Apple Support Communities.
Regards,
-Norm G.

I continually have to "sign in" even after checking "stay signed in".

I continually have to sign in. I check the stay signed in box and it works for 3 or 4 times then I have to go through the email sign in process all over again.

Hello Patrick.
Hopefully this support article is what you need:
http://support.mozilla.com/en-US/kb/Cannot+log+in+to+websites

Mail is dowloading same emails after being deleted... continuously.

Upgraded to OS X Yosemite (mistake...) when first available. Ever since I completed the Yosemite upgrade, my mail app will not function properly. It is continuously downloading all messages since the upgrade date, even though I have deleted them and continue to delete them. This is happening with all my e-mail addresses (no Google or Yahoo), which are @comcast.net accounts. I have tried deleting accounts and reentering accounts to no avail. Any help would be appreciated.

Try re-indexing the mailboxes. This can take awhile if you have a lot of mail.
Reindex messages Mavericks/Yosemite

Labview application continues to run in taskbar even after quit labview

Hi,
My application is supposed to quit labview upon the press of a 'close application' button. But the application continues to run in the task bar and goes away only if task manager is brought up and the app is killed. Why does this happen? my code is quite heavy (7.45MB after installing)and uses lot of front panel controls (more than 300 since its for a batch testing bay)and also uses many synchronisation elements such as notifier, semaphores etc.
What can I do to make the application go away once the quit labview is true?
thanks!

Hi,
Using a lot of Notifiers and Queues could lead to this behavior, if obtained a lot of times. From the LabVIEW help:
"If you use the Obtain Queue function to return a reference to a named queue inside a loop, LabVIEW creates a new reference to the named queue each time the loop iterates. If you use Obtain Queue in a tight loop, LabVIEW slowly increases how much memory it uses because each new reference uses an additional four bytes. These bytes are released automatically when the VI stops running. However, in a long-running application it may appear as if LabVIEW is leaking memory since the memory usage keeps increasing. To prevent this unintended memory allocation, use the Release Queue function in the loop to release the queue reference for each iteration.."
Check/Verify if/that all references to Queues/ Notifiers ... are closed if no longer needed or used in a proper way.
Otherwise LabVIEW will close all the previously opend references in the end, what could take a while.
Regards,
CMW..
LV 13.0.1 Developer Suite with Automated Test; Win7 x64

MDB in a Cluster using Local JMS Queue (not distributed)

 Can I create a MDB that receives messages from a Local JMS Queue (created on each
 node) rather than a distributed queue?
 When I try to deploy such an MDB I get the following exception:
 weblogic.management.DeploymentException: Exception:weblogic.management.ApplicationException:
 activate failed for TestLocalMDBCluster Module: TestLocalMDBCluster Error: Exception
 activating module: EJBModule(TestLocalMDBCluster,status=PREPARED) Unable to deploy
 EJB: AsyncProcessor from TestLocalMDBCluster.jar: [EJB:011046]Unable to create
 EJBRuntimeMBean. javax.management.InstanceAlreadyExistsException: mydomain:ApplicationRuntime=Node2_TestLocalMDBCluster,EJBComponentRuntime=Node2_TestLocalMDBCluster_TestLocalMDBCluster,Location=Node2,Name=Node2_TestLocalMDBCluster_TestLocalMDBCluster_AsyncProcessor_jms/myserver,ServerRuntime=Node2,Type=MessageDrivenEJBRuntime
 at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
 at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:2371)
 at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:876)
 at weblogic.management.internal.RemoteMBeanServerImpl.private_registerMBean(RemoteMBeanServerImpl.java:582)
 at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanServerImpl.java:524)
 at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:166)
 at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:122)
 at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:85)
 at weblogic.ejb20.monitoring.EJBRuntimeMBeanImpl.<init>(EJBRuntimeMBeanImpl.java:33)
 at weblogic.ejb20.monitoring.MessageDrivenEJBRuntimeMBeanImpl.<init>(MessageDrivenEJBRuntimeMBeanImpl.java:30)
 at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.initPool(MessageDrivenBeanPoolInfoImpl.java:182)
 at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.activate(MessageDrivenBeanPoolInfoImpl.java:245)
 at weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.activatePoolInfo(MessageDrivenBeanInfoImpl.java:474)
 at weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanInfoImpl.java:440)
 at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1327) at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610)
 at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3127)
 at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2081)
 at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2062)
 at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592)
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515)
 at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317)
 at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:608)
 at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 Is there any way to do this?


I assume you are using queues.
 I truly wonder what you are doing different. Since the
 error is occuring outside of JMS and in the EJB - before JMS is called -
 I suggest posting to the ejb newsgroup.
 Note that yours is a standard use case which distributed destinations
 are actually specifically designed for (if you
 are using customer connection factories, just
 make sure ServerAffinity is enabled on the connection factory to
 ensure that clients always connect to the local physical destination,
 configure the MDB to refer to the JNDI name of the distributed
 destination, and then target the MDB to the cluster - an MDB pool
 will then automatically be dedicated to each physical destination).
 Tom
 Mark Colwell wrote:
 > Nope. It happens every time we try the scenario no matter what the application
 > is or which cluster. It always happens if we try to deploy even just a single
 > MDB (no other beans in the jar) to a cluster where the queue specified in the
 > deployment descripter is a local queue created on each node in the cluster. When
 > the jar is deployed we get the error.
 >
 > We have a strange situation were we really need the queue to be local and not
 > distributed but existing on every node. We can create all the local queues no
 > problem but trying to then deploy the application goes boom.
 >
 > Thanks for the response!
 >
 > Cheers,
 > Mark
 >
 > Tom Barnes <[email protected].bea.com>
 > wrote:
 >
 >>Mark Colwell wrote:
 >>
 >>
 >>>Can I create a MDB that receives messages from a Local JMS Queue (created
 >>
 >>on each
 >>
 >>>node) rather than a distributed queue?
 >>
 >>Yes. In fact this is the most common use case.
 >>
 >>
 >>>When I try to deploy such an MDB I get the following exception:
 >>
 >>I don't recall seeing this exception before. It looks like a naming
 >>conflict - it appears that somehow something is already running with
 >>the same name. Are you somehow deploying the same app twice?
 >>
 >>javax.management.InstanceAlreadyExistsException:
 >>mydomain:ApplicationRuntime=Node2_TestLocalMDBCluster,
 >>EJBComponentRuntime=Node2_TestLocalMDBCluster_TestLocalMDBCluster,
 >>Location=Node2,
 >>Name=Node2_TestLocalMDBCluster_TestLocalMDBCluster_AsyncProcessor_jms/myserver,
 >>ServerRuntime=Node2,
 >>Type=MessageDrivenEJBRuntime
 >>
 >>FYI: As of one or two weeks ago, the MDB section of the
 >>EJB docs has been heavily updated. I highly recommend
 >>reading it.
 >>
 >>
 >>>weblogic.management.DeploymentException: Exception:weblogic.management.ApplicationException:
 >>>activate failed for TestLocalMDBCluster Module: TestLocalMDBCluster
 >>
 >>Error: Exception
 >>
 >>>activating module: EJBModule(TestLocalMDBCluster,status=PREPARED) Unable
 >>
 >>to deploy
 >>
 >>>EJB: AsyncProcessor from TestLocalMDBCluster.jar: [EJB:011046]Unable
 >>
 >>to create
 >>
 >>>EJBRuntimeMBean. javax.management.InstanceAlreadyExistsException: mydomain:ApplicationRuntime=Node2_TestLocalMDBCluster,EJBComponentRuntime=Node2_TestLocalMDBCluster_TestLocalMDBCluster,Location=Node2,Name=Node2_TestLocalMDBCluster_TestLocalMDBCluster_AsyncProcessor_jms/myserver,ServerRuntime=Node2,Type=MessageDrivenEJBRuntime
 >>>at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
 >>>at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:2371)
 >>>at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:876)
 >>>at weblogic.management.internal.RemoteMBeanServerImpl.private_registerMBean(RemoteMBeanServerImpl.java:582)
 >>>at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanServerImpl.java:524)
 >>>at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:166)
 >>>at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:122)
 >>>at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:85)
 >>>at weblogic.ejb20.monitoring.EJBRuntimeMBeanImpl.<init>(EJBRuntimeMBeanImpl.java:33)
 >>>at weblogic.ejb20.monitoring.MessageDrivenEJBRuntimeMBeanImpl.<init>(MessageDrivenEJBRuntimeMBeanImpl.java:30)
 >>>at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.initPool(MessageDrivenBeanPoolInfoImpl.java:182)
 >>>at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.activate(MessageDrivenBeanPoolInfoImpl.java:245)
 >>>at weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.activatePoolInfo(MessageDrivenBeanInfoImpl.java:474)
 >>>at weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanInfoImpl.java:440)
 >>>at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1327)
 >>
 >>at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610)
 >>
 >>>at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3127)
 >>>at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2081)
 >>>at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2062)
 >>>at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592)
 >>>at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515)
 >>>at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317)
 >>>at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:608)
 >>>at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
 >>>at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at
 >>
 >>weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 >>
 >>>Is there any way to do this?
 >>
 >

Connecting to SeeBeyond JMS queue

Hello everybody,
we have J2EE application on Oracle Application Server. Right now we try to add MDB that has to listen on SeeBeyond JMS Queue. What do I need to specify in configure orion-ejb-jar.xml?
thanks

The howto is not a standalone resource adpater example, so the RA's archive file .rar is wrapped in an EAR file.
So if you deploy a standalone resource adapter, you will deploy a .rar file. But also you could embed your resource adapter file - .rar inside an application .ear file, as the howto example. so the structure looks like:
.ear -- .rar
-- .jar
-- xml descriptors
-- native libraries
If you take a look at build.xml it shows how the ear file is constructed.
-Frances

Doubt in Flat File Format in sender jms queue?

Hi All,
I have a JMS-IDOC scenario with Content Conversion. The input file can have fixed length, multiple records.
Each record comes in a newline.
But , heard, one cannot place a multiline data as a single message in the JMS Queue.
Each new line of the data will be placed as a single separate message.
so for every line , a new xml message gets created and the scenario gets triggered.
But I want the all records (lines) in a single xml message
Could someone tell me what is to be done?

> But , heard, one cannot place a multiline data as a single message in the JMS Queue.
That is wrong. You can put anything in the JMS queue, even binary.
Regards
Stefan

Consumer number for a JMS queue continues to grow

 I am using WLS 7.0 SP2. I have a JMS Queue and number of consumers continues to
 grow.
 Is there any way to stop it from growing? If not, should I be concerned about
 the memory usage by those consumers?
 Thanks.
 Rick


 Tom,
 You are right on JMS resources. We found that developer didn't close JMS session
 and conneciton which caused the memory leak. Now it has being running more than
 10 hours without crashing.
 Thanks.
 Rick
 Tom Barnes <[email protected]> wrote:
 >
 >Rick Chang wrote:
 >> I am using WLS 7.0 SP2. I have a JMS Queue and number of consumers
 >continues to
 >> grow.
 >>
 >> Is there any way to stop it from growing?
 >
 >No.
 >
 >> If not, should I be concerned about
 >> the memory usage by those consumers?
 >
 >Before jumping to conclusions though, make sure
 >that you are looking at the right statistic, there
 >are three for consumer count:
 > current -- active consumer count
 > high -- highest active consumer count
 > total -- total consumers ever created
 > (ever increasing by definition)
 >
 >If you are looking at "current"
 >the statistics point to a likely memory/resource leak.
 >Perhaps some part of your application is failing to close
 >its JMS resources when it is finished with them.
 >
 >>
 >> Thanks.
 >>
 >> Rick
 >

MDB (2-phase commit) behavior during abnormal JMS termination

Hello to everyone!
I plan to test the following scenario tomorrow (sort of a bug replication in our system).
Anyway, wanted to know in advance the expected behavior (just in case one of you already know
or have an experience related to this test). Thank you in advance.
Scenario:
I want to test/know the behavior of a 2-phase commit (2PC) MDB when JMS server abnormally exits
(say the process was killed).
Test flow:
start app server --> deploy 2pc-mdb --> send dummy data --> kill jms process --> restart jms process
1. will the connection be closed properly?
2. when jms server restarts, will the value of active consumer(count) doubled?
note: i think after mdb deployment, corresponding destination consumer count is 1.
the problem that occurred in our system was that the consumer count doubled after server restarted.
it seem like the previous connection was not closed when the jms server abnormally terminated.
any inputs will be greatly appreciated.
thanks and best regards.

You have to use TxDataSource for container managed tx or if you are using JTA (in
addition to ofcourse doing 2PC).
S
"Dale Olzer" <[email protected]> wrote:
>
Using weblogic 6.1 SP 4
I have a simple container managed Message Driven Bean. Using a destination
type
javax.jms.Queue.
When the onMessage method finishes the Message is still Pending on the
queue.
see the ejb-jar.xml below
<ejb-jar>
<enterprise-beans>
<message-driven>
<display-name>IvrMessageBean</display-name>
<ejb-name>IvrMsgBean</ejb-name>
<ejb-class>com.edocs.ps.ivr.IvrMsgBean</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
</ejb-jar>
I noticed when I set a JDBC TX DataSource to 2 Phase Commit, the JMS
transaction
started commitig and nothing was left pending in the Queue.
Does 2PC have to be set in a DataSource for Container Managed MDB's to
work?

MDBs in 9.1 continue to consume JMS queues even after being deleted

Similar Messages

Maybe you are looking for