I try to configure login/password authentication for jmxremote connection on Tomcat 7 and MFP 7.1
With the properties -Dcom.sun.management.jmxremote.authenticate=false in file setenv.sh, all works fine. I can see the runtimes in the MFP Operational Console
When I change the properties -Dcom.sun.management.jmxremote.authenticate to true, I don't be able to see the runtime in the MobileFirst Operational Console and I have the following error in the file catalina.out
Exception in thread Initialization thread for Worklight runtime prod" java.lang.RuntimeException: Timeout while waiting for the management service to start up.120 secs.
Thanks
com.sun.management.jmxremote.authenticate=true means that you activate JMX on Tomcat with client authentication based on a user ID and password, without SSL. In this case other properties are required. See for example https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.jazz.repository.web.admin.doc/topics/t_server_mon_tomcat_option2.html&scope=null.
Related
I am trying to debug deployed application which is running in the remote WebSphere server version 7. When I try to configure server, I am getting error presented on the picture below. Please advise me how to configure the debug mode
I have referred following source https://www.jetbrains.com/idea/help/run-debug-configuration-websphere-server.html#d1145856e682
I deployed a worklight sample project "sample.war" into a clustered environment in IBM WAS ND 8.5.5 using Worklight Server Configuration tool.
ENVIRONMENT DETAILS:
Worklight build: 6.2.0.00.20140801-1709
IBM WAS ND: 8.5.5.0
"Server error.Contact the server administrator" while try to access the Worklight Console[http:// servername:9080/worklightconsole]
Error log from Sytemout.log
[10/5/14 6:31:54:373 PDT] 000000b2 RuntimeServic E No user in security context! A <security-constraint> may be missing from web.xml.
[10/5/14 6:31:54:630 PDT] 000000af PrivExAction W J2CA0144W: No mappingConfigAlias found for ConnectionFactory or DataSource jdbc/WorklightAdminDS_Work
server.xml
SystemOut.log traces
SystemOut.log traces
The error No user in security context! is an indication that application security is not enabled in the application server.
The remedy is:
Enable administrative security in the WAS console. Then enable application security in the WAS console. See also http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/admin/c_securing_wladmin.html?lang=en
Configure the mappings of the JEE roles, as described in http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/install_config/t_configuring_was_for_wl_admin.html?lang=en
There's no obvious application problem in your log file.
And the runtime declared it could sucesfully synchronize line 371 of the log ' Result: worklight: worklight1/ihsCell01/wl1Node01/10.10.11.117: Runtime was synchronized successfully'
I suspect that the issue is that the console fails to communicate with the administration service.
I would try to define the endpoint property for the Console
https://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/install_config/c_endpoint_admin_services.html?lang=en
I got this problem after deploy worklight app inside websphere. I already follow exactly all these steps carefully without any mistakes.
http://blog.revivalx.com/2014/06/18/deploy-worklight-war-file-into-websphere/
When I try to invoke this URL inside my browser, it throw an error.
Service unavailable since initialization failed.
Already search out the log file, it said like this
[10/2/14 17:46:39:474 MYT] 0000009b Authenticatio E com.worklight.core.auth.impl.AuthenticationFilter isWaitingForInitialization FWLSE0242E: Failed to synchronize application runtime information. The servlet initialization failed and the servlet will deny service. The most common reason is a failure in JMX communication with the ''worklightadmin'' service. You need to restart the web application after fixing the problem. [project xxxxxxxx]
Worklight version
version=6.2.0
fixpack=00
buildNumber=20140613-0730
Websphere version
Webspshere Base v 8.5.5.0
build gm1319.01
First thing first, you are using an outdated version of Worklight 6.2; download the latest studio and server artifacts from IBM Fix Central.
Second, you are using Worklight 6.2, don't follow guides written for 6.1...
Instead, follow the official installation documentation.
Worklight 6.2 contains a new management service that you must take into account when deploying Worklight to an application server, this is not taken into account in the guide you linked to.
From the error message:
The servlet initialization failed and the servlet will deny service.
The most common reason is a failure in JMX communication with the
''worklightadmin'' service
Read carefully the Knowledge Center for 6.2, then try to install.
Also read this: How to solve management service not starting up in Worklight 6.2
My app runs well on Worklight Development Server, but not on WebSphere Application Server V8.5 Liberty Profile.
I tried both Oracle JDK and IBM JDK, there was no difference.
There was no problem connecting to the server with jconsole, although I had to connect without ssl.
On Eclipse Console,
[2014-07-11 17:18:10] Starting build process: application 'U1', all environments
[2014-07-11 17:18:12] Application 'U1' with all environments build finished.
[2014-07-11 17:18:12] Deploying application 'U1' with all environments to Worklight Server...
[2014-07-11 17:19:02] 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: "Connection refused".".
Thank you.
I do not know how the Studio deploys to an external Liberty server.
You could also:
Install Worklight Server and deploy using
- the Server Configuration Tool
- or the ant tasks (provided by the Worklight Server installer)
- or manual procedure documented at https://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/install_config/t_wlconsole_install.html
The manual procedure may give you hints about what is missing in your External Liberty Server.
It could be:
- rest connector and it's configuration https://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/install_config/t_optional_config_app_server_liberty.html
- JNDI properties so that Liberty can use the REST connector (step 3 at https://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/admin/t_configuring_liberty_profile_for_wladmin_manually.html )
I deployed Confluence 5.1 as a WAR to an OpenShift Tomcat 6 Cartridge.
Visiting the instance with my web-browser I get:
Error occurred during template rendering: Velocimacro : Error using VM library : template/includes/macros-deprecated.vm. Contact your administrator for assistance.
With the relevant portion of the server logs saying:
2013-04-14 05:32:03,322 FATAL [ContainerBackgroundProcessor[StandardEngine[Catalina]]] [atlassian.spring.container.SpringContainerContext] getComponent Spring Application context has not been set
2013-04-14 05:32:03,323 ERROR [ContainerBackgroundProcessor[StandardEngine[Catalina]]] [confluence.user.listeners.UserSessionExpiryListener] sessionDestroyed Application server does not give us access to expired sessions. Listeners that depend on receiving LogoutEvent will not be reliable. This web server is probably unsupported.
java.lang.IllegalStateException: Spring Application context has not been set
Atlassian support tells me to chown the Tomcat directories; but OpenShift doesn't seem to allow this.
How can I successfully install Confluence 5.1 on OpenShift?
You could use a DIY cartridge and deploy tomcat yourself. Using an action hook (for example the deploy hook) you could also adjust permissions if this is still required.