Configuring MDB to listen to external destination

Hi,
Let me start by explaining the setup.
I have installed Sun MQ in a server lets say serverMQ and have created a Queue by name QueryQueue.
Application server is installed in another machine (serverAS).
Configured the file system based objectstore for the adminstered objects in the SunMQ and created external jndi resources in the application server to bind to the MQ objects.
I am trying to deploy an ejb application with an MDB in it which has to listen to the queue created in serverMQ.
I get the following exception during deployment
[#|2005-04-20T15:20:04.019-0400|SEVERE|sun-appserver-ee8.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=10;|com.sun.enterprise.connectors.ConnectorRuntimeException
com.sun.enterprise.connectors.ConnectorRuntimeException:
JMS resource not created : jms/test/QueryQueue
at
com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:558)
at
com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:442)
at
com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:139)
at
com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:187)
at
com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:221)
at
com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:477)
at
com.sun.enterprise.server.EJBModuleLoader.load(EJBModuleLoader.java:93)
at
com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:180)
at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:197)
at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:300)
at
com.sun.enterprise.server.PEMain.run(PEMain.java:294)
at
com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Can some one please throw some light on
What am I missing which causes the above problem?
or
Is there a limitation with Sun appserver to be used with external MQ middleware?
Thanks in advance
P

Hi pJava,
Did you follow the steps defined in the "Creating a JMS Connection Factory Resource" of the "Admin Console Tasks for JMS Connection Factories" in the chapter 8 of the SJS App Server 8 EE admin guide ? (p.162 in my guide) This will let you define a connection factory, in a way that it will be visible to the application server.
TE

Similar Messages

MDB to listen external destination

two weblogic servers (WL1 & WL2). MDB deployed in WL1. Mesaages will be posted in JMS server of WL2. My requirement is MDB will listen to these messages posted in WL2. How can i implement this using foreign JMS server?? or any other idea?? or online sample application or materials or tutorials??
Please send some suggestion.
Thanks in advance.

Hi!
I have had this kind of problem in other systems (acces JMS SeeBeyond server from Websphere). The solution for me was defining an external JMS provider pointing to our SeeBeyond server IP:port. However, i cant remember as much as where this option would be in Weblogic console :(
Good luck!

Configuring a BEA WebLogic 7.0 Server and MDB to Listen on an Oracle Queue

I am tasked with configuring a BEA WebLogic 7.0 SP1 Server, and deploying an MDB to listen to a queue created in Oracle Advanced Queuing. Has anyone had any experience in making this work? And if so, could you send me some sample code/XML that illustrates such?
Thanks!

See my reply at Deploying MDB on BEA WebLogic 7.0 to listen to Oracle AQ

How do I configure a Pioneer DVR-XD10 external dvd writer to my macbook pro laptop?

How do I configure a Pioneer DVR-XD10 external dvd writer to my macbook pro laptop?
I read online that you could use an external dvd writer on a macbook pro when the internal dvd writer died.
Please help?
It shows power running through the external dvd writer when I plug in the two usb ends into the respective ports, but it doesn't recognize it when I try to write media to a DVD.
Any help would be greatly appreciated.
Thanks in advance!

If you have not already done so, your chances will really improve if you....
1) Connect the printer to the USB port on the AirPort Extreme
2) Download and install Bonjour Print Services for Windows on the PC

Urgent : MDB stops listening to the queues after some time !!!

Hi,
I am using OJMS with OC4J 10.1.2 and db 9.2.0.5. I have a web application which send messages into the queue very frequently.
But the problem is the MDBs stop listening to the queues after some time (1-2 days) and no more messages will be dequeued from that point.
All these messages will move to the exception queue after their expiry.
But the dequeing agains resumes after restarting the OC4J !.
I guess, at some point mdbs are either becoming busy (locked ) or some exception occured while dequeing, hence they stop listening to the queues.
Please throw some light on this issue as it is very crucial in my project.
Regards
Prashanth

I've noticed this lately as well, with my iPhone 4. I couldn't confidently pin it directly on any particular iOS update, but my iPhone used to automatically connect up via Bluetooth with my Prius's handsfree feature, and now it doesn't. I work with a CE-based device at my job, with Bluetooth capability, and I used to test out that feature by having it discover my iPhone. This no longer works either.
What I have found (not really a solution, but it does work and may be a clue for Apple) is that if I simply go to the Settings app then the General -> Bluetooth screen and let it sit there, it will pair right up with my car within a few seconds. Bluetooth is always on, and always says "Now Discoverable" at the bottom of the settings screen.

