I had the need to be able to place a JMS Message onto a Service Integration Bus Queue. I tried to use the SIBus Explorer, but it really didn’t like my WebSphere v6.1 configuration and would always throw an exception. I then checked out the IBM Client Application Tool for JMS pointed out to me […]
Default Messaging (SIBus): Modifying JMS ConnectionFactory Provider Endpoints requires a server restart
Just a quick tip, if you need to modify a JMS ConnectionFactory’s Provider Endpoints in WebSphere Application Server, be sure to re-start your server. You normally need to perform this task when you are outside the application server hosting the queue and performing remote JNDI lookups. I modified the value but always got the error […]
IBM APAR PK49507: PROFILE RECREATION Required!
In a case of something I have never seen before, it appears that PK49507: THE SIBUS RESOURCE ADAPATER WILL NOW INDICATE THAT AN MDB SHOULD BE STOPPED IF A CERTAIN NUMBER OF FAILURES ARE HIT actually requires you to recreate your entire server profile from scratch! It contains the statement: This property will only be […]
The WebSphere Contrarian: Are you sure you want to reorg that messaging engine database?
The standard practice for database administration is to periodically
check on the database and table organization to insure optimal performance —
but do these standard practices apply to a database used for JMS persistent
message storage with IBM WebSphere Application Server? (IBM WebSphere Developer Technical Journal)
Do not use forward slashes in SIBus Destination names with JMS
I have an SIBus destination called: ‘MY/QUEUE’. I create a JMS QueueConnectionFactory and JMS Queue definition to this destination. jms/LoggingPoisonQueueCF and jms/LoggingPoisonQueue. When I attempt to put a message on the destination (using Spring JMS) I get the following exception: org.springframework.jms.InvalidDestinationException: CWSIA0046E: The parameter queue://MY/QUEUE?busName=SIBJMSBus is from a foreign implementation that is not supported.; nestedexception […]
WebSphere Application Server: Non-Deterministic Error when configuring Default Messaging Activation Specs
I’m in the process of moving an application from my test server to a development server. I started creating activation specifications for my MDBs. Everything was fine. Then I tried to start my ear and received the following exception: The JMS activation specification has invalid values – the reason(s) for failing to validate the JMS […]
WebSphere Application Server: High Availability to JMS Clients?
I was asked an interesting question. If your messaging engine is in a cluster and it fails over from one node to the next, how to my clients know which node is now hosting the Messaging Engine? I haven’t run this scenario myself so I don’t know. I do know that the datapower allow you […]
WAS: Resolution to Messages in the SIB locked forever
In a cluster where the messaging engine has failed over between nodes, a situation could arise where the transaction log (‘tranlog’) has become corrupt or is unrecoverable. In this situations, you may see messages on SIB Queues that are in the LOCKED state but are unprocessed. If you factor in a sequential delivering of messages, […]
WebSphere Default Messaging (SIBus) and WebService Error Handling
An interesting situation arose the other day for a solution to the following requirements on WPS 6.0.2.3: We have a JMS queue that collects message for a web service Endpoint. We have a web service that is only available during business hours (say 9-5). If we send a request outside business hours, we will get […]
JMS Function Selectors & Method Bindings
JMS Function Selectors and Method bindings are properties that you define inside of an SCA JMS component that answer the question “Which {component,interface} pair should a message arriving on a queue be delivered to?”. I had intended to go and write up in lay-mans terms what it all meant, but luckily (for me) I stumbled […]