Exception runnig a application

Hi...
I am develop a small test application using fusion web application wiht ADF and Jdeveloper 11g, but I have un error message when run a simple page. This is the error:
oracle.jbo.JboException: JBO-29000: Unexpected exception caught: java.sql.SQLDataException, msg=ORA-01882: timezone region not found
note: I am using a oracle database: 9i version.
Please could someone help me?

That's a database level parameter you set when installing it.
Your DBA might be able to help you on this - and you can check the environment variable as well on the DB server.

Similar Messages

Exception in SAP Application Integrator occured: Unable to process templat

Hi,
We are trying to execute a BI report in portal through BEx web and we are getting the below error
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to process template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-ext-sid=<ESID[url_ENCODE]>&Language=<Request.Language>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<Authentication>&<Report>&<BusinessParameters>', because 'Report' is an invalid terminal property of the Root context.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
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:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
I have tested the connection in the system and also checked the webas name and host details in the system. they look fine.
please help me with your inputs.
Thanks.
Kind Regards,
Priyanka.

This could be the problem . In your portal , copy the pcd path of a folder under which you would like to place this report and paste it in the bex analyser while publishing (pcd link) , see if this helps . A few more points .
1) You can also publish these queries as reports in portal using Bex Query designer - there will be an option to publish in portal . You will see it depending upon the version of designer. If you are able to see that option , selecting the pcd location would require you to have content admin role in portal .
2) Manually create iviews in portal (BI Reports) using the query string given to you by your BI folks . You can create either Bex 3.X or 7.0 depending upon the query string .
Regards
Mayank

Reg: Runtime exception occurred during application mapping

Dear SAP Gurus,
This is Amar Srinivas Eli working currently on SOAP to SOAP Scenario on PI 7.1 Server.
I Would like to inform you that I have done all steps regarding DESIGN and CONFIG and also regarding SERVICE REGISTRY part successfully.
While Testing the data in the WS Navigator by giving the input parameters I am getting an error that
*<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
*- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_HRS_LISTReferral_Response_MM_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns1:PI_ListRefer</SAP:P3>
<SAP:P4>ral_Response_MT. Values missing in queue context.~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_HRS_LISTReferral_Response_MM_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns1:PI_ListReferral_Response_MT. Values missing in queue context.~</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
These are the steps I did while implementing..
1. Importing the XSD's successfully
2. Developed the design and config part and also checked nearly 3-4 times regarding both REQ and
 RESPONSE Mappings.
3. I already checked the link of WSDL once again...
4. Even I found REsponse Interface once again...
Still I am not getting where the error was ? Please guide me in detail in a right way in this issue.
Regards:
Amar Srinivas Eli
Edited by: Amar Srinivas Eli on Jan 13, 2009 7:53 AM

Hello,
I already checked all those queues and context fields////
Based on my Observation I found
1) As I am unable to view the SOAP BODY I increased the RUN TIME Trace Level to 3 and LOG_VAlue to 3
2) ANother most Important that I found later doing these settings are....
 I found Receiver Pay LOAD and I copied that entire pay load and pasted it in
 REceiver Message Mapping> Test Tab and Code->PASTED...and compared all those parameters
 in the TEST TAB and DEFINITION TAB in Tree View whether all the mandatory receiver mapped
 elements are coming I mean passing from source or not...