MDB topic listener and concurrent processing

Hello to everybody.
I ve prototyped simple db publisher ,which publishes changed data from database to JMS topic. Then I have my MDB which listens on JMS topic.
I setup and implemented all correctly and it worked. There was 1 consumer = 1 mdb instance. Then I tried to do load testing , So I triggered 8000 changes from database. The db adapter did the job and published the 8000 messages on the JMS topic in a while. To mimic processing in MDB I put the sleep(10seconds) in MDB.
MDB topic processing seems to me as not concurrent one. Why? I observed 10 message decrease with 5-10 seconds.
What I expected was: concurrent processing of 8000 JMS messages by 1 MDB (so MDB is poolable component isnt it?).
So for 500 instances of topic MDB and 8000 messages on the JMS topic, I expected at least 8000/500 X 10 = 160 seconds to process message load.
I am using WLS 816.
Can You give me some hits.
Thanks
Roman

I did the same test on Weblogic 10 and it worked as expected. MDB durable subscriber consumed 8000 messages (each msg processing had 10 secs sleep inside.) within 2 minutes. So it is ok.
But why it did not worked on WLS 8.1? Is this a bug ?

How to configure webcenter services to use external LDAP?

Reassociating the identity store with an external LDAP server is mandatory only if you're using the Documents service and/or the Discussions service, in which case the WC_Spaces server, Content Server, and Collaboration server must all be configured to use the same external LDAP server.
The question is how to configure?
Is there any document which details this?
Please help! this is urgent.
Regards

Refer
http://docs.oracle.com/cd/E28280_01/webcenter.1111/e12405/wcadm_security_id_store.htm#WCADM1845
http://docs.oracle.com/cd/E28280_01/webcenter.1111/e12405/wcadm_security_id_store.htm#WCADM345
Thanks

Error when sending control recipe to external destination

Hi,
When Iam trying to send control recipe to external destination through CO53, Iam getting the status of the control recipe as 'Sent'. But when I check the tRFC log, I get the status, "connection closed (no data) ".
By selecting the line in the log and executing the LUW I get the message, target system/gate way not active.
In the external system I get the message " Illigal activity"
I checked the RFC connection in SM59 and connection is ok.
The RFC is working from SE37 and the control recipe can be processed without any issues through SE37. The problem is when I try to send from CO53.
Request your expert advice to solve at the earliest.
Thanks in advance
Prathib

Hi Prathib, Have you got the solution to this problem

Setting External Destination

I have a website (made in VS 2005) that calls the creation of reports from Crystal Enterprise 10. I am trying to get it such that through the website coding I can modify the external destination that the reports are sent to, as they are different each time a report is run. So far I have not been able to successfully get this to work. This is what I am currently getting in CMC when a report is run:
Status: Failed
Printer: The instance is not printed.
External Destination: Not Authorized
Data Refresh Settings: Use the server defaults.
Start Time: 30/09/2008 2:25:59 PM
End Time: 30/09/2008 2:26:06 PM
Server Used: dest.reportjobserver
Error Message: destination DLL disabled. //dest... /CURRENT/ME/309/2009/Maintenance/M/:
I believe that I may inadvertently be setting the instance location, and that it why it is failing, but can't figure out how I should be setting the external destination then. The report runs fine from CE from the same user, even if I modify the destination directory to be what would otherwise fail. I've more than triple checked the security settings for the directory, but perhaps there is still something I missed?
I have tried to set this location through a schedulingInfo object by way of
ceSchedulingInfo.Destination.Name = destination
and directly from the InfoObject through ceReportObject.SchedulingInfo.Destination.Name = destination
and neither worked.
Any ideas?
Edited by: Ryan Beaulieu on Sep 30, 2008 10:51 PM

This forum is dedicated to topics related to legacy SDKs, including the Report Designer Component (RDC), OCX, VCL, and Crystal Reports Print Engine (CRPE).
Please post this query to the .NET Development - BusinessObjects Enterprise forum:
.NET SDK Application Development
That forum is monitored by qualified technicians and you will get a faster response there.
Thank you for your understanding,
Ludek

