Lenovo and IBM have entered into a definitive agreement in which Lenovo plans to acquire IBM’s x86 server business. This includes System x, BladeCenter and Flex System blade servers and switches, x86-based Flex integrated systems, NeXtScale and iDataPlex servers and associated software, blade networking and maintenance operations. The purchase price is approximately US$2.3 billion, approximately two billion of which will be paid in cash and the balance in Lenovo stock.
IBM will retain its System z mainframes, Power Systems, Storage Systems, Power-based Flex servers, and PureApplication and PureData appliances.
The agreement builds upon a longstanding collaboration that began in 2005 when Lenovo acquired IBM’s PC business, which included the ThinkPad line of PCs. In the period since the companies have continued to collaborate in many areas.
IBM will continue to develop and evolve its Windows and Linux software portfolio for the x86 platform. IBM is a leading developer of software products for x86 servers with thousands of products and tens of thousands of software developer and services professionals who build software for x86 systems.
For more information on this acquisition, read the full announcement.
Tag: IBM news
Server Issues With WebSphere Application Server In Relational Database
WebSphere news from IBM: December 11, 2013
Technote (troubleshooting)
Problem(Abstract)
If you have chosen to store your WebSphere Application Server transaction and compensation logs in a Relational Database, and your system has constrained resources, the server might fail to start.
Cause
The recovery log service has attempted to obtain information from the WebSphere Application Server Directory Service before that service has fully initialized, and this recovery log service operation has timed out. The length of time taken for the directory service to initialize can vary depending on your system environment.
Diagnosing the problem
The following exception is reported in the WebSphere Application Server log file:
WsServerImpl E WSVR0009E: Error occurred during startup
com.ibm.ws.exception.RuntimeError: com.ibm.ws.recoverylog.spi.InternalLogException: Failed to locate DataSource, com.ibm.ws.recoverylog.spi.InternalLogException: Failed to locate DataSource
at com.ibm.ws.tx.util.WASTMHelper.asynchRecoveryProcessingComplete(WASTMHelper.java:176)
at com.ibm.tx.util.TMHelper.asynchRecoveryProcessingComplete(TMHelper.java:57)
at com.ibm.tx.jta.impl.RecoveryManager.recoveryFailed(RecoveryManager.java:1412)
at com.ibm.tx.jta.impl.RecoveryManager.run(RecoveryManager.java:1942)
at java.lang.Thread.run(Thread.java:773)
Caused by: com.ibm.ws.recoverylog.spi.InternalLogException: Failed to locate DataSource, com.ibm.ws.recoverylog.spi.InternalLogException: Failed to locate DataSource
at com.ibm.ws.recoverylog.custom.jdbc.impl.SQLMultiScopeRecoveryLog.openLog(SQLMultiScopeRecoveryLog.java:525)
at com.ibm.tx.jta.impl.RecoveryManager.run(RecoveryManager.java:1886)
… 1 more
Caused by: Failed to locate DataSource, com.ibm.ws.recoverylog.spi.InternalLogException: Failed to locate DataSource
at com.ibm.ws.recoverylog.custom.jdbc.impl.SQLNonTransactionalDataSource.getDataSource(SQLNonTransactionalDataSource.java:249)
at com.ibm.ws.recoverylog.custom.jdbc.impl.SQLMultiScopeRecoveryLog.getConnection(SQLMultiScopeRecoveryLog.java:760)
at com.ibm.ws.recoverylog.custom.jdbc.impl.SQLMultiScopeRecoveryLog.openLog(SQLMultiScopeRecoveryLog.java:393)
… 2 more
Resolving the problem
Increase the timeout value for the recovery log service operation by completing the following steps:
- Open the WebSphere Application Server administrative console.
- Click Servers > Server Types > WebSphere application servers > server_name.
- Under Server Infrastructure, click Java and Process Management > Process definition.
- Under Additional properties, click Java Virtual Machine > Custom properties > New.
- In the Name field, enter com.ibm.ws.recoverylog.custom.jdbc.impl.ConfigOfDataSourceTimeout.
- In the Value field, enter an integer timeout value in milliseconds; for example, to set the timeout to 10 seconds, enter 10000.
- Click OK, then click Save to save your changes to the master configuration.
The default value for the com.ibm.ws.recoverylog.custom.jdbc.impl.ConfigOfDataSourceTimeout property is two seconds.
The rebirth of the mainframe
For anyone who thinks that the demand for mainframes is on the decline, take a look at this. In the fourth quarter of 2010, the demand for IBM’s System zEnterprise 196 mainframes skyrocketed their sales to a six year high. They helped drive IBM’s company sales up to $99.9bn, which is an increase of 4% compared to last year.
In a time when the economy seems to be fledgling, it is so nice to see a big company like IBM report such a large profit. It’s a testament to their business practices that they were able to reach almost a $100bn profit in 2010. And I think that should provide hope for all of us out there in the technology industry that there’s no direction for us to head, but up.
Just a note, while IBM hasn’t provided revenue projections for the first quarter of 2011, sources say that IBM is on track to deliver at least $13 in earnings per share this year. Maybe we need to go out and buy into IBM!