OBSERVATION::
I found that for nearly 3 fields there is a difference when I compared on Tree View in DEFINITION TAB and also parallely in the TEST TAB Tree View which I got by copied from MONI,,,,
see for example ::
CENTRE <----
> DISCHARGE DATE..
For going to CENTRE..here I found that in DEfiniition TAB...
Control Act Event-->Subject->document-->Component>Structured body> component> Section>Component>PatientCareProvisionEvent->EffectiveTime-->CENTRE
But immediately I have gone to TEST TAB and TREE VIEW and I found that respective field CENTRE is posting I mean passing any value or parameter to Discharged Date or not...
But I found that...
Control Act Event-->Subject->document-->Component>Structured body> component> Section>Component-->_PatientCareProvisionEvent_
This Implies that Effective Time and Centre are missing in the XML and I mean no values are passing to receiver right..
In PI XSD 's it is there but in I think after Compiling REQUEST MAPPING and while in returning to RESPONSE MAPPING I mean whenever the Response is posting to SOAP WEBSERVICE it is unable to found those target elements and I think due to this...
Am I Correct ?
If that is the case...Let me know where the issue is whether in the data present in the WEBSERVICE created on target side or in PI Side..any issue...
Regards:
Amar Srinivas Eli
Edited by: Amar Srinivas Eli on Jan 13, 2009 10:00 AM

Runtime exception occurred during application mapping

Hi All,
Please find the error message which we are getting:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_CRM_COD_ProductCategoryHierarchy_R~</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns0:ProductCateg</SAP:P3>
<SAP:P4>oryHierarchyMassReplicationRequest/ProductCategor~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_CRM_COD_ProductCategoryHierarchy_R~; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:ProductCategoryHierarchyMassReplicationRequest/ProductCategor~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please give your expert Advice on the same.
Regards
RK

Dear Rableen,
As Muniyappan and peter told about the mandatory field value is missing for the target element
"/ns0:ProductCategoryHierarchyMassReplicationRequest/ProductCategor", I am able to see other fields are also not getting input data.
as below
"Cannot create target element /ns0:ProductCateg"
Request you to test with the payload in message mapping and activate the message mapping first and then edit your operation mapping and call the same message mapping in your operation mapping and activate all your objects.
Thank you!
Regards
Hanumantha Rao

Runtime exception occurred during application mapping in SAP PI

Hi Team,
Please help me regarding this issue is very urgent:
Runtime Error in configuration part:
Here i test the XML message in Receiver Determintion:
Below i am getting error:
Runtime exception occurred during application mapping com/sap/xi/tf/_MaterialStockUpdate_Multi_AllPlant~; com.sap.aii.utilxi.misc.api.BaseRuntimeException:The processing instruction target matching "[xX][mM][lL]" is not allowed
SXMB_MONI:
I am getting below error:
Runtime exception occurred during application mapping

Hi,
Actually my problem is what i am getting,I am trying to test the data in runtime workbench and configuration part copied from inbound payload XML structure .
I already sent the screenshots of above errors,
Configuartion:
Runtime workbench:
This the error i am getting below in "Runtime Workbench"
Error While Sending Message: Additional error text from response: com.sap.engine.interfaces.messaging.api.exception.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=MHEPL_Sandbox_100;TS=;AN=MaterialStockUpdate_Multi_AllPlants_N;ANS=http://www.manipalhospitals.com/his/mm; in the current context [Unknown].

Runtime exception occurred during application mapping "EXCEPTION_DURING_EX"

Hi Gurus,
I am getting following error in MONI:
SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_MDM_CMS_Backfeed_Group_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.MessageMappingExceptio</SAP:P2>
<SAP:P3>n: Runtime exception when processing target-field</SAP:P3>
<SAP:P4>mapping /ns0:BackfeedGroup/group/MasterId; root m~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_MDM_CMS_Backfeed_Group_; com.sap.aii.mappingtool.tf7.MessageMappingException: Runtime exception when processing target-fieldmapping /ns0:BackfeedGroup/group/MasterId; root m~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have tried to refresh the mapping cache and restart the message but stil this message persists.
For me it seems an issue with a wrong mapping or some wrong value in the inbound scenario.
Please suggest if any one of you had come across this error before.
With Reg,
Vikash