BASIS Configuration needed to send an external mail from SAP Program

Can you please help me about the BASIS configuration needed to send an external mail from SAP Program?
Regards,
Subhasish

Hi Subhasish,
Please go thru the below link.
Re: SCOT Configuration--for external mail
Regards,
Lakshman.

Listening to external WS from the process

Hi
How can I listener to external web service?
My goal is to know if the WS call this current process (as bepel in openESB).
I start to do it by putting another Receive component in the process. Is it the best way?
I got this error: The Receive activity 'Receive' does not use correlation set.
How to set correlation?
Thank's and have a nice day,
Yael

I'm not sure I understand the first part of your question. Do you want to place some sort of interceptor between a WS client and the BPEL engine that receives requests from that client (via a binding component)? If so, there are various ways to do this, depending on the protocol used, and your purposes in using such an interceptor (debugging or application function?)
As for the error you got: your process would appear to need correlation sets, and simply adding a <receive> activity breaks the correlation rules of WS-BPEL. The problem arises from the fact that you can have multiple instances of the same process running at once. A <receive> activity needs to be able to figure out which instance an incoming message belongs to. The is called correlation: some piece (or pieces) of the incoming message must uniquely match a correlation key (or keys) for a running process instance.
For more information see the WS-BPEL 2.0 Primer, at [http://docs.oasis-open.org/wsbpel/2.0/Primer/wsbpel-v2.0-Primer.pdf|http://docs.oasis-open.org/wsbpel/2.0/Primer/wsbpel-v2.0-Primer.pdf] .

Configure OC4J MDB to listen WebLogic queue

Hi
Is it possible to configure message driven beans (via deployment descriptors and OC4J config files with OracleAS JMS or OJMS) to listen to a remote queue? The remote queue is hosted on a WebLogic platform?
I've tried quite a few ways of doing it using only OracleAS JMS (OJMS is for AQ only) and fiddled endlessly with deployment descriptors and config files but no luck!
Help will be appreciated.
Thanks

Zain,
Actually, Oracle Application Server does not support WebLogic in a transparent way. You may have to write a message listener thread that runs on the server side and use the orion-application.xml descriptor to include the url of the WebLogic server where the Queues do reside.
I have a similar setup currently in production, if you are interested in further details.
Rick B.

How to configure MDB as Durable Subscriber

          I can't seem to find any documentation on how to set up an MDB as a Durable Subscriber.
          I tried using the Edit EJB Descriptor link in the console. I then drilled down
          to Message Driven Destination. For Subscription Durability, I selected Durable.
          I clicked Apply. I also went back to the jar and pressed the Persist button to
          "Persist changes made to the Descriptor(s)".
          I check the Topic to see if there were any Durable Subscribers listed. No. I bounced
          the server. Still no.
          What am I missing? The only info I can find in the documentation about setting
          up Durable Subscriptions is via the JMS API (http://e-docs.bea.com/wls/docs61/jms/implement.html#1097632)
          Using WL v6 SP5, not clustered.
          Any help would be appreciated.
          Jim


Hi James,
          I'm unfamiliar with the console ejb xml editor. I suggest
          posting to the ejb newsgbroup, which is more familiar
          with these things. Meanwhile, the attached notes
          and the following example may help if your willing
          to hand-edit the xml.
          Tom, BEA
          <ejb-jar>
          <enterprise-beans>
          <message-driven>
          <ejb-name>exampleMessageDrivenA</ejb-name>
          <ejb-class>MessageBean</ejb-class>
          <transaction-type>Container</transaction-type>
          <message-driven-destination>
          <destination-type>javax.jms.Queue</destination-type>
          
          </message-driven-destination>
          </message-driven>
          </enterprise-beans>
          <assembly-descriptor>
          <container-transaction>
          <method>
          <ejb-name>exampleMessageDrivenA</ejb-name>
          <method-name>onMessage()</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
          </container-transaction>
          </assembly-descriptor>
          </ejb-jar>
          
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>exampleMessageDrivenA</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>5</max-beans-in-free-pool>
          <initial-beans-in-free-pool>5</initial-beans-in-free-pool>
          </pool>
          
          <destination-jndi-name>MDBQ</destination-jndi-name>
          
          </message-driven-descriptor>
          <jndi-name>someid</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          James Goodwin wrote:
          > I can't seem to find any documentation on how to set up an MDB as a Durable Subscriber.
          > I tried using the Edit EJB Descriptor link in the console. I then drilled down
          > to Message Driven Destination. For Subscription Durability, I selected Durable.
          > I clicked Apply. I also went back to the jar and pressed the Persist button to
          > "Persist changes made to the Descriptor(s)".
          >
          > I check the Topic to see if there were any Durable Subscribers listed. No. I bounced
          > the server. Still no.
          >
          > What am I missing? The only info I can find in the documentation about setting
          > up Durable Subscriptions is via the JMS API (http://e-docs.bea.com/wls/docs61/jms/implement.html#1097632)
          >
          > Using WL v6 SP5, not clustered.
          >
          > Any help would be appreciated.
          >
          > Jim
          A durable topic subscriber MDB uses its name to generate its client-id.
          Since JMS enforces uniqueness on this client-id, this means that if a durable
          subscriber MDB is deployed to multiple servers only one server will be able
          to connect. Some applications want a different behavior where
          each MDB pool on each server gets its own durable subscription.
          The MDB durable subscription id, which must be unique on its topic, comes from:
          1) <jms-client-id>MyClientID</jms-client-id>
          (the weblogic dtd)
          2) if (1) is not set then the client-id
          comes from the ejb name.
          The durable subscription is uniquely identified within a cluster by a
          combination of "connection-id" and "subscription-id". Only one active
          connection may use a particular "connection-id" within a WebLogic cluster.
          The connection id comes from:
          1) The "ClientId" attribute configured on the WebLogic connection factory.
          This defaults to null. Note that if the ClientId is set on a connection
          factory, only one connection created by the factory
          may be active at a time.
          2) If (1) is not set, then, as with the subscriber-id,
          the connection-id is derived from jms-client-id descriptor attribute:
          <jms-client-id>MyClientID</jms-client-id>
          (the weblogic dtd)
          3) If (1) and (2) are not set, then, as with the subscriber-id,
          the connection-id is derived from the ejb name.
          Work-around:
          A) Create a custom connection-factory for each server:
          1) configure "JNDIName" to the same value across all servers
          ("myMDBCF" in this example)
          2) configure "ClientId" to a unique value per server
          3) enable "UserTransactionsEnabled"
          4) enable "XAConnectionFactoryEnabled"
          5) set "AcknowledgePolicy" to "ACKNOWLEDGE_PREVIOUS"
          6) target the CF at a single WebLogic server
          (Number 5 is required for non-transactional topic MDBs)
          B) In the MDB's weblogic-ejb-jar.xml descriptor, set the MDB's connection
          factory to the JNDI name of the custom connection factories configured in
          (A). Optionally, also specify the subscriber-id via the jms-client-id
          attribute.
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>exampleBean</ejb-name>
          <message-driven-descriptor>
          <connection-factory-jndi-name>myMDBCF</connection-factory-jndi-name>
          <jms-client-id>myClientID</jms-client-id>
          </message-driven-descriptor>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          C) Target the application at the same servers that have the custom connection
          factories targeted at them.
          Notes/Limitations:
          1) If the MDB is moved from one server to another, the MDB's corresponding
          connection-factory must be moved with it.
          2) This work-around will not work if the destination is not in the same
          cluster as the MDB. (The MDB can not use the local connection factory, which
          contains the connection-id, as connection factories do not work unless they
          are in the same cluster as the destination.)
          3) This work-around will not work for non-WebLogic JMS topics.

