RDS 2008 R2 Internet explorer auto log out after 20 seconds IE9

I have Windows RDS (remote Desktop services) 2008 r2 running (2 Gateway servers, 1 Session host, and 1 licence\broker server) and it has been working fine for past several months. Currently whenever a user launches an app that is internet biased or try
to browse the web, if it is the first app they are lunching from either the RDS webpage or from the RDS feed on their box it will log the user out after 20 seconds (according to event viewer). I have no clue why it is doing this, please help. Not sure what
other information to include
RDS 2008 R2 Internet Explorer

Hi,
Thank you for posting in Windows Server Forum.
Which latest update you have installed on your server?
Does this issue occurs for all users?
In meantime, please try to reboot server once if possible and check whether your issue getting resolved. In addition you can try enhanced security configuration which might work for your case.
Internet Explorer: Enhanced Security Configuration
http://technet.microsoft.com/en-us/library/dd883248(v=ws.10).aspx
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

Screen sharing log out after 10 seconds

I am able to establish screen sharing and video chat between two mac via messages, but am quickly logged out with an error message that there has been no data transfer for ten seconds. Then I am prompted to send a report to Apple.
Is this a glitch in messages, or am I neglecting something? Both macs are running the latest system software and have no problem connecting via facetime.
Thanks for any help!

From the Messages menu bar, select
Video ▹ Connection Doctor
In the window that opens, select
Show: Capabilities
There should be a checkmark on the line with the words "1-on-1 video chat." Select
Show: Network Status
You should have two green dots.
Make sure that you and the other party meet the applicable requirements shown in these support articles:
Share your screen
Requirements for audio chats, video chats, and screen sharing
See also:
Fix video chat issues

Auto log out issue

Since upgrading to Maverick, my iMac has started to log out after about 15-20 minutes of inactivity. The energy settings are 1hr computer sleep and 10min display sleep. And I have tried both unchecking the auto log out in “Advanced” Security & Privacy, and checking the box and setting it to 360min. Also tried deleting a couple of the Library/Preferences files that have been suggested before.
The computer first goes to screen saver at 10min, it can be awakened to the desktop, but if you leave it inactive for 15-20 min it will first go to the screen saver, then log out after another 5-10 min to the login screen. The apps that were open will re-open when you log back in.
iMac 2.66 Core 2 Duo(early 2008), 4 GB SDRAM(early 2008), OS X 10.9.1

I would like to add to this issue, just noticed that even though the screen saver is now set to 15 min, the display goes to screen saver at ~5 min. The clock in the upper right corner shows the correct time.

Internet Explorer begins blocking out-of-date ActiveX controls

On Wednesday 6th August 2014, we announced that as part of our ongoing commitment to delivering a more secure browser, starting September 9th Internet Explorer will block out-of-date ActiveX controls. (Note: The original post stated that the ActiveX blocking
would begin on August 12th. Please refer to the addendum for further details).
Please take a look at this important update via the
blog post as well as the FAQ contained therein and commence testing within your domain.
Thanks and Regards
Mark
http://blogs.msdn.com/b/ie/archive/2014/08/06/internet-explorer-begins-blocking-out-of-date-activex-controls.aspx
Mark Feetham Senior Supportability Program Manager, Internet Explorer.

