Sometimes when Worklight adapter is invoked, the following error "No SessionManager" is encountered in server log. When the adapter is invoked again, result is returned. I have checked that the session ID remains the same.
May I know what is the possible reason to have this kind of error? Thanks!
Environment: Worklight 5.0.6.1
server log:
[2013-09-09 17:55:38] FWLSE0099E: An error occurred while invoking procedure TestAdapter/getTestDataFWLSE0100E: parameters:{
"arr": [
]
}
No SessionManager
FWLSE0101E: Caused by: null
.metadata.log:
!ENTRY com.worklight.studio.plugin 4 0 2013-09-09 17:55:38.709
!MESSAGE FWLSE0099E: An error occurred while invoking procedure TestAdapter/getTestDataFWLSE0100E: parameters:{
"arr": [
]
}
No SessionManager
FWLSE0101E: Caused by: null
This error is no longer reproduced in newer versions of Worklight. My suggestion to you is to update to the latest iFix of Worklight v5.0.6.2, or better yet - upgrade to MobileFirst Platform (previously Worklight) v6.3 / v7.0.
Related
I create a new project in MobileFirst 7.0, but as soon as I am deploying it into MobileFirst Development server it is giving me following error:
[ERROR ] FWLSE0081E: Failed synchronizing application from the administration service. This prevents the application from running. The reason is No constructor has a #ConstructorProperties for this set of items: [adapters, applications, configProfiles, transactionId]. Please restart the application server after taking the proper corrective actions. [project MyProject]
No constructor has a #ConstructorProperties for this set of items: [adapters, applications, configProfiles, transactionId]
[ERROR ] Synchronize operation failed.
No constructor has a #ConstructorProperties for this set of items: [adapters, applications, configProfiles, transactionId]
[ERROR ] Result: MyProject: worklight///10.80.111.52: Runtime synchronization failed
[ERROR ] MyProject: worklight///10.80.111.52: 2015-03-28T22:36:55.555Z: No constructor has a #ConstructorProperties for this set of items: [adapters, applications, configProfiles, transactionId]
[ERROR ] FWLST0003E: ========= Failed starting project /MyProject [project MyProject]
java.lang.reflect.InvocationTargetException
[ERROR ] null
java.lang.reflect.InvocationTargetException
[ERROR ] MyProject: worklight///10.80.111.52: 2015-03-28T22:36:55.774Z: null
[ERROR ] RuntimeMBeanCallable.call() exception
java.lang.reflect.UndeclaredThrowableException
[ERROR ] SRVE0315E: An exception occurred: com.ibm.ws.webcontainer.webapp.WebAppErrorReport: javax.servlet.ServletException: Worklight Console initialization failed.Logged Exception: java.io.InvalidObjectException: No constructor has a #ConstructorProperties for this set of items: [adapters, applications, configProfiles, transactionId]
at com.worklight.core.auth.impl.AuthenticationFilter.verifyServletInitialized(AuthenticationFilter.java:522)
at com.worklight.core.auth.impl.AuthenticationFilter.doFilter(AuthenticationFilter.java:134)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:192)
at [internal classes]
Caused by: javax.servlet.ServletException: Worklight Console initialization failed.Logged Exception: java.io.InvalidObjectException: No constructor has a #ConstructorProperties for this set of items: [adapters, applications, configProfiles, transactionId]
... 5 more
I am using Windows 7, Eclipse Luna 4.4.1 and JRE 7.
Per my comment, my initial thought was that the installed went bad.
Re-installation seemed to have resolved the issue, thus this is the answer here.
I also encountered this when upgrading a project from v6.3 to v7.0. I had already been using my MFP Studio installation to build other projects, so I was confident the installation was ok.
I created a second Eclipse Workspace. I added the project to the new workspace and was able to build with no issues in the new workspace.
You may be able to resolve this issue without reinstalling MFP if you switch to a new workspace.
I have faced a problem like Mobilefirst server not starting until i
edit the JVM.options (-DOS.name = Windows 8) in the eclipse.
I need to do the above step manually whenever i create a new workspace
Is there
any other way to completely resolve this problem.
Note : I am using Windows 8.1
Error Log
Listening for transport dt_socket at address: 10777
CWWKE0005E: The runtime environment could not be launched.
CWWKE0018E: An exception occurred while launching the runtime environment: java.lang.IllegalArgumentException: WebSphere-DefaultExtension-windowsnt(unknown)
com.ibm.ws.kernel.boot.LaunchException: Caught unexpected exception java.lang.IllegalArgumentException: WebSphere-DefaultExtension-windowsnt(unknown)
at com.ibm.ws.kernel.boot.internal.KernelBootstrap.rethrowException(KernelBootstrap.java:418)
at com.ibm.ws.kernel.boot.internal.KernelBootstrap.go(KernelBootstrap.java:183)
at com.ibm.ws.kernel.boot.Launcher.createPlatform(Launcher.java:131)
at com.ibm.ws.kernel.boot.Launcher.main(Launcher.java:55)
at com.ibm.ws.kernel.boot.cmdline.EnvCheck.main(EnvCheck.java:52)
Caused by: java.lang.IllegalArgumentException: WebSphere-DefaultExtension-windowsnt(unknown)
at java.util.jar.Attributes$Name.<init>(Unknown Source)
at java.util.jar.Attributes.getValue(Unknown Source)
at com.ibm.ws.kernel.boot.internal.BootstrapManifest.getOSExtensionDefinition(BootstrapManifest.java:157)
at com.ibm.ws.kernel.boot.internal.KernelBootstrap.go(KernelBootstrap.java:123)
... 3 more
Try adding that option to the eclipse.ini file located in your Eclipse installation folder, instead of in the JVM.options of your workspace.
I am using:
Mobilefirst platform studio 6.3.0.
I have followed the IBM training modules to create a new mobilefirst adapter.
I am getting an error while trying to invoke a procedure. I have added the required JDBC driver jar file in the server/lib folder. But, I am getting this error.
[ERROR ] FWLSE0035E: Invocation of procedure 'procedure1' failed. [project pocket]
Class com.mysql.jdbc.Driver not found in Worklight platform or project /pocket
Try using mysql-connector-java-5.1.26-bin.jar in the server/lib folder as well in the build path of the project.
I have IBM Worklight 6.2 development environment with the following setup.
Oracle Java 1.7
Eclipse 4.3
IBM Worklight 6.2 Developer Edition
A sample Hybrid project had been created and deployed in the Worklight development server and app works fine in the Mobile Browser Simulator.
I am getting the following error in Worklight Server console in Eclipse:
[ERROR ] Failed to obtain JMX connection to access an MBean.
There might be a JMX configuration error: Read timed out
[ERROR ] FWLSE3000E: A server error was detected.
FWLSE3012E: JMX configuration error. Unable to obtain MBeans. Reason: "Read timed out".
And also I am getting the following error in Worklight Console[Web Console].
FWLSE3012E: JMX configuration error. Unable to obtain MBeans. Reason: "Read timed out".
Note:
I have read the following questions but no luck.
IBM Worklight - Can't run an app on WebSphere Application Server
How to solve management service not starting up in Worklight 6.2
Additional Info:
I used to get the following error whenever the Worklight development server is started from eclipse.
*[WARNING ] CWNEN0070W: The javax.ws.rs.QueryParam annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.
[WARNING ] CWNEN0070W: The javax.ws.rs.PathParam annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.
[WARNING ] CWNEN0070W: The javax.ws.rs.HeaderParam annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.
[WARNING ] CWNEN0070W: The javax.ws.rs.CookieParam annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.
[WARNING ] CWNEN0070W: The javax.ws.rs.core.Context annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.
[WARNING ] CWNEN0070W: The javax.ws.rs.MatrixParam annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.*
I hope necessary information's I have provided. Let me know if u still need.
The JMX timeout error in Worklight 6.2 is a known issue.
Typically when this error occurs to me, a way to resolve it is to either 'wait' a while and then to stop & restart the Worklight Server (in Eclipse > Servers view > 'play' button). Another option is to restart Eclipse.
You can also try the suggestions from the comments:
Try to edit the file
WorklightServerConfig/servers/worklight/jvm.options in your Eclipse
workspace, adding the line
"-Dcom.ibm.ws.jmx.connector.client.rest.readTimeout=180000". Then stop and restart the Worklight Development Server.
and
Try to edit the file
WorklightServerConfig/servers/worklight/server.xml and add in the
section the following line, then restart and try again:
<executor name="LargeThreadPool" id="default" coreThreads="40"
maxThreads="80" keepAlive="60s" stealPolicy="STRICT"
rejectedWorkPolicy="CALLER_RUNS" />
Best is to open a PMR (support ticket) and request an iFix as this is due to be fixed.
I'm using worklight 6.1 for my mobile app project. My problem is, I got this error message when I try to upload war file into worklight server. I already install worklight server into my websphere.
Error 500: javax.servlet.ServletException: Filter [authenticationFilter]: Could not find required filter class - com.worklight.core.auth.impl.AuthenticationFilter.class
These are steps for uploading war file into worklight server.
1.Build project_name.war file from IBM Worklight Studio v6.1.
2.Deploy the .war file to IBM Websphere Integrated Solutions Console v8.5.5.0.
3.Open the WebSphere enterprise application and click install.
4.Choose the project.war file from the worklight project directory.
5.Click on next button for fast path.
6.Click on next button.
7.Choose the server 1.
8.Choose on the target JNDI.
9.Set the Virtual Host to default_host.
10.Set the context root.
11.Click on finish button.
12.Save directly to master configuration.
13.Start the application.
14.Open the server URL to get into the wroklight server to deploy application, adapter and etc, but failed to open the server URL with this error and the error log as below.
[3/6/14 10:18:50:442 MYT] 0000009e webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor]: java.lang.ClassNotFoundException: class java.lang.ClassNotFoundException: com.worklight.core.auth.impl.AuthenticationFilter
at java.beans.Beans.instantiate(Beans.java:195)
at java.beans.Beans.instantiate(Beans.java:80)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager._loadFilter(WebAppFilterManager.java:533)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.loadFilter(WebAppFilterManager.java:475)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.getFilterInstanceWrapper(WebAppFilterManager.java:308)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.getFilterChain(WebAppFilterManager.java:380)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:892)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1025)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3761)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:976)
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:459)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:526)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:312)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:283)
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:1862)
My latest error message on 10 March 2014
Error 500: javax.servlet.ServletException: Worklight Console initialization failed.Logged Exception: java.lang.RuntimeException: FWLSE0206E: The project /rmbp failed to initialize, because the project database schema for data source jdbc:db2://192.168.1.80:50001/APPCNTR is from version N/A, which is not supported by the server from version 6.1.0.00.20131126-0630. Use the Worklight ant tasks to upgrade the project database schema.
You may want to look at this similar post for suggestions:
IBM Worklight 6.0 - Worklight Console does not show up after installing WL 6.0 server on Liberty profile - Error 500
Importantly "you need to make sure that your worklight-jee-library.jar is in the application classloader." Like Idan suggested above you can easily use the ant scripts we provide in order to accomplish this in a more automated fashion:
https://pic.dhe.ibm.com/infocenter/wrklight/v6r1m0/index.jsp?topic=%2Fcom.ibm.worklight.deploy.doc%2Fdevref%2Ft_transporting_apps_and_adapters.html