I have installed Worklight 6.2 on Linux, using Liberty 8.5.5 and DB2 10.5. Created the DB2 databases for WRKLGHT and WLREPORT. Have executed the Server Configuration Tool and successfully created a Worklight Server configuration (did not have any errors in the Console view when running the Ant tasks, tables were created successfully in the database, and configuration shows deployed status in the SCT). Created a runtime environment in the SCT, also seemed to succeed (no errors in Console view, tables created/updated, runtime environment shows deployed in the SCT). Stopped and restarted the Liberty server.
Can hit Worklight admin at (/worklightconsole) and log in successfully using my demo user, however it then indicates there are no runtime environments. When trying to access runtime environment at /worklight/console (which should be the correct URL given how I created the runtime config in SCT using my Worklight project WAR), I get various errors: first "Service unavailable since initialization is not yet complete." then after retrying for about a minute or two I get "javax.servlet.ServletException: java.lang.RuntimeException: Timeout while waiting for the management service to start up at com.worklight.core.auth.impl.AuthenticationFilter.isWaitingForInitialization(AuthenticationFilter.java:561)".
Seems the management service is not starting up successfully. Upon reviewing the messages.log I see the following error precede it: "FWLSE0242E: Failed to synchronize application runtime information. The servlet initialization failed and the servlet will deny serve. 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 worklight]" and this creates an FFDC log.
I know this is a lot of information but trying to be complete. Anything I should check to fix the JMX communication issue and get the management service starting?
Thank you for the replies back. Turns out there is an issue with Liberty (I was on 8.5.5.0) and the IBM JDK I was using (1.7_64). Swapped out to the Oracle JRE (1.7.0_60-b19), pointed Liberty to use it, and the problem was solved. I am pursuing a fix with the Liberty team through IBM Support for this issue.
I cannot give a unique solution, but I can explain the situation and this may lead to a solution.
The runtime servlet initialization tries to contact the Worklight Admin service. The Worklight Admin service is a web application that must be running when the runtime starts. The runtime was not able to find the Worklight Admin service. It waited a while, in case that the Worklight Admin service is just starting up, but then gave up due to a timeout because within a given time, it could not find the Worklight Admin service.
Possible reasons:
the web server is not at all configured to run the Worklight Admin service. In your case, this seems not the problem, since you can access the Worklight Console. You should also see in the log file whether the Worklight Admin service did start.
the worklightadmin service might never start up ... this could be a configuration problem, e.g. with the WLADMIN data base. This could also be detected from the server logs.
when the runtimes and the Worklight Admin service start up together, it might be that the Worklight Admin service simply takes too long to start. Let's say you have 100 webapps, and the runtime starts first and the Worklight Admin service starts last, it could be that the 98 other webapps take too much time to start. In that case, make your web server lighter ... run only Worklight on that webserver, nothing else.
the Worklight Admin service starts, but the runtime cannot communicate with it. This indicates that the JMX communication is misconfigured. Follow the documentation of the webserver how to configure JMX. For liberty, see http://www-01.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.ibm.websphere.wlp.core.doc/ae/twlp_admin_restconnector.html?cp=SSD28V_8.5.5%2F1-5-2-10-1&lang=en
Related
I have deployed my application running on my local server # http://localhost:8048/myservice?day=xx&month=yy&year=zzzz , it works succesfully on my local machine, in that it downloads a file from the http site. However when I deploy to Mule Management console . I understand that the default port is 8585. When I change the URL to MMC & give the default port with the same path, it does not download the file . Am I missingsomething
The MMC is a utility for managing and monitoring Mule Standalone Runtimes.
One of its functions is to deploy apps to a Runtime. You are not actually deploying to the MMC.
Does this help clarify the situation or do you want any further help on want The MMC is used for and how to do it?
Please check the logs inside MMC.It stores the logfiles date wise.See if your application has been deployed in MMC successfully and if yes then do the following things:
1)If you are using any path to download the file then cross check the path details.You can put a logger to crosscheck that.
2)Put a logger before the business logic and after the business logic and follow what it is logging in the log file.
3)In case your server is Linux then check the path separator pattern
MMC is a Mule Management Console which is used (provides provision) to deploy, undeploy, manage, monitor application and server both. From the statement you mentioned in your query it seems you are trying to deploy the app in the MMC - MMC is not a server its a console where you can register your ESB Runtimes -or- API Gateways (on-Prem) servers so that you can deploy the applications to the server/runtimes (which will go to the runtimes location $MULE_HOME/apps).
Please check if you have registered the server under MMC's Server tab - if not then you have to do this first and then it will allow you to perform application deployment using the MMC's APplication tab where you can upload your deployment archive/artifacts/build to the mmc repo and then you can deploy through the deployment options by selecting your server (which you have registered).
If I am missing something from your statement then please clarify more and will try to help you out here.
I installed Apache Tomcat 7. During the install, it asks if I want to do a full install or if I want to install just the web service. I chose to install the full package (Tomcat and a web service). When it finished, I had a windows service I could start. I could then view/use the web-based tomcat admin panel.
I shut down the service and re-ran the installer to setup an additional web service. I will have a couple dozen web apps to setup. During the install, I selected the "Web Service Only" so I could install the additional web app without installing Tomcat again. The installation finished OK.
I checked the installation folders and see both of my web services setup in the webapps folder. I start the tomcat service OK. When I attempt to view the web-based admin panel for either web service .. the originally installed web service and the second web service, tomcat seems to hang. When I attempt to shutdown the service, it doesn't shutdown properly and displays the windows error "unable to shutdown service". Eventually I can kill the process.
What could be causing this issue? I'm new to Tomcat on Windows so I apologize if I did not provide enough information. The web-based admin panel DOES work when I have a single webapp. When I have two or more webapps, the admin panel quits working (hangs).
Any ideas?
If you have Tomcat install a separate service for each web application, then you should be able to control each of them separately. They will be running separate JVMs, separate Tomcat services, etc.
If you had instead intended to have a single service with multiple applications deployed on it, then it appears that you may have made a mistake and configured multiple services instead.
From the command-line, you can launch the Tomcat service manager and specify exactly which of the Windows Services you'd like to control. For example:
C:\path\to\tomcat> tomcat8w.exe //ES//MyService
(Where MyService is the name you gave to your Windows Service when you configured it.)
You can find more information on Tomcat's Windows Service Documentation.
I had build a stand alone application on grails 2.1 which uses quart scheduler.
Now I need to deploy this application on Apache tomcat cluster using mod_jk connector.
I am running multiple instance of tomcat and and using Delta Manager for managing the session, but it's not working as I am able to log in the first tomcat instance deployed apps but when I am trying to log into the second instance ,then it won't fetch user information from database and give message that user name or password incorrect.
Even if I stop the first instance, still it won't let me log into the system. I try to find solution online for this problem but didn't get any information on how to deploy grails 2.1 web application on tomcat cluster using mod_jk connector. All the information is available for grails 1.3 version which is pretty old and not relevant for grails 2.1.
Any help would be appreciated.
I have succeeded in getting an embedded ApacheDS instance to start with a Java Web App thanks to the example found here, and have added partitions to it. The problem is that the resulting LDAP server instance doesn't show 'ou=config'. Any idea why or what I can do to to get this important element?
In embedded mode you configure the server programmatically, ou=config is for configuring the server running in network mode.
I implemented a web application that connects to a ProjectServer.svc web service. The application works on a project environment server, but returns an error in the production server. Unluckly, due to security settings the text and code of the exception taking place on the server is not shown, instead I get this message:
The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs
I modified the wcf settings in the web config of project server to make the web service return the error...but nothing happened, because probably Project server overrides the web config wcf settings.
How can I get the error message, so I can understand what is wrong with the server configuration?
Sometimes ULS log may help - when Project server process accepted your call and error somewhere inside of the process.
I touched the configs only once to create Proxy assembly and that time it worked... maybe the same approach will help you to find proper config. Here is a link http://msdn.microsoft.com/en-us/library/office/ff621594(v=office.14).aspx
Don't forget iisreset after you change the config