More servicesWindows Live
HomeHotmailSpacesOneCare
 
MSN
Sign in
 
 
Spaces home  Zhiyi's blogs, books and...PhotosProfileFriendsMore Tools Explore the Spaces community
July 15

WSJ exception

Java, Struts, IBM (for web container) and Oracle (for database). 
================================================

Error page exception

The server cannot use the error page specified for your application to handle the Original Exception printed below. Please see the Error Page Exception below for a description of the problem with the specified error page.


Original Exception:

Error Message: Listener refused the connection with the following error: ORA-12516, TNS:listener could not find available handler with matching protocol stack The Connection descriptor used by the client was: (DESCRIPTION=(FAILOVER=ON)(ADDRESS_LIST=(LOAD_BALANCE=ON)(ADDRESS=(PROTOCOL=TCP)(HOST=sbkj2kjdbp01v)(port=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=sbkj2kjdbp02v)(port=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=sbkj2kjdbp03v)(port=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=sbkj2kjdbp04v)(port=1521)))(CONNECT_DATA=(SERVICE_NAME=J20))) DSRA0010E: SQL State = null, Error Code = 0
Error Code: 500
Target Servlet: action
Error Stack:
com.dowjones.bo.BOException: Listener refused the connection with the following error:
     ORA-12516, TNS:listener could not find available handler with matching protocol stack
     The Connection descriptor used by the client was:
     (DESCRIPTION=(FAILOVER=ON)(ADDRESS_LIST=(LOAD_BALANCE=ON)(ADDRESS=(PROTOCOL=TCP)(HOST=sbkj2kjdbp01v)(port=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=sbkj2kjdbp02v)(port=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=sbkj2kjdbp03v)(port=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=sbkj2kjdbp04v)(port=1521)))(CONNECT_DATA=(SERVICE_NAME=J20)))
     DSRA0010E: SQL State = null, Error Code = 0
     at com.dowjones.bo.PageCacheBO.getPage(PageCacheBO.java:90)
     at com.dowjones.j4j.util.MSTUtils.addMSTContext(MSTUtils.java:160)
     at com.dowjones.j4j.struts.actions.IncludeDynamicModuleAction.execute(IncludeDynamicModuleAction.java:51)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:989)
     at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:501)
     at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:464)
     at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
     at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744)
     at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1439)
     at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:112)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:263)
     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
     at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
     at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
     at com.ibm.io.async.AsyncChannelFuture$1.run(AsyncChannelFuture.java:205)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
    


Error Page Exception:

Error Message: JSPG0036E: Failed to find resource /utils/error.jsp
Error Code: 404
Target Servlet: /utils/error.jsp
Error Stack:
java.io.FileNotFoundException: JSPG0036E: Failed to find resource /utils/error.jsp
     at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionProcessor.findWrapper(AbstractJSPExtensionProcessor.java:300)
     at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionProcessor.handleRequest(AbstractJSPExtensionProcessor.java:273)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:321)
     at com.ibm.ws.webcontainer.webapp.WebApp.sendError(WebApp.java:2804)
     at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:111)
     at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744)
     at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1439)
     at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:112)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:263)
     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
     at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
     at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
     at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
     at com.ibm.io.async.AsyncChannelFuture$1.run(AsyncChannelFuture.java:205)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
June 24

Microsoft packs search to Yahoo.

It's almost a reality show between Yahoo and Microsoft for the past 5 months. They talked, they disliked and they broke up. Apparantly they couldn't live without each other, so they talked again, and they broke up again. Now they're talking again.
 
More seriously, Microsoft waries about the full integration with Yahoo, so that rules out the full buyout. Yahoo doesn't want to rely on Microsoft's search due to it uncertain future. Let's brainstorm on another option: Microsoft packs search plus cash to Yahoo and owns 40%+ of Yahoo.
 
- Yahoo get the huge boost and maintains its identity.
- Microsoft now rely on Yahoo for search, of which it maintains a dominant position.
May 05

It ain't over

I dreamed about it twice last night.
 
Both Yahoo shareholders and employees appear dispirited, if not angry, so it's possible that Yahoo board feels pressured to go back to the negociation table.
 
 
On the hindsight, I should have hedged against the deal-off.
May 03

Ballmer walks

It's over, finally. It's quite a loss finantially for me. At least I can sleep better.
 