Hi Vikash
Whenever you have a problem in your mapping you will get this kind of error in monitoring
According to your log the problem is in parameter /ns0:BackfeedGroup/group/MasterId
First of all check your mapping. If it is fine than check the value of this parameter from your payload.
Also try to copy your xml and test the mapping in IR. Check wether you are getting same error there .
If same error comes than try to manipulate the value of that field and try the same test again
Regards,
Shradha

Cannot create target element(Runtime exception occurred during application

Hi ,
this is IDOC TO HTTP Scenario. in error description it is shoein g below error.
Runtime exception occurred during application
Cannot create target element (inbound)
please advice
thank you.

Copy the payload from sxmb_moni and test it in the mapping tool using debug mode. I suspect some mandatory elements in target structure requires value but it is missing during mapping. Sometime sender data structure due to values are not getting at runtime does not create target structure element. Check all the individual fields in the mapping tool.

Exception in SAP Application Integrator occured

Hi,
I am facing a problem while opening transaction iviews in portal.In the default trace file below is the logs:
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component :pcd path of the component
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Exception occured in layer CommonTopLayer
Please suggest.Its urgent.
Regards,
Rajani

Hi,
Thanks for the reply.
Please find the default trace log:
=============================================
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd path of component
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : name of user as in portal
 at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
 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:524)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
 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:175)
 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(Native Method)
 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.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>&\#39;; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &\#39;SAP_LocalSystem&\#39;,
Attribute: &\#39;client&\#39;.
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
 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)
 ... 29 more
=============================================
Regards,
Rajani

Exception in SAP Application Integrator occured: ApplicationIntegratorExcep

Hello All
I have encountered a quite peculiar problem.
In My Portal( WAS SP 14), whenever i go to
System admin-> system config->uwl-> Universal Worklist Administration
It shows me Portal exception.
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: ApplicationIntegratorException .
Also when i check inside Content provided by SAP-> Admin content->system administrator->iviews->Universal worklist iview,( ALL UWL Iviews), throw Portal exception...
I tried uploading the com.sap.portal.appintegrator.sap.par from another WAS 7.0, SP14
but still it shows me same error in worklist iviews.
Also i trannsported the iviews via .epa files to My Portal, But no Success.
Help...
What to do????
Thanks...

EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: ApplicationIntegratorException
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.doPreview(AbstractPortalComponent.java:240)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:168)
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:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Exception in SAP Application Integrator occured while proccesing HCM F&P

Hi
I am getting following error, while Start Process.It's part of the HR Administrator; HCM forms & Proccess.
Open Process
Portal Runtime Error
An exception occurred while processing your request
Exception id: 05:05_11/03/10_0004_9166150
See the details for the exception ID in the log file.
Detail :
#1.5 #0050568F649300690000001E0000024800047FEF69B04AFB#1266566154115#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#CAP.GEMINI1#8121##torepdev_SPD_9166150#CAP.GEMINI1#983566c01d2b11dfb5c60050568f6493#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#/System/Server#Java###Exception ID:02:55_19/02/10_0001_9166150
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service/com.sap.pct.erp.mss.manager/overview/com.sap.pct.erp.mss.work_overview/com.sap.pct.erp.mss.work_overview_page/com.sap.pct.erp.common.key_figure_monitor
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : CAP.GEMINI1
 at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
 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:524)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
 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:386)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 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(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>&\#39;; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &\#39;SAP_LocalSystem&\#39;,
Attribute: &\#39;client&\#39;.
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
 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)
 ... 29 more
#1.5 #0050568F64930069000000200000024800047FEF69B3E251#1266566154349#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#CAP.GEMINI1#8121##torepdev_SPD_9166150#CAP.GEMINI1#983566c01d2b11dfb5c60050568f6493#SAPEngine_Application_Thread[impl:3]_4##0#0#Error##Java###02:55_19/02/10_0001_9166150
[EXCEPTION]
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>&\#39;; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &\#39;SAP_LocalSystem&\#39;,
Attribute: &\#39;client&\#39;.
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
 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:524)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
 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:386)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 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(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Please help.
Points Gauranteed.

Hi,
I am also facing same kind of error , can you suggest where can I check HCM F&P under webdynpro in portal side.
can you suggest which one is best way for to resolve my querry.
Full Message Text
04:43_12/04/11_0006_116801251
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
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:524)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Thanks
Renu

