I opened up my ageing T42p laptop last night to be greeted by the ominous message “Fan error”. A quick Google using Christine’s machine revealed that I could bypass this warning simply by pressing escape. This set my mind at rest to a certain extent as a) it meant I could see that I hadn’t lost any data and b) I could copy off the information I needed for the next day. If this was going to happen, it couldn’t have happened at a much better time as I had just returned from my last customer engagement in Norway and was intending to spend today in the IBM office (where I have managed to borrow a machine – thanks Kristin!). Next week I’ll be back in Hursley where hopefully a quick repair can be arranged.
Archive for the ‘Technology’ Category
Fan error
Thursday, August 14th, 2008Locks and leaks
Thursday, July 17th, 2008I was called upon yesterday to review some WebSphere product code I wrote about six years ago. It was a bit of a shock to see from the change history the number of fixes that had been made in the intervening time! Many of these related to deadlock situations, often when I was merely taking a lock whilst I iterated over a set in toString or some such seemingly innocuous method. It is very hard to get the lock ordering correct when you are just a component in the middle of the stack. The lesson there is, I suspect, to only trace when entries are added or removed from the set and perhaps just give the size at other times.
(more…)
Configuring SIB J2SE client with SSL
Wednesday, July 16th, 2008If configuring the service integration bus J2SE client for SSL is a topic of interest to you then make sure you register for next week’s presentation from Rich Montjoy in level 2 service.
Dynamic JMS endpoints
Tuesday, July 15th, 2008In an earlier post I promised an example of where service integration bus mediations still have a role to play in a WebSphere ESB environment. WebSphere ESB currently only supports dynamic endpoints on an import or callout (those that can be changed at runtime by a mediation flow) for SCA and web service bindings. In this post I’ll show how a service integration bus mediation can be used to add dynamic behaviour to a JMS binding.
(more…)
Deployment environments during profile creation
Tuesday, July 8th, 2008Today I was trying to work out why a WebSphere ESB customer wasn’t seeing the default deployment environment created when using manageprofiles to create a Network Deployment topology. They had specified the appropriate topologyPattern and topologyRole parameters. It turned out that they were missing the ndtopology option which should be set to true. This was perhaps excusable as the help for the template doesn’t list this option and even the InfoCenter documentation manages to get the case incorrect. As on previous occasions, I spotted this omission by running through the graphical Profile Management Tool and comparing the parameters that it generates in the invokeWSProfile entry near the top of the logs/manageprofiles/<profile_name>_create.log file.
Event sequencing qualifier and WebSphere ESB
Saturday, June 14th, 2008As this has cropped up a couple of times recently and, as far as I’m aware, there is still no information in the public domain, I thought I’d stick my neck out and post about it. WebSphere Integration Developer allows you to add an event sequencing qualifier to components in a mediation module but the required runtime support for that qualifier only exists in WebSphere Process Server not in WebSphere ESB. In other words, for that qualifier to work, the mediation module must then be deployed to WebSphere Process Server.
Mediation handler tooling broken
Tuesday, June 10th, 2008Despite being sidelined by the arrival of WebSphere ESB, there are still times when it is useful to use the mediation support in WebSphere’s service integration bus (of which more in another post). It’s obviously a while since I’ve done it though as apparently the mediation handler tooling in Rational Application Developer has been broken since v7 was released. I’m told that the fix will finally make it in to 7.0.0.7.
Feature Pack for Web Services notes
Friday, May 30th, 2008A couple of notes if you have, or are thinking of, embarking on use of the Feature Pack for Web Services, based on a recent client’s experiences. Firstly, make sure you heed the rules on profile augmentation in the InfoCenter. In particular, note that augmentation of a Cell profile is not supported. For Network Deployment you must have a separate deployment manager profile.
Secondly, if you are experiencing sluggish response times, 100% CPU or even hangs when either deploying or accessing applications following augmentation, then consider applying APAR PK58537. Note that the application need not be using any new functionality in order to experience this behaviour and it’s possible that you might not see the particular IOException stated in the problem description. This fix is targeted for inclusion in 6.1.0.17.
RSS - Posts