I am working with worklight on Eclipse on a windows machine. I can never get it to stop or restart properly. Normally I have to spend 5 minutes trying to delete the server and add back the worklight projects and then it may startup again. Has anyone experienced this and what is a fix?
When I start Worklight server (local machine), the server just hangs, the bottom right message displays "Starting Worklight Developer Server".
I am using:
Launching worklight (WebSphere Application Server 8.5.5.0/wlp-1.0.3.20130524-0951) on Java HotSpot(TM) 64-Bit Server VM, version 1.6.0_30-b12 (en_US), Worklight Studio / 6.1.0.01 - 2014
Version: Kepler Service Release 2
Build id: 20140224-0627
Code Base: nothing really, just a simple HelloWorld Adapter and javascript client code.
There are no error messages, this is the last message in the console.
CWWKZ0001I: Application _MobileBrowserSimulator started in 0.498 seconds.
When visiting the server in the browser, there is no response because it looks like the server is still trying to start.
I usually wait 5 minutes before killing the server in the task manager. Even after killing the server in the task manager and then closing Eclipse and trying to start the server again...the server still hangs. Normally, I end up deleting the server and creating another one.
Note: I see a potential issue with the mobile simulator application, but when I remove the mobile simulator, worklight seems to inject it back into the server.
Edit-1: Nothing has really worked. I am now using Kepler SR1 and new workspace. It is possible that the server hanging issue has died down but it still happens. Basically, the only way to kickstart the worklight server is to change the server.xml, delete all the wars/applications (all 2 of them) and then kill the server in the task manager, possibly restarting eclipse and then starting the server again. There are no errors in the message log.
It's hard to say what might be wrong with just that information. Can you provide your messages.log file when the server has failed? (It should be under workspace_path/WorklightServerConfig/servers/worklight/logs)
The best way to get the real one we want, would be to use a fresh Eclipse workspace and then reproduce the problem.
Just blinded eyes, as a potential solution, I would try to set a valid IP to the Worklight Development Server, instead using "localhost" which is the default. Have you tried that? In Servers View, double click Worklight Development Server -> Host Name -> SET TO YOUR CURRENT IP. Then do a Run As -> Run on Worklight Development Server again for your application.
Kepler SR2 isn't supported for Worklight 6.1x. I don't know if this is the cause, but there was some unpredictable behavior with SR2. I would suggest trying it on Kepler SR1 and see if you get the same behavior. Get links to supported eclipse releases and editions here: https://www.ibm.com/developerworks/mobile/worklight/download/
Related
I am using Jmeter 2.13 version and with that I used to record many scripts earlier successfully without any issue . Now, my OS has been reinstalled and I am holding Windows 8.1 , 64 bit version.After re installation, I am not able to record HTTPS web applications even though my proxy configuration is correct. After I setup everything in Jmeter, and click on start from work bench and I navigate to the browser try to access the application, it shows "Server not found" message.
However, the scripts which I saved earlier are working fine without any issues. only the new recording is not working.
Help me with the possible solutions.
"Server not found" indicates that browser is unable to access Internet (or intranet).
Most likely you're sitting behind the corporate proxy server and in previous JMeter installation you had these proxy server details specified in system.properties file like:
http.proxyHost=10.20.30.40
http.proxyPort=3128
https.proxyHost=10.20.30.40
https.proxyPort=3128
Double check with your network administrator if this is the case, if yes - take steps from Using JMeter behind a proxy User Manual chapter.
You can also try out JMeter Chrome Extension as an alternative solution - in that case you don't have to worry about proxies and SSL certificates substitution.
I am currently implementing a single signon solution for a customer that is based on Java, Tomcat and Kerberos.
Users are to access the URL of an intranet Tomcat application from their client browsers, the Tomcat application acquires the users' credentials via Kerberos and redirects them to the actual web application.
Our customer's environment is a typical mixture of a Windows AD server acting as the KDC and Linux Tomcat application servers. The SSO functionality is supposed to be used from both Windows and Linux clients. This is what appears to be different from most answers I can find on the net where people have Linux web application servers but only use Windows clients.
Now, in my local setup I get some strange behaviour. My development environment is a Tomcat 7.0.26 running from MyEclipse 8.6 under Windows 7. My test environment is a Tomcat 7.0.26 or 7.0.53 behind an Apache web server on a Centos 6 machine. I have set up the AD server correctly, generated the necessary keytab files etc. and everything is running smoothly in the development environment. I can access the Tomcat application from both Linux and Windows clients using IE and Firefox, Kerberos authentication proceeds and I get redirected properly.
When deploying the Tomcat application on the test server this keeps working when trying to sign on from Windows clients. However, when I try to access the test server from a Linux client (I have tried from Linux Mint 13 and Ubuntu 13.10), I get the following error:
javax.servlet.ServletException: GSSException: No credential found for: 1.3.6.1.5.2.51.3.6.1.5.2.5 usage: Accept
net.sourceforge.spnego.SpnegoHttpFilter.doFilter(SpnegoHttpFilter.java:233)
I have to admit that I do not properly understand this message. Does it point to a problem with the credentials supplied by the client or a problem with the application server negotiating with the KDC? I have done some research on this problem and have found out that the indicated oid 1.3.6.1.5.2.5 stands for GSS_IAKERB_MECHANISM and not GSS_KRB5_MECHANISM or GSS_SPNEGO_MECHANISM which I find strange. Also, nobody else appears to have exactly the same problem.
I have tried switching from MIT Kerberos to Heimdal Kerberos and back. I have tried Firefox and Chromium, on the application server I have switched between Tomcat 7.0.26 and 7.0.53, the problem still persists. I am using the latest spnego.jar.
Now: Calls from Linux to the Tomcat running on the Windows development machine succeed and calls from Linux clients to the Linux application server fail with the same error message for both browsers tried.
Any ideas on this one?
GSS_IAKERB_MECHANISM means that the client is not able to determine the realm/kdc to create a service ticket and asks the server to serve as an intermediate to the target KDC. Check Wireshark traffic. Your task now is to analyze why the client is not able to create a service ticket for that SPN. I have observed this issue on Heimdal on FreeBSD with Microsoft KDC.
So the problem ist not your Tomcat instance.
the error when I go to localhost:8080 in browser:
I have tried the following by searching on google and stackoverflow but still the same error shows up:
Restart PC to end all the servers shutdown.
Manually shutdown all servers from the Windows Services
Also Provided the Full control access pertaining to the "no output folder" issue
Note: I am yet to start learning jsp and all Java EE stuff. I am on initial stage where one downloads the apache tomcat server and runs the hello world application.
Reinstall Tomcat. There is something fundamentally wrong with your installation. Tomcat is pretty basic and runs "as is" out of the box, with no configuration, so something has happened to your installation. It is much easier to just reinstall it than to try and fix it.
We are currently evaluating upgrading from XP to Windows 7, but have one last sticking point, we can't seem to run our Java RMI application from Windows 7.
I'm using the same JRE / Classpath from both machines, is there any other gotcha's that I'm missing?
Update
I have run Wireshark on both machines, and it appears the Windows 7 box makes the request, but the response coming back from the server fails with
Trans2 Response, QUERY_PATH_INFO, Error: STATUS_OBJECT_PATH_NOT_FOUND
any ideas where I go from here?
Update 2
I have created a fresh XP installation (gotta love virtual machines) and the application runs without a problem, clearly something has changed in Windows 7
Update 3
We've created a fresh Windows 7 install, in the same datacenter as the server and that connects fine, so my friendly(!) network admin needs to sort out his network, definitely looking like a firewall issue somewhere. Thanks to all (especially Lucian) for all the time you've spent on this.
Did you unblock the port you use for your application's RMI?
I remember having this problem once.
The default port for RMI is 1099 if I remember correctly, but you can set that in the command line.
Edit:
Are sections A.3 or C.4 from here or section 6.0 from here of any help?
Edit2:
Here's a link to an access permissions thread related to the response found with Wireshark.
In case this helps anyone in future, there was a "Policy Map Inspection" on our Cisco router, we disabled "inspect skinny" and everything works. Cisco Tech note this was stopping all returning RMI traffic before it made it to the firewall, so was very hard to debug.
I have Tomcat 5.0.30 installed as a Windows service. This service is starting perfectly fine. However when I try to restart or stop the service from the Windows services console, I'm getting the following error:
*
Could not stop Tomcat service on Local Computer. Error 1053: The
service did not respond to the start
or the control request in a timely
fashion
*
I recently upgraded to Tomcat 5.0.30 from 5.0.28 and earlier this was working perfectly fine. Its the latest version that's causing this issue. Google wasn't of much help.
Does anybody have any clue as to why this is happening?
Are you positive that you have removed all references to the old version. I found a similar problem once when the service was referring to the old version. I had to uninstall it and reinstall the service to pick up the new version.
I would suggest try starting tomcat from command line and then press control + C and see if it stops. I guess its hanging that is why giving error. If that is the case than try again by switching on logging at DEBUG level and see if anything in the logs. Still no clue then you can take thread dump and analyze to see what threads are hanging.