Software exception (0xc001000e) in application on ...

Hello, after installing the new version I have got following message (I am translating it form the Czech language): software exception (0xc001000e) in application on place 0x7c812fd3 What can I do??? Is there any chance my skype will work on windows XP? Thanks, regards, jakub.
Solved!
Go to Solution.

Please, run the DirectX diagnostics tool (32-bit version).
Go to Windows Start and in the Run box type dxdiag.exe and press the OK button. This will start the DirectX diagnostics program. Run this diagnostics and save the results to a file. Please, attach this file to your post.
Be aware that you will have to zip this file before attaching it here.

Spotlight seems to be of no use except for finding applications

Whenever I search for music, pictures, videos, or even simple word documents on Spotlight, it returns no results unless I first click "Show All" so the Spotlight window comes up and then only by selecting "Home" under "Where". Whenever I search directly from the Spotlight icon, however, it's basically useless, except for finding applications. What's wrong with it? How can I fix it so that it searches for everything that it was made to find?

Eyeonic -
As you seem to be finding, Spotlight's kind of problematic. In my experience it manages both to find too little and too much.
-- "Too little" because, rather than search your hard drive, Spotlight searches its own index, which by design doesn't include everything on your computer; plus from time to time the indexing process simply doesn't complete itself, or the index becomes silently corrupt. I don't trust Spotlight searches.
-- "Too much" because the unrestricted Spotlight search from the menubar returns every document that contains even a whiff of your search term, the result being that you may have to slog through 400 hits to find the one document with the filename you specified. (You can perform the search using cmd-F and that will help a bit but it's a few more keystrokes.)
For simple filename searches I've found it is best to simply bypass Spotlight altogether and use the non-index-based utility EasyFind (http://www.versiontracker.com/dyn/moreinfo/macosx/11706). It's not as fast as the pre-Tiger cmd-F find but it produces more reliable and more predictable results than anything Spotlight can currently offer.
I'm hoping (without any particular basis for it however) that Apple makes Spotlight a little more useable in Leopard.

Invocation Target Exception while Migrating application to weblogic 10.3

Hi All,
We are currently migrating our application from weblogic 8.1 to weblogic 10.3.
The deployment in wls 10.3 is successful, but while performing some operations(User Registration.. etc)
we are getting SQLIntegrityConstraintViolationException.
=================================================================================================
2010-10-27 17:03:50,968 DEBUG com.sns.ana.services.ConnPoolService - Param 0: java.util.Hashtable
2010-10-27 17:03:50,968 DEBUG com.sns.ana.services.ConnPoolService - Param 1: java.lang.String
2010-10-27 17:03:50,968 DEBUG com.sns.ana.services.ConnPoolService - Param 2: weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection
2010-10-27 17:03:50,968 DEBUG com.sns.ana.dbsource.AuthorisationDBSource - [addRolesToDB] rows: 0, sql: delete from tana_role where userid = 'odcwls104'
2010-10-27 17:03:51,030 ERROR com.sns.ana.services.ConnPoolService - [getRestrictedService] InvocationTargetException:
java.sql.SQLIntegrityConstraintViolationException: ORA-02291: integrity constraint (ESIUSER.FK_TANAROLE_UID) violated - parent key not found
     at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:85)
     at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1030)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194)
     at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:947)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1222)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3381)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3462)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1349)
     at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:159)
     at com.sns.ana.dbsource.AuthorisationDBSource.addRolesToDB(AuthorisationDBSource.java:684)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sns.ana.services.ConnPoolService.getRestrictedDataService(ConnPoolService.java:39)
     at com.sns.ana.services.DataServiceProvider.getRestrictedDataService(DataServiceProvider.java:45)
     at com.sns.ana.user.SNSUser.updateRoles(SNSUser.java:303)
     at com.sns.ana.utils.RoleUtility.processNewRequest(RoleUtility.java:114)
     at com.sns.ana.ui.servlet.ManageUserServlet.doPost(ManageUserServlet.java:395)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at com.sns.ana.ui.servlet.AuthorisationBaseServlet.service(AuthorisationBaseServlet.java:86)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:502)
     at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
     at com.sns.ana.ui.servlet.ANAADMMainServlet.doPost(ANAADMMainServlet.java:741)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at com.sns.ana.ui.servlet.AuthorisationBaseServlet.service(AuthorisationBaseServlet.java:86)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3495)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
