Orbeon Thread starvation or clock leap detected on Liferay 7.0 - orbeon

we have an issue when we are trying to intgrate the orbeon proxy portlet in our liferay 7.0 distribution.
As fas as I know, we have to include the license.xml into the "WEB-INF/resources/config" inside the .war file.
After this, I deployed the .war file into the "deploy" folder under our "budles" folder but out tomcat server freezes and after a while we are starting to get messages like this:
11:07:39,304 WARN [HikariPool-2 housekeeper][HikariPool:676] HikariPool-2 - Thread starvation or clock leap detected (housekeeper delta=50s936ms528µs270ns).
11:07:50,174 WARN [HikariPool-1 housekeeper][HikariPool:676] HikariPool-1 - Thread starvation or clock leap detected (housekeeper delta=45s279ms904µs144ns).
What I'm doing wrong? Any help will be appreciate.
Thanks in advance.

Related

Grails 5 app is constantly redeploying during development

I had been using Grails 3.3.2 for about 3-4 years now and never had this issue. I just recently started migrating our apps to Grails 5 and now this started happening. Everytime I save a change to a file (gson, groovy, etc) the app redeploys and I have to wait a good 5-6 seconds before I can test it (url becomes available).
In Grails 5 my console looks like this when I make changes:
Grails application running at http://localhost:8081 in environment: development
File C:\Workspaces\Intellij\ecpp\grails-app\controllers\ecpp\service\LookupSvcController.groovy changed, recompiling...
Grails application running at http://localhost:8081 in environment: development
File C:\Workspaces\Intellij\ecpp\grails-app\controllers\ecpp\service\LookupSvcController.groovy changed, recompiling...
Grails application running at http://localhost:8081 in environment: development
File C:\Workspaces\Intellij\ecpp\grails-app\controllers\ecpp\service\LookupSvcController.groovy changed, recompiling...
Grails application running at http://localhost:8081 in environment: development
Each one of those Grails application running [...] lines is a 5+ second delay I have to wait through before the app comes back up
When I would work on my 3.3.2 projects my console would look like this during changes
Grails application running at http://localhost:8081 in environment: development
File C:\Workspaces\Intellij\ecpp\grails-app\controllers\ecpp\service\LookupSvcController.groovy changed, recompiling...
File C:\Workspaces\Intellij\ecpp\grails-app\controllers\ecpp\service\LookupSvcController.groovy changed, recompiling...
File C:\Workspaces\Intellij\ecpp\grails-app\controllers\ecpp\service\LookupSvcController.groovy changed, recompiling...
I never had to wait, I could immediately refresh the page and see the changes. Needless to say, my DEV time has taken a hit having to stop and wait for a redeploy. Is there some configuration I missed while upgrading that I can set to resolve this?
This happens while running the app with gradlew bootRun as well as grailsw run-app
Grails 5.1.7
JDK: 11.0.13

I just recently started migrating our apps to Grails 5 and now this
started happening. Everytime I save a change to a file (gson, groovy,
etc) the app redeploys and I have to wait a good 5-6 seconds before I
can test it (url becomes available).
The behavior you described is expected and by design.
Older versions of Grails were configured by default with a reloading agent. Grails 5 is not. The default behavior you will get with Grails 5 is a recompile and restart. If you don't want that behavior you can remove the devtools from your build.
You didn't ask about configuring a reloading agent but if you are interested, see the Spring Boot Developer Tools and Spring Loaded section at https://docs.grails.org/5.1.7/guide/single.html#upgrading33x.

Fatal slow performance after Grails 3 upgrade

I have updated small application to Grails 3.2.3. After some issues this is now resolved Grails 3.x update - bootRun failed
But unfortunately the application is unusable. On my high-end laptop ThinkPad 460p I cant even load home page of application. It's loading for ages and then CSS styles are not loaded at all. There is no error messages for grails run-app or IDEA Run Configuration.
I have no idea what to do now, all configuration is described here Grails 3.x update - bootRun failed
Thank you.
Chrome network profiling

