I got this error in the log while working with an XPage today.
CLFAD0111W: The PropertyMap was in an invalid state. evaluateValueBindings was enabled but not disabled before the saveState phase.
Anybody know what it means?
This is from the log
<CommonBaseEvent creationTime="2013-02-05T14:22:52.738+01:00" globalInstanceId="ELc0a85e0a00013ca95661f6000000ca" msg="CLFAD0111W: The PropertyMap was in an invalid state. evaluateValueBindings was enabled but not disabled before the saveState phase." severity="30" version="1.0.1">
<extendedDataElements name="CommonBaseEventLogRecord:level" type="noValue">
<children name="CommonBaseEventLogRecord:name" type="string">
<values>VARNING</values>
</children>
</extendedDataElements>
<extendedDataElements name="CommonBaseEventLogRecord:sourceClassName" type="string">
<values>com.ibm.xsp.binding.PropertyMap</values>
</extendedDataElements>
<extendedDataElements name="CommonBaseEventLogRecord:sourceMethodName" type="string">
<values>saveRoot</values>
</extendedDataElements>
<sourceComponentId component="Expeditor 6.2" componentIdType="ProductName" instanceId="" location="qner" locationType="Hostname" subComponent="" threadId="18" componentType="http://www.w3.org/2001/XMLSchema-instance"/>
<situation categoryName="ReportSituation">
<situationType xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ReportSituation" reasoningScope="INTERNAL" reportCategory="LOG"/>
</situation>
The error refers to something going wrong during a saveRoot of the UI serializer API.
You will need to generate HTTP thread logs and match them to when the error occurred to see what XPage is causing the issue.
Here is the related tech note on how to do that.
http://www-01.ibm.com/support/docview.wss?uid=swg27003598
I'd also recommend having DEBUG_THREADID=1 set so you can map threads in the console logs.
Thanks everybody for the help.
After alot of trouble shooting I found the cause of the error.
a faulty function that should do a JS Client reload for old Domino forms and a panel refresh on XPages. But in this case both where preformed, that caused the problem.
Related
Describe the bug
im facing the issue after the server to getting the clientsecret successfully after that i'm setup the stripe code then i click to hit the request of stripe payment getting I'm showing the platform exception i'm already update mainactivity.kt file fluttteractvity to fragment
below im paste the my issue which one showing into log please check and help me how to fix
PlatformException(flutter_stripe initialization failed, The plugin failed to initialize: Your theme isn't set to use Theme.AppCompat or Theme.MaterialComponents. Please check the README: https://github.com/flutter-stripe/flutter_stripe#android, null, null)
I think You are using
<style name="LaunchTheme" parent="#android:style/Theme.AppCompat.Light.NoTitleBar">
And it should be:
<style name="LaunchTheme" parent="Theme.AppCompat.Light.NoActionBar">
or just, copy and paste all the file in style.xml
https://github.com/flutter-stripe/flutter_stripe/blob/main/example/android/app/src/main/res/values/styles.xml
Please add this to your both style file.
/android/app/src/main/res/values/styles.xml
2./android/app/src/main/res/values-night/styles.xml
#drawable/launch_background
true
?android:colorBackground
First of all thanks to Paul S Withers for his work:
https://openntf.org/main.nsf/project.xsp?r=project/XPages%20OpenLog%20Logger
I would like to use his logger (v8.0), but after some tests, I have to deal with one strange behaviour concerning the error document reference.
Here an example:
After logging an error or event including a doc reference e.g.:
OpenLogUtil.logEvent(new Throwable(), "This is a Java message with Doc", Level.INFO, doc);
all following logging calls - without an explicit doc parameter - now referencing the document of the prior call, e.g.:
openLogBean.addError(e, this);
OpenLogUtil.logError(e);
etc...
OpenLog Database - Entries:
UPDATE:
If you are logging from two different databases, the logging will crash with the following exceptions:
HTTP JVM: XOL_DEBUG error: Notes error 4091: Invalid universal id
HTTP JVM: XOL_DEBUG error trace: NotesException: Invalid universal id
HTTP JVM: XOL_DEBUG error trace: NotesException: Object has been removed or recycled
Thanks in advance for any help
Mea culpa, it's re-using the same OpenLogItem. I suspect, because it's scoped to the session, the 4091 error will occur. Please try this version https://openntf.org/main.nsf/project.xsp?r=project/XPages%20OpenLog%20Logger/releases/94080D45393E3DC88525835100495C88
Did some research on this and found a few posts regarding people facing the same issue in their application. I too am facing this crash in the google console for my app and followed the posts I found (java.lang.ClassNotFoundException dalvik.system.BaseDexClassLoader.findClass) and similar others. All of these suggest to follow steps mentioned on the link, https://developer.android.com/studio/build/multidex.html.
Followed all the workarounds mentioned on the page but still getting the same issue. MinSdkVersion for my app is 15 and thus added all workarounds to get rid of this but no luck as of yet.
I am left with the option to change the minimum sdk version to 21 as mentioned int he documentation, but that would affect me big time. *
I am getting this issue on Android 5.1 and lower versions only.
java.lang.RuntimeException:
at android.app.LoadedApk.makeApplication (LoadedApk.java:563)
at android.app.ActivityThread.handleBindApplication (ActivityThread.java:4540)
at android.app.ActivityThread.access$1500 (ActivityThread.java:151)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1371)
at android.os.Handler.dispatchMessage (Handler.java:102)
at android.os.Looper.loop (Looper.java:135)
at android.app.ActivityThread.main (ActivityThread.java:5268)
at java.lang.reflect.Method.invoke (Method.java)
at java.lang.reflect.Method.invoke (Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:902)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:697)
Caused by: java.lang.ClassNotFoundException:
at dalvik.system.BaseDexClassLoader.findClass (BaseDexClassLoader.java:56)
at java.lang.ClassLoader.loadClass (ClassLoader.java:511)
at java.lang.ClassLoader.loadClass (ClassLoader.java:469)
at android.app.Instrumentation.newApplication (Instrumentation.java:980)
at android.app.LoadedApk.makeApplication (LoadedApk.java:558)
Post a lot of research, the below post details this appropriately and concludes hat this is not fixable,
Unexpected crash in BaseDexClassLoader
I'm running myFaces 2.1.7 and desperatly trying to reduche the mmeory usage of our web application. Basically session size of each users ballons to up to 10MB which we can't handle.
I tried adding the following to Descriptor:
<context-param>
<param-name>org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION</param-name>
<param-value>3</param-value>
</context-param>
result was ok and the session size of any given user wasn't going higher than 1MB. But then alot of users aren't able to login since the change. What is happening is that on login screen ViewExpiredException is thrown , and i wrote a custom viewExpiredException class that redirects the user back to login screen, so essentially they're stuck on login screen loop
try to log in ---> ViewExpiredException thrown ---> Custom ViewExpiredHandler ----> Forward user to Login Screen
<----------------------------------------------------------------------------------------------------------------
Removing the above context-param fixes the issue! My question is one -
1) why is the viewException is thrown when the NUMBER_OF_VIEWS_IN_SESSION is reduced from its default value
2) is it possible to work around the issue by using the custom ViewExpiredHandler class ? how?
3) am i doing something wrong in causing this issue?
P.S. in testing why this is happening, if i open for example IE and try to login all is ok, but then if i try to open another browser (e.g. chrome) and login using another username above issues are encountered mirroring issues reported by users not being able to login.
Also following hints of myFaces wiki i have added the following to descriptor but i don't believe it can contribute to the issue:
<context-param>
<param-name>org.apache.myfaces.SERIALIZE_STATE_IN_SESSION</param-name>
<param-value>false</param-value>
</context-param>
Update:
As suggested by BalusC i change the STATE_SAVING_METHOD to client in order to resolve the memory issues we are having . immediately all UAT testers reported dramatic slow down on all page load speeds so i had to revert back to having STATE_SAVING_METHOD set to server.
Since I've been experimenting with value of org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION and with the current value of 6 (an improvement of 70% over the default 20 sessions) i am not getting the ViewExpiredException errors any more.(reason why this question was created originally)
But in a way i am playing russian roulette. I don't really know why having the value of org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION set to 3/4/5 didn't work and why 6 is working and it bothers me not being able to explain it. Is anyone able to provide information?
I originally asked this question after noticing how the use of browser's BACK button was causing ViewExpired Exception to be thrown.
I had also reduced the default value of 20 for org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION to 3 and then 6 (in trying memory foot print) which aggravated the problem.
Having wrote a ViewExpired Exception Handler, i was now looking for a way to do something about the Exception when it was thrown and below is how i am dealing with it:
1 - `org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION ` value is 6
2 - when ViewExpired Exception is thrown in ViewExpired Handler retrieve the request URL
HttpServletRequest orgRequest = (HttpServletRequest) fc.getExternalContext().getRequest();
3 - insert a boolean into user session (used as flag to be used below)
Map<String, Object> sessionMap = FacesContext.getCurrentInstance()
.getExternalContext().getSessionMap();
sessionMap.put("refreshedMaxSesion",true);
4 - redirect back to URL retrieved in step 2
fc.getExternalContext().redirect(orgRequest.getRequestURI());
5 - Since page is reloaded , see if the flag in step 3 exists and if so flag a notification to be shown to user and remove from session
if(sessionMap.containsKey("refreshedMaxSesion")){
showPageForceRefreshed = true;
sessionMap.remove("refreshedMaxSesion");
}
6 - I'm using Pines Notify to show subtle "FYI, this page way refreshed" type message".
<h:outputText rendered="#{ myBean.showPageForceRefreshed }" id="PageWasRefreshedInfoId" >
<script type="text/javascript">
newjq(document).ready(function(){
newjq.pnotify({
pnotify_title: 'Info',
pnotify_text: 'Ehem, Page was Refreshed.' ,
pnotify_mouse_reset: false,
pnotify_type: 'info',
pnotify_delay: 5000
});
});
</script>
</h:outputText>
I am getting the following errors in SystemOut logs:
[11/4/11 2:53:13:876 ZZZ] 00000245 srt W
com.ibm.ws.webcontainer.srt.SRTServletResponse setStatus WARNING:
Cannot set status. Response already committed.
[11/4/11 2:53:13:876 ZZZ] 00000245 srt W
com.ibm.ws.webcontainer.srt.SRTServletResponse addHeader WARNING:
Cannot set header. Response already committed.
A bit of searching got me here: http://www-01.ibm.com/support/docview.wss?uid=swg21316420
The solution talked about here says that we should disable "Cookie Acceptance test". But i am not able to find out where exactly is that checkbox in admin console.
The technote you are referring to is for a specific application (WebSphere Commerce). If you are getting these warnings with your own application, then the technote doesn't apply. What these warnings mean is that you have a JSP or servlet that calls setStatus or addHeader after too much output has already been written to the response. You need to determine where this happens and either fix your code or increase the output buffer size.