MDB+JMS+JMSAppender
Hi,
I'm trying to run JMSAppender i have a few questions.
First is related with MDB. I deployed it on Oracle9iAS this kind of mdb:
<message-driven >
<description><![CDATA[]]></description>
<display-name>iateLogginMDB</display-name>
<ejb-name>iateLogginMDB</ejb-name>
<ejb-class>cdt.iate.jms.JmsLoggin</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Topic</destination-type>
<subscription-durability>NonDurable</subscription-durability>
</message-driven-destination>
- <resource-ref>
<description>Topic Queue</description>
<res-ref-name>jms/TopicConnectionFactory</res-ref-name>
<res-type>javax.jms.TopicConnectionFactory</res-type>
<res-auth>Application</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
</message-driven>
It works perfect on JBoss, but I'm not sure, that it works here. Question: how can
I be sure, that it was delpoyed? I took a look through admin console and it says to me, that ejb-app is deployed, but inside I can't see any bean. I suspect, that it shows only CMP beans, I'm right?
Is any way to see MDB status, how many active connections and so on?
Next thing is related with JMSAppender. I'm not sure, that it works ok. I didn't find some log file to see all errors of application. I read about a possibility here:
http://www.oracle.com/technology/tech/java/oc4j/htdocs/oc4j-logging-debugging-technote.html, but my application.log is prety empty. Is it possible to get log4j error in this file?
I tested JMS and I got through JNDI JMS object. But I don't know how can I test MDB and JMSAppender. Of course MDB can be tested through some web layer, but it will take same time:)
Could you help?
yael800 wrote:
Tank's for your replays.
I just want to create MDB project that listening to the JMS.
I need a small example for that goal.To be honest, writing an MDB is an absolute piece of p!ss. Where you'll find things getting complex is the configuring of your containers and brokers. And that very much depends on what containers and brokers you're using. You're just going to have to bite the bullet and read some documentation
Similar Messages
-
MDB-JMS Connection Failure : User Denied.
I am trying to deploy an EAR Containing three MDB, and all MDB use the same User created in Secuity Realms. All three MDb connect to different JMS. But Only one MDb fails to connect to its JMS even though login credentials are same for all three MDBs.
I am sure password set at Security Realm and password of the queue are same. I am able to successfully connect to JMS from a standalone java application
I see below error in Weblogic for the MDB that is failing.
javax.naming.AuthenticationException [Root exception is javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User NettingEng javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User NettingEng denied]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:44)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:674)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:469)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl$2.run(MessageDrivenBeanInfoImpl.java:746)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.doPrivilagedAction(MessageDrivenBeanInfoImpl.java:2238)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:733)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:689)
at weblogic.jms.common.CDS$DD2Listener$1.run(CDS.java:1018)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
at weblogic.jms.common.CDS$DD2Listener.getInitialContextFromListener(CDS.java:1012)
at weblogic.jms.common.CDS$DD2Listener.getInitialContext(CDS.java:984)
at weblogic.jms.common.CDS$1.run(CDS.java:436)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
at weblogic.jms.common.CDS.createInitialContext(CDS.java:431)
at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:270)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)Can you share your standalone java program and mdb?
It will be interesting to see the difference.
[email protected]
-Faisal
http://weblogic-wonders.com
Edited by: Faisal Khan on Feb 25, 2011 11:17 AM -
Help setting up my first MDB JMS in websphere studio
Hello gurus,
In my servlet I have set the connection factory name to "jms/QCF" and queue to "jms/Q".
* Under JMS tab I set the JMS Provider to MQ Simulator for Java Developers.
* I set JMS Connection Factories name to jms/QCF and jndi value to jms/QCF.
* Under JMS Destinations I set the Queue name to Q and jndi name to jms/Q
* Under JMS Server Properties I added a queue Q since I set the Queue name to Q above.
I send the message using QueueSender but the MDB is not receiving it..
In my MDB I just have a print statement in the onMessage method but its not being fired..
What am I doing wrong?
Please help.Hello gurus,
In my servlet I have set the connection factory name to "jms/QCF" and queue to "jms/Q".
* Under JMS tab I set the JMS Provider to MQ Simulator for Java Developers.
* I set JMS Connection Factories name to jms/QCF and jndi value to jms/QCF.
* Under JMS Destinations I set the Queue name to Q and jndi name to jms/Q
* Under JMS Server Properties I added a queue Q since I set the Queue name to Q above.
I send the message using QueueSender but the MDB is not receiving it..
In my MDB I just have a print statement in the onMessage method but its not being fired..
What am I doing wrong?
Please help. -
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
-
Issue with MDB (jms Queue) in weblogic 8.1
Hi all...
I'm facing a strange kind of problem with MDB using weblogic 8.1.
The code worked perfectly in weblogic 7.0.
This is wht i'm trying to achieve..
i'm having a MDB which implements a onMessage().
I'm publishing message thru a standalone client. Publishing works fine..
The problem is onMessage(javax.jms.Message msg) is never been called :-(.
when i monitor it shows that messages are recieved..
Am is missing something that is really important..
here is my code
package com.csxwt.zodiac.service.domain;
import javax.ejb.*;
import javax.jms.*;
import javax.naming.*;
import java.io.Serializable;
//import com.csxwt.zodiac.service.domain.TestObject;
public class MDBTestBean implements MessageDrivenBean, MessageListener {
MessageDrivenContext messageDrivenContext;
public void ejbCreate() throws CreateException {
System.out.println("into the ejb create");
/**@todo Complete this method*/
public void ejbRemove() {
/**@todo Complete this method*/
public void onMessage(javax.jms.Message msg) {
System.out.println("into the onMessage method 1 ");
ObjectMessage objectMsg = null;
String strObject = "Test";
try
System.out.println("into the onMessage method 2 ");
if (msg instanceof ObjectMessage)
System.out.println("into the onMessage method 3");
objectMsg = (ObjectMessage) msg;
Serializable serializableObj = objectMsg.getObject();
String test = serializableObj.toString();
System.out.println("value of the message sent " + test);
TestObject test1 = null;
if(serializableObj instanceof TestObject )
test1 = (TestObject) serializableObj;
System.out.println("after getting the test value ");
System.out.println("getting the test object valuye " + test1.getName());
else
return;
catch (Exception e)
System.out.println("Message Bean:unexpected Exception thrown ");
e.printStackTrace();
public void setMessageDrivenContext(MessageDrivenContext messageDrivenContext)
System.out.println("into MDB context");
this.messageDrivenContext = messageDrivenContext;
here are the 2 xml files....
<ejb-jar>
<enterprise-beans>
<message-driven>
<display-name>MDBTest</display-name>
<ejb-name>MDBTest</ejb-name>
<ejb-class>com.csxwt.zodiac.service.domain.MDBTestBean</ejb-class>
<transaction-type>Container</transaction-type>
<message-selector>GATE_LANE</message-selector>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>MDBTest</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>MDBTest</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>200</max-beans-in-free-pool>
<initial-beans-in-free-pool>20</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>zodiac.jms.queue.HardWareOutMessageQueue</destination-jndi-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Am i missing something somewhere?????
any help in this is highly appreciated..
thanks in advance.
r
sasi
Check your log for error and warning messages. If there
are some, they should help trace down the problem. If there
aren't any, try confirm that your MDB is deploying in
the first place.
The MDB below is a Q MDB, but you write below that your client
is a "publisher". "Publisher" implies a topic producer, not
a queue producer, and topic producer can't publish to queues.
Tom
T. Sasii Dharma wrote:
> Hi all...
>
> I'm facing a strange kind of problem with MDB using weblogic 8.1.
> The code worked perfectly in weblogic 7.0.
> This is wht i'm trying to achieve..
> i'm having a MDB which implements a onMessage().
> I'm publishing message thru a standalone client. Publishing works fine..
> The problem is onMessage(javax.jms.Message msg) is never been called :-(.
> when i monitor it shows that messages are recieved..
> Am is missing something that is really important..
>
> here is my code
>
> package com.csxwt.zodiac.service.domain;
>
> import javax.ejb.*;
> import javax.jms.*;
> import javax.naming.*;
> import java.io.Serializable;
> //import com.csxwt.zodiac.service.domain.TestObject;
>
> public class MDBTestBean implements MessageDrivenBean, MessageListener {
> MessageDrivenContext messageDrivenContext;
> public void ejbCreate() throws CreateException {
> System.out.println("into the ejb create");
> /**@todo Complete this method*/
> }
> public void ejbRemove() {
> /**@todo Complete this method*/
> }
> public void onMessage(javax.jms.Message msg) {
> System.out.println("into the onMessage method 1 ");
> ObjectMessage objectMsg = null;
> String strObject = "Test";
> try
> {
> System.out.println("into the onMessage method 2 ");
> if (msg instanceof ObjectMessage)
> {
> System.out.println("into the onMessage method 3");
> objectMsg = (ObjectMessage) msg;
> Serializable serializableObj = objectMsg.getObject();
> String test = serializableObj.toString();
> System.out.println("value of the message sent " + test);
> TestObject test1 = null;
> if(serializableObj instanceof TestObject )
> {
> test1 = (TestObject) serializableObj;
> System.out.println("after getting the test value ");
> System.out.println("getting the test object valuye " + test1.getName());
> }
>
> }
> else
> {
> return;
> }
>
> }
> catch (Exception e)
> {
> System.out.println("Message Bean:unexpected Exception thrown ");
> e.printStackTrace();
> }
>
> }
> public void setMessageDrivenContext(MessageDrivenContext messageDrivenContext)
> {
> System.out.println("into MDB context");
>
> this.messageDrivenContext = messageDrivenContext;
> }
> }
>
>
> here are the 2 xml files....
>
> <ejb-jar>
> <enterprise-beans>
> <message-driven>
> <display-name>MDBTest</display-name>
> <ejb-name>MDBTest</ejb-name>
> <ejb-class>com.csxwt.zodiac.service.domain.MDBTestBean</ejb-class>
> <transaction-type>Container</transaction-type>
> <message-selector>GATE_LANE</message-selector>
> <message-driven-destination>
> <destination-type>javax.jms.Queue</destination-type>
> </message-driven-destination>
> </message-driven>
> </enterprise-beans>
> <assembly-descriptor>
> <container-transaction>
> <method>
> <ejb-name>MDBTest</ejb-name>
> <method-name>*</method-name>
> </method>
> <trans-attribute>Required</trans-attribute>
> </container-transaction>
> </assembly-descriptor>
> </ejb-jar>
>
> <weblogic-ejb-jar>
> <weblogic-enterprise-bean>
> <ejb-name>MDBTest</ejb-name>
> <message-driven-descriptor>
> <pool>
> <max-beans-in-free-pool>200</max-beans-in-free-pool>
> <initial-beans-in-free-pool>20</initial-beans-in-free-pool>
> </pool>
> <destination-jndi-name>zodiac.jms.queue.HardWareOutMessageQueue</destination-jndi-name>
> </message-driven-descriptor>
> </weblogic-enterprise-bean>
> </weblogic-ejb-jar>
>
> Am i missing something somewhere?????
> any help in this is highly appreciated..
>
> thanks in advance.
>
> r
> sasi
-
Hi,
Please I need your help!
I just want to create a MDB project that listening to the JMS.
I need a small example for that goal.
Have a supper day,
Yael.Thanx,
I created EJB project as you told me.
In folow this link:
[Else Example|http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JMS5.html#wp79938]
I created 2 EJB in netbeats 6.1:
SimpleProducer
SimpleProducer-ejb --> I added SimpleProducer.java
SimpleProducer-war
SimpleSynchConsumer
SimpleSynchConsumer-ejb --> I added SimpleSynchConsumer.java
SimpleSynchConsumer-war
Please I need your helppppp heare from heare,
Have a good day,
Yael.
Edited by: yael800 on Aug 26, 2008 4:18 AM -
MDB,MDB container or JMS adapter stops processing messages from JMS queue
Hi guys,
we have created a component using Enterprise Java Beans, let's say a product catalog, deployed it on a Glassfish v2 instance, and connected it to a legacy system using JMS and Sun MQ v4.1 as messaging system. The catalog component thus starts one MDB that listens on a JMS queue, let's say a queue named catalog_business_events_in, and waits for incoming messages, i.e. in our case update events. The problem is, that in general this approach works well, but sometimes the MDBs/JMS adapter stops for some reason fetching and processing messages from the JMS queue. We don't know why - no exceptions, etc.. Seems to be a Glassfish EJB container, JMS adapter or Sun MQ configuration issue. It seems to be that our component is not the problem.
The messages are compressed/uncompressed by Sun MQ automatically. We actually have 2 Sun MQ instances in clustered mode running to have some kind of failover - no HA cluster, yet. Sun MQ instances are accessed from Glassfish instances running in different Glassfish clusters - so we have a dedicated Sun MQ cluster not a Sun MQ instance per Glassfish instance. Each Glassfish instance is configured such that it knows both Sun MQ instances to allow automatic failover.
Has someone an idea, why the MDBs/ MDB container/ JMS adapter - stops processing messages? We are kind of puzzled as it happens more often now and apparently when traffic is (very) low not high!
Thanks for your help.
Cheers,
Martin
Edited by: east1979 on Jan 13, 2009 8:06 AMHi Manoj,
I have a very similar if not identical issue,
Error while running realtime jobs that read from JMS tables via JMS MQ adapter:
15/11/12 09:10:08 JMS GET OPERATION ERROR : TIMEOUT.UNABLE TO RECEIVE RESPONSE FROM THE INVOKED DATA SERVICES SERVICE.ADAPTER OPERA
TION TO CONTINUE.
15/11/12 09:10:15 Communication Error. See real time job log for details.
Dump available:
https://sapmats.wdf.sap.corp/download/download.cgi?id=5C0KZAHA3RSXBJW3ABLMUUT2P5UUKWO2TM3EJDM5W2HGDZUDID
Version of DS:14.0.3.273
Any comments?
Thansk and kind Regards,
Kenneth -
Is there any tutorial for jms development with jdeveloper out there ?
Hi
Thank you for reading my post
is there any tutorial which show us how to use jdeveloper +oc4j for JMS stuff ?
I mean an end 2 end tutorial to build mdb+jms resources in oc4j + client
it will be far better if the tutorial shows how we can use jdeveloper features for this task (if it provide any wizard...)This is an example of a client:
public String listeningJMS (Context context) throws Exception
String topicName = "jms/demoTopic";
String topicConnectionFactoryName = "jms/TopicConnectionFactory";
TopicConnectionFactory topicConnectionFactory = null;
TopicConnection topicConnection = null;
TopicSession topicSession = null;
Topic topic = null;
TopicSubscriber topicSubscriber = null;
TextMessage message = null;
String fileName = null;
* Look up connection factory and topic. If either does
* not exist, exit.
try
topicConnectionFactory = (TopicConnectionFactory)
context.lookup(topicConnectionFactoryName);
topic = (Topic) context.lookup(topicName);
* Create connection.
* Create session from connection; false means session is
* not transacted.
* Create subscriber.
* Register message listener (TextListener).
* Receive text messages from topic.
* When all messages have been received, enter Q to quit.
* Close connection.
topicConnection =
topicConnectionFactory.createTopicConnection();
topicSession =
topicConnection.createTopicSession(false,
Session.AUTO_ACKNOWLEDGE);
topicSubscriber =
topicSession.createSubscriber(topic);
topicConnection.start();
System.out.println("Receiving: ");
TextMessage msg = (TextMessage) topicSubscriber.receive();
String xmlString =msg.getText();
topicConnection.close();
System.err.println("Received: "+xmlString);
fileName = this.getFileName(msg.getText());
} catch (Exception e) {
throw e;
} finally {
if (topicConnection != null) {
try {
topicConnection.close();
} catch (JMSException e) {throw e;}
return fileName;
public static Context getInitialContext() throws NamingException {
Hashtable env = new Hashtable();
// Standalone OC4J connection details
env.put( Context.INITIAL_CONTEXT_FACTORY, "oracle.j2ee.rmi.RMIInitialContextFactory" );
env.put( Context.SECURITY_PRINCIPAL, "oc4jadmin" );
env.put( Context.SECURITY_CREDENTIALS, "welcome1" );
env.put(Context.PROVIDER_URL, "ormi://localhost:12401");
//env.put(Context.PROVIDER_URL, "ormi://localhost:23791");
return new InitialContext( env );
} -
WLS 8.1sp3 blocked threads halt MDB processing
Under Weblogic Server 8.1 SP3 JMS consumers stop processing the JMS queues. This only started happening following our upgrade from SP2. We had numerous test baselines as well as months of production data to validate this.
Specifically it appears that internal weblogic threads are blocked, preventing the MDBs (JMS consumers) from being dispatched. This doesn't immediately impact the user experience, but eventually unprocessed JMS messages accumulate and consume heap. You can figure out the rest.
We had 5 MDBs working on this particular JMS queue, so under moderate traffic all 5 would need to be blocked before the problem was realized.
As a work around, you'll need to request a patch from BEA. CR188391 appears to resolve this issue. You must request this however. BEA will not contact you - regardless of functional or economic impact.
Thanks
-SeanSean,
I've forwarded your comments internally. Usually, one can look in the release notes of future service-packs to see what's been fixed. I would think upgrading from SP3 to sp4, or even sp5 (the latest) would also have fixed the problem.
Tom, BEA -
Hi,
what does the bean technology add to the JSM by using the message driven beans instead of just using the regular asynchronus JMS?that's my question when and why should we chose:
1. simple asynchronous JMS
2. message-driven beansYou presumably mean:
1. "simple" JMS client
2. MDB JMS client
That'll depend first on your existing architecture.You'll go for the second option if you're already using EJB , as to leverage your existing IT investment.
Second, the EJB container gives you a number of services, so you don't have to worry about those yourself: life cycle management, scalability, transaction support, concurrency etc..
With a plain JMS client, you'll have to handle concurrency yourself, for example, by spawning different JMS instances.
If you're using an EJB container, that container will instantiate multiple MDB instances to handle multiple messages simultaneously.
OTOH, The EJB contract implies some limitations of use. For example, an MDB can be associated with only one queue or topic. So if you need a JMS client to be able to handle multiple queues ot topics, you'll need to create multiple MDB clients, or go for a simple non-MDB JMS consumer. -
JCA Message Inflow Integration With JMS Queue
Hi,
I want to integrate JCA message inflows with JMS Queue. I know JCA Message Inflow destination can be Message Driven Bean. But is it possible to specify a JMS queue as destination of JCA Message Inflow.
i.e.
JCA -> MDB -> JMS Queue
OR
JCA -> JMS Queue
ThanksHi Manish,
As of now there is no out-box-adapter for JMS queue.
If you don’t want JNBridge adapter (I hope you’re referring to same. There is no “jt” adapter as you mentioned), you can create a custom adapter which access the JMS queue.
Use WCF LOB adaper (WCF Lob
Adapter Wizard)and create an adapter.
Following article details about the .NET code for messaging with JMS queue, try the code.
Use JMS Messaging in your C# Applications
And following articles give details about using WCF LOB adapter/Wizard:
What Is the WCF LOB Adapter SDK?
Sample:
https://msdn.microsoft.com/en-us/library/bb798102.aspx
http://geekswithblogs.net/michaelstephenson/archive/2009/02/10/129302.aspx
Use similar code (one from above codeproject article where how to do messaging between JMS queue is shown) to wrapper it around custom WCF LOB adapter.
Give it a try, if you don’t want to spend anything on a 3<sup>rd</sup> party adapter.
Regards,
M.R.Ashwin Prabhu
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply. -
Can somebody explain the MDB rollback behaviour in Queues and Topics.
My specific questions are:
1) When a MDB, listening to a Queue, performs a rollback, does the message go back to the head of the queue (assumption is that the message should go back to the head of the queue)? Is this somewhere in the spec? Seems like different providers have different interpretations, all the JMS providers do not gurantee this behaviour.
2) If we replace the queue with Topic, where does the message go on a rollback?
3) Where does the message go when there are multiple subscribers to the Topic? Can the other subscribers that did consume the message successfully get the message again, if a subscriber performs a rollback?
The JMS specification does not cover these situation very well, so we are left to the mercy of the JMS providers.
4) Can somebody share the experience in this context, if we are trying to build a 'JMS agnostic' solution, how should we handle this rollback?
Thanks1. Its dependent on the JMS provider. In ActiveMQ 4.x it is replayed to the consumer a number of times before being placed on the head of the queue - so ordering is maintained if the message is successfully processed by the same consumer.
However ordering is often broken if the message is put back on the head of the queue if you have multiple consumers, since they compete for messages. Though if you have multiple consumers anyway, you often loose total ordering unless you use a technique like Exclusive Queues or Message Groups.
2. Typically it'll be replayed to the same consumer again. Most JMS providers provide a way to customize the redelivery policy; how many times will it be redelivered before sending to a dead letter queue, what is the replay exponential back off time etc.
3. Yes. Each topic subscriber gets their own copy of the message. It doesn't matter if one consumer does or does not process the message; other consumers are unaffected.
4. I'd just retry the operation and rely on the MDB/JMS providers dead letter queue and you should be fine.
BTW if ever you need a tool to browse the dead letter queues and maybe move messages from the dead letter queue back to the originating queue, you could try Hermes
http://www.hermesjms.com/
James
http://logicblaze.com/ -
JMS bridge and MQSeries. looking for statistics
Hi !
I have to use Weblogic 7 SP4 in cluster with a distant MQSeries queue manager.
I know I can't have a "exactly once" quality of service. I use a MDB (deplyed
on each instance of the server).
I'm looking for statistics about how often a message can be treated 2 (or more)
times.
Thanks a lot for any help !
Florent
Hi Florent,
Since these are MQ messages, it might be possible to find
such statistics in MQ. Also, I think that MQ stores a
redelivery count in their messages - so you can likely
instrument your application code to get at the count.
Note that 7.0 actually does support exactly once with WL MDBs driven
by MQ. If you use transactions you can infer some stats on redeliveries
by checking the relevant transaction statistics for rollback counts.
I'm attaching some notes on JMS integration for your
convenience.
Tom
florent wrote:
> Hi !
>
> I have to use Weblogic 7 SP4 in cluster with a distant MQSeries queue manager.
> I know I can't have a "exactly once" quality of service. I use a MDB (deplyed
> on each instance of the server).
>
> I'm looking for statistics about how often a message can be treated 2 (or more)
> times.
>
> Thanks a lot for any help !
>
> Florent
JMS Integration of Foreign Vendors with BEA WebLogic Server
The following notes are derived mostly from "http://dev2dev.bea.com/technologies/jms/index.jsp".
For additional questions, a good forum for WebLogic questions in general is "newsgroups.bea.com". These can be mined for information by using Google's newsgroup search function.
JMS Integration Overview
- For integration with "non-Java" and/or "non-JMS" platforms, see "Non-Java Integration Options" below.
- For a foreign JMS vendor to participate in a WL transaction it must support XA. Specifically, it must support the javax.jms.XA* interfaces.
- In WL versions 6.0 and up it is possible to make synchronous calls to foreign JMS vendors participate in a WL transaction as long as the foreign vendor supports XA.
- WL 6.0 and 6.1 MDBs can be driven by foreign vendors non-transactionally. They can be driven transactionally by a select few foreign vendors (MQ is not part of the select few)
- WL 7.0 and later, MDBs can be driven by foreign vendors transactionally and non-transationally.
- WL 6.1 and later WL provides a messaging bridge feature. Messaging bridges forward messages between any two JMS destinations, including foreign destinations, and can transfer messages transactionally or non-transactionally.
- WL 8.1 JMS provides additional features that simplify transactional and JNDI integration of foreign vendors. See http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
Integration with 8.1 Details
A good overview of 8.1 JMS interop capability is the presentation "Integrating Foreign JMS Providers with BEA WebLogic Server" here:
http://www.bea.com/content/files/eworld/presentations/Wed_03_05_03/Application_Servers/1097-Foreign_JMS_Providers_WLS.pdf
This document refers to helpful new 8.1 features, which simplify integration. These include:
http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_foreign_providers
http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
And are also summarized here (under interoperability):
http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
Also read the extensive MDB documentation, which extensively covers integrating foreign vendors:
http://edocs.bea.com/wls/docs81/ejb/message_beans.html
The 8.1 features are likely sufficient for most 8.1 integration needs, and you may not need to refer "Using Foreign JMS Providers With WLS" white-paper mentioned below.
Integration with 6.1 and 7.0 Details
Read the "Using Foreign JMS Providers With WLS" white-paper:
http://dev2dev.bea.com/products/wlserver/whitepapers/jmsproviders.jsp
Note that this white-paper does not take into account 8.1 features.
For 7.0 read the extensive 8.1 MDB documentation, which largely also applies to 7.0:
http://edocs.bea.com/wls/docs81/ejb/message_beans.html
Non-Java Integration Options
- WL JMS has a JNI based C client which is available for Windows and some UNIX platforms. This C client supports 7.0 and up, and will be officially packaged with WLS in 9.0 (virtually unchanged). The C API is currently only supported through the jms newsgroup. See "JMS C API", here:
http://dev2dev.bea.com/technologies/jms/index.jsp
- WL supports direct Windows COM access through its "JCOM" feature. This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
http://e-docs.bea.com/wls/docs61/jcom.html
http://e-docs.bea.com/wls/docs70/jcom/
http://e-docs.bea.com/wls/docs81/jcom/
- Similar to JCOM, but more advanced, WL supports IIOP standard based access on multiple platforms. You can use the BEA Tuxedo C client for this purpose (no license fee). This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
http://e-docs.bea.com/wls/docs81/rmi_iiop/
http://e-docs.bea.com/wls/docs70/rmi_iiop/
http://e-docs.bea.com/wls/docs61/rmi_iiop/
Unlike most other approaches, the IIOP client approach also allows the client to begin and commit user (JTA) transactions (not configured).
- If you already have a BEA Tuxedo license, one option is communicate through BEA Tuxedo (which has various APIs on Windows) and configure a WebLogic Server to respond to these requests via the WTC bridge. Search for "WTC" in the BEA docs. Unlike most other approaches, the Tuxedo API approach also allows the client to begin and commit user (JTA) transactions.
- Another approach is to interop via web-service standards. Or even to simply to invoke a servlet on the WL server using a basic HTTP call from Windows. These in turn can invoke the JMS API. There is a white-paper on "Interoperability Study of BEA WebLogic Workshop 8.1 and Microsoft .NET 1.1 Web Services", that demonstrates web-services here:
http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf
- Yet another approach is to use a third party product that is designed to wrap any JMS vendor. There are even open source versions. In no particular order, here are some examples: Open3 WinJMS, CodeMesh, Active JMS, SpiritSoft
- Finally, there are .NET/C/C++ integration libraries that not specific to JMS, some examples are JNBridge, Jace, and CodeMesh.
Notes on MQ Remote Capable XA Clients
Until recently, IBM MQ JMS clients could not work transactionally unless they were running on the same host as their MQ server. This is a limitation unique to MQ that was relaxed with the introduction of IBM's new "WebSphere MQ Extended Transactional Client". See:
http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf
The product is new, and for some reason, configuration of this client seems to be tricky, even when WebLogic is not involved at all. Oddly, the main sticking point seems to be simply making sure that class paths refer to the required IBM jars:
- Required on WLS where MQ objects are bound into JNDI:
com.ibm.mq.jar, com.ibm.mqjms.jar
- Required only if MQ objects are bound into JNDI on a different server:
com.ibm.mq.jar
If there are problems when using this client, first get it to work using a pure IBM client without any BEA classes involved. Once that is working, search the WL JMS newsgroup for answers and/or contact BEA customer support.
Notes on Oracle AQ Integration
If problems are encountered integrating Oracle's built-in queuing (Oracle AQ) JMS client, there is publicly available wrapper code that can aid integrating AQ directly into MDBs, JMS, or the messaging bridge. The solution is titled "Startup class to bind AQ/Referenceable objects to WLS JNDI", is not supported by BEA, and is posted to:
http://dev2dev.bea.com/codelibrary/code/startupclass.jsp
Caveats:
The solution doesn't directly support concurrent consumers. Perhaps Oracle requires that concurrent consumers each have a unique JMS connection? As a work-around, parallel message processing can be achieved indirectly by forwarding AQ messages into a WL JMS destination - which do support concurrent processing.
Up-to-date versions of Oracle may be required. For more information, google search the weblogic.developer.interest.jms newsgroup for "Oracle" and "AQ".
The solution doesn't seem to support transactions, it may be possible to extend it to do so.
MDB Thread Pool Notes
WL7.0SP? and WL8.1 and later support the "dispatch-policy" field to specify which thread pool an MDB uses to run its instances. In most cases this field should be configured to help address potential performance issues and/or dead-locks:
http://edocs.bea.com/wls/docs81/ejb/DDreference-ejb-jar.html#dispatch-policy
(Note that "dispatch-policy" is ignored for non-transactional foreign vendors; in this case, the MDB "onMessage" callback runs in the foreign vendor's thread.)
MDB Concurrency Notes
Queue MDBs driven by foreign providers can run multiple instances concurrently. Topic MDBs driven by foreign providers are limited to one instance (not sure, but transactional foreign driven topic MDBs may not have this limitation). The size of the thread pool that the MDB runs in and the "max-beans-in-free-pool" descriptor limit how many instances run concurrently.
Design Guide-Lines and Performance Tuning Notes
The "WebLogic JMS Performance Guide" white-paper contains detailed design, performance, and tuning information for Clustering, Messaging Bridge, JMS, and MDBs.
http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD.jsp
-
hello
i can find tons of tutoriala about developing session bean and entity bean by using jdeveloper,but can't find even one article that tell me how to develop message driven bean and jms by using jdeveloper,who can help me,where can i find such tutorial?
thank you!While it isn't a tutorial on how to develop an MDB/JMS application using JDev, this one:
http://otn.oracle.com/tech/webservices/htdocs/series/jms/content.html
does provide a working sample of an MDB and JMS application within JDeveloper (and the associated configuration setup) as well as plugging in an extra piece on Web services.
Mike. -
WebLogic with WebSphere MQ as an XA resource
I have been using WebLogic MDBs with WebSphere MQ as an external JMS provider. We just bought MQ Extended Client that would let external transaction managers do XA management with MQ. I have looked at IBM's document @
http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf. This document indicates that Weblogic cannot be used to do XA with MQ; only three txn managers are mentioned - CICS, Encina, and Tuxedo.
I don't believe that to be true because it says that it can be used with any XA compliant transaction manager. Is anyone aware of documents showing how to configure a WebLogic server (expecially MDBs) to use MQ extended client to do XA?WL is an XA compliant TM, and many customers use it with MQ. For more information, you can start with this FAQ:
http://e-docs.bea.com/wls/docs81/faq/interop.html#268632
Also see the notes I've appended below.
Finally, you can search this newsgroup - you will see that your question comes up quite a bit.
Tom, BEA
JMS Integration of Foreign Vendors with BEA WebLogic Server
The following notes are derived mostly from "http://dev2dev.bea.com/technologies/jms/index.jsp".
For additional questions, a good forum for WebLogic questions in general is "newsgroups.bea.com". These can be mined for information by using Google's newsgroup search function.
JMS Integration Overview
- For integration with "non-Java" and/or "non-JMS" platforms, see "Non-Java Integration Options" below.
- For a foreign JMS vendor to participate in a WL transaction it must support XA. Specifically, it must support the javax.jms.XA* interfaces.
- In WL versions 6.0 and up it is possible to make synchronous calls to foreign JMS vendors participate in a WL transaction as long as the foreign vendor supports XA.
- WL 6.0 and 6.1 MDBs can be driven by foreign vendors non-transactionally. They can be driven transactionally by a select few foreign vendors (MQ is not part of the select few)
- WL 7.0 and later, MDBs can be driven by foreign vendors transactionally and non-transationally.
- WL 6.1 and later WL provides a messaging bridge feature. Messaging bridges forward messages between any two JMS destinations, including foreign destinations, and can transfer messages transactionally or non-transactionally.
- WL 8.1 JMS provides additional features that simplify transactional and JNDI integration of foreign vendors. See http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
Integration with 8.1 Details
A good overview of 8.1 JMS interop capability is the presentation "Integrating Foreign JMS Providers with BEA WebLogic Server" here:
http://www.bea.com/content/files/eworld/presentations/Wed_03_05_03/Application_Servers/1097-Foreign_JMS_Providers_WLS.pdf
This document refers to helpful new 8.1 features, which simplify integration. These include:
http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_foreign_providers
http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
And are also summarized here (under interoperability):
http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
Also read the MDB documentation, which extensively covers integrating foreign vendors:
http://edocs.bea.com/wls/docs81/ejb/message_beans.html
The 8.1 features are likely sufficient for most 8.1 integration needs, and you may not need to refer "Using Foreign JMS Providers With WLS" white-paper mentioned below.
Integration with 6.1 and 7.0 Details
Read the "Using Foreign JMS Providers With WLS" white-paper:
http://dev2dev.bea.com/products/wlserver/whitepapers/jmsproviders.jsp
Note that this white-paper does not take into account 8.1 features.
For 7.0 read the extensive 8.1 MDB documentation, which largely also applies to 7.0:
http://edocs.bea.com/wls/docs81/ejb/message_beans.html
Non-Java Integration Options
- WL JMS has a JNI based C client which is available for Windows and some UNIX platforms. This C client supports 7.0 and up, and will be officially packaged with WLS in 9.0 (virtually unchanged). The C API is currently only supported through the jms newsgroup. See "JMS C API", here:
http://dev2dev.bea.com/technologies/jms/index.jsp
- WL supports direct Windows COM access through its "JCOM" feature. This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
http://e-docs.bea.com/wls/docs61/jcom.html
http://e-docs.bea.com/wls/docs70/jcom/
http://e-docs.bea.com/wls/docs81/jcom/
- Similar to JCOM, but more advanced, WL supports IIOP standard based access on multiple platforms. You can use the BEA Tuxedo C client for this purpose (no license fee). This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
http://e-docs.bea.com/wls/docs81/rmi_iiop/
http://e-docs.bea.com/wls/docs70/rmi_iiop/
http://e-docs.bea.com/wls/docs61/rmi_iiop/
Unlike most other approaches, the IIOP client approach also allows the client to begin and commit user (JTA) transactions (not configured).
- If you already have a BEA Tuxedo license, one option is communicate through BEA Tuxedo (which has various APIs on Windows) and configure a WebLogic Server to respond to these requests via the WTC bridge. Search for "WTC" in the BEA docs. Unlike most other approaches, the Tuxedo API approach also allows the client to begin and commit user (JTA) transactions.
- Another approach is to interop via web-service standards. Or even to simply to invoke a servlet on the WL server using a basic HTTP call from Windows. These in turn can invoke the JMS API. There is a white-paper on "Interoperability Study of BEA WebLogic Workshop 8.1 and Microsoft .NET 1.1 Web Services", that demonstrates web-services here:
http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf
- Yet another approach is to use a third party product that is designed to wrap any JMS vendor. There are even open source versions. In no particular order, here are some examples: Open3 WinJMS, CodeMesh, Active JMS, SpiritSoft
- Finally, there are .NET/C/C++ integration libraries that not specific to JMS, some examples are JNBridge, Jace, and CodeMesh.
Notes on MQ Remote Capable XA Clients
Until recently, IBM MQ JMS clients could not work transactionally unless they were running on the same host as their MQ server. This is a limitation unique to MQ that was relaxed with the introduction of IBM's new "WebSphere MQ Extended Transactional Client". See:
http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf
The product is new, and for some reason, configuration of this client seems to be tricky, even when WebLogic is not involved at all. Oddly, the main sticking point seems to be simply making sure that class paths refer to the required IBM jars:
- Required on WLS where MQ objects are bound into JNDI:
com.ibm.mq.jar, com.ibm.mqjms.jar
- Required only if MQ objects are bound into JNDI on a different server:
com.ibm.mq.jar
If there are problems when using this client, first get it to work using a pure IBM client without any BEA classes involved. Once that is working, search the WL JMS newsgroup for answers and/or contact BEA customer support.
Notes on Oracle AQ Integration
If problems are encountered integrating Oracle's built-in queuing (Oracle AQ) JMS client, there is publicly available wrapper code that can aid integrating AQ directly into MDBs, JMS, or the messaging bridge. The solution is titled "Startup class to bind AQ/Referenceable objects to WLS JNDI", is not supported by BEA, and is posted to:
http://dev2dev.bea.com/codelibrary/code/startupclass.jsp
Caveats:
The solution doesn't directly support concurrent consumers. Perhaps Oracle requires that concurrent consumers each have a unique JMS connection? As a work-around, parallel message processing can be achieved indirectly by forwarding AQ messages into a WL JMS destination - which do support concurrent processing.
Up-to-date versions of Oracle may be required. For more information, google search the weblogic.developer.interest.jms newsgroup for "Oracle" and "AQ".
The solution doesn't seem to support transactions, it may be possible to extend it to do so.
MDB Thread Pool Notes
WL7.0SP? and WL8.1 and later support the "dispatch-policy" field to specify which thread pool an MDB uses to run its instances. In most cases this field should be configured to help address potential performance issues and/or dead-locks:
http://edocs.bea.com/wls/docs81/ejb/DDreference-ejb-jar.html#dispatch-policy
(Note that "dispatch-policy" is ignored for non-transactional foreign vendors; in this case, the MDB "onMessage" callback runs in the foreign vendor's thread.)
MDB Concurrency Notes
Queue MDBs driven by foreign providers can run multiple instances concurrently. Topic MDBs driven by foreign providers are limited to one instance (not sure, but transactional foreign driven topic MDBs may not have this limitation). The size of the thread pool that the MDB runs in and the "max-beans-in-free-pool" descriptor limit how many instances run concurrently.
Design Guide-Lines and Performance Tuning Notes
The "WebLogic JMS Performance Guide" white-paper contains detailed design, performance, and tuning information for Clustering, Messaging Bridge, JMS, and MDBs.
http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD.jsp
Maybe you are looking for
-
I have recently transferred my iPhoto Library to my external hard drive (WD MyBook Live) and have some questions. Since I have done this and used the "alt + option" to select it as my default library I have been having some issues. When using the l
-
Pass jstl sql query result to jsp
Hi I have the following code which works perfectly <%@ taglib prefix="sql" uri="http://java.sun.com/jsp/jstl/sql" %> <%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %> <sql:setDataSource dataSource="jdbc/dbtest"/> <sql:query var="items"
-
BUS6035 - create vendor invoice (without PO)
Hi Friends, I want create a Vendor invoice (FB60) through BUS6035. Now I have to indicate is it a credit note or an invoice, but I could not find a corresponding field in the LSMW- target structure. Can someone give me some help on this issue? Thank
-
Accessing a system object in the code
Hi all How can i lookup a system object based on an system alias in java code? Best regards Thomas
-
Is it possible to load transaction with multiple batch_source_name??
Hi, I am calling 'Autoinvoice Master Program' for creating transactions in my custom package. I have 15 lines in my data file. They are invoices, credit memos, debit memos with different batch_source_name. Import program is picking tranasctions with