=================================================================================================
Upon weblogic server shut down below NameNotFoundException is thrown.
=================================================================================================
BaseException: ClassName=null,MethodName=null,MajorCode=-1,MajorMsg=Message Not Available,MinorCode=null,ExceptionObjMsg=[DBConnection][getConnec
tion]Unable to init database connection due to unresolved DataSource Name com.fortressit.ejb.PortableContextException: javax.naming.NameNotFoundE
xception: While trying to look up comp/env/jdbc/ap2esiDSLocal in /app/webapp/webadminesi/26700672. [Root exception is java.rmi.ConnectIOException
: Server is being shut down]; remaining name 'comp/env/jdbc/ap2esiDSLocal'
While trying to look up comp/env/jdbc/ap2esiDSLocal in /app/webapp/webadminesi/26700672.
at com.sns.base.util.DBConnection.getConnection(Unknown Source)
at com.sns.ana.services.ConnPoolService.getParamsWithDBConnection(ConnPoolService.java:93)
at com.sns.ana.services.ConnPoolService.getRestrictedDataService(ConnPoolService.java:35)
at com.sns.ana.services.DataServiceProvider.getRestrictedDataService(DataServiceProvider.java:45)
at com.sns.ana.ui.servlet.listener.CleanupAppSessionListener.sessionDestroyed(CleanupAppSessionListener.java:43)
at weblogic.servlet.internal.EventsManager.notifySessionLifetimeEvent(EventsManager.java:265)
at weblogic.servlet.internal.session.SessionData.remove(SessionData.java:873)
at weblogic.servlet.internal.session.MemorySessionContext.invalidateSession(MemorySessionContext.java:69)
at weblogic.servlet.internal.session.MemorySessionContext$SessionCleanupAction.run(MemorySessionContext.java:114)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.session.MemorySessionContext.destroy(MemorySessionContext.java:90)
at weblogic.servlet.internal.WebAppServletContext.destroy(WebAppServletContext.java:3062)
at weblogic.servlet.internal.ServletContextManager.destroyContext(ServletContextManager.java:240)
at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:457)
at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:1398)
at weblogic.servlet.internal.WebAppModule.deactivate(WebAppModule.java:492)
at weblogic.application.internal.flow.ModuleStateDriver$2.previous(ModuleStateDriver.java:188)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:148)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:138)
at weblogic.application.internal.flow.ModuleStateDriver.deactivate(ModuleStateDriver.java:71)
at weblogic.application.internal.flow.ScopedModuleDriver.deactivate(ScopedModuleDriver.java:206)
at weblogic.application.internal.flow.ModuleListenerInvoker.deactivate(ModuleListenerInvoker.java:124)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.previous(DeploymentCallbackFlow.java:417)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:148)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:138)
at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:91)
at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:83)
at weblogic.application.internal.BaseDeployment$2.previous(BaseDeployment.java:641)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:148)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:138)
at weblogic.application.internal.BaseDeployment.deactivate(BaseDeployment.java:234)
at weblogic.application.internal.EarDeployment.deactivate(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.deactivate(DeploymentStateChecker.java:199)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.deactivate(AppContainerInvoker.java:98)
at weblogic.deploy.internal.targetserver.BasicDeployment.deactivate(BasicDeployment.java:263)
at weblogic.deploy.internal.targetserver.BasicDeployment.deactivateFromServerLifecycle(BasicDeployment.java:458)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doDeactivate(DeploymentAdapter.java:73)
at weblogic.management.deploy.internal.DeploymentAdapter.deactivate(DeploymentAdapter.java:211)
at weblogic.management.deploy.internal.AppTransition$6.transitionApp(AppTransition.java:66)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.deactivate(ConfiguredDeployments.java:198)
at weblogic.management.deploy.internal.ConfiguredDeployments.undeploy(ConfiguredDeployments.java:191)
at weblogic.management.deploy.internal.DeploymentServerService.shutdownApps(DeploymentServerService.java:188)
at weblogic.management.deploy.internal.DeploymentServerService.shutdownHelper(DeploymentServerService.java:120)
at weblogic.application.ApplicationShutdownService.halt(ApplicationShutdownService.java:142)
at weblogic.t3.srvr.ServerServicesManager.haltInternal(ServerServicesManager.java:502)
at weblogic.t3.srvr.ServerServicesManager.halt(ServerServicesManager.java:334)
at weblogic.t3.srvr.T3Srvr.shutdown(T3Srvr.java:948)
at weblogic.t3.srvr.T3Srvr.forceShutdown(T3Srvr.java:854)
at weblogic.t3.srvr.T3Srvr$2.run(T3Srvr.java:867)
##### proxy instance has been created !!!
=================================================================================================
From the above exceptions i can infer that, the database connection failed due to unresolved datasource name.
However we have configured all the Datasources, application seems to be having problem in wls 10.3.
Waiting in anticipation for replies.
Regards
Avinash

Hi Avinash,
It seems that the application is not able to get the DataSource JNDI name which you have given that the reason you are getting the NameNotFoundException exception.
Try to give the same JNDI name in the datasource which your application is trying to lookup, once you have created the datasource make sure you test the connection using Test Connection option by which you can be sure that if the test connection can get a connection from the DB everything is fine also check the JNDI tree if you can see the datasource JNDI name in there.
Hope this helps you.
Regards,
Ravish Mody

Getting class cast exception in Web application.

I have a web application deployed using standard specs for deployment. I
 have and web-inf directory with a web.xml file set up. All the servlet
 classes are in the classes sub-directory of web-inf.
 If I deploy this application using the Tomcat application server,
 everything works as expected. When I deploy this application using the
 Weblogic software, I can get to the initial page, put once I select a
 link that calls the main servlet, I get a classcast exception. Both the
 Tomcat and Weblogic software point to the same directory for the
 application.
 I double checked and made sure that no other instances of my servlet
 classes exist anywhere else in the class path.
 Any one have any thoughts or suggestions. I am perplexed that this web
 app runs fine under the Tomcat software and yet...
 Thanks.
 Paul Garduno


Thanks for your reply. I am not using any EJBs. From what I have
 gathered since writing my message, this may be the "dreaded" class cast
 exception (although I don't know why since it runs under Tomcat).
 Basically, the initial page is displayed. When you select the SEARCH
 button (for example), the request goes to a servlet which puts a vector
 of custom classes into a session parameter. The request is then
 forwarded to the JSP page which uses the information in the classes to
 help build some information on the page. The first line in the JSP is
 processed (a simple output line to the system console) and then the
 classcast exception occurs.
 According to the info that I have seen, this shouldn't happen since I am
 not changing either the servlet or JSP files which would mean that
 nothing should be re-compiled.
 I have a call into tech support. I will post their answer and copy you
 on the message.
 Thanks.
 Paul
 Cameron Purdy wrote:
 >
 > Are you using EJBs hosted on the same instance of WebLogic? If so, delete
 > the home/remote interfaces from your web deployment. Otherwise, post the
 > exception listing ....
 >
 > Cameron Purdy, LiveWater
 >
 > "Paul Garduno" <[email protected]> wrote in message
 > news:[email protected]...
 > > I have a web application deployed using standard specs for deployment. I
 > > have and web-inf directory with a web.xml file set up. All the servlet
 > > classes are in the classes sub-directory of web-inf.
 > >
 > > If I deploy this application using the Tomcat application server,
 > > everything works as expected. When I deploy this application using the
 > > Weblogic software, I can get to the initial page, put once I select a
 > > link that calls the main servlet, I get a classcast exception. Both the
 > > Tomcat and Weblogic software point to the same directory for the
 > > application.
 > >
 > > I double checked and made sure that no other instances of my servlet
 > > classes exist anywhere else in the class path.
 > >
 > > Any one have any thoughts or suggestions. I am perplexed that this web
 > > app runs fine under the Tomcat software and yet...
 > >
 > > Thanks.
 > >
 > > Paul Garduno

Exception when deploying application using admin console

Whenever I deploy an application using the admin console window, I get a DistributedExcpetion,
The application gets deployed though! so I am assuming that this is not very critical,
but If somebody can tell me what this is then It would be really helpful.
Thx-
Iqbal
Here is the exception stack trace:-
java.lang.reflect.InvocationTargetException: weblogic.management.DistributedManagementException:
Distributed Management [1 exceptions]
 at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:443)
 at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
 at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
 at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
 at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
 at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
 at $Proxy10.setDeployed(Unknown Source)
 at java.lang.reflect.Method.invoke(Native Method)
 at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
 at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
 at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
 at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.console.utils.SetException: An error occurred while updating
Deployed on Proxy for mydomain:Name=cmeEJB,Type=Application - with nested exception:
[java.lang.reflect.InvocationTargetException - with target exception:
[weblogic.management.DistributedManagementException: Distributed Management [1 exceptions]]]
 at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:151)
 at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
 at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Hi.
