- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- Can't find resource for bundle java.util.PropertyR...
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Can't find resource for bundle java.util.PropertyResourceBundle
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 07-28-2008 10:50 PM
Hi All,
We have customized PCRs and all were working fine. But today it started giving problem, whenever those PARs are called. In the customized PARs we are referring to "com.sap.pct.hcm.util.pcrutilities". But whenever we are using this reference class it is giving exception as :
An exception occurred while processing a request for :
iView : pcd:portal_content/com.freescale.EP_Portal_Projects/hcmiViews/com.freescale.mgrpcr_ivu_0026
Component Name : com.freescale.hcm.pcr_deleteorg.default
Can't find resource for bundle java.util.PropertyResourceBundle, key ScNameDeleteOrg.
Exception id: 12:51_28/07/08_0044_303694150
See the details for the exception ID in the log file.
This is happening in one of our system that got its hostname changed. Not sure but is that related to the hostname change??
On other systems it is working fine. In all the PCRs it is giving the same exception as:
Can't find resource for bundle java.util.PropertyResourceBundle
Could you please let us know how to resolve this? and whats the cause for this? Its really urgent for us.
Thanks in advance!!!
Regards,
Gurmat Bhatia
- SAP Managed Tags:
- SAP NetWeaver
Accepted Solutions (0)
Answers (3)
Answers (3)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
(per Gurmat)
We identify the cause of the problem. Standard
JAR "com.sap.pct.hcm.util.pcrutilities" was missing from the PAR. We
picked the PAR that was deployed on the system. When we downloaded the
PAR on NWDS, that JAR was missing then we have to manually add that JAR
to the PAR. Do everytime we have to manually add the JAR or it should
automatically be coming under the PAR.
If there is any JAR added to the PAR, the reference to that JAR is not
lost even if you are picking the deployed PAR. But for PCRUtilities PAR
this is happening.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
I am on 7.3 EP Portal and trying to use old JSP PCR forms on this portal. I migrated all of the standard and custom par files to ear files. As per above issue, I added PCRUtiles.jar file to the standard par file.
But after deploying I am getting following error:
[EXCEPTION]
java.lang.ClassCastException: class com.sap.pct.hcm.util.pcrutilities.PCRBundleBean:sap.com/com.sap.pct.hcm.pcrutilities@com.sap.engine.boot.loader.ResourceMultiParentClassLoader@3a06b6b4@alive incompatible with interface com.sapportals.portal.prt.component.IPortalComponent:library:tc~epbc~prtc~api@com.sap.engine.boot.loader.ResourceMultiParentClassLoader@69ae8935@alive
at com.sap.portal.prt.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:191)
at com.sap.portal.prt.broker.PortalComponentItem.load(PortalComponentItem.java:371)
at com.sap.portal.prt.om.ObjectsManager.craeteObejctHandle(ObjectsManager.java:221)
at com.sap.portal.prt.om.ObjectsManager.getObjectHandle(ObjectsManager.java:141)
at com.sap.portal.prt.broker.PortalAppBroker.getPortalComponent(PortalAppBroker.java:374)
at com.sap.portal.prt.component.PortalComponentContext.getPortalComponentApp(PortalComponentContext.java:115)
at com.sap.portal.prt.component.PortalComponentContextFactory.createPortalComponentContext(PortalComponentContextFactory.java:188)
at com.sap.portal.prt.component.PortalComponentContextFactory.getPortalComponentContext(PortalComponentContextFactory.java:82)
at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:442)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:201)
at com.sap.portal.prt.dispatcher.DispatcherServlet.service(DispatcherServlet.java:132)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
Can we somehow get this deployed to EP 7.3 Portal?
Regards,
Nitesh
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi gurmat
We have a similar issue in producition server, where a single user is getting this error. Were you able to solve this issue ?
Please advice.
Thanks in advance!
Regards,
anupama
Edited by: AnupamaD on Mar 26, 2010 9:57 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
In our ISRMain.JSP, we are using the following code:
<jsp:useBean id="rb" scope="page" class="com.sap.pct.hcm.util.pcrutilities.PCRBundleBean" />
and when we are accessing this bean
<%= rb.getLocalString("ScNameModifyOrg") %>
It is giving the exception.
This is the default trace file:
com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.sapportals.portal.htmlb.page.JSPDynPage.doOutput(JSPDynPage.java:76)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.navigation.workAreaiView.doContent(workAreaiView.java:228)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:174)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Original exception:
at pagelet._sapportalsjsp_IsrMain.doContent(_sapportalsjsp_IsrMain.java:69)
at pagelet._sapportalsjsp_IsrMain.service(_sapportalsjsp_IsrMain.java:43)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
... 45 more
Caused by: java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key ScNameModifyOrg
at java.util.ResourceBundle.getObject(ResourceBundle.java:330)
at java.util.ResourceBundle.getObject(ResourceBundle.java:327)
at java.util.ResourceBundle.getString(ResourceBundle.java:290)
at com.sap.pct.hcm.util.pcrutilities.PCRBundleBean.getLocalString(PCRBundleBean.java:17)
at pagelet._sapportalsjsp_IsrMain.subDoContent(_sapportalsjsp_IsrMain.java:263)
at pagelet._sapportalsjsp_IsrMain.doContent(_sapportalsjsp_IsrMain.java:63)
... 49 more
#
#1.5#001A64A833AE003C000038B00016502400045319666B8F56#1217268464455#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
#1.5#001A64A833AE003C000038B1001650240004531966F56996#1217268473489#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
#1.5#001A64A833AE003C000038B20016502400045319677F7CDA#1217268482538#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
#1.5#001A64A833AE003C000038B300165024000453196809454B#1217268491568#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
#1.5#001A64A833AE003C000038B4001650240004531968932979#1217268500605#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
#1.5#001A64A833AE003C000038B50016502400045319691CF3E6#1217268509635#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
#1.5#001A64A833AE003C000038B6001650240004531969A695F4#1217268518655#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
#1.5#001A64A833AE003C000038B700165024000453196A30B8A3#1217268527708#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
#1.5#001A64A833AE003C000038B800165024000453196ABB152A#1217268536775#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
#1.5#001A64A833AE003C000038B900165024000453196B45799F#1217268545845#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
#1.5#001A64A833AE003C000038BA00165024000453196BCFB86C#1217268554905#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
#1.5#001A64A833AE003C000038BB00165024000453196C59824D#1217268563935#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
#1.5#001A64A833AE003C000038BC00165024000453196CE33318#1217268572959#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
#1.5#001A64A833AE003C000038BD00165024000453196D6D1565#1217268581995#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
#1.5#001A64A833AE003C000038BE00165024000453196DF6B83A#1217268591015#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
#1.5#001A64A833AE003C000038BF00165024000453196E809230#1217268600050#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
#1.5#001A64A833AE003C000038C000165024000453196F0A97EF#1217268609095#com.sapportals.wcm.service.crawler.wcm.StatusThread#sap.com/irj#com.sapportals.wcm.service.crawler.wcm.StatusThread#Guest#1####c8a80d805b9e11ddcfbe001a64a833ae#Thread[Thread-70,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Warning##Plain###failed to create lock file for crawler status#
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Start page of SAP Signavio Process Insights, discovery edition, the 4 pillars and documentation in Technology Blogs by SAP
- Consuming SAP with SAP Build Apps - Mobile Apps for iOS and Android in Technology Blogs by SAP
- Easy way to automate and configure the setup of a BTP account and Cloud Foundry using Terraform. in Technology Blogs by Members
- Analyze Expensive ABAP Workload in the Cloud with Work Process Sampling in Technology Blogs by SAP
- Deployment Error "ABAP language version is not supported for objecttype WAPA." in Technology Q&A
| User | Count |
|---|---|
| 84 | |
| 10 | |
| 10 | |
| 9 | |
| 7 | |
| 6 | |
| 5 | |
| 5 | |
| 4 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.