Hello,
There seems to be an entry missing in the
versionlist.xml file.
There is an entry missing for wsdetect.dll (isInstalled Class ActiveX Control) from Java 1.7, I believe (there is an entry for 1.6, 1.5, 1.4 but 1.7 is missing).
Here is the relevant portion of the XML file:
<blocklistentry key="{5852f5ed-8bf4-11d4-a245-0080c6f74284}" entrytype="2">
<versionentries numberofelements="4">
<versionentry groupname="Java(TM) 1.6.0_81" filename="wsdetect.dll" productversion="6.0.810.0-6.65535.65535.65535" fileversion="6.0.810.0-6.65535.65535.65535" />
<versionentry groupname="Java(TM) 1.5.0_71" filename="JavaWebStart.dll" productversion="5.0.710.0-5.65535.65535.65535" fileversion="5.0.710.0-5.65535.65535.65535" />
<versionentry groupname="Java(TM) 1.4.2_43" filename="JavaWebStart.dll" productversion="1.4.2.430-1.4.65535.65535.65535" fileversion="1.4.2.430-1.4.65535.65535.65535" />
<versionentry groupname="Java(TM)" filename="*" productversion="*" fileversion="*" />
</versionentries>
This causes the alert prompt to appear when using Java 1.7 update 67 even though it's allowed by XML.
To reproduce, please go to a site that uses wsdetect.dll like Wikipedia (like here
http://commons.wikimedia.org/wiki/File:Example.ogg) and check if the prompt appears for you.

Auto log out from xbox :S in lumia 1520

Auto log out from Xbox account in my 1520 every time I restart the mob and join any game .. Need your Xbox
Website I do use remember me and nothing happens . That is happens with all websites I use
A.A
Solved!
Go to Solution.

hi mate, have you checked you are up to date with latest firmware and all latest Nokia system app updates from the Store? also try performing a soft reset and double checking that everything is ok with your Microsoft account online.

Guest account and auto log out

I will be using Snow Leopard machines in a computer lab with guest accounts. However, I've read that when the idle timer ticks over, the dialog box confirming the Guest account's files will be deleted comes up and does not time out (like a normal account would).
So the machines never auto log out. In an environment where most users don't log off to protect their privacy, this is an annoying problem.
Is this still an issue? Is there a way to turn off that dialog box confirming logout? Or some other way to get my Guests to auto log off?
Thanks.

it would actually be pretty easy to create a automator script that runs a bash script like "sudo exit" which would then prompt for the password of a admin.
i also did a quick google search and found these:
http://hintsforums.macworld.com/showthread.php?t=89181
and
http://hints.macworld.com/article.php?story=20050216114450735
the second one will probably be more helpful but hopefully this little nudge will help out.

I want to disable auto log-out

I have a Mac Air OS 10.9.5. Normally, when I it is either idle for a time or I close the computer, it goes into sleep mode (but it does NOT quit all applications and log out) and requires a password to use it again -- that's the way I want it.
But sometimes, it when it goes idle or I shut it, it logs out or there is a count-down to logging out that I need to cancel when I come back in. Although I DO want to have to key in my password, I don't want to have to log back in because when it logs out, it quits all my applications.
How do I retain the password function while disabling the auto-log-out function?

From the menu bar, select
 ▹ System Preferences... ▹ Security & Privacy
If there's a closed padlock icon in the lower left corner of the preference pane, click it and enter your login password when prompted.
Click the Advanced button and, in the sheet that opens, uncheck the box marked
Log out after … minutes of inactivity

How do I keep myself active so I don't get auto-logged out?

Hi,
My wife & I have a computer that we share with our young kids. They each have their own account with Parental Controls turned on and time limits and it all works well with one exception. When they run out of time, their programs (often resource-intensive Safari) stay open and using CPU and memory and making the computer run slowly. We want to try setting the Security preference to log out after X minutes of inactivity, but we don't want the account we use to be auto-logged out.
My thought was that maybe there is a simple piece of software that could do something every few minutes that would keep her account active. Thinking about it now, I'll bet there are a lot of users who have the opposite problem - they want to be logged out when they are inactive, but something is keeping them active!
Anyway, does anyone know of a simple program that will keep her active so she doesn't seem to be inactive even when she is so we can 'trick' the Mac into thinking she never goes inactive? Then we can set the preference to log out inactive users, thus fixing the problem of our kids' programs running even after they've used up their time for the day.
Or maybe there is another solution to this problem. Any thoughts?
TIA,
Thad

Mac OS X is a multi-User system. Settings for Parental Controls are on a per-User basis.
Parental Controls do not apply to your Account, unless you set your account to have some Parental Controls as well.

Auto log out

I am not sure why this is happening but it seems in the last couple weeks, my PB will log out after a period of inactivity. It's only happened a couple times, and I haven't sat around to determine the sequence of events. I just leave the computer alone (normally, I close the lid when I am not around it) for a half hour or so, come back, and the log in screen is there.
It's only a minor glitch, but I can't find a setting that seems like it would stop the computer from logging out automatically...
Thanks!
ez
PowerBook G4 15in 1.67 GHz / eMac (original) Mac OS X (10.4.6) 1 GB RAM; Airport; Photoshop; iPod 5th Gen (black)

Open the Security pane of System Preferences and uncheck the box that logs you out after a period of inactivity.
(13177)

Auto log out fails to paint screen with login options

With Lion, my computer is set to log out after x minutes of inactivity. When I move the mouse or press a key to display the screen, the screen continues to display my desktop as it existed with open applications except that the desktop is non-responsive. Movement of the mouse incrementally repaints the screen to display the real active screen which is the login dialog. If you move the mouse enough you eventuall see the login icons so that you can log in again.

See this link:
Last post
http://www.mactalk.com.au/11/105092-lion-login-screen-wants-me-paint-back-togeth er.html
Hope it works!

Automatic log out after 60 min inactivity

Is it possible to increase time for the system log out after inactivity of 60 minutes?
In other cloud solutions it is possible via adapt mode to change it
(15 min, 25 min, 1 hour, 2 hours, 4 hours)
Thanks in advance,
André

Hi Angi,
thanks a lot. It is working fine.
Regards,
André

When "Log out after X minutes of inactivity" is on, display gets black and a weird pixelation when I move the mouse

When "Log out after X minutes of inactivity" is on, and those X minutes pass by, my MBA logs out. After that, when I want to use it again, I found that display is totally black and if I use the touchpad, then I can start seeing "what is behind" that black screen (Login Window), like you can see on the picture:
I took it to Tech Service and they didnt find out any hardware issue. Any ideas?

I recently found out that this only happens when DISPLAY is set to go to sleep minutes before the "Log out after X minutes of inactivity". I had "Display sleep" option set to 5 minutes and "Log out after 10 minutes of inactivity" and this causes the display to go to sleep first (screen goes black) and then, 5 minutes later, it logs out.
If "Display sleep" is off and "Log out after X minutes of inactivity" is on, the issue does not replicate. So Im thinking it has something to do with the screen being black at the moment it logs out. Can you try and replicate that?
I will be checking the thread you suggested and hopefully oudgrad1764 can find a solution. Thanks a lot.

I just upgraded to Mavericks and find that I'm being logged out after 15 mins even though I have set security

I just upgraded my IMac to OS X MAVERICKS and find that I'm being prematurely logged out after 15 mins of inactivity even though my Privacy & Security settings are set to 1 hour. Any suggestions on how to correct this problem?

I just upgraded my IMac to OS X MAVERICKS and find that I'm being prematurely logged out after 15 mins of inactivity even though my Privacy & Security settings are set to 1 hour. Any suggestions on how to correct this problem?

I have connected an AirPlay enabled device to iphone4s. I started palying songs. I was able to access internet through 3G from iphone.After few seconds 3G symbol disappears and WiFi symbol appears. After that I'm not able to access internet. Why is it so?

I have connected an AirPlay enabled device to iphone4s. I started palying songs. I was able to access internet through 3G from iphone.After few seconds 3G symbol disappears and WiFi symbol appears. After that I'm not able to access internet. Why is it so?

SMS. Deggie, had them check that. After a lengthy discussion with Senior Tech advisor, it appears it is iMessage/Face Time server (they are the same) issue, which will strong arm those into purchasing Data if they use iMessage over multiple devices, as the server registers the phone number associated with apple ID. Not impressed. I put what I've learned here in a simliar thread
https://discussions.apple.com/message/17416082#17416082
and this is what I've put in apple.com/feedback
"iMessage requires internet. SMS does not. iMessage/FaceTime auto logs phone numbers to the iMessage/Facetime server (it's the same server as I've come to learn), this means that when iMessage/Face Time is turned on anyone sending a message through the server to me will only be sent as an iMessage- not when I'm not connected to internet, meaning I will not receive the message as an SMS by default, when I have another device using iMessage (such as MacBook) logged in.
This feature is a problem for me, bottom line, in that iMessage strong arms the consumer (me) into having to buy a data plan that they either do not want, or do not need."

The transaction is no longer active - Transaction timed out after 30 second

We have an intermittent error here, and I'm a rookie. The error results in a 500 being sent to the customer every 10th-20th POST and only occurs under heavy load. The heavy loading is over the for the day, but it'll be back.
My first suspicion was the app code doing transaction work and having database performance problems. But the app is non-transactional and the database is fine. The server farm nodes (4) are all experiencing the problems at equal rates, and the other apps on the farm are fine, so it appears to be app-specific rather than rooted in server state or database state.
I looked at the stack a little more closely and it appears to be some kind of internal persistence issue, but a completely foreign one to me. We have no Persistent Stores configured, so I don't know where to even start on this puppy.
EJB Exception occurred during invocation from home: weblogic.ejb.container.internal.StatelessEJBLocalHomeImpl@d1e1f4 threw exception: <1.0.0 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds
BEA1-32AE928C966AC66F424D]'. No further JDBC access is allowed within this transaction.
<1.0.0 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds
BEA1-32AE928C966AC66F424D]'. No further JDBC access is allowed within this transaction.
at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:3784)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:97)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:83)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:59)
at org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.handleCheckedException(SelectResultObjectProvider.java:155)
at org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:40)
at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1219)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:987)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:839)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:770)
at kodo.kernel.KodoQuery.execute(KodoQuery.java:47)
at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:525)
at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:229)
at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:269)
at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactionsExcludingApplication(ApproveApplicationHelper.java:167)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactions(ApproveApplicationHelper.java:129)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.stageAction(ApproveApplicationHelper.java:74)
at com.company.buapp.buslogic.session.ApproveApplicationSessionBean.performAction(ApproveApplicationSessionBean.java:348)
at sun.reflect.GeneratedMethodAccessor2150.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:281)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:187)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:154)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at weblogic.ejb.container.injection.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:68)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
at $Proxy365.performAction(Unknown Source)
at com.company.buapp.buslogic.session.ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.performAction(ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.java:148)
at com.company.buapp.si.ApplicationWS.performAction(ApplicationWS.java:114)
at sun.reflect.GeneratedMethodAccessor2149.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:50)
at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:42)
at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:247)
at com.sun.xml.ws.server.sei.SEIInvokerPipe.process(SEIInvokerPipe.java:97)
at weblogic.wsee.jaxws.MonitoringPipe.process(MonitoringPipe.java:98)
at com.sun.xml.ws.protocol.soap.ServerMUPipe.process(ServerMUPipe.java:62)
at com.sun.xml.ws.server.WSEndpointImpl$1.process(WSEndpointImpl.java:139)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:153)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:235)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:97)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:36)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:218)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
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:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds
BEA1-32AE928C966AC66F424D]'. No further JDBC access is allowed within this transaction.
at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:178)
at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:188)
at weblogic.jdbc.wrapper.ResultSet.preInvocationHandler(ResultSet.java:57)
at weblogic.jdbc.wrapper.ResultSet_oracle_jdbc_driver_OracleResultSetImpl.next(Unknown Source)
at org.apache.openjpa.lib.jdbc.DelegatingResultSet.next(DelegatingResultSet.java:106)
at org.apache.openjpa.jdbc.sql.ResultSetResult.nextInternal(ResultSetResult.java:210)
at org.apache.openjpa.jdbc.sql.SelectImpl$SelectResult.nextInternal(SelectImpl.java:2209)
at org.apache.openjpa.jdbc.sql.AbstractResult.next(AbstractResult.java:168)
at org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.next(SelectResultObjectProvider.java:99)
at org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:35)
at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1219)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:987)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:839)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:770)
at kodo.kernel.KodoQuery.execute(KodoQuery.java:47)
at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:525)
at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:229)
at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:269)
at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactionsExcludingApplication(ApproveApplicationHelper.java:167)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactions(ApproveApplicationHelper.java:129)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.stageAction(ApproveApplicationHelper.java:74)
at com.company.buapp.buslogic.session.ApproveApplicationSessionBean.performAction(ApproveApplicationSessionBean.java:348)
at sun.reflect.GeneratedMethodAccessor2150.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:281)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:187)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:154)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at weblogic.ejb.container.injection.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:68)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
at $Proxy365.performAction(Unknown Source)
at com.company.buapp.buslogic.session.ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.performAction(ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.java:148)
at com.company.buapp.si.ApplicationWS.performAction(ApplicationWS.java:114)
at sun.reflect.GeneratedMethodAccessor2149.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:50)
at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:42)
at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:247)
at com.sun.xml.ws.server.sei.SEIInvokerPipe.process(SEIInvokerPipe.java:97)
at weblogic.wsee.jaxws.MonitoringPipe.process(MonitoringPipe.java:98)
at com.sun.xml.ws.protocol.soap.ServerMUPipe.process(ServerMUPipe.java:62)
at com.sun.xml.ws.server.WSEndpointImpl$1.process(WSEndpointImpl.java:139)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:153)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:235)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:97)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:36)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:218)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
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:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