Thanks for the additional info.
I found 2 similar issues with similar stack traces for WLS 6.1 sp2. One of the issues we could not reproduce, and in the
end the customer reinstalled WLS and the problem went away. The other issue was found internally and is not currently
active. I'm not 100% sure your situation is identical to one of these.
Therefor I suggest the following course of action:
1. Since this is an intermittant problem try reinstalling WLS. If that doesn't help then...
2. open a case with support. It may not be a major issue, but we need to be sure of this.
Hope this helps,
Michael
Iqbal wrote:
I am running WLS version 6.1 with sp2. I get this error every once in a while.
Thx!
-Iqbal
Michael Young <[email protected]> wrote:
Hi.
This may be a known issue, but I need more info. What version (including
service pack level) of WLS are you running?
Also, if you are not running sp2 please apply it and test to see if you
are still seeing this.
Let me know what you find.
Thanks,
Michael
Iqbal wrote:
Whenever I deploy an application using the admin console window, I geta DistributedExcpetion,
The application gets deployed though! so I am assuming that this is notvery critical,
but If somebody can tell me what this is then It would be really helpful.
Thx-
Iqbal
Here is the exception stack trace:-
java.lang.reflect.InvocationTargetException: weblogic.management.DistributedManagementException:
Distributed Management [1 exceptions]
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:443)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy10.setDeployed(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.console.utils.SetException: An error occurred whileupdating
Deployed on Proxy for mydomain:Name=cmeEJB,Type=Application - with nestedexception:
[java.lang.reflect.InvocationTargetException - with target exception:
[weblogic.management.DistributedManagementException: Distributed Management
[1 exceptions]]
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:151)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)--
Michael Young
Developer Relations Engineer
BEA Support
Michael Young
Developer Relations Engineer
BEA Support

Exception runnig a application

Similar Messages

Maybe you are looking for