aspose file tools*
The moose likes Websphere and the fly likes WAS 6.0 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "WAS 6.0" Watch "WAS 6.0" New topic
Author

WAS 6.0

Shashi Kant
Ranch Hand

Joined: Aug 08, 2006
Posts: 117
Hi All

I had migrated my application from WAS 5.0 to WAS 6.0
The server and application starts normally. But when I try to access the same through i-explorer the error page comes. Following is the stack trace ->

2007-02-05 16:02:32,783 ERROR [WebContainer : 0] common.ErrorPage - Error occurred and redirected to error jsp. The error details are:
java.lang.NullPointerException
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1212)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:555)
at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:117)
at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:171)
at com.ibm.ws.jsp.webcontainerext.JSPExtensionProcessor.handleRequest(JSPExtensionProcessor.java:230)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:250)
at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:509)
at com.ibm._jsp._WsbcHome._jspService(_WsbcHome.java:110)
at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:88 )
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1212)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498)
at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:117)
at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:171)
at com.ibm.ws.jsp.webcontainerext.JSPExtensionProcessor.handleRequest(JSPExtensionProcessor.java:230)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:250)
at com.ibm.dse.cs.html.HtmlPresentationHandler.forward(HtmlPresentationHandler.java)
at com.ibm.dse.cs.html.HtmlPresentationHandler.processReply(HtmlPresentationHandler.java)
at com.ibm.dse.cs.html.HtmlRequestHandler.processSessionRequest(HtmlRequestHandler.java)
at com.ibm.dse.cs.servlet.CSEstablishSessionServlet.service(CSEstablishSessionServlet.java)
at com.hc.hmf.pls.servlet.StartSessionServlet.service(StartSessionServlet.java:58 )
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1212)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:2837)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:220)
at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:204)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1681)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:421)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:367)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters(NewConnectionInitialReadCallback.java:201)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:103)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:548)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:601)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:934)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1021)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)

Is there in change in MQ connection from WAS5 to WAS 6?
If yes what would be the solution?

Please help me on urgent basis.


If it's true that we are here to help others, then what exactly are the others here for?
Abelard Chow
Greenhorn

Joined: Jan 25, 2005
Posts: 7
Hi Shashikant,

Why do you think it has something to do with MQ connection?

Based on your stack trace (com.ibm.dse.cs.html.HtmlPresentationHandler.forward), your HtmlPresentationHandler try to forward your JSP, then there is a problem.

There is a NullPointerException. Does one of the object used in your JSP is NULL?

Please try to debug your page or forward() method and see what variable is NULL.

Beside, just curious, you are using a "dse" package. Are you trying to use BTT 4.x or CBTF 4.x in WAS6? What project are you working on?

Thanks

Abelard Chow


Abelard Chow<br /> <br />Some see things as where they were and ask why, I dream things that never are and ask why not.
Shashi Kant
Ranch Hand

Joined: Aug 08, 2006
Posts: 117
Hi

I had debug my code, but I don't found any object that is null.
Additionally I found the "server1_excxeption.log" under folder
"\runtimes\base_v6\profiles\default\logs\ffdc".
Does this make any difference.
This file shows follwing exception message -->

Index Count Time of last Occurrence Exception SourceId ProbeId
------+------+---------------------------+--------------------------
1 50 07.02.13 16:50:36:217 IST org.omg.CosNaming.NamingContextPackage.NotFound com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info 1045
2 2 07.02.13 16:48:59:201 IST javax.naming.NameAlreadyBoundException com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.do_bind_new_corba_context 1042
3 1237 07.02.13 16:58:29:545 IST java.lang.ClassNotFoundException com.ibm.ws.classloader.CompoundClassLoader.loadClass 248
4 2 07.02.13 16:48:59:201 IST javax.naming.NameAlreadyBoundException com.ibm.ws.naming.jndicos.CNContextImpl.createSubcontext 756
5 6 07.02.13 16:48:58:998 IST org.omg.CosNaming.NamingContextPackage.NotFound com.ibm.ws.naming.jndicos.CNContextImpl.doCreateSubcontext 2161
6 6 07.02.13 16:48:58:998 IST org.omg.CosNaming.NamingContextPackage.NotFound com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.bind_new_corba_context 944
7 6 07.02.13 16:48:59:014 IST javax.naming.NameNotFoundException com.ibm.ws.naming.jndicos.CNContextImpl.createSubcontext 756
8 2 07.02.13 16:48:59:201 IST org.omg.CosNaming.NamingContextPackage.AlreadyBound com.ibm.ws.naming.jndicos.CNContextImpl.doCreateSubcontext 2155
9 50 07.02.13 16:50:36:217 IST javax.naming.NameNotFoundException com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.do_resolve_complete_info 1133
------+------+---------------------------+--------------------------