MDB cannot connect to JMS destination using Foreign Server

Hi everyone,
I have configured foreign jms server in weblogic but when MDB tries to connect to specific queue, it gets the following exception:
I would really appreciate if anyone could help me.
<Sep 28, 2012 5:23:34 PM CEST> <Warning> <EJB> <BEA-010096> <The Message-Driven EJB: SmsReceiver is unable to connect to the JMS destination or bind to JCA resource adapter: xcg2/smsInQueue. Connection failed after 2 attempts. The MDB will attempt to reconnect/rebind every 10 seconds. This log message will repeat every 600 seconds until the condition clears.>
<Sep 28, 2012 5:23:34 PM CEST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: SmsReceiver is unable to connect to the JMS destination: xcg2/smsInQueue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jmsxcg.out could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml or corresponding annotation is correct, and the JMS destination has been deployed.
javax.naming.InvalidNameException: jmsxcg.out: [LDAP: error code 34 - Invalid DN]; remaining name 'jmsxcg.out' NestedException Message is :jmsxcg.out: [LDAP: error code 34 - Invalid DN]>
MDB annotation looks like this:
@MessageDriven(name="SmsReceiver", mappedName="xcg2/smsInQueue",
activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
@TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED)
public class SmsReceiverBean implements MessageListener
weblogic-ejb-jar.xml excerpt:
     <weblogic-enterprise-bean>
          <ejb-name>SmsReceiver</ejb-name>
          <message-driven-descriptor>
               <pool>
                    <max-beans-in-free-pool>10</max-beans-in-free-pool>
                    <initial-beans-in-free-pool>5</initial-beans-in-free-pool>
               </pool>
               <connection-factory-jndi-name>echoQueueConnectionFactory</connection-factory-jndi-name>
          </message-driven-descriptor>
          <transaction-descriptor>
               <trans-timeout-seconds>600</trans-timeout-seconds>
          </transaction-descriptor>