Ballmer explains at length why he doesn't want to go proxy fight. He especially warns about yahoo-google ad deal, in a sense also reminding yahoo of the fact that it's detrimental to yahoo as well. Ballmer's tone sounds friendly, as opposed to his threatening tone in his proxy fight warning letter 4 weeks ago, yet as he lays out his case, he essentially tells Yahoo: go to hell.
 
I think Ballmer made the right decision. Now it's time for Yahoo to face it future, amidst some angry shareholders. I wish Yang would accept the offer, but I accept and respect his decision as well.

May 3, 2008

Mr. Jerry Yang
CEO and Chief Yahoo
Yahoo! Inc.
701 First Avenue
Sunnyvale, CA 94089

Dear Jerry:

After over three months, we have reached the conclusion of the process regarding a possible combination of Microsoft and Yahoo!.

I first want to convey my personal thanks to you, your management team, and Yahoo!’s Board of Directors for your consideration of our proposal. I appreciate the time and attention all of you have given to this matter, and I especially appreciate the time that you have invested personally. I feel that our discussions this week have been particularly useful, providing me for the first time with real clarity on what is and is not possible.

I am disappointed that Yahoo! has not moved towards accepting our offer. I first called you with our offer on January 31 because I believed that a combination of our two companies would have created real value for our respective shareholders and would have provided consumers, publishers, and advertisers with greater innovation and choice in the marketplace. Our decision to offer a 62 percent premium at that time reflected the strength of these convictions.

In our conversations this week, we conveyed our willingness to raise our offer to $33.00 per share, reflecting again our belief in this collective opportunity. This increase would have added approximately another $5 billion of value to your shareholders, compared to the current value of our initial offer. It also would have reflected a premium of over 70 percent compared to the price at which your stock closed on January 31. Yet it has proven insufficient, as your final position insisted on Microsoft paying yet another $5 billion or more, or at least another $4 per share above our $33.00 offer.

Also, after giving this week’s conversations further thought, it is clear to me that it is not sensible for Microsoft to take our offer directly to your shareholders. This approach would necessarily involve a protracted proxy contest and eventually an exchange offer. Our discussions with you have led us to conclude that, in the interim, you would take steps that would make Yahoo! undesirable as an acquisition for Microsoft.

We regard with particular concern your apparent planning to respond to a “hostile” bid by pursuing a new arrangement that would involve or lead to the outsourcing to Google of key paid Internet search terms offered by Yahoo! today. In our view, such an arrangement with the dominant search provider would make an acquisition of Yahoo! undesirable to us for a number of reasons:

* First, it would fundamentally undermine Yahoo!’s own strategy and long-term viability by encouraging advertisers to use Google as opposed to your Panama paid search system. This would also fragment your search advertising and display advertising strategies and the ecosystem surrounding them. This would undermine the reliance on your display advertising business to fuel future growth.

* Given this, it would impair Yahoo’s ability to retain the talented engineers working on advertising systems that are important to our interest in a combination of our companies.

* In addition, it would raise a host of regulatory and legal problems that no acquirer, including Microsoft, would want to inherit. Among other things, this would consolidate market share with the already-dominant paid search provider in a manner that would reduce competition and choice in the marketplace.

* This would also effectively enable Google to set the prices for key search terms on both their and your search platforms and, in the process, raise prices charged to advertisers on Yahoo. In addition to whatever resulting legal problems, this seems unwise from a business perspective unless in fact one simply wishes to use this as a vehicle to exit the paid search business in favor of Google.

* It could foreclose any chance of a combination with any other search provider that is not already relying on Google’s search services.

Accordingly, your apparent plan to pursue such an arrangement in the event of a proxy contest or exchange offer leads me to the firm decision not to pursue such a path. Instead, I hereby formally withdraw Microsoft’s proposal to acquire Yahoo!.

We will move forward and will continue to innovate and grow our business at Microsoft with the talented team we have in place and potentially through strategic transactions with other business partners.

I still believe even today that our offer remains the only alternative put forward that provides your stockholders full and fair value for their shares. By failing to reach an agreement with us, you and your stockholders have left significant value on the table.

But clearly a deal is not to be.

Thank you again for the time we have spent together discussing this.

Sincerely yours,
Steven A. Ballmer

View more entries
 

Zhiyi's blogs, books and links

Updated 6/21/2008
Updated 6/18/2008
Updated 4/13/2008
Updated 6/19/2008
Updated 2/9/2008
Updated 1/30/2008
Updated 11/3/2007
Updated 11/3/2007
Updated 11/3/2007
Updated 11/3/2007
Updated 4/28/2007