Upon attempting to walk through install guide of MFP Operational Analytics, I encountered an OverlappingFileLockException when trying to start the MFP server. However, such issue doesn't occur when I exclude Operational Analytics from server.xml of Liberty Core. Is there anyone can help us with this issue?
Installing Operational Analytics
[11/03/15 12:37:27:261 EST] 0000002c com.ibm.puremeap.util.DataUtil I getDataSource Returning Data Source based upon jndiName=java:comp/env/jdbc/AppCenterDS dataSource=com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource#59649184
[11/03/15 12:37:28:696 EST] 00000032 com.ibm.ws.webcontainer.osgi.webapp.WebGroup I SRVE0169I: Loading Web Module: Worklight Console.
[11/03/15 12:37:28:696 EST] 00000032 com.ibm.ws.webcontainer I SRVE0250I: Web Module Worklight Console has been bound to default_host.
[11/03/15 12:37:28:696 EST] 00000032 com.ibm.ws.http.internal.VirtualHostImpl A CWWKT0016I: Web application available (default_host): http://auworklighttest.gabraus.local:9080/worklightconsole/
[11/03/15 12:37:28:743 EST] 00000032 com.ibm.ws.session.WASSessionCore I SESN0176I: A new session context will be created for application key default_host/worklightconsole
[11/03/15 12:37:28:743 EST] 00000032 com.ibm.ws.util I SESN0172I: The session manager is using the Java default SecureRandom implementation for session ID generation.
[11/03/15 12:37:28:790 EST] 00000032 com.ibm.ws.webcontainer.servlet I SRVE0242I: [worklightconsole] [/worklightconsole] [servicesServlet]: Initialization successful.
[11/03/15 12:37:28:790 EST] 00000032 com.ibm.ws.app.manager.AppMessageHelper A CWWKZ0001I: Application worklightconsole started in 5.523 seconds.
[11/03/15 12:37:29:585 EST] 0000002d com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper I DSRA8203I: Database product name : DB2/NT64
[11/03/15 12:37:29:585 EST] 0000002d com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper I DSRA8204I: Database product version : SQL10014
[11/03/15 12:37:29:585 EST] 0000002d com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper I DSRA8205I: JDBC driver name : IBM Data Server Driver for JDBC and SQLJ
[11/03/15 12:37:29:585 EST] 0000002d com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper I DSRA8206I: JDBC driver version : 4.15.113
[11/03/15 12:37:29:585 EST] 0000002c com.ibm.ejs.j2c.FreePool E J2CA0046E: Method createManagedConnectionWithMCWrapper caught an exception during creation of the ManagedConnection for resource jdbc/AppCenterDS, throwing ResourceAllocationException. Original exception: <=================================>Exception Message -> null
java.nio.channels.OverlappingFileLockException
at sun.nio.ch.SharedFileLockTable.checkList(FileLockTable.java:268)
at sun.nio.ch.SharedFileLockTable.add(FileLockTable.java:165)
at sun.nio.ch.FileChannelImpl.lock(FileChannelImpl.java:1034)
at java.nio.channels.FileChannel.lock(FileChannel.java:1064)
at com.ibm.db2.jcc.am.jp.a(jp.java:629)
at com.ibm.db2.jcc.am.ip.a(ip.java:403)
at com.ibm.db2.jcc.am.ip.a(ip.java:475)
at com.ibm.db2.jcc.am.Connection.isLicenseValidatedWithServerLicenseProc(Connection.java:8506)
at com.ibm.db2.jcc.am.Connection.checkForLicenseRestrictions(Connection.java:4787)
at com.ibm.db2.jcc.am.Connection.completeConnect(Connection.java:4730)
at com.ibm.db2.jcc.t4.b.completeConnect(b.java:611)
at com.ibm.db2.jcc.t4.b.a(b.java:423)
at com.ibm.db2.jcc.t4.b.a(b.java:395)
at com.ibm.db2.jcc.t4.b.<init>(b.java:333)
at com.ibm.db2.jcc.DB2PooledConnection.<init>(DB2PooledConnection.java:83)
at com.ibm.db2.jcc.DB2ConnectionPoolDataSource.getPooledConnectionX(DB2ConnectionPoolDataSource.java:348)
at com.ibm.db2.jcc.DB2ConnectionPoolDataSource.getPooledConnection(DB2ConnectionPoolDataSource.java:131)
at com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper$1.run(InternalGenericDataStoreHelper.java:1196)
at java.security.AccessController.doPrivileged(AccessController.java:333)
at com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper.getPooledConnection(InternalGenericDataStoreHelper.java:1212)
at com.ibm.ws.rsadapter.spi.InternalDB2UniversalDataStoreHelper.getPooledConnection(InternalDB2UniversalDataStoreHelper.java:1509)
at com.ibm.ws.rsadapter.spi.WSRdbDataSource.getPooledConnection(WSRdbDataSource.java:331)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.getConnection(WSManagedConnectionFactoryImpl.java:1180)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.createManagedConnection(WSManagedConnectionFactoryImpl.java:930)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.createManagedConnection(WSManagedConnectionFactoryImpl.java:615)
at com.ibm.ejs.j2c.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1768)
at com.ibm.ejs.j2c.FreePool.createOrWaitForConnection(FreePool.java:1512)
at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:3040)
at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:2392)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:1109)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:676)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:354)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:325)
at com.ibm.puremeap.resources.data.impl.PureMeapData.recordDataBaseInfo(PureMeapData.java:270)
at com.ibm.puremeap.resources.data.impl.PureMeapData.<init>(PureMeapData.java:173)
at com.ibm.puremeap.resources.data.impl.PureMeapData.fromDataSource(PureMeapData.java:103)
at com.ibm.puremeap.resources.data.DataStoreFactory.getJPADBStore(DataStoreFactory.java:46)
at com.ibm.puremeap.resources.data.DataStoreFactory.getDataStore(DataStoreFactory.java:34)
at com.ibm.puremeap.util.DataUtil.getData(DataUtil.java:453)
at com.ibm.puremeap.listeners.AppCenterServletContextListener.checkAndUpgradeTo60(AppCenterServletContextListener.java:171)
at com.ibm.puremeap.listeners.AppCenterServletContextListener.contextInitialized(AppCenterServletContextListener.java:88)
at com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:2374)
at com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:1044)
at com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:6342)
at com.ibm.ws.webcontainer.osgi.DynamicVirtualHost.startWebApp(DynamicVirtualHost.java:446)
at com.ibm.ws.webcontainer.osgi.DynamicVirtualHost.startWebApplication(DynamicVirtualHost.java:441)
at com.ibm.ws.webcontainer.osgi.WebContainer.startWebApplication(WebContainer.java:761)
at com.ibm.ws.webcontainer.osgi.WebContainer.startModule(WebContainer.java:739)
at com.ibm.ws.app.manager.web.internal.WebModuleHandlerImpl.deployModule(WebModuleHandlerImpl.java:106)
at com.ibm.ws.app.manager.module.internal.DeployedAppInfoBase.deployModule(DeployedAppInfoBase.java:538)
at com.ibm.ws.app.manager.module.internal.DeployedAppInfoBase.deployModules(DeployedAppInfoBase.java:457)
at com.ibm.ws.app.manager.module.internal.DeployedAppInfoBase.deployApp(DeployedAppInfoBase.java:411)
at com.ibm.ws.app.manager.war.internal.WARApplicationHandlerImpl.install(WARApplicationHandlerImpl.java:73)
at com.ibm.ws.app.manager.internal.statemachine.StartAction.execute(StartAction.java:139)
at com.ibm.ws.app.manager.internal.statemachine.ApplicationStateMachineImpl.enterState(ApplicationStateMachineImpl.java:1166)
at com.ibm.ws.app.manager.internal.statemachine.ApplicationStateMachineImpl.run(ApplicationStateMachineImpl.java:779)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1177)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.lang.Thread.run(Thread.java:795)
<=================================>
I've not hit this problem but that may be because my practice has been to install the Operational Analytics server on its own Liberty instance. While this should not be necessary it is closer to the pattern you would use in production where not only would you have a separate Java EE Server instance but probably would have one or more dedicated OA machines.
The tech note http://www-01.ibm.com/support/docview.wss?uid=swg21664366 explains that this is due to "more than one instance of the com.ibm.db2.jcc.DB2Driver class in the JVM". In other words, the application server configuration contains two or more "libraries":
In Liberty, you have two or more elements that declare a DB2 JDBC driver.
In WebSphere Application Server Full Profile, you have two or more "JDBC providers" that use a DB2 JDBC driver.
The fix is to use a single element or a single JDBC provider instead.
Related
Environment details:
OS RHEL 6.8 64bits
IBM MobileFirst Platform Server Version - 7.0.0.00.20160526-2153
Project WAR Version - 7.0.0.00.20161114-0240
Application Version - 7.0.0.00.20160526-2153
IBM Websphere Liberty Verison - 8.5.5.4
Java - IBM JRE 1.7.0
Created a farm configuration following IBM Knowledge Center MobileFirst 7.0 Configure Farm with uniques values for jndiName="ibm.worklight.admin.serverid",farm_member_1 and farm_member_2.
At start, both servers show these into the messages.log:
[1/8/17 18:53:14:313 CST] 00000034 SystemErr R 1111 WorklightManagementPU-db2 INFO [LargeThreadPool-thread-10] openjpa.Runtime - Starting OpenJPA 1.2.2
[1/8/17 18:53:14:315 CST] 00000034 SystemErr R 1113 WorklightManagementPU-db2 INFO [LargeThreadPool-thread-10] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.DB2Dictionary" (DB2/LINUXX8664 SQL10053 ,IBM Data Server Driver for JDBC and SQLJ 4.17.29).
[1/8/17 18:53:14:364 CST] 00000034 SystemErr R 1162 WorklightManagementPU-db2 INFO [LargeThreadPool-thread-10] openjpa.Runtime - Though you are using optimistic transactions, OpenJPA is now beginning a datastore transaction because you have requested a lock on some data.
Almost every time an app is upload to the runtime, server 2 (farm_member_2) becomes unresponsive (Web console Home-->Runtime-->Server Farm Nodes).When that occurs, the server 2 is updating all the resources, like it was rebooting , loading all the apps and adapters from the runtime. Once finished to load all the apps, these error is shown again:
[1/9/17 1:43:19:868 CST] 00000b05 com.ibm.worklight.admin.jmx.ManagementMXBeanImpl I runtime01: server01///10.77.230.146: 2017-01-09T07:43:19.850Z: Transaction handler reset
[1/9/17 1:43:19:869 CST] 0000005e com.worklight.core.auth.impl.AuthenticationFilter I FWLSE0273I: Set sync required to 'false' [project runtime01]
[1/9/17 1:43:19:872 CST] 00000a86 SystemErr R 16601596 WorklightManagementPU-db2 INFO [LargeThreadPool-thread-1589] openjpa.Runtime - Though you are using optimistic transactions, OpenJPA is now beginning a datastore transaction because you have requested a lock on some data.
[1/9/17 1:43:19:880 CST] 00000a86 SystemErr R 16601604 WorklightManagementPU-db2 INFO [LargeThreadPool-thread-1589] openjpa.Runtime - Though you are using optimistic transactions, OpenJPA is now beginning a datastore transaction because you have requested a lock on some data.
Is that a common thing with this type of configuration? If not,any ideas on how to avoid this?
These are warnings and can be safely ignored. These are logged by OpenJPA packages.
Using MobileFirst 7.1 (7.1.0.00.20151130-1648) - Studio and server both using same version.
Deploying MobileFirst 7.1 application to WebSphere Full-Profile production-like test server and getting NullPointer thrown from within MobileFirst.
I have made several attempts to modify worklight.properties and authenticationConfig.xml and same result including setting mfp.session.independent = false.
I currently have everything set back to out-of-box generated defaults and same issue. Adapters are currently wl_unprotected and no security test on the apps.
WAR , Apps and Adapters all deploy fine and logs look clean until you attempt to invoke an adapter or application URL from a browser.
[1/21/16 9:52:08:420 EST] 000000a4 webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[GadgetAPIServlet]: java.lang.NullPointerException
at com.worklight.core.auth.impl.AuthenticationContext.isSessionIndependent(AuthenticationContext.java:1219)
at com.worklight.core.util.HttpSessionUtil.setLockOnSession(HttpSessionUtil.java:108)
at com.worklight.core.auth.impl.AuthenticationFilter.doFilter(AuthenticationFilter.java:136)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:967)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1107)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3923)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1006)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:463)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:530)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:316)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:287)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1881)
Looking through the MobileFirst source code I see that it is failing to get an instance of Worklight Configuration due to Project Local not currently be set.
This has all worked fine with various configurations locally using MobileFirst Studio and Liberty Profile.
Any help determining what in my application settings could be causing this behavior is greatly appreciated.
The question is very dull on the actual details of the problem. Instead it only lists what was attempted.
The only real clues are this
eploying MobileFirst 7.1 application to WebSphere Full-Profile production-like test server and getting NullPointer thrown from within MobileFirst.
And this:
WAR , Apps and Adapters all deploy fine and logs look clean until you attempt to invoke an adapter or application URL from a browser.
In 7.1 there is no support for a browser environment (better known as "Desktop Browser", and there's also "Mobile Web") in session-independent mode. Mobile environments support it, browser environments do not. If you want to test in a browser environment you must change the server mode, but then it won't work in mobile environments...
The other thing is that in "production-like" environments there is no preview servlet. You cannot preview your applications outside of the development environment. To test, you need to use either simulators/emulators or physical devices.
If this does not answer your question, edit your question with the full steps to reproduce your scenario.
This issue has been resolved! Their build process was overwriting generated web.xml with a stale version from a previous version of MobileFirst so expected servlets where not configured properly.
I installed the following on my RHEL 6
(1) MFP63
(2) MySQL56
(3) WAS 8.5.5.6
and trying to set up my first mobile first project but 'messages.log' has the following errors
I FFDC1015I: An FFDC Incident has been created: "javax.persistence.PersistenceException: Exception [EclipseLink-28018] (Eclipse Persistence Services - 2.6.0.WAS-v20150513-26196d2): org.eclipse.persistence.exceptions.EntityManagerSetupException
Exception Description: Predeployment of PersistenceUnit [appcenterdb-oracle] failed.
Internal Exception: Exception [EclipseLink-7157] (Eclipse Persistence Services - 2.6.0.WAS-v20150513-26196d2): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Entity class [class com.ibm.puremeap.jpa.entity.PushBatchDeviceEntity] must use a #JoinColumn instead of #Column to map its relationship attribute [device]. com.ibm.ws.jpa.management.JPAPUnitInfo.createEMFactory 759" at ffdc_15.07.27_21.00.27.0.log
[7/27/15 21:00:27:238 IST] 00000068 com.ibm.ws.jpa.management.JPAPUnitInfo E CWWJP0015E: An error occurred in the org.eclipse.persistence.jpa.PersistenceProvider persistence provider when it attempted to create the container entity manager factory for the appcenterdb-oracle persistence unit. The following error occurred: Exception [EclipseLink-28018] (Eclipse Persistence Services - 2.6.0.WAS-v20150513-26196d2): org.eclipse.persistence.exceptions.EntityManagerSetupException
Exception Description: Predeployment of PersistenceUnit [appcenterdb-oracle] failed.
Internal Exception: Exception [EclipseLink-7157] (Eclipse Persistence Services - 2.6.0.WAS-v20150513-26196d2): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Entity class [class com.ibm.puremeap.jpa.entity.PushBatchDeviceEntity] must use a #JoinColumn instead of #Column to map its relationship attribute [device].
Message says 'Predeployment of PersistenceUnit [appcenterdb-oracle] failed' but I am using 'MySQL' instead of 'oracle' which is bit confusing to me
I am using Java 8 (with JDK6 and 7 I was facing other issues)
http://pastebin.com/WcWBUjVn (server.xml)
http://pastebin.com/QzByZ63T (messages.log)
Thanks
Sathish Kumar
There are three issues in total:
You are using Java 8 with a MobileFirst Foundation version that does not support it. The system requirements of MobileFirst Foundation 7.0 state that only Java 6 and Java 7 are supported. The symptom is seen in your first messages.log: It is the exception java.lang.IllegalStateException: Context namespace element 'annotation-config' and its parser class [org.springframework.context.annotation.AnnotationConfigBeanDefinitionParser] are only available on JDK 1.5 and higher
Your server.xml contains two elements <application id="worklightconsole" name="worklightconsole" location="worklightconsole.war" type="war">. That is, you have two web applications with the same id, the same name, and the same context root. This can never work. The cause is apparently that you passed worklightconsole.war as argument to <configureApplicationServer>. Instead, as documented in Deploying the project WAR file, the WAR file that you specify should be a MobileFirst project WAR file, built through MobileFirst Studio or through the <war-builder> Ant task.
The second messages.log file contains the log messagesFWLSE2008I: MBean registration succeeded for: com.worklight.common.server.jmx.api:type=WorklightAdmin,qualifier=worklightadmin
FWLSE2008I: MBean registration succeeded for: com.worklight.common.server.jmx.api:type=ProjectManagement_simpleServer,qualifier=worklightconsole [project worklightconsole]
The first one shows an empty environment id, whereas the second one shows an environment id "simpleServer". This environment id is also visible in the server.xml file:<jndiEntry jndiName="worklightconsole/ibm.worklight.admin.environmentid" value='"simpleServer"'/>
But according to the documentation of <configureApplicationServer>, you should pass the same environment id value in both cases.
#Sathish, In the server.xml you have uploaded, I can see those features
<feature>javaee-7.0</feature>
<feature>servlet-3.1</feature>
<feature>jdbc-4.1</feature>
The last two features are not installed by MobileFirst Ant tasks or the Server Configuration Tool.
This let me think you changed them manually after the installation process because you are using an unsupported Liberty profile flavour like
WAS Liberty V8.5.5.6 with Java EE 7 Web Profile or WAS Liberty V8.5.5.6 with Java EE 7 Full Platform
which does not provide the expected features servlet-3.0 and jdbc-4.0 but instead servlet-3.1 and jdbc-4.1.
Actually, MFP 6.3 only supports MFP 6.3 only supports WebSphere Application Server Liberty Core
http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/prereqsForProduct?deliverableId=1404132386734#!
which contains
You may get it from the FixCentral website
http://www-933.ibm.com/support/fixcentral/
On Select product tab, choose
Product Group : WebSphere
Select from WebSphere : WebSphere Application Server
Installed Version : 8.5.5.6
Platform : All
Then select
Individual fix IDs : wlp-core-runtime-8.5.5.6
As 'slowhand' suggested the issue was with 'server.xml' because of multiple 'application id' with the same name
It appears 'ant' tasks does not generate all the tags correctly and I made little corrections to make it work
Thanks
Sathish Kumar
I am installing MobileFirst Platform Operational Analytics on WebSphere Application Server Liberty 8.5.5.1 as per this guide. As soon as I start the server it gives me the message on console:
INFO ] SRVE0169I: Loading Web Module: analytics.
[INFO ] SRVE0250I: Web Module analytics has been bound to default_host.
[AUDIT ] CWWKT0016I: Web application available (default_host): http://hqdvwkl001:9080/analytics/
[INFO ] SESN0176I: A new session context will be created for application key default_host/analytics
[INFO ] SESN0172I: The session manager is using the Java default SecureRandom implementation for session ID generation.
[INFO ] FFDC1015I: An FFDC Incident has been created: "java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory com.ibm.ws.webcontainer.osgi.VirtualHost startWebApp" at ffdc_15.04.09_13.28.41.0.log
[INFO ] FFDC1015I: An FFDC Incident has been created: "com.ibm.ws.container.service.state.StateChangeException: startWebApplication com.ibm.ws.webcontainer.osgi.WebContainer startModule" at ffdc_15.04.09_13.28.41.1.log
[INFO ] FFDC1015I: An FFDC Incident has been created: "com.ibm.ws.container.service.state.StateChangeException: com.ibm.ws.container.service.state.StateChangeException: startWebApplication com.ibm.ws.app.manager.web.internal.WebModuleHandlerImpl 142" at ffdc_15.04.09_13.28.41.2.log
[INFO ] FFDC1015I: An FFDC Incident has been created: "java.util.concurrent.ExecutionException: com.ibm.ws.container.service.state.StateChangeException: com.ibm.ws.container.service.state.StateChangeException: startWebApplication com.ibm.ws.threading.internal.FutureMonitorImpl$FutureMonitorInfo 54" at ffdc_15.04.09_13.28.41.3.log
[ERROR ] CWWKZ0106E: Could not start web application analytics-ear.
[INFO ] FFDC1015I: An FFDC Incident has been created: "com.ibm.ws.container.service.state.StateChangeException: com.ibm.ws.container.service.state.StateChangeException: startWebApplication com.ibm.ws.app.manager.internal.statemachine.StartAction$1 applicationStartFail" at ffdc_15.04.09_13.28.42.0.log
[ERROR ] CWWKZ0002E: An exception occurred while starting the application analytics-ear. The exception message was: com.ibm.ws.container.service.state.StateChangeException: com.ibm.ws.container.service.state.StateChangeException: startWebApplication
I was using MFP Operational Analytics 7.0 on Liberty Profile 8.5.5.1. The minimum version of Liberty Profile for MFP Operational Analytics 7.0 is 8.5.5.3. Refer to system requirement document here and here
After upgrading my test environment from Liberty Profile 8.5.5.1 to 8.5.5.3, the issue was eliminated, and I was able to successfully start the Operational Analytics platform and access the analytics console.
I installed Maximo Anywhere 7.5.1.2. We have Worklight 6.1.0.2. I got following error on Worklight console. I have updated Maximo OSLC web resource in web.xml as per mentioned on IBM knowledge center. I appreciate any help
[2/22/15 20:09:40:922 EST] 0000002e TpaeCustomAut I processRequest() - Request URI=/worklight/apps/services/preview/WorkApproval/common/0/default/js/platform/ui/control/css/large-landscape-controls.css
[2/22/15 20:10:39:606 EST] 0000002b TpaeCustomAut I processRequest() - Request URI=/worklight/apps/services/api/WorkApproval/common/query
[2/22/15 20:10:39:639 EST] 0000002a TpaeCustomAut I processRequest() - Request URI=/worklight/apps/services/api/WorkApproval/common/query
[2/22/15 20:10:39:688 EST] 0000002a TpaeCustomAut I processRequest() - Request URI=/worklight/apps/services/api/WorkApproval/common/query
[2/22/15 20:10:39:719 EST] 0000002a ServletWrappe E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet GadgetAPIServlet in application IBM_Worklight_Console. Exception created : com.worklight.server.auth.api.WorkLightAuthenticationException
at com.worklight.core.auth.impl.AuthenticationContext.checkAuthentication(AuthenticationContext.java:548)
at com.worklight.core.auth.impl.AuthenticationContext.processRealms(AuthenticationContext.java:414)
at com.worklight.core.auth.impl.AuthenticationContext.pushCurrentResource(AuthenticationContext.java:391)
at com.worklight.core.auth.impl.AuthenticationServiceBean.accessResource(AuthenticationServiceBean.java:75)
at com.worklight.integration.services.impl.DataAccessServiceImpl.invokeProcedureInternal(DataAccessServiceImpl.java:384)
at com.worklight.integration.services.impl.DataAccessServiceImpl.invokeProcedure(DataAccessServiceImpl.java:112)
at com.worklight.gadgets.serving.handler.BackendQueryHandler.getContent(BackendQueryHandler.java:184)
at com.worklight.gadgets.serving.handler.BackendQueryHandler.doPost(BackendQueryHandler.java:75)
at com.worklight.gadgets.serving.GadgetAPIServlet.doGetOrPost(GadgetAPIServlet.java:141)
at com.worklight.gadgets.serving.GadgetAPIServlet.doPost(GadgetAPIServlet.java:103)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied(ServletWrapper.java:307)
at com.ibm.ws.cache.servlet.CacheHook.handleFragment(CacheHook.java:576)
at com.ibm.ws.cache.servlet.CacheHook.handleServlet(CacheHook.java:250)
at com.ibm.ws.cache.servlet.ServletWrapper.service(ServletWrapper.java:259)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1661)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1602)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:149)
at com.worklight.core.auth.impl.AuthenticationFilter$1.execute(AuthenticationFilter.java:191)
at com.worklight.core.auth.impl.AuthenticationServiceBean.accessResource(AuthenticationServiceBean.java:76)
I ran into similar issue. Following checklist resolved my issue.
Assuming you have installed Maximo Anywhere component of Maximo EAM, verify the security groups, ANYWHERE_TECHNICIAN and ANYWHERE_APPROVER are created and have the user assigned to these groups
Verify if you can make OSLC request from the browser
http://host:port/maximo/oslc/os/oslcwodetail?_lid=replaceduserid&_lpwd=replacepassword
clean build the project by touching app.xml file
deploy the OSLCGenericAdapter
deploy the app on WorklightDevelopment server from eclipse
AnywhereWorkManager->apps->WorkApproval->Run As -> Run on Worklight Development Server
Open the chrome browser and clean the cache
Preview the app from apps -> WorkApproval -> Common