Are you behind a company firewall? Are your pages trying to access remote javascript and/or css files? The process trying to access these may hang or timeout eventually.

ActiveMQ (5.8.0) with Spring Integration JMS failing to stop Windows Service

While running Spring Integration JMS deployed on Tomcat 7.0.26 (running as a Windows Service) communicating to ActiveMQ (5.8.0) , we find that periodically the Tomcat Service fails to stop.
Can anyone shed some light on how we go about tracking this issue down?
We have taken Thread and Heap dumps using VisualVM but don't know what we are looking for! Any guidance would be helpful.
To get around this issue we have to stop Tomcat using Task Manager and then restart the process.
There are no exceptions in the logs around the time of the failure, although Tomcat does appear to be attempting to stop.
The last couple of entries in the tomcat log file are shown below in case that helps:
2013-06-05 10:07:28,582 INFO pool-2-thread-2 org.springframework.beans.factory.support.DefaultListableBeanFactory - Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory#6517a4c6: defining beans [org.springframework.integration.internalDefaultConfiguringBeanFactoryPostProcessor,debugLoggingChannel,org.springframework.integration.handler.LoggingHandler#0,debugLoggingChannel.adapter,infoLoggingChannel,org.springframework.integration.handler.LoggingHandler#1,infoLoggingChannel.adapter,org.springframework.integration.channel.interceptor.WireTap#0,incomingRadarEventsString,org.springframework.jms.listener.DefaultMessageListenerContainer#0,org.springframework.integration.jms.ChannelPublishingJmsMessageListener#0,jmsinalerts,org.springframework.integration.transformer.HeaderEnricher#0,org.springframework.integration.transformer.MessageTransformingHandler#0,processingChannelEnricher,org.springframework.integration.xml.transformer.UnmarshallingTransformer#0,org.springframework.integration.transformer.MessageTransformingHandler#1,unmarshallingAlertsChannel,convertToRadarAlertObjects,cepRadarAlertsUnMarshaller,processRadarEventsMessage,org.springframework.integration.config.ServiceActivatorFactoryBean#0,alertEventsServiceActivator,org.springframework.integration.transformer.HeaderEnricher#1,org.springframework.integration.transformer.MessageTransformingHandler#2,addMessageProcessingHeaders,messageProcessingHeadersEnricher,alertsEventsProcessor,org.springframework.integration.config.SplitterFactoryBean#0,splitAlertsChannel,org.springframework.integration.config.ConsumerEndpointFactoryBean#0,org.springframework.integration.config.FilterFactoryBean#0,singleAlertsPoleObject,org.springframework.integration.config.ConsumerEndpointFactoryBean#1,org.springframework.integration.channel.interceptor.WireTap#1,incomingPutPoleObjectsString,org.springframework.jms.listener.DefaultMessageListenerContainer#1,org.springframework.integration.jms.ChannelPublishingJmsMessageListener#1,jmsin,org.springframework.integration.transformer.HeaderEnricher#2,org.springframework.integration.transformer.MessageTransformingHandler#3,processingPutPoleObjectsChannelEnricher,failedUnmarshalMessage,org.springframework.integration.config.TransformerFactoryBean#738bf6bf,org.springframework.integration.config.ServiceActivatorFactoryBean#69f4b0dc,org.springframework.integration.handler.MessageHandlerChain#0,org.springframework.integration.config.ConsumerEndpointFactoryBean#2,failedUnmarshalMessageToJmsOut,org.springframework.integration.jms.JmsSendingMessageHandler#0,failedUnmarshalMessageDispatcher,toSplitPutPoleObjects,org.springframework.integration.xml.transformer.UnmarshallingTransformer#1,org.springframework.integration.transformer.MessageTransformingHandler#4,unmarshallPutPoleObjectsString,convertToPutPoleObjects,cepMarshaller,singlePoleObject,org.springframework.integration.config.SplitterFactoryBean#1,org.springframework.integration.config.ConsumerEndpointFactoryBean#3,org.springframework.integration.config.FilterFactoryBean#1,org.springframework.integration.config.ConsumerEndpointFactoryBean#4,discardEvent,filteredEvent,org.springframework.integration.transformer.HeaderEnricher#3,org.springframework.integration.transformer.MessageTransformingHandler#5,matchedFilterEnricher,org.springframework.integration.channel.interceptor.WireTap#2,toSubscribedChannels,org.springframework.integration.router.RecipientListRouter#0,org.springframework.integration.config.ConsumerEndpointFactoryBean#5,profileEventChannel,aggregateEventChannel,messageErrorHandler,channelExecutor,org.springframework.integration.config.ServiceActivatorFactoryBean#1,org.springframework.integration.config.ConsumerEndpointFactoryBean#6,exceptionGatewayProfile,profileEventChannelEnriched,org.springframework.integration.config.FilterFactoryBean#2,profileFilter,profileNotify,org.springframework.integration.config.ServiceActivatorFactoryBean#2,profileNotifier,profileOut,splitMatchedQueriesForMessage,org.springframework.integration.config.SplitterFactoryBean#2,org.springframework.integration.config.ConsumerEndpointFactoryBean#7,notificationChannel,org.springframework.integration.config.FilterFactoryBean#3,gemNotificationChannelFilter,org.springframework.integration.config.FilterFactoryBean#4,workflowChannelFilter,notificationExecutor,gemNotificationAcceptedChannel,org.springframework.integration.config.ServiceActivatorFactoryBean#3,profileNotifierActivator,org.springframework.integration.config.FilterFactoryBean#5,mopiChannelFilter,mopiOutputChannel,org.springframework.integration.config.ServiceActivatorFactoryBean#6dca1837,org.springframework.integration.handler.MessageHandlerChain#1,org.springframework.integration.config.ConsumerEndpointFactoryBean#8,org.springframework.integration.channel.interceptor.WireTap#3,mopiOutputChannelToJmsOut,org.springframework.integration.jms.JmsSendingMessageHandler#1,mopiOutputQueueDispatcher,workflowAcceptedChannel,org.springframework.integration.config.ServiceActivatorFactoryBean#4,workflowTriggerActivator,failedProfile,org.springframework.integration.config.TransformerFactoryBean#6128453c,org.springframework.integration.config.ServiceActivatorFactoryBean#1ad997f9,org.springframework.integration.handler.MessageHandlerChain#2,org.springframework.integration.config.ConsumerEndpointFactoryBean#9,failedProfileToJmsOut,org.springframework.integration.jms.JmsSendingMessageHandler#2,failedProfileDispatcher,incomingResolvedProfileString,org.springframework.jms.listener.DefaultMessageListenerContainer#2,org.springframework.integration.jms.ChannelPublishingJmsMessageListener#2,org.springframework.integration.jms.JmsMessageDrivenEndpoint#0,org.springframework.integration.xml.transformer.UnmarshallingTransformer#2,org.springframework.integration.transformer.MessageTransformingHandler#bd5d765,org.springframework.integration.config.ServiceActivatorFactoryBean#4302df5,org.springframework.integration.transformer.HeaderEnricher#4,org.springframework.integration.transformer.MessageTransformingHandler#771931f8,org.springframework.integration.handler.MessageHandlerChain#3,org.springframework.integration.config.ConsumerEndpointFactoryBean#10,discardProfile,org.springframework.integration.config.ServiceActivatorFactoryBean#5,org.springframework.integration.config.ConsumerEndpointFactoryBean#11,exceptionGatewayAggregate,aggregateEventChannelEnriched,org.springframework.integration.config.ServiceActivatorFactoryBean#6,receiveAggregate,aggregateEventChannelStarted,org.springframework.integration.config.FilterFactoryBean#6,aggregateFilter,toFieldRetreiver,org.springframework.integration.config.ServiceActivatorFactoryBean#7,fieldCapture,toEvalFunction,org.springframework.integration.config.ServiceActivatorFactoryBean#8,evalFunction,toAggregateCompleted,org.springframework.integration.config.ServiceActivatorFactoryBean#9,aggregateCompleted,splitAggregate,org.springframework.integration.config.SplitterFactoryBean#3,aggregateSplitter,aggregateOut,failedAggregate,org.springframework.integration.config.TransformerFactoryBean#2904b5ae,org.springframework.integration.config.ServiceActivatorFactoryBean#7433c78b,org.springframework.integration.handler.MessageHandlerChain#4,org.springframework.integration.config.ConsumerEndpointFactoryBean#12,failedAggregateToJmsOut,org.springframework.integration.jms.JmsSendingMessageHandler#3,failedAggregateDispatcher,incomingResolvedAggregateString,org.springframework.jms.listener.DefaultMessageListenerContainer#3,org.springframework.integration.jms.ChannelPublishingJmsMessageListener#3,org.springframework.integration.jms.JmsMessageDrivenEndpoint#1,org.springframework.integration.xml.transformer.UnmarshallingTransformer#3,org.springframework.integration.transformer.MessageTransformingHandler#7371b246,org.springframework.integration.config.ServiceActivatorFactoryBean#2d6f4ce0,org.springframework.integration.transformer.HeaderEnricher#5,org.springframework.integration.transformer.MessageTransformingHandler#61735602,org.springframework.integration.handler.MessageHandlerChain#5,org.springframework.integration.config.ConsumerEndpointFactoryBean#13,org.springframework.integration.config.ServiceActivatorFactoryBean#10,toAggregateDiscard,aggregateDiscarder,discardAggregate,org.springframework.integration.endpoint.MethodInvokingMessageSource#0,org.springframework.scheduling.support.CronTrigger#0,org.springframework.integration.config.SourcePollingChannelAdapterFactoryBean#0,org.springframework.integration.config.SplitterFactoryBean#4,jobProcessingChannel,org.springframework.integration.config.ConsumerEndpointFactoryBean#14,singleJobChannel,org.springframework.integration.config.ServiceActivatorFactoryBean#11,singleJobSA,cepNotification-marshaller,cepNotification-messageSender,cepNotification-webServiceTemplate,cepNotificationClient,cepNotificationUddiDestinationProvider,cepNotificationPropertiesDestinationProvider,cepNotificationService,securityServiceCacheHelper,cepPoleUddiDestinationProvider,cepPolePropertiesDestinationProvider,cepPoleUddiDestinationProviderWorkflowService,cepWorkflowUddiDestinationProvider,cepWorkflowPropertiesDestinationProvider,cepPoleService,cepPoleFlowService,queryService,cepUddiClient,securityService,cepSecurityMarshaller,cepSecurityMessageSender,cepSecurityWebServiceTemplate,cepSecurityUddiDestinationProvider,cepSecurityPropertiesDestinationProvider,cepSecurityServiceClient,connectionFactory,localConnectionFactory,jmsTransactionManager,radarEventsAlertQueue,requestQueue,persistedProfileEvents,persistedAggregateEvents,errorUnmarshalMessageQueue,errorProfileQueue,mopiOutputQueue,resolvedProfileQueue,errorAggregateQueue,resolvedAggregateQueue,placeholderConfig,baseQueryFilter,profileQueryFilter,aggregateQueryFilter,eventTypeFilter,aggregateReceiver,aggregateComplete,aggregateDiscarded,notificationActionsUtility,replyBasedNotificationsUtility,notificationsFactory,profileQueryNotifier,poleQueryLoader,queryResolver,queryCache,fieldRetriever,poleFieldCapture,groupByFieldsFilter,evaluateFunction,notificationDispatcher,convertJmsPayloadToCommonServicesXml,errorUnwrapper,errorHandler,resolvedPoleHandler,gemNotificationFilterBean,workflowFilterBean,mopiFilterBean,profileQueryNotifierBean,aggregateSplitterBean,workflowTriggerBean,org.springframework.aop.config.internalAutoProxyCreator,com.googlecode.ehcache.annotations.key.CachingReflectionHelper,com.googlecode.ehcache.annotations.key.ListCacheKeyGenerator.DEFAULT_BEAN_NAME,com.googlecode.ehcache.annotations.key.HashCodeCacheKeyGenerator.DEFAULT_BEAN_NAME,com.googlecode.ehcache.annotations.key.MessageDigestCacheKeyGenerator.DEFAULT_BEAN_NAME,com.googlecode.ehcache.annotations.key.ReflectionHashCodeCacheKeyGenerator.DEFAULT_BEAN_NAME,com.googlecode.ehcache.annotations.key.StringCacheKeyGenerator.DEFAULT_BEAN_NAME,com.googlecode.ehcache.annotations.impl.CacheAttributeSourceImpl#0,com.googlecode.ehcache.annotations.impl.CacheStaticMethodMatcherPointcut#0,com.googlecode.ehcache.annotations.interceptor.EhCacheInterceptor#0,com.googlecode.ehcache.annotations.config.internalEhCacheCachingAdvisor,cepEhCacheManager,ehcacheWrapper,splitterHelper,matchedProfileQueriesSplitter,scheduledJobTrigger,jobBuilder,validQueriesTaskExecutor,delQueryDataTaskExecutor,jobProcessor,ObjectBeanInfoBuilder,cepConnectionManager,cepResilienceConnectionManager,cepRepository,dataSource,cepResilienceRepository,nullChannel,errorChannel,_org.springframework.integration.errorLogger,taskScheduler]; root of factory hierarchy
2013-06-05 10:07:29,456 INFO pool-2-thread-2 org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor - Shutting down ExecutorService
2013-06-05 10:07:29,456 INFO pool-2-thread-2 org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler - Shutting down ExecutorService 'taskScheduler'
2013-06-05 10:07:29,456 INFO pool-2-thread-2 org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor - Shutting down ExecutorService
Thanks,
Mark.

