Solved

Webshere portal server 6.0 exception

Posted on 2007-03-21
5
994 Views
Last Modified: 2012-05-05
When ever I am trying to deploy war file on webshere portal server 6.0  I am getting an exception.

 [3/20/07 5:42:21:819 CST] 00000060 TextTag       E com.ibm.wps.engine.tags.TextTag doStartTag EJPEJ0076E: The key link.page.actions could not be found in bundle nls.engine.
                                 java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key link.page.actions
      at java.util.ResourceBundle.getObject(ResourceBundle.java(Compiled Code))
      at java.util.ResourceBundle.getString(ResourceBundle.java(Compiled Code))
      at com.ibm.wps.engine.tags.TextTag.doStartTag(TextTag.java:74)
      at com.ibm._jsp._Default._jspx_meth_portal$1fmt_text_25(_Default.java:4370)
      at com.ibm._jsp._Default._jspService(_Default.java:2045)
      at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:91)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
      at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1282)
      at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1239)
      at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:113)
      at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:82)
      at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:670)
      at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:117)
      at com.ibm.ws.jsp.webcontainerext.JSPExtensionServletWrapper.handleRequest(JSPExtensionServletWrapper.java:178)
      at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include(WebAppRequestDispatcher.java:613)
      at com.ibm.wps.services.dispatcher.DispatcherServiceImpl.handleRequest(DispatcherServiceImpl.java:87)
      at com.ibm.wps.services.dispatcher.DispatcherServiceImpl.include(DispatcherServiceImpl.java:52)
      at com.ibm.wps.services.dispatcher.Dispatcher.include(Dispatcher.java:45)
      at com.ibm.wps.engine.templates.themes.Default.render(Default.java:142)
      at com.ibm.wps.engine.templates.ThemeTemplate.render(ThemeTemplate.java:67)
      at com.ibm.wps.engine.phases.WPRenderPhase.processRendering(WPRenderPhase.java:322)
      at com.ibm.wps.engine.phases.WPRenderPhase.execute(WPRenderPhase.java:137)
      at com.ibm.wps.state.phases.AbstractRenderPhase.next(AbstractRenderPhase.java:106)
      at com.ibm.wps.engine.phases.WPAbstractRenderPhase.next(WPAbstractRenderPhase.java:93)
      at com.ibm.wps.engine.Servlet.callPortal(Servlet.java:791)
      at com.ibm.wps.engine.Servlet.doGet(Servlet.java:629)
      at com.ibm.wps.engine.Servlet.doPost(Servlet.java:814)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
      at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1282)
      at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1239)
      at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:136)
      at com.ibm.wps.state.filter.StateCleanup.doFilter(StateCleanup.java:86)
      at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:142)
      at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:121)
      at com.ibm.wps.mappingurl.impl.URLAnalyzer.doFilter(URLAnalyzer.java:257)
      at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:142)
      at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:121)
      at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:82)
      at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:670)
      at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:2965)
      at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:221)
      at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:210)
      at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1931)
      at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:84)
      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:472)
      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:411)
      at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:101)
      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:566)
      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:619)
      at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:952)
      at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1039)
      at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
0
Comment
Question by:rajaamirapu
5 Comments
 
LVL 18

Expert Comment

by:Serena Hsi
ID: 18773343
I'd say that from the error log, you'd need to upgrade your Java library. IBM's knowledgebase has a technote on this topic "FileNotFoundException or PathNameTooLongException during start of a deployed WebApplication or when deploying WAR file" which says:

Due to a path length limitation of the Windows JDK, a resource path must not exceed 256 characters. Access to resources that are stored with longer pathnames results in a FileNotFoundException. Consequently the resource cannot be loaded and the operation is aborted.

These also may help:

Using Java 2 Security with WebSphere Portal
http://publib.boulder.ibm.com/infocenter/wpdoc/v510/topic/com.ibm.wp.ent.doc/wpf/sec_java2.html

IBM developerWorks : WebSphere Portal zone
http://www.ibm.com/developerworks/websphere/zones/portal/

WebSphere Portal RSS
http://www-128.ibm.com/developerworks/forums/dw_forum_rss.jsp?forum=168&full=true


0
 
LVL 5

Author Comment

by:rajaamirapu
ID: 18807447
Please close this question, as i have solved the problem by myselft
0
 

Expert Comment

by:schaumi
ID: 18945329
Here is a solution (though the question is closed)

The engine_xx.properties are in <WPS_HOME>/shared/app/nls.
Make sure that the files exist and are not taken from an older Portal version.
e.g. the "link.page.actions" property is new in WPS 6.0

In our case, the nls files are part of an automatic deployment. During the first deployment we overwrote the nls files of Version 6 with the ones from 5.1.
0
 

Accepted Solution

by:
AnnieMod earned 0 total points
ID: 19390695
PAQed with points refunded (500)

AnnieMod
Cleanup Admin
0

Featured Post

Master Your Team's Linux and Cloud Stack

Come see why top tech companies like Mailchimp and Media Temple use Linux Academy to build their employee training programs.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Envision that you are chipping away at another e-business site with a team of pundit developers and designers. Everything seems, by all accounts, to be going easily.
Because your company can’t afford for you to make SEO mistakes, you’ll want to ensure you’re taking the right steps each and every time you post a new piece of content. This list of optimization do’s and don’ts can help you become an SEO wizard.
Explain concepts important to validation of email addresses with regular expressions. Applies to most languages/tools that uses regular expressions. Consider email address RFCs: Look at HTML5 form input element (with type=email) regex pattern: T…
The viewer will learn how to dynamically set the form action using jQuery.

803 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question