<dispatch-policy>MdbSmsWorkManager</dispatch-policy>
     </weblogic-enterprise-bean>
and the configuration of foreign-server:
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms">
<foreign-server name="serverr">
<sub-deployment-name>Subdeployment</sub-deployment-name>
<foreign-destination name="sms queue>
<local-jndi-name>xcg2/smsInQueue</local-jndi-name>
<remote-jndi-name>jmsxcg.out</remote-jndi-name>
</foreign-destination>
<foreign-connection-factory name="Connection Factory">
<local-jndi-name>echoQueueConnectionFactory</local-jndi-name>
<remote-jndi-name>QueueConnectionFactory</remote-jndi-name>
</foreign-connection-factory>
<initial-context-factory>com.tibco.tibjms.naming.TibjmsInitialContextFactory</initial-context-factory>
<connection-url>tibjmsnaming://xx.xx.xx.xx:7222</connection-url>
</foreign-server>
</weblogic-jms>
PS. I'm able to connect to the weblogic jndi, get connectionFactory echoQueueConnectionFactory, then lookup queue and grab messages so that's i suspect there is something wrong with configuration

Hmm - I'm not sure what's going on. Two thoughts --
Thought 1 - According to my (admittedly minimal) research, Tibco is complaining about a syntax error in the lookup name. Perhaps the problem has something to do with your use of a "." in the queue name "jmsxcg.out": WL or Tibco JNDI might be interpreting the "." as a subcontext or some-such. Perhaps try renaming the queue to "jmsxcg_out" throughout (in Tibco and in your Foreign JMS reference).
Thought 2 - It probably won't make a difference, but you might want try specifying the source destination via the "destinationJndiName" config property instead of via "mappedName".
@MessageDriven(
name = "MyMDB",
activationConfig = {
    @ActivationConfigProperty(propertyName = "destinationType",
                              propertyValue = "javax.jms.Queue"),
    @ActivationConfigProperty(propertyName = "destinationJndiName",
                              propertyValue = "MyQueue") // Ext. JNDI Name
)HTH,
Tom

Configuring the port of the syslog destination address

Hello,
Is there a way to configure not just the internet address, but also the port number, to which the AEBS sends logging information?
The "Syslog Destination Address" field doesn't accept the ":port"-style address syntax. But I was wondering if there is a hidden workaround, like doing Option-click to expose a larger number frequencies selections.
Why do I care? For diagnostic purposes, I would like to enable the logging feature on my AEBS 802.11n and receive the logs on an OS X box. The app LogMaster can act as a syslogd daemon. The problem is it can't listen at the default port 514, since OS X's built-in syslogd daemon uses that port. This is despite the fact the built-in syslogd doesn't listen for log messages from the network and cannot be configured to do so without hacking inside the /System directory.
Any thoughts?

The configurations for extend the CoS value to teh ip phone port looks rigth. The fact that you have to unplug the phone for it to work seems to suggest that this is an issue with the phone. Is it running the latest phone load? What kind of switch is this?

Configuring MDB to listen to external destination

Similar Messages

Maybe you are looking for