websphere url context error (JSPG0036E)

Issue on Websphere 6.1 I hope I'm missing something obvious: We have an application which gets deployed to a configured Websphere environment. We're trying to mimic this WebSphere configuration on a different platform (Linux vs Solaris), but maybe we're missing some obvious settings. The application deploys and starts without an error, but after logon on url localhost:port/app/index.jsp
(via j_spring_security_check) Websphere redirects to localhost:port/index.jsp. This gives an JSP processing Error (HTTPError 404), with code JSPG0036E.
The webapplication is wrapped in an ear, because those are the standards here. And that ear works well on our solaris WAS 6.1 environment but not on the linux WAS. Furthermore in development we've the wrapped war running on Tomcat without problem.
I think I missed the context root somewhere but It's not to be found in Websphere's console, I wouldn't be surprised if it is a Websphere (6.1.0.33) Bug, hopefully I'm wrong or are there workarounds?

Hyperic JMX monitoring threads not closing

I'm using tomcat 6 and HypericHQ for monitoring via JMX.
The issue is the following:
hyperic, overtime, opens hundreds of jmx connection and never closes them.. after few hours our tomcat server is using 100% cpu without doing anything.
Once I stop hyperic agent, tomcat will go back to 0-1% cpu..
Here is what we are seeing virtual vm:
http://forums.hyperic.com/jiveforums/servlet/JiveServlet/download/1-11619-37096-2616/Capture.PNG
I don't know if this is an hyperic issue or not, but I wonder if there is an option to fix it via tomcat/java configuration? The reason that I don't know if this is an hyperic or a tomcat/java configuration issue is because that when we use hyperic on other standard java daemon it doesn't have the same connection leak issue.
The JMX is exposed using Spring, and it's working great when connecting with JMX clients (JConsole/VisualVM). When I close the client, I see that the number of connections drops by one.
Is there any thing that we can do to fix this via java configuration? (forcing it to close a connection that is open for more than X seconds?)
One more thing, in tomcat we see (from time to time) the following message (while hyperic is running):
Mar 7, 2011 11:30:00 AM ServerCommunicatorAdmin reqIncoming
WARNING: The server has decided to close this client connection.
Thanks

Resources