Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Intelligence (Analytics)
The viewing session not available ...
skorc
Hi all,
I searched the forum found some help but not enough.
My problem is that when I run a report from the server it works when I try to run it from another computer i get an error message (see attachement).
Any ideas?
(using Eclipse 2.5M7 all-in-one and runtime 2.5M7)
Thank you, Zoran
Find more posts tagged with
Comments
mwilliams
Hi Zoran,
Is this using IE? If so, does it work if you use Firefox? Also, I see you're using frameset in your URL. What happens if you use run or preview? Do you get the same result?
mwilliams
Zoran,<br />
<br />
Also, this may be the thread that you saw previously, but maybe there's something valuable you can pick up out of this if you haven't seen it.<br />
<br />
<a class='bbc_url' href='
http://www.birt-exchange.org/forum/deploying-integrating-birt-report-engine-applications/14911-using-birt-flex.html'>http://www.birt-exchange.org/forum/deploying-integrating-birt-report-engine-applications/14911-using-birt-flex.html</a>
;
skorc
Hi
It works with Mozilla but not with IE7.
When I run it with run instead of frameset I get the following error:
java.lang.IllegalStateException: The viewing session is not available or has expired.
at org.eclipse.birt.report.service.ReportEngineService.createRunAndRenderTask(ReportEngineService.java:994)
at org.eclipse.birt.report.service.ReportEngineService.runAndRenderReport(ReportEngineService.java:853)
at org.eclipse.birt.report.service.BirtViewerReportService.runAndRenderReport(BirtViewerReportService.java:973)
at org.eclipse.birt.report.service.actionhandler.BirtGetPageAllActionHandler.__execute(BirtGetPageAllActionHandler.java:131)
at org.eclipse.birt.report.service.actionhandler.AbstractBaseActionHandler.execute(AbstractBaseActionHandler.java:90)
at org.eclipse.birt.report.soapengine.processor.AbstractBaseDocumentProcessor.__executeAction(AbstractBaseDocumentProcessor.java:47)
at org.eclipse.birt.report.soapengine.processor.AbstractBaseComponentProcessor.executeAction(AbstractBaseComponentProcessor.java:143)
at org.eclipse.birt.report.soapengine.processor.BirtDocumentProcessor.handleGetPageAll(BirtDocumentProcessor.java:183)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.birt.report.soapengine.processor.AbstractBaseComponentProcessor.process(AbstractBaseComponentProcessor.java:112)
at org.eclipse.birt.report.soapengine.endpoint.BirtSoapBindingImpl.getUpdatedObjects(BirtSoapBindingImpl.java:66)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet.doPost(BirtSoapMessageDispatcherServlet.java:265)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet.service(BirtSoapMessageDispatcherServlet.java:122)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.eclipse.birt.report.filter.ViewerFilter.doFilter(ViewerFilter.java:68)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
wagner1845
Hello.
I had the same problem. After explicitly adding the servers IP address to the intranet-zone of IE the problem disappeared.
Regards,
Christian
anir
Searched extensively everywhere with no significant success. This is listed down as a bug. We recently switched to 2.5 (from 2.2) for leveraging the new features and started facing this error (java.lang.IllegalStateException: The viewing session is not available or has expired). Rolling back to 2.2 will be certainly taking a foot backward.
So is there any workaround/fix to temporarily solve this problem until this bug is resolved?
Thanks
anir
I am getting this error on deploying my reports on tomcat.
Birt version used - 2.5.1
As a workaround I am just refreshing the page once on load and the problem seems to disappear. This is just a fix for the bug. Would love to hear more on this bug from more senior members.
Thanks
P.S. : I like the way the senior members help us here, first by hand-holding and then by leaving us on our own to fly
henryh
<blockquote class='ipsBlockquote' data-author="anir"><p>Searched extensively everywhere with no significant success. This is listed down as a bug. We recently switched to 2.5 (from 2.2) for leveraging the new features and started facing this error (java.lang.IllegalStateException: The viewing session is not available or has expired). Rolling back to 2.2 will be certainly taking a foot backward.<br /></p></blockquote>
<br />
I have a similar error to Anir's. I upgraded from 2.3.1 BIRT Runtime Viewer to 2.5.1 and now all my reports, including ones that I created in 2.5.1 designer runs into the problem in the framset mode. However, when I put it in the run mode with output to PDF, the PDF generates.<br />
<br />
Does anyone have an idea whether this is a bug or some configuration/installation differences between 2.3.1 and 2.5.1 BIRT Runtime Viewer?<br />
<br />
Thanks.
henryh
<blockquote class='ipsBlockquote' data-author="henryh"><p>I have a similar error to Anir's. I upgraded from 2.3.1 BIRT Runtime Viewer to 2.5.1 and now all my reports, including ones that I created in 2.5.1 designer runs into the problem in the framset mode. However, when I put it in the run mode with output to PDF, the PDF generates.<br />
<br />
Does anyone have an idea whether this is a bug or some configuration/installation differences between 2.3.1 and 2.5.1 BIRT Runtime Viewer?<br /></p></blockquote>
<br />
I think I found the problem. My directory was named "birt-viewer". For some reason, 2.5.1 doesn't like the dash "-". Simply deleting the cookie related to the server didn't help. This is what you should do to solve the problem:<br />
<br />
1) shutdown Tomcat or whatever your webserver.<br />
2) rename the directory so there is no dash. I renamed mine to "birt_viewer" (underscore is OK).<br />
3) restart Tomcat / webserver<br />
<br />
Hope that helps you!
Rob77
Hello,
unfortunately that's not my case. I have this problem since first Birt installation - when run report for the first time (frameset) it goes fine. Then when I wait (no action) for a few minutes, select "Report parameters" and re-run report, it would display "The viewing session is not available[...]". I can press F5 (refresh page in Firefox) then, reselect parameters and click ok and the report would run just fine.
My Birt directory has name birt2, so there's no point in removing dash from it.
Birt version: 2.3.2
Haven't found solution to that, only abovementioned workaround.
The issue was present on Firefox, not present on Google Chrome.
I've changed the following settings in Firefox about:config:
network.cookie.alwaysAcceptSessionCookies
to true. It appears that it helped.
Regards,
Robert
Rob77
Hello,
let me repeat what I've sain on other thread:
Hello,
unfortunately that's not my case. I have this problem since first Birt installation - when run report for the first time (frameset) it goes fine. Then when I wait (no action) for a few minutes, select "Report parameters" and re-run report, it would display "The viewing session is not available[...]". I can press F5 (refresh page in Firefox) then, reselect parameters and click ok and the report would run just fine.
My Birt directory has name birt2, so there's no point in removing dash from it.
Birt version: 2.3.2
Haven't found solution to that, only abovementioned workaround.
Regards,
Robert
Rob77
The issue was present on Firefox, not present on Google Chrome.
I've changed the following settings in Firefox about:config:
network.cookie.alwaysAcceptSessionCookies
to true. It appears that it helped.
Regards,
Robert
henryh
<blockquote class='ipsBlockquote' data-author="Rob77"><p>Hello,<br />
unfortunately that's not my case. I have this problem since first Birt installation - when run report for the first time (frameset) it goes fine. Then when I wait (no action) for a few minutes, select "Report parameters" and re-run report, it would display "The viewing session is not available[...]". I can press F5 (refresh page in Firefox) then, reselect parameters and click ok and the report would run just fine.<br />
My Birt directory has name birt2, so there's no point in removing dash from it.<br />
Birt version: 2.3.2<br />
Haven't found solution to that, only abovementioned workaround.<br />
<br />
<br />
The issue was present on Firefox, not present on Google Chrome.<br />
I've changed the following settings in Firefox about:config:<br />
network.cookie.alwaysAcceptSessionCookies<br />
to true. It appears that it helped.<br />
Regards,<br />
Robert</p></blockquote>
<br />
Here is another possibility. In the 2.5.1 Sample Viewer, there is this configuration option in: WEB-INFviewer.properties <br />
<br />
# [VIEWING SESSION CONFIGURATION]<br />
# The BIRT viewing session is a sub-session of the HTTP session.<br />
# An HTTP session can have multiple BIRT viewing sessions.<br />
# Each time a new viewer is opened, a new viewing session is created. <br />
# The following parameters are used to configure the viewing session<br />
# management.<br />
# If the matching HTTP session expires, all the viewing sessions<br />
# attached to it will expire as well.<br />
<br />
# Timeout value in seconds after which a viewing session will expire.<br />
# The value 0 means that a session will never expire, and the cached files<br />
# will never be cleant unless the belonging HTTP session expires.<br />
viewer.session.timeout=1800<br />
<br />
Maybe a larger number will help you too?
Rob77
My reply seems to be too fast.
Changing the Firefox preference helped a bit, but the problem persisted. I only _feel_ that it takes longer to trigger the error.
As for the recommended setting - in my case it is set to 0, which should (according to the description) keep the session forever.
Currently I still guess it is browser related issue.
Regards,
Robert
henryh
Rob77,
Just wanted to let you know that I only found the setting in the 2.5.1 version, so it may or may not work in the 2.3.2 viewer version.
kevin23_hy
i got solved that not set browers cookie and rename the directory but is that use birt2.5viewer to overide birt.2.3.x is can work correctly.
henryh
<blockquote class='ipsBlockquote' data-author="kevin23_hy"><p>i got solved that not set browers cookie and rename the directory but is that use birt2.5viewer to overide birt.2.3.x is can work correctly.</p></blockquote>
Kevin,<br />
I don't understand your question...
SrinivasaRao
<blockquote class='ipsBlockquote' data-author="mwilliams"><p>Hi Zoran,<br />
<br />
Is this using IE? If so, does it work if you use Firefox? Also, I see you're using frameset in your URL. What happens if you use run or preview? Do you get the same result?</p></blockquote>
<br />
Hi,<br />
<br />
I am also facing the same problem.<br />
<br />
if iam using the run or preview report running successfully without any errors.But that doesn't have the export options.<br />
<br />
I need report export options in my report.So i need to use frameset only.<br />
How can i solve this problem. <br />
<br />
Please help me to solve this problem.
areh
I got the same error message, and these are my two fixes:
I am developing a small web application that runs a report in an HTML iframe tag. This webapp was deployed on a local OC4J standalone container, while the Birt example report viewer was deployed on a local Tomcat server. When I deployed both applications to the same Tomcat installation it worked.
But not quite
It worked with Goggle Chrome and Firefox, but I still got the same error message in Internet Explorer 8. Luckily, all that was necessary was to let Internet Explorer accept all cookies.
(Windows XP, Tomcat 5.5, Internet Explorer 8, Birt Viewer version 2.5.1, Birt Engine version 2.5.1, JRE version 1.6.0_18)
Mudor
If you are using Tomcat 5.5 or above, you can edit TOMCAT_HOMEconfweb.xml and change the session-timeout (expressed in minutes):
<session-config>
<session-timeout>30</session-timeout>
</session-config>
It worked for me. (birt-viewer 2.5.0, Tomcat 6.0.20)
