Vivek Agarwal’s Portal/Java Blog

An IBM Gold Consultant’s weblog about IBM, Lotus, WebSphere, J2EE, IT Processes, and other IT technologies

Archive for the ‘WebSphere’ Category

Deploying WebSphere Portal Document Manager (PDM) on a guest page

Posted by Vivek Agarwal on April 17, 2008

Recently our team needed to deploy the Portal Document Manager (PDM) portlet on a public WebSphere Portal page for guest user access. It turned out that this was not as trivial as expected if you don’t know what actions are required and there is nothing on IBM’s site documenting the steps involved in getting the document manager portlet to work for guest users. I figured I would capture the key steps here in case you need to do the same and are having a hard time with this task!
Read the rest of this entry »

Posted in Portal, WebSphere, WebSpherePortal | Tagged: , , | 16 Comments »

Missing log4j log files with DailyRollingFileAppender when they should roll over?

Posted by Vivek Agarwal on February 9, 2008

Yes, I am back with a blog entry after quite a gap here! I have been knocked out sick for 5 weeks now and I am sick of being sick! Better now and hoping to be back at a 100% soon. Enough excuses – onto the subject of this blog entry. We use Log4j’s DailyRollingFileAppender in a WebSphere Portal environment to generate daily log files for various custom portlets that we have deployed. This worked just fine on some WPE v6 test servers with multiple portlets logging to the same log file, and the daily rollover occurring every midnight. However, on some other WPE v6 test servers running the exact same applications, while logging did work the daily rollover did not. Instead of us having multiple log files with date timestamps in their names, we would only have today’s log file – the previous log files would simply disappear! This issue results from the fact that the DailyRollingFileAppender (DRFA) tries to rename the log file during rollover. However, when the rename fails, it ends up overwriting the log file, hence losing information. On checking the application server’s SystemErr.log, we found an error each midnight similar to –

log4j:ERROR Failed to rename [logfilename] to logfilename.2008.01.11].

This appears to be a fairly common issue with log4j 1.2.x in Java application servers running on Windows. While there is no good resolution for this issue there is a workaround that works pretty well. Read the rest of this entry »

Posted in Java, log4j, WebSphere, WebSpherePortal | 18 Comments »

XA Errors on server startup after an ungraceful shutdown of WebSphere Portal v6

Posted by Vivek Agarwal on November 14, 2007

There is a new technote out about an issue that I have seen in the past with WebSphere Portal v6 on a test server, where you find XA errors in SystemOut.log during server startup after WP6 was shutdown ungracefully – for example, on a Windows server reboot after installing a Windows update. Resolving the error was relatively straightforward and involved clearing the transaction logs. Read the rest of this entry »

Posted in WebSphere, WebSpherePortal | Tagged: , , | Comments Off on XA Errors on server startup after an ungraceful shutdown of WebSphere Portal v6

How to enable “synchronous portlet edits” in a WebSphere Portal 6.0 cluster?

Posted by Vivek Agarwal on November 13, 2007

My blogs are getting more and more infrequent recently – things have been more crazy lately at work and I have also been reading a few non-technical books, leaving me less time to write on my blog. Today – I decided to prioritize blogging over other things and write about an issue that had plagued a WebSphere Portal v6.0 cluster. Essentially, if you create a WP6 cluster following the instructions from IBM, you will end up with an issue whereby a portlet edit on one node in the cluster does not appear on other cluster nodes without a server restart on the other nodes. Read the rest of this entry »

Posted in Java, Portal, WebSphere, WebSpherePortal | Tagged: , , , | 6 Comments »

WebSphere Portal v6 cluster secondary node performance issues

Posted by Vivek Agarwal on August 19, 2007

I am back writing about performance issues that we are running into with the secondary node in a WebSphere Portal v6 cluster. I had written sometime back about a startup performance issue on a secondary node in a cluster – at the time, we were not seeing any performance issues subsequent to server start-up. However, now we are seeing horrendous performance issues on the secondary node Read the rest of this entry »

Posted in Java, WebSphere, WebSpherePortal | 4 Comments »