Hello - a user is experiencing this error message in our PRODUCTION environment, and the logs seem to bare minimal information for me to decipher this issue. User reports Submitting a Review page and sometimes receiving the following error (and then sometime not receiving this error. It seems random, and I am not aware of any specific one thing, or data that causing this to error or process successful.
Production use/environment info:
LSPS v. 3.1.1029
Wildfly v.9.0.2.Final
OS Windows 7
As far as I know, the user does nothing different when the process fails vs when the process completes successfully.
When investigating the logs, I only find the following. - Does anyone see/know something that stands out, or have a good idea of what would cause such an error?
08:28:51,549 INFO [com.kenco.lite.vaadin.core.LspsUI] (default task-10) Setting theme to lsps-dark
08:28:51,549 INFO [com.kenco.lite.vaadin.core.LspsUI] (default task-10) Setting theme to lsps-dark
08:28:52,549 INFO [com.whitestein.lsps.modulemanager.ModelProviderServiceBean] (default task-10) Model cache synchronized, took 0ms
08:48:23,503 DEBUG [com.kenco.lite.vaadin.core.AppFormConnector] (default task-30) Event processing produced 1 validation error(s)
08:48:23,503 DEBUG [com.kenco.lite.vaadin.core.AppFormConnector] (default task-30) Event processing produced 1 validation error(s)
09:01:17,335 ERROR [com.kenco.lite.vaadin.core.AppHub] (default task-6) unknown error occurred: com.whitestein.lsps.common.LspsRuntimeException: Failed to process view models.
at com.whitestein.lsps.vaadin.ui.ViewModelMerger.processViewModels(ViewModelMerger.java:113)
at com.whitestein.lsps.vaadin.ui.UIScreen.processEvents(UIScreen.java:771)
at com.whitestein.lsps.vaadin.ui.UIScreen.doTriggerEventProcessing(UIScreen.java:629)
at com.whitestein.lsps.vaadin.ui.UIScreen.triggerEventProcessing(UIScreen.java:560)
at com.whitestein.lsps.vaadin.util.UIComponents.fireAndProcess(UIComponents.java:557)
at com.whitestein.lsps.vaadin.util.UIComponents.fireAndProcess(UIComponents.java:541)
at com.whitestein.lsps.vaadin.ui.components.UIButton.buttonClick(UIButton.java:88)
at sun.reflect.GeneratedMethodAccessor261.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:508)
at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:198)
at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:161)
at com.vaadin.server.AbstractClientConnector.fireEvent(AbstractClientConnector.java:1008)
at com.vaadin.ui.Button.fireClick(Button.java:377)
at com.vaadin.ui.Button$1.click(Button.java:54)
at sun.reflect.GeneratedMethodAccessor258.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.vaadin.server.ServerRpcManager.applyInvocation(ServerRpcManager.java:158)
at com.vaadin.server.ServerRpcManager.applyInvocation(ServerRpcManager.java:118)
at com.vaadin.server.communication.ServerRpcHandler.handleInvocations(ServerRpcHandler.java:408)
at com.vaadin.server.communication.ServerRpcHandler.handleRpc(ServerRpcHandler.java:273)
at com.vaadin.server.communication.UidlRequestHandler.synchronizedHandleRequest(UidlRequestHandler.java:79)
at com.vaadin.server.SynchronizedRequestHandler.handleRequest(SynchronizedRequestHandler.java:41)
at com.vaadin.server.VaadinService.handleRequest(VaadinService.java:1409)
at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:364)
at com.whitestein.lsps.vaadin.util.VaadinServletWithTransaction.service(VaadinServletWithTransaction.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:86)
at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51)
at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56)
at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58)
at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:72)
at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:282)
at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:261)
at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:80)
at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:172)
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199)
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.whitestein.lsps.common.LspsException: Failed to merge model instance.
at com.whitestein.lsps.vaadin.LspsContextHolder.persist(LspsContextHolder.java:339)
at com.whitestein.lsps.vaadin.ui.UIScreen.persist(UIScreen.java:221)
at com.whitestein.lsps.vaadin.ui.UIScreen$1.doPersist(UIScreen.java:203)
at com.whitestein.lsps.vaadin.ui.ViewModelMerger.processViewModels(ViewModelMerger.java:105)
... 57 more
Caused by: javax.ejb.EJBTransactionRolledbackException: Merging of model instance failed
at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:159)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:256)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:329)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ejb3.security.AuthorizationInterceptor.processInvocation(AuthorizationInterceptor.java:138)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:634)
at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195)
at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73)
at com.whitestein.lsps.engine.ModelInstanceUtilsService$$$view112.attachAndMergeLevel(Unknown Source)
at com.whitestein.lsps.vaadin.LspsContextHolder.performPersist(LspsContextHolder.java:352)
at com.whitestein.lsps.vaadin.LspsContextHolder.persist(LspsContextHolder.java:328)
... 60 more
Caused by: com.whitestein.lsps.common.LspsRuntimeException: Merging of model instance failed
at com.whitestein.lsps.engine.ModelInstanceUtilsServiceBean.attachAndMergeLevel(ModelInstanceUtilsServiceBean.java:138)
at sun.reflect.GeneratedMethodAccessor289.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:70)
at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:80)
at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93)
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
at com.whitestein.lsps.engine.sharedrecord.SharedRecordNotifierInterceptor.handleSharedRecordNotification(SharedRecordNotifierInterceptor.java:85)
at sun.reflect.GeneratedMethodAccessor284.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:89)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73)
at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ejb3.component.interceptors.NonPooledEJBComponentInstanceAssociatingInterceptor.processInvocation(NonPooledEJBComponentInstanceAssociatingInterceptor.java:59)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:254)
... 97 more
Failed to process view models
Forum rules
Make sure every topic contains information about your LSPS version and if relevant also your server OS, client OS, database name and version, and application server name and version.
Make sure every topic contains information about your LSPS version and if relevant also your server OS, client OS, database name and version, and application server name and version.
- eric.graham
- Posts: 58
- Joined: Tue May 13, 2014 12:20 pm
- Roman Kubascik
- Posts: 57
- Joined: Thu Apr 16, 2015 9:05 am
Re: Failed to process view models
Hi Eric,
please send us longer server log we can analyze, thanks.
Roman
please send us longer server log we can analyze, thanks.
Roman
- eric.graham
- Posts: 58
- Joined: Tue May 13, 2014 12:20 pm
Re: Failed to process view models
Thanks for the response Roman.
A little background of what user is experiencing:
When the user creates a ticket, the process runs some web services, and pulls back some information to pre-populate a couple of forms. (some times the WS does not find this info and returns i.e. "ERROR in TicketProcess::'Ticket Initiation'::TicketSetup::'Get Order Information " - we are aware of this, and working on that for upcoming releases to our app. - but this never stopped the application from running, and most always pulls the data in.)
- Once the user enters the needed data and clicks Submit, and "review" portion (same forms with a couple of addition ones are shown to user). - User has the option to click a drop-down (TicketStatus) with a "Need More Information" choice that shows a text area. This will not progress any processes. It is more a flag for another your to enter the needed information, and then the drop-down can be changed and Submitted to the next process.
- The the user sometime sees the red error shows after clicking Submit when choosing the "Need More Information" choice.
So once TicketStatus is set to "Need More Information", the process will not process, it will Save the information so other users can open and edit to enter the needed data. Once that is satisfied with correct data, the TicketStatus and be updated and ticket Submit to the following process. (I hope that seems clear). - But instead, we have a particular user saying when they do the above, they sometime see the red error box. I have attached a log that shows when this occurs. (also, there is an error "Conflict on property: jdeStatus" that is completely separate from this issue. I just wanted to point that out, as we are aware of this also, but this does not pertain to the specific issue the user is seeing with "Merging of model instance failed". - One last thing. "String or binary data would be truncated" has been addressed, and caused from a Search feature, again, we have seen this and has never caused a error "Merging of model instance failed".
A little background of what user is experiencing:
When the user creates a ticket, the process runs some web services, and pulls back some information to pre-populate a couple of forms. (some times the WS does not find this info and returns i.e. "ERROR in TicketProcess::'Ticket Initiation'::TicketSetup::'Get Order Information " - we are aware of this, and working on that for upcoming releases to our app. - but this never stopped the application from running, and most always pulls the data in.)
- Once the user enters the needed data and clicks Submit, and "review" portion (same forms with a couple of addition ones are shown to user). - User has the option to click a drop-down (TicketStatus) with a "Need More Information" choice that shows a text area. This will not progress any processes. It is more a flag for another your to enter the needed information, and then the drop-down can be changed and Submitted to the next process.
- The the user sometime sees the red error shows after clicking Submit when choosing the "Need More Information" choice.
So once TicketStatus is set to "Need More Information", the process will not process, it will Save the information so other users can open and edit to enter the needed data. Once that is satisfied with correct data, the TicketStatus and be updated and ticket Submit to the following process. (I hope that seems clear). - But instead, we have a particular user saying when they do the above, they sometime see the red error box. I have attached a log that shows when this occurs. (also, there is an error "Conflict on property: jdeStatus" that is completely separate from this issue. I just wanted to point that out, as we are aware of this also, but this does not pertain to the specific issue the user is seeing with "Merging of model instance failed". - One last thing. "String or binary data would be truncated" has been addressed, and caused from a Search feature, again, we have seen this and has never caused a error "Merging of model instance failed".
- Attachments
-
- log.zip
- attached log file
- (11.23 KiB) Downloaded 303 times
- Roman Kubascik
- Posts: 57
- Joined: Thu Apr 16, 2015 9:05 am
Re: Failed to process view models
Hi Eric,
thank you for the server log. It seems like the reason behind error "Failed to process view models." is "BatchUpdateException: String or binary data would be truncated."
This error usually means that you are trying to store value which is bigger than size of the DB field.
You might try to log your queries on the application server or DB server to identify the field.
It's not clear to me why it didn't cause problem before.
Regards,
Roman
thank you for the server log. It seems like the reason behind error "Failed to process view models." is "BatchUpdateException: String or binary data would be truncated."
This error usually means that you are trying to store value which is bigger than size of the DB field.
You might try to log your queries on the application server or DB server to identify the field.
It's not clear to me why it didn't cause problem before.
Regards,
Roman
4 posts
Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest