Report not running "session expired error"
while trying to run a query...its not opening and showing "session expired error after 30 mts.
how to rectify it
hi devi,
use the following links
Error msg in BW after session timeout
Retain hierarchy node value on selection screen during execution of report
with hopes
Raja Singh
Similar Messages
-
Report not run inexplorer and report server not start
sir
i install dev suit 10g and
1. create new form and test that run in explorer
2. create report and test in report builder that run and give right result, but when i test in explorer that not run and no error and report server OC4J not start i try but window appear and hide
please give me idea how run report in explorer
regard
fahimThe normal procedure for the Developer Suite is:
1. Start OC4J instance via Windows Start menu.
2. Run a report:
http://127.0.0.1:8889/reports/rwservlet?module=....
That doesn't work?
Can you see the in-process report server?
http://127.0.0.1:8889/reports/rwservlet/showenv?
Or errors in the job queue?
http://127.0.0.1:8889/reports/rwservlet/showjobs?
(note that your port number may be different) -
Session expired error after migration 11.1.1.1
We are taking a lots of session expired error after migrating our projects from 11.1.1.1. to the 11.1.1.0
How can we control session parameters in Jdev 11.1.1.1 and Web logic 10.1.3.1 ?
Thanks.Hi,
its still the same setting in the web.xml file. However, I think the expiry you mean is the one raised by the client framework. As far as I remember there is no way to configure itslength. I'll take a not to see what the plans are in this regards. Can you confirm that its not the serve expiry but the message you get from ADF Faces RC?
Frank -
BIP event trigger throwing session expired error!
Hi,
I am trying to have some event triggers in my data model, but as soon as i click on the UpdateDefaultPackage button the box throws session expired error.
I am using Firefox for development, and when i do the same in IE the function list doesn't get populated.
Give me some suggestions.
Thanks and Regards
PrakharCheck your browser settings for accepting cookies from this domain, you must have tried this by now clearing all your browser cache and cookies.
try solutions beacon site where they have Oracle Apps Demo Instances for Public
http://www.solutionbeacon.com/tools_vision.htm -
Just attempted to download current update of Itunes into my HP computer with Windows 7. I've never had trouble before but now it will not run. Runtime Error R6034 an app has make an attempt to load the C runtime library incorrectly. Itunes Error 7
Click here and follow the instructions. You may need to completely remove and reinstall iTunes and all related components, or run the process multiple times; this won't normally affect its library, but that should be backed up anyway.
(99714) -
Session Expired Error in Oracle Vision Demo due to absence of a cookie !!
Hi Folks,
I kept getting the session expired error in Vision Demo even after I had supplied the right user id/password combos. So I set up a on-logon trigger in the APPS schema and it turns out that the Front End JSP page calls the ICX_SEC package.
Herein it refers to the function valiadateSession inside this package. I did some digging around and it turns out that inside this function using the OWA_COOKIE utility the function tries to get the details of a cookie called 'WF_SESSION' and passes this to the Front End.
And this is where it is failing. I checked to see and the return from the OWA_COOKIE.GET('WF_SESSION') does return a value of NUM_VALS=0. So the problem remains that the intial JSP page is unable to either set the cookie or I am reading this all wrong.
Plan to dig deep into this. Meanwhile if anyone has faced this error any helpful tips would be deeply appreciated.
PS: I am new to Oracle Apps and have to learn it in a hurry :(( Sad part is am unable to even get into the Application as of now :P I have installed and am using 11i.8 (11.5.8).
cheers
~
kaushikCheck your browser settings for accepting cookies from this domain, you must have tried this by now clearing all your browser cache and cookies.
try solutions beacon site where they have Oracle Apps Demo Instances for Public
http://www.solutionbeacon.com/tools_vision.htm -
Reports not Running. RAS is erroring CORBA communication error
Hi, One of the boxi XI R2 SP3 server in cluster is not working correctly. WHen I stopped all other servers and ran report on this server and I got the below error message.
Can someone help on this issue. Our Crystal reports are taking forever to run.
The error message in crystalras_2009211_132028_1872_ras.log is given below.
Thanks,
Kalpesh
=========================================================================
ErrorLog 2009 2 11 8:31:00.396 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:31:01.396 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:31:22.490 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:31:23.490 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:31:44.585 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:31:45.585 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:32:06.789 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:32:07.789 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:32:28.774 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:32:29.774 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:32:50.853 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:32:51.853 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:33:12.838 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:33:13.838 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:33:34.948 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:33:35.948 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:33:57.152 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:33:58.152 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:34:19.246 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:34:20.246 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:34:41.434 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:34:42.434 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:35:03.544 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:35:04.544 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:35:25.514 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:35:26.514 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:35:47.499 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:35:48.499 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:36:09.609 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:36:10.609 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:36:31.578 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:36:32.578 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:36:53.563 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:36:54.563 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:37:15.658 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:37:16.658 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:37:37.643 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:37:38.643 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:37:55.581 1872 7944 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:37:56.581 1872 7944 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:37:59.628 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:38:00.628 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:38:17.582 1872 7944 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:38:18.582 1872 7944 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:38:21.738 1872 7392 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:38:39.567 1872 7944 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:38:40.567 1872 7944 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:39:01.755 1872 7944 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:39:02.755 1872 7944 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:39:23.865 1872 7944 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:39:24.865 1872 7944 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:39:45.944 1872 7944 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:39:46.944 1872 7944 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:40:08.054 1872 7944 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:40:09.054 1872 7944 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
ErrorLog 2009 2 11 8:40:30.023 1872 7944 (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2009 2 11 8:40:31.023 1872 7944 (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
====================================================Hello Pandeyji,
We have a similar problem. Can you please let us know, on which server the ports are opened. We appreciate your immediate response.
Thanks.
Madhu Allani -
SSRS 2012 Session Expired Error..
We have reporting environment with SSRS 2012 configured with forms authentication…
When users taking reports we are getting following errors randomly. We increased the valued of Query Timeout and Session Timeout in WebConfig. But still the error is persisting…Any one help us to resolve this issue?
microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: , An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.;
session!ReportServer_0-9!1070!08/11/2014-03:08:58:: e ERROR: Error in getting session data: Invalid or Expired Session: e3z2csibgn4kmbum1wm2cs2bHi Vichu,
According to your description, you encountered the timeout issue when rendering your report. Right?
In Reporting Services, sometimes this issue happens when rendering big report, and it exceed the default Query Timeout time. Generally, we increase the Query Timeout and Session Timeout so that it will have more time to retrieving data.
In this scenario, since you have done this adjustment and the issue still exists randomly. We suggest you optimize the performance of your report. Please refer to the articles below:
Processing large reports:
http://technet.microsoft.com/en-us/library/ms159638.aspx
Performance (Reporting Services):
http://technet.microsoft.com/en-us/library/bb522786.aspx
Improving report performance with caching:
http://technet.microsoft.com/en-us/library/ms155927.aspx
Report performance optimization tips:
http://blogs.msdn.com/b/robertbruckner/archive/2009/01/08/report-performance-optimization-tips-subreports-drilldown.aspx
In addition, we recommend you install the Updates for SSRS 2012:
http://sqlserverbuilds.blogspot.com/
If you have any question, please feel free to ask.
Best Regards,
Simon Hou -
New installation of Prime Infrastructure 2.2.0 (PI-VA-2.2.0.0.158.ova)
installed fixes/software/device packs:
PI 2.2.1 Poodle Fix (installed)
PI 2.2.1 Maintenance Release (installed,ncs stopped,rebooted)
Prime Infrastrucutre 2.2 Device Pack 3 (installed,ncs stopped,rebooted)
Licences installed (ncs stopped,rebooted)
Added all devices via Bulk Import (Inventory>Device Management>Network Devices)
Problem 1:
The Cisco 5500 WLCs are not listed in Inventory>Device Management>Network Devices (see screen shot) but listed under "All Devices"!
The Cisco 4400 WLCs and the 8500 WLCs are listed within their subgroup.
Devices are in "Managed State"
Problem 2: fixed! (Browser issue)
Problem 3:
Unable to run "Wired Detailed Device Inventory" report because I get the error message: Failed to run report: Unable to retrieve data for: Chassis Information (if Chassis Information is selected, if System Information is selected I get the error message with ...retrieve data for:System Information)
All devices do have an "Admin Status = Managed" and the Last Inventory Collections Status = Completed.
Has anyone the same issues or a tip for me?
Another topic, the "User Defined Fileds" are not exported when with running a "Device Export" (Inventory > Device Management > Network Devices). ;-(
BR
BastianHallo Bastian,
I think you still have browser issue, Using IE is still the best with Prime.
I have exactly same prime 2.2 and installed fixes/software/device packs.
I have no problem I can see all views. I use now IE 11, with Chrome 42.0.2311.90 and firefox 37.01 I have problems too with lots of views. You have not tell what browser + version you have.
Since you have same prime 2.2 as me. I have other problems, can you check yours?
Can you see a functional CLI template page at Configuration > Templates > Features & Technologies:
https://supportforums.cisco.com/discussion/12481691/can-cisco-prime-22-still-do-simple-ad-hoc-deployment-job-cli-over-all-switches
Do you have SNMP Connectivity Failed while Verify Credentials has no errors all green and checked.
https://supportforums.cisco.com/discussion/12494786/snmp-request-exceeds-internal-data-buffer-512-bytes-prime-22-asa-5545 -
Session expired error(ISS , ASP related problem
We have one server which contain both ISS & WEB server ,on this server the database is running perfectly all right, also we are able to access the our site also (Named as UMPIRE ), but after few seconds , we get an error that the session is expired. Again when we refresh the page it start running. As per my knowledge, I think the session expire time given to the site is very less
Actually the web page is on ASP and ISS is installed on the server , i think some configuration setting is to be required for the ISS , after the installation
Can anybody help in this regard , what are the reason to get this error
Session expired
and whhat is the solution to remove this errorAnd just how does this forum's subject matter, SQL and PL/SQL, factor into your problem and question about ISS configuration?
-
Session expired error when creating dataset
Hi all,
I am using BI 11.1.1.6.
I am unable to create a specifically one data set where when I click on OK after giving in the query and dataset name, it says "session expired, please login again". I am able to create other datasets querying from the same schema and tables however this one specifically keeps failing with the same error.
Is this a bug or am I doing something wrong? The query is as shown below however please note that I am able to put in this query in sqldeveloper and even get data output.
Thank you.
SELECT
proj.project_title,
proj.project_name,
rqmt.application_no,
rqmt.amount_certified,
rqmt.period_to,
rqmt.prev_additions,
rqmt.prev_amount_cert,
rqmt.prev_deductions,
rqmt.sub_total_addtns,
rqmt.sub_total_ddctns,
rqmt.sum_to_date,
rqmt.total_additions,
rqmt.total_balance,
rqmt.total_deductions,
rqmt.total_prev_appl,
rqmt.contractor_claim_amount,
cnmt.document_number,
rqmt.orig_contrct_sum,
rqmt.contractor_commit_total_amount,
(select sum(this_period) + sum(PREV_APPLCATIONS) from rqdt where rqdt.parent_key = rqmt.master_key and RETENTION_LINE <>1)
FROM proj,
rqmt,
cnmt
WHERE ( proj.project_name = rqmt.project_name )
and ( rqmt.cntr_master_key = cnmt.master_key )
and (( cnmt.document_type = 'INITIALCONTRACTCOMMITMENT' ) )
AND rqmt.IT_IS_THE_LATEST = 1;hey there, sorry i did not but the error stopped after a few days, no idea why and how
-
Report Still Runs When Validation Errors Occur
Hello.
I'm using Apex 4.2.1 against Oracle 11gR2 and Oracle App Server (mod_plsql).
My Set-Up:
I created an application containing a "classical" type report that is driven by a WHERE clause. I also have two date fields in an HTML region on this same page. These fields are used in the report WHERE clause. And the report is run by clicking a GO button on the page.
Here's what the WHERE clause looks like:
where table_date >= to_date(nvl(:P1_BEGIN_DATE, '01-jan-1900'), 'dd-mon-yyyy') and table_date <= to_date(nvl(:P1_END_DATE, '31-dec-2300'), 'dd-mon-yyyy')This is designed so that, if any of the date fields are NULL, then the minimum or maximum date will be used for the query.
These date fields should always have a value when the report is run, and so, I created two after submit NOT NULL validations, one for each of the date fields. If any of these fields is NULL when the GO button is clicked, an error message appears in the notification area at the top of the page.
Looking at all this, you might realize (as I do) that the nvl() functions in the above WHERE clause are redundant. After all, the validations are supposed to prevent these date fields from becoming NULL when the report is run. In any case, this set-up does work ok and points out a strange behavior with Apex.
My Problem:
If any of these validations throws an error message, the report still runs. In previous versions of Apex, if a validation (or, for that matter, any error) is thrown, the report remains static. The report region does not disappear and the report is not invoked until the user corrects the error.
If both date fields are filled, I click the GO button and the report correctly returns, say, 100 rows. But when I empty both of the date fields and click GO, the validation errors appear and the report still runs, now returning the maximum number of rows, say, 1000.
What I've Tried:
I added a Branch-to-Page with condition "No Inline Validation Errors Displayed" so that the page branches back to itself only when no errors appear inline and I changed the validation error messages to appear inline. This has no effect.
And if I remove the nvl() functions from the above WHERE clause, then, when validation errors are thrown, the report data is replaced with the "No data found" message. All very disconcerting to my users.
Does anyone know why Apex reports are still run in presence of validation errors?
And how do I get around this behavior?
Thank you for any help.
ElieHi, Scott.
Thank you for your help/suggestions.
I like your first suggestion: creating a DA on the GO button that causes my report region to refresh only if both begin and end date fields are populated. And so, I tried doing this.
My DA looks like:
Event: Click
Type: Button
Button Name: P1_GO
Condition: - No Condition -
Action: Refresh
Fire When Event Result Is: True
Fire On Page Load: Checked
Selection Type: Region
Region Name: People Count
Event Scope: Static
Condition Type: PL/SQL Function Body Returning A Boolean
My PLSQL Code in Expression 1:
IF ( (:P1_BEGIN_DATE IS NOT NULL) AND (:P1_END_DATE IS NOT NULL) ) THEN
RETURN TRUE;
ELSE
RETURN FALSE;
END IF;My P1_GO button was automatically changed to "Controlled by Dynamic Action". And "Execute Validations" for this button is set to "Yes".
Unfortunately, this DA does not work. When both date fields are filled, clicking the GO button does not cause the report (nor anything else) to refresh. However, if I navigate to another application tab and then return back to my report page, I notice that the report does refresh at that point. But clicking the GO button has no effect.
And when either or both of the date fields is NULLed, clicking the GO button does not cause my validation error messages to appear.
By the way, I do agree with your comment about the NVL() functions. As I had mentioned in my original post, I also realize that, with my WHERE clause, checking for NULLs in my date fields is not needed. Still, if users fail to fill these date fields, then it would be useful to remind users that these fields should be populated. This is why having the validation checks are still needed despite my WHERE clause.
In any case, would you know what I am doing wrong here with this Dynamic Action?
Also, with respect to my first question, why is Apex causing my report to refresh when validaion errors have occurred? This did not occur prior to version 4.2.
Thank you very much for any further help/advice.
Elie -
"Could not deserialize session data" error during sign out
Hello,
I have an application deployed on WLS 8.1, one instance, no clustering. The application EAR contains 1 web module and 2 ejb modules. When I try to sign out(I use Single Sign-On for Multiple Applications - a sign out application deployed separately) I receive the attached error.
Notes: my session is serializable - I did a test that serialize and deserialize the session and I have no errors.
Q: Why does WLS try to deserialize the session data during sign out? I don't use any session persistance/replication.
The error ClassNotFoundException from my point of view is normal: UsersTableModel(from web modile) is not visible from the Application Classloader.
Here is the error:
<> <BEA-100028> <Could not deserialize session data.
java.lang.ClassNotFoundException: xxx.controller.actions.UsersTableModel: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
at weblogic.j2ee.ApplicationManager.loadClass(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.ClassLoader;Z)Ljava.lang.Class;(ApplicationManager.java:344)
at weblogic.j2ee.ApplicationManager.loadClass(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.ClassLoader;)Ljava.lang.Class;(ApplicationManager.java:258)
at weblogic.j2ee.ApplicationManager.loadClass(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Ljava.lang.Class;(ApplicationManager.java:253)
at weblogic.j2ee.ApplicationManager.loadClass(Ljava.lang.String;Ljava.lang.String;)Ljava.lang.Class;(ApplicationManager.java:216)
at weblogic.common.internal.WLObjectInputStream.resolveClass(Ljava.io.ObjectStreamClass;)Ljava.lang.Class;(WLObjectInputStream.java:48)
at java.io.ObjectInputStream.readNonProxyDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
at java.io.ObjectInputStream.readClassDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
at weblogic.servlet.internal.AttributeWrapper.convertBytesToObject([B)Ljava.lang.Object;(AttributeWrapper.java:173)
at weblogic.servlet.internal.AttributeWrapper.getObject(Z)Ljava.lang.Object;(AttributeWrapper.java:114)
at weblogic.servlet.internal.AttributeWrapper.getObject()Ljava.lang.Object;(AttributeWrapper.java:69)
at weblogic.servlet.internal.session.SessionData.removeAttribute(Ljava.lang.String;Z)Ljava.lang.Object;(SessionData.java:614)
at weblogic.servlet.internal.session.SessionData.removeAttribute(Ljava.lang.String;)V(SessionData.java:596)
at weblogic.servlet.internal.session.SessionData.remove()V(SessionData.java:808)
at weblogic.servlet.internal.session.MemorySessionContext.invalidateSession(Lweblogic.servlet.internal.session.SessionData;)Z(MemorySessionContext.java:69)
at weblogic.servlet.internal.session.SessionData.invalidate()V(SessionData.java:750)
at weblogic.servlet.security.ServletAuthentication.invalidateAll(Ljavax.servlet.http.HttpServletRequest;)Z(ServletAuthentication.java:184)
at xxx.framework.authentication.WebAuthenticationHelper.invalidateSessions(Ljavax.servlet.http.HttpServletRequest;)V(WebAuthenticationHelper.java:574)
at xxx.framework.authentication.WebAuthenticationHelper.closeSession(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(WebAuthenticationHelper.java:523)
at xxx.framework.authentication.WebAuthenticationHelper.logout(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(WebAuthenticationHelper.java:250)
at xxx.yyy.ViewDispatcher.process(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(ViewDispatcher.java:75)
at xxx.yyy.ViewDispatcher.doGet(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(ViewDispatcher.java:42)
at javax.servlet.http.HttpServlet.service(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(ServletStubImpl.java:996)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(ServletStubImpl.java:315)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava.lang.Object;(WebAppServletContext.java:6452)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(SecurityManager.java:118)
Edited by: user11291053 on 22-Jun-2009 02:52
Edited by: user11291053 on 22-Jun-2009 03:01
Edited by: user11291053 on 23-Jun-2009 01:42When OptimisticSerialization is turned on, WebLogic server does not serialize-deserialize context and request attributes upon getAttribute(name) when a request gets dispatched across servlet contexts. This means you will need to make sure that the attributes common to Web applications are scoped to a common parent classloader (they are application-scoped) or placed in the system classpath if the two Web applications do not belong to the same application.
When OptimisticSerialization is turned off (which is the default) WebLogic Server does serialize-deserialize context and request attributes upon getAttribute(name) to avoid the possibility of ClassCastExceptions. The value of OptimisticSerialization can also be overridden for specific Web applications by setting the optimistic-serialization value in weblogic.xml.
[http://edocs.bea.com/wls/docs100/ConsoleHelp/pagehelp/Corecoredomaindomainconfigwebapptitle.html]
[http://e-docs.bea.com/wls/docs90/webapp/weblogic_xml.html#1067857]
I hope this helps :) -
Reports not running in Infoview
I just migrated some reports from our Dev server to Test Server. The reports in Test Infoview do not run,. How ever I am able to run them in Crystal designer.
This did not happen in the past when ever I migrated the reports.
Any suggestions on what could be wrong? Using BO XI
The report in Infoview window keeps on running but does not even display the prompts for parameters. There is no error message, not sure whats going on.
Also I just noticed, there are other reports in different folder in Infoview which connect to a different Universe, If I try to run those reports from infoview, they can run. Onlt the ones that I migrated did not run.
Pls help.Hi,
Try this step; open the same report in crystal reports designer. Go to file menu-> page setup -> check the option u201CNo printeru201D. Save the report again back to the enterprise and then try and run the report.
Let me know if this works for you.
Thanks,
Kuldeep -
"Could not deserialize session data" error during shutdown WLS 6.0SP2
Hello all,
I get this Error ("Could not deserialize session data") when shutting down WLS
6.0 SP2.
I set the property 'PersistentStoreType' to 'memory' in weblogic.xml to use memory-based
storage for session data. So WLS should not try to serialize the session and save
it to disk (and I didn't find any files). I set a breakpoint in the writeObject()/readObject()
methods and realized that WLS calls writeObject on all in the session saved objects
and readObject directly afterwards. Here's the stackTrace:
ObjectOutputStream.writeObject()/ObjectOutputStream.readObject()
AttributeWrapper.getObject()
SessionData.removeAttribute()
SessionData.removeValue()
SessionData.remove()
MemorySessionContext.invalidateSession()
MemorySessionContext.shutDown()
WebAppServletContext.destroyServlets()
HttpServer.destroyServlets()
HttpServer.shutDown()
WebService.shutDown()
ServerServiceList.shutDown()
T3srvr.die()
T3srvr.waitForDeath()
T3srvr.run()
Server.main()
I do save some objects which are not Serializable in the session. I understand
that session data can be made persistent in a file/jdbc and then the objects must
be Serializable but not when saving the session data in memory.
Why is WLS trying to Serialize the Session Data and how can I switch it off ?
The Documentation says that it is allowed to store any object in the sessio, as
long as it is not persistet.
Thanks for your help,
Oliver
[weblogic.xml]
Hello Oliver & All-
Did anyone ever make any progress with this question, or come up with an answer?
I've found similar behavior when properly shuting down a WLS server with this command:
java -classpath $CLASSPATH weblogic.Admin -url t3://localhost:7001 -username <user>
-password <passwd> SHUTDOWN
TIA.
--oliver.
"Oliver Seiler" <[email protected]> wrote:
>
>Hello all,
>
>I get this Error ("Could not deserialize session data") when shutting down
>WLS
>6.0 SP2.
>I set the property 'PersistentStoreType' to 'memory' in weblogic.xml to
>use memory-based
>storage for session data. So WLS should not try to serialize the session
>and save
>it to disk (and I didn't find any files). I set a breakpoint in the writeObject()/readObject()
>methods and realized that WLS calls writeObject on all in the session saved
>objects
>and readObject directly afterwards. Here's the stackTrace:
>
>ObjectOutputStream.writeObject()/ObjectOutputStream.readObject()
>AttributeWrapper.getObject()
>SessionData.removeAttribute()
>SessionData.removeValue()
>SessionData.remove()
>MemorySessionContext.invalidateSession()
>MemorySessionContext.shutDown()
>WebAppServletContext.destroyServlets()
>HttpServer.destroyServlets()
>HttpServer.shutDown()
>WebService.shutDown()
>ServerServiceList.shutDown()
>T3srvr.die()
>T3srvr.waitForDeath()
>T3srvr.run()
>Server.main()
>
>I do save some objects which are not Serializable in the session. I understand
>that session data can be made persistent in a file/jdbc and then the objects
>must
>be Serializable but not when saving the session data in memory.
>Why is WLS trying to Serialize the Session Data and how can I switch it
>off ?
>The Documentation says that it is allowed to store any object in the sessio,
>as
>long as it is not persistet.
>
>Thanks for your help,
> Oliver
>
Maybe you are looking for
-
I have two servers. One is for databases (DB) with the mail server configured and the other is for SSIS without mail server. Both servers are in the same network. On the SSIS server the SSIS package exports data from the DB server table to xls file.
-
Qty in MIGO of Input material should not be editable
Dear All, While making GR for subcontract PO we are entering GR qty for output materials but system is also allowing to change Input material qty (543 Mov type) and we need to restrct the same i.e. to make uneditable. Pl suggest. Regards, Vimlesh
-
Transporting standard table from DEV to PROD
Hi All, I have updated a table called T166K and T166P for Purchase Order Printouts. I have entered few values in the above mentioned tables in DEV server. Now, i would like to move these tables to Production, since i can not create values to these ta
-
My ipod touch is locked up and non-responsive
I have tried to reset by holding lock and power buttons at the same time with no success. I have a white screen and the ipod is non-responsive to anything.
-
Hi, How to change the navigation in swing appplication from tab key to enter key. Its the user requirement that i need to under go. and also tell me how to myownfocus traversal. Thanks in advance.