I'm using Worklight Studio 6.2, WebSphere Application Server 8.5 Liberty Profile and Worklight Server. Using IBM DB2, and a remote server where i've installed all this stuff.
When i deploy an app to the server that's what i get.
Application Error
SRVE0777E: Exception thrown by application class 'com.worklight.core.auth.impl.AuthenticationFilter.verifyServletInitialized:422'
javax.servlet.ServletException: Worklight Console initialization failed.Logged Exception: java.lang.ClassNotFoundException: Class org.hsqldb.jdbcDriver not found in Worklight platform or project /app1
at com.worklight.core.auth.impl.AuthenticationFilter.verifyServletInitialized(AuthenticationFilter.java:422)
at com.worklight.core.auth.impl.AuthenticationFilter.doFilter(AuthenticationFilter.java:127)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:194)
at [internal classes]
Dunno what could be, hope you can help me :S
Thanks
The error message "Class org.hsqldb.jdbcDriver not found in Worklight platform or project /app1" effectively means that there is a problem with the data source definition, for the data source with JNDI name "app1/jdbc/WorklightDS" or "app1/jdbc/WorklightReportsDS". See the Worklight documentation for how to define these data sources.
Related
I am new to worklight when I try to deploy I am getting the following error
Adapter deployment failed: No server host specified
& No Mbean found
.
Make sure that you have an address specified in Eclipse > Servers view > Worklight Development Server (double-click it) > Host name. Also attempt an Eclipse restart.
When I tried to deploy my projects running on IBM MobileFirst 6.3 using JDK1.7 I am getting the following error in MobileFirst Server console in Eclipse kepler SR2:
[ERROR ] Failed to obtain JMX connection to access an MBean. There
might be a JMX configuration error: Connection refused: connect
[ATTENTION] No running mxbeans found
and also I get this error message shown in the MobileFirst console:
FWLSE3030E: The runtime "myproject" does not exist in the Worklight
administration database. The database may be corrupted.
Everything was just working fine till this error appears with all my projects .
I tried to create a new project but I get the same error each time.
I even tried to delete the MobileFirst development server and add it again but nothing is changed.
Full log:
Application Error SRVE0777E: Exception émise par la classe
d'application
'com.worklight.core.auth.impl.AuthenticationFilter.isWaitingForSynchronization:607'
javax.servlet.ServletException: java.lang.RuntimeException: Timeout
while waiting for the management service to start up.120 secs.
at
com.worklight.core.auth.impl.AuthenticationFilter.isWaitingForSynchronization(AuthenticationFilter.java:607)
at
com.worklight.core.auth.impl.AuthenticationFilter.doFilter(AuthenticationFilter.java:144)
at
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:194)
at [internal classes]
Caused by: java.lang.RuntimeException: Timeout while waiting for the
management service to start up.120 secs.
at
com.worklight.core.init.WorklightServletInitializer$1.run(WorklightServletInitializer.java:121)
at java.lang.Thread.run(Thread.java:745)
these is another error that appears in the eclipse console when i tried to run it on the Mobilefirst developpement server
[ERROR ] FWLSE3000E: A server error was detected.
FWLSE3012E: JMX connection error. Reason: "FWLSE3012E: JMX connection
error. Reason: "Connection refused: connect". Check the application
server logs for details.". Check the application server logs for
details.
[ERROR ] FWLSE0242E: Failed to synchronize application runtime
information. The servlet initialization failed and the servlet will
deny service due to a failure to communicate with the worklightadmin
service.
Common reasons are that the worklightadmin service is not started
correctly or that the ibm.worklight.admin.environmentid property has
not the same value for the worklightadmin service and the runtime.
[project myproject] Timeout while waiting for the management service
to start up.120 secs.
here is a the error log :
Application Error
SRVE0777E: Exception émise par la classe d'application 'com.worklight.core.auth.impl.AuthenticationFilter.isWaitingForSynchronization:607'
javax.servlet.ServletException: java.lang.RuntimeException: Timeout while waiting for the management service to start up.120 secs.
at com.worklight.core.auth.impl.AuthenticationFilter.isWaitingForSynchronization(AuthenticationFilter.java:607)
at com.worklight.core.auth.impl.AuthenticationFilter.doFilter(AuthenticationFilter.java:144)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:194)
at [internal classes]
Caused by: java.lang.RuntimeException: Timeout while waiting for the management service to start up.120 secs.
at com.worklight.core.init.WorklightServletInitializer$1.run(WorklightServletInitializer.java:121)
at java.lang.Thread.run(Thread.java:745)
these is another error that appears in the eclipse console when i tried to run it on the Mobilefirst developpement server
[ERROR ] FWLSE3000E: A server error was detected.
FWLSE3012E: JMX connection error. Reason: "FWLSE3012E: JMX connection error. Reason: "Connection refused: connect". Check the application server logs for details.". Check the application server logs for details.
[ERROR ] FWLSE0242E: Failed to synchronize application runtime information. The servlet initialization failed and the servlet will deny service due to a failure to communicate with the worklightadmin service.
Common reasons are that the worklightadmin service is not started correctly or that the ibm.worklight.admin.environmentid property has not the same value for the worklightadmin service and the runtime. [project myproject]
Timeout while waiting for the management service to start up.120 secs.
See this tech note: The Worklight Development Server times out.
Steps:
Open the Servers view.
Double-click the Worklight Development Server to open the Overview pane.
Expand the Timeouts section.
Increase the value in the Start (in seconds) field. The value that can be appropriate for your case depends on your startup environment. Consider starting with a value of 180 seconds (3 minutes).
I am developing a hybrid app in Worklight 6.2. I have a WorkLight Server installed Red Hat Linux 6 base as remote server.
I have give the servers ip address, port number and context root as"/worklight" in the "build settings and deploy target".
Then i added my adapter file and wlapp file into the remote servers "app" folder. I haven't made any changes in the server.xml file.
Now when i call the procedure from my app i am getting "[IPADDRESS:PORT/worklight/apps/services/api/MyApp/ipad/query] failure. state: 404, response: The server was unable to process the request from the application. Please try again later."
What am i missing and What changes do i have to make to make the request to work.?
The steps you are describing are not clear.
Make sure you are following the steps as provided in the IBM Worklight Knowledge Center.
First make sure the Worklight Server deployment to the application server was done correctly
You can verify this then by loading the Worklight Console (there will be no deployed projects)
Then follow the Worklight project (.war, .wlapp, .adapter) deployment to the Worklight Server instructions
You can verify this then by loading the Worklight Console (there will be 1 deployed application)
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:
Failed to deploy the application to Worklight server: : JMX configuration error. Unable to obtain MBeans.
Reason: "FWLSE3012E: JMX configuration error. Unable to obtain MBeans. Reason: "Unrecognized SSL message, plaintext connection?".".
According to this question, the error message means that a JMX connection over HTTPS is attempted, when in fact the server speaks the HTTP protocol on that port.
Review the settings that determine the protocol and port used for JMX. See the set of JNDI properties for Worklight administration and the set of JNDI properties for Worklight projects, and check their values.
I installed a worklight .war on my Websphere Application server, following this tutorial :
http://pic.dhe.ibm.com/infocenter/wrklight/v6r0m0/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fdevref%2Fc_dev_test_server_and_console.html
After starting my application, when I try to reach it using the following URL : http://<ip address>:9080/<context root>/console
I have this error in my Websphere SystemOut.log :
com.ibm.ws.webcontainer.webapp.WebApp logError SRVE0293E: [Servlet Error]-[Worklight Project not initialized]: javax.servlet.ServletException: Worklight Project not initialized
at com.worklight.core.auth.impl.AuthenticationFilter.doFilter(AuthenticationFilter.java:110)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
environment config :
Windows Server 2008 R2 - Entreprise
WebSphere Application server V7
Worklight server V6
DataBase Derby (default install trough worklight server install)
The same user asked the same question also in: IBM Worklight 6.0 - Custom authentication - custom java code doesn't seem to be found
His solution was:
I [re] Installed a Websphere Application server 8.5 and a DB2 with the
worklight server V6, and now everything is working great!