Please help soon



[ February 13, 2007: Message edited by: Shashikant Dahatonde ]
Hanumanth Kanthi
Ranch Hand

Joined: May 27, 2004
Posts: 74
Yes, there is a big change in messaging infrastructure btw. WAS v 5.x and WAS v 6.x

WAS v 5.x was bundled with scaled down version of MQ which runs as a separate process from application server process.....

...where as WAS v6.x came with Service Integration Bus (SIBus) as a messaging infrastructure which runs in the same process as application server.

Having said that.... for more information I recommend you look into WebSphere Migration reference @ http://www.redbooks.ibm.com/redbooks/pdfs/sg246369.pdf

Hope this helps....Good luck

Cheers
H. Kanthi
Abelard Chow
Greenhorn

Joined: Jan 25, 2005
Posts: 7
Hi Shashikant,

It is strange, the exception trace you show orginally indicate the problem occured when the application is replying. This mean the business transaction is completed. Your business transaction may be implemented in a way that problem is supressed. That will lead to a NULL pointer exception when forwarding the page.

I am not sure, but are you sure the version of your "dse" framework is certified in WAS 6.0?
Shashi Kant
Ranch Hand

Joined: Aug 08, 2006
Posts: 117
Hi

And this is the error log from SystemErr.log

[3/2/07 12:10:16:598 IST] 00000077 SystemErr R java.lang.NullPointerException
[3/2/07 12:10:16:598 IST] 00000077 SystemErr R at com.ibm.ws.classloader.SinglePathClassProvider.getRealResourcePath(SinglePathClassProvider.java:374)
[3/2/07 12:10:16:598 IST] 00000077 SystemErr R at com.ibm.ws.classloader.SinglePathClassProvider$1.run(SinglePathClassProvider.java:187)
[3/2/07 12:10:16:598 IST] 00000077 SystemErr R at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
[3/2/07 12:10:16:598 IST] 00000077 SystemErr R at com.ibm.ws.classloader.SinglePathClassProvider.getClassBytesFromDir(SinglePathClassProvider.java:180)
[3/2/07 12:10:16:598 IST] 00000077 SystemErr R at com.ibm.ws.classloader.SinglePathClassProvider.getClassBytes(SinglePathClassProvider.java:170)
[3/2/07 12:10:16:598 IST] 00000077 SystemErr R at com.ibm.ws.classloader.CompoundClassLoader.findClass(CompoundClassLoader.java:496)
[3/2/07 12:10:16:614 IST] 00000077 SystemErr R at com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:414)
[3/2/07 12:10:16:614 IST] 00000077 SystemErr R at java.lang.ClassLoader.loadClass(ClassLoader.java:560)
[3/2/07 12:10:16:614 IST] 00000077 SystemErr R at com.ibm.dse.base.TracesWindow.getTraceFile(TracesWindow.java)
[3/2/07 12:10:16:614 IST] 00000077 SystemErr R at com.ibm.dse.base.TracesWindow.writeTrace(TracesWindow.java)
[3/2/07 12:10:16:614 IST] 00000077 SystemErr R at com.ibm.dse.base.Trace.run(Trace.java)
[3/2/07 12:10:16:614 IST] 00000077 SystemErr R at java.lang.Thread.run(Thread.java:813)

Vijay Rmk
Greenhorn

Joined: Mar 27, 2007
Posts: 4
i personally had an experience of migrating an application from was 5.1 to was 6.0(6.1.1 to be specific ...)..Thot i could share it wit you , if in case it comes handy for someone ...
1.Get the fix pack installed, else you will have great problems running jsp's .
2. WAS 6.0 is very strict abt the formatting of tags in jsp. Even if formatting of tags is not proper , was 5.0 allows it with warnings.
3. I have also found that, to facilitate jar dependencies, proper entries should be there in MANIFEST files..
Any specific issues, i will be most happy to help if i can ...
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: WAS 6.0