This was actually my first conclusion as well. But when I went to the Data Source for this connection, I found it's a non-transactional driver. That's what made me go back and give the trace a second look. I don't see any references to the Data Source in question. It's OpenJPA stuff and Session persistence stuff.Non-XA drivers can still participate in an XA transaction via a variety of JDBC data source options - for example, labeled "1PC" and "LLR" on the console. (If you want to understand the particulars search for "JTS" or "LLR" in the JDBC edocs).
You seem to be suggesting maybe the setting can be made in a config doc, possibly of the app itself, right? Right. EJBs have a transaction-timeout attribute.
As opposed to setting it in the console. WebLogic has a domain wide default transaction-timeout setting that can be set on the console, but I tend not to recommend using it. In addition, there's something called a "deployment plan" which can be used to override some of the common EJB attributes via configuration, but I'm not personally familiar with its usage.
But isn't the setting vapor if we're using a nonXA driver?No.
I wonder if this thing couldn't be telling me it's waiting on the persistence subsystem to come available to store simple session data? Sometimes the problem is that there are periodic app requests that are more complex/larger than others. Sometimes the system is simply overloaded, and takes 30 seconds to honor a request that might normally take 10 seconds.
That other app is all about persistence. What if app2 is sucking some persistence subsystem dry and app 1 is waiting just to store session data? Could be.
If the nonXA thing really does kill the quick timeout workaround, how could I health-check the persistence subsystem?Don't know. At a wild guess I'd check for CPU's at 100% on all involved serves, and examine database stats.

RDS 2008 R2 Internet explorer auto log out after 20 seconds IE9

Similar Messages

Maybe you are looking for