Comments on: Messaging Engine Startup Problems

By: Dave

Dave — Sat, 07 Aug 2010 19:59:05 +0000

Javier – I’d need a lot more detail than that to be able to assist. As with my last comment, I’d suggest posting on the developerWorks forum with more details of your problem.
Regards,
David

By: Javier

Javier — Tue, 03 Aug 2010 11:06:37 +0000

In a publish subscribe environment, the problem is the one who publish is the one who receive, but not the others… why?

By: Dave

Dave — Tue, 02 Feb 2010 15:26:18 +0000

Hi Ranjit, There's not really enough information to determine what the cause might be. One point to check is that you are using different schema for each data source. You might also like to take a look at the Problem Determination Redpaper. If you're still not having any luck then post again on the developerWorks forum and I'll follow up there. Regards, David

By: Ranjit

Ranjit — Tue, 02 Feb 2010 02:01:28 +0000

HI Dave,

Here i have an issue with ME ,

we want to configure HA in our environment,In our environment there are two nodes and 1 dmgr all these are on different boxes.

Here we created 2 clusters .one is for application servers with 8 cluster members and another is for SIBUS with 8 bus members.

and i created new Bus with 8 message engines and created seperate data sources for application server and SIBUS at cluster level .with Data store and created the schema

here is the problem when we started the 2 cluster all the cluster member are starting fine but message engine are not starting ” they are always in “STARTING ” Status.

so we tried creating schemas and tables manually as well as via WAS

so it would be great if you can help me out here

Thanks in advance

Ranjit

By: Dave

Dave — Mon, 06 Jul 2009 19:58:47 +0000

Yes – you can use the application bus for your own JMS queues. Note, however, that is also where queues generated by the default JMS bindings will get created. It is the system bus that you should avoid using entirely.

By: Prashanth

Prashanth — Mon, 06 Jul 2009 19:25:52 +0000

Ok. I see this messaging bus SCA.APPLICATION.cell_name… Can I use this to configure my queues or should I create a new bus? Do you know if this existing bus can be used for my JMS queues?

By: Dave

Dave — Sun, 14 Jun 2009 16:29:15 +0000

Sorry Prashanth, that’s not a problem I’ve seen before. I can only suggest that you raise a support request.

By: Prashanth

Prashanth — Fri, 12 Jun 2009 20:33:10 +0000

HI Dave
I am running across a very weird issue in my application server. I have an app that runs on IBM Websphere 6.0. This app has a piece of code that drops messages to a JMS queue. Now I have set up the queue in the application server (Messaging Bus, Connection Factory, Queue and activation specification). When I restart the server, everything is fine. The problem occurs when I make a change to my app and redeploy the EAR file. When I redeploy the EAR file, for some reason the messaging engine stops. I got the following exception factoryEXCEPTIONclass javax.jms.JMSExceptionCWSIA0241E: An exception was received during the call to the method JmsManagedConnectionFactoryImpl.createConnection: com.ibm.websphere.sib.exception.SIResourceException: CWSIT0088E: There are currently no messaging engines in bus cesuMessagingBus running.
If I restart the server, then this particular messaging engine is running again and then my app works. But everytime there is a deployment on the server, the messaging engine stops running. This is causing huge problems as we need to restart the server everytime we deploy an EAR otherwise the app does not work because it does not identify the messaging engine. Do you have any solutions for this?

By: Harish

Harish — Fri, 12 Jun 2009 04:08:43 +0000

The Question for scheduler is posted on this Link

https://www.ibm.com/developerworks/forums/thread.jspa?threadID=265838

By: Harish

Harish — Fri, 12 Jun 2009 03:44:33 +0000

Thanks Dave for the suggestion. I will post the same

By: Dave

Dave — Thu, 11 Jun 2009 19:04:17 +0000

Apologies for the delay in responding – a bit busy at the moment. Rather than turn this in to a general support thread, can I suggest you post your question in the appropriate forum? I’m equally likely to answer it there and there’s a good chance you’ll get a quicker answer from someone else…

By: Harish

Harish — Tue, 09 Jun 2009 10:56:44 +0000

Dave,

I have a question on websphere scheduler on cluster environment.

I have a cluster environment with 2 was member servers. In this scenario, on which scope the scheduler should be created.

please let me know if you need any other information

Thanks in advance
harish

By: Harish

Harish — Mon, 08 Jun 2009 12:44:09 +0000

Thanks Dave for your input.

While surfing i got a link which talks about the same.

http://www-01.ibm.com/software/integration/wbimessagebroker/v6/faqs.html

By: Dave

Dave — Tue, 02 Jun 2009 19:01:29 +0000

Harish,

I’ve seen hour long presentations on that subject so I’m not sure I can really do it justice here. What I will say is that the products increasingly cover the same functionality although there are still areas where this is not the case so consider carefully what you are going to do with the ESB. Perhaps more pertinent is the surrounding environment and existing skills (of both developers and administrators) – WebSphere Message Broker obviously fits more naturally in to a WebSphere MQ environment and WebSphere ESB in to a WebSphere Application Server or Process Server environment.

Regards,
David

By: Harish

Harish — Tue, 02 Jun 2009 05:32:50 +0000

Thanks dave, let me do some hands on the other approach.

I need some suggestions from you.

We are planning to use Websphere Message broker for one more assignment along with SOA BPEL, but my view is why cant we use the SOA ESB instead of WMB.

I want your views on using WMB and SOA ESB and when we can go for which one.

By: Dave

Dave — Mon, 01 Jun 2009 19:33:13 +0000

Prior to 6.2 then your options are custom Java coding or the approach I outline here.

By: Harish

Harish — Mon, 01 Jun 2009 09:17:32 +0000

So with 6.1.2 do we have any other way of achieving the above said behavior.

By: Dave

Dave — Mon, 01 Jun 2009 09:14:03 +0000

In 6.1.2 dynamic endpoint selection was only available for SCA and web service bindings. The syntax you have above is that for a SOAP/JMS binding. In 6.2 dynamic endpoint selection is available for all bindings types and the one I linked to is that for a JMS binding. It doesn’t include any component name though.

By: Harish

Harish — Mon, 01 Jun 2009 06:22:26 +0000

Dave,

We already tried this solution. But with this ESB6.2.0 version i see a difference in JMS URI syntax with ESB 6.1.2.

In 6.1.2 we have to provide syntax similar to this

jms:/queue?destination=jms/WSjmsExport&connectionFactory=jms/WSjmsExportQCF&targetService=WSjmsExport_ServiceJmsPort

Here we have to specify the component name also.

Does the feature you referred is available only in 6.2.x or is it applicable for 6.1.2 also.

By: Dave

Dave — Thu, 28 May 2009 12:36:45 +0000

Providing you have the queues defined in JNDI then, yes, it is possible. Set the /headers/SMOHeader/Target/address to the appropriate JMS URI syntax prior to calling the service invoke.