I'm actually in a nightmare. My webapp uses websockets for the chat and here comes the problem:
Using Glassfish 4.1u13 everything worked fine, until I activated the Access Log Monitoring. since that, every ws request was made 2 times and the web socket couldn't did the handshake.
https://java.net/jira/browse/GLASSFISH-21007
Tried to update to glass fish 4.1.1 -> problem PERSIST
Tried to switch to Payara 4.1.1.115 (which is a patched version of glassfish) and everything went smooth. I could now have websockets AND access logging in my Glassfish instance.
Some minutes after noticed that when I reload the page, not always the communication between client app and server were done.
Inspect network -> handshakes correctly but can't exchange data.
On server side then, I made 2 system out: one in the filter of the request servlet and one in the websocket endpoint.
Every request arrives to the server and do the handshake BUT sometimes #OnOpen will not be called, even if the wss is upgraded to 101. How's that possible? tried to update to Tyrus 1.12 (payara uses 1.11) and also downgrade it to 1.8.1 (which is the version used by functioning Glassfish 4.1u13) but nothing happens.
How I can debug this behaviour?
This was a bug which was raised against Payara (Github issue #536) and has now been fixed.
The fix has been released in Payara version 4.1.1.161, which is available for download.
Related
I have attempting to upgrade a web application that uses .NET Framework 4.5 to 4.8.
The application runs on a server that both compiles and runs the application, so I installed the .NET Framework 4.8 Developer Pack. I restarted the server and it has booted up successfully.
TeamCity successfully built and compiled the application and Octopus successfully deployed as per usual. However, when I now attempt to access the website, I get a 404 at the login page.
Looking at the folder structure, the file is definitely there. The code builds and runs successfully on my local machine, allowing me to login and perform any function on the system.
Is there something that I have missed running or doing on the server to get this to work?
Edit: Request for IIS Configuration
The configuration of this hasn't changed since I've upgrade the .NET Framework but here is what I have. If this isn't the configuration that is being asked about, please let me know.
Bindings
Everything else has been left as the default values.
In our install4j installed application we use HttpClient (Apache) with "useSystemProperties" to perform http requests. Up until v9.0 of install4j that meant windows proxy settings were automatically applied. However, since 9.0.4 this no longer works (probably since 9.0.1 since proxy handling was reworked there, but I haven't been able to verify this). The installer itself still detects proxy settings (update check uses the proxy as before), but they are no longer "forwarded" to the installed application.
Is there a way to turn this "forwarding" back on?
In install4j 9.0.1+ the proxy settings are no longer available as system properties.
On Windows, install4j 9.0.1+ uses native code, not Java sockets for HTTP requests. To force the use of Java sockets you can set the VM parameter
-Dinstall4j.noWinInetConnection=true
The auto-detected proxy that is used for the connection can then be obtained from
com.install4j.runtime.installer.helper.content.ProxyHelper.getProxyHostInfo(url)
I have ran into something interesting. We are upgrading our SAP BO from 4.2 SP2 to 4.2 SP5. So we have a java application which runs on JBoss connects to the BO reports.
So as part of upgrade I have updated all my SAP jars and tried connecting to the new CMS. To test out initially i used the below code and ran it using main method I was able to connect to the CMS and get the Session.
ITrustedPrincipal trustedPrincipal = sessionMgr.createTrustedPrincipal("user1", "myCMS:6400");
session = sessionMgr.logon(trustedPrincipal);
But when I run the same code on JBoss, I get
Could not reach CMS 'myCMS:6400'. Specify the correct host and port
and check for network issues
Can some one please suggest what I am doing wrong?
I have started working with ZK recently. I really like the framework but I am having a lot of problems in configuring it to work correctly with Websphere Application Server v8.0. Namely, I am developing an EJB application with accessing the database via JPA entities and using the ZK framework for GUI. I am developing the application using the Rational Software Architect 8.5.
When I start working on a fresh ZK project in a fresh workspace and server profile everything seems to be working correctly. However, after some time I start having strange problems. I think the problem occurs in the moment when ZK tries to initialize my ViewModel class. I do not get any exceptions or errors, but get the timeout message in my browser: "The page or component you request is no longer available. This is normally caused by timeout, opening too many Web pages, or rebooting
the server."
My ViewModel initializes by resolving the EJB bean I am using for business logic. That normally works, but as I said, after working for some time on the project, or after restarting my computer the ViewModel object cannot get initialized and the timeout error appears no matter what I do (when ZK tries to bind a variable or when I fire an event needed to be handled by my ViewModel. As before, I do not get any additional errors or exceptions.
Has anybody already had this problem? Is there a solution? Can I change the configuration of my server or ZK to avoid this problem?
Thank you.
Seems that I have solved the problem myself. I was using internal Rational Software Architect (Eclipse) browser which apparently has problems handling ZK sessions. When I switched to Firefox, the problems I explained stopped appearing.
I'm working with Google App Engine in Eclipse w/ JSP pages in Windows 7.
I already have an app deployed and working, but I am unable to make changes to it for some reason.
If I make changes and debug locally, my localhost page is showing the changes that I implement.
While I am not getting any errors in the deployment, the same changes that work on my local debug are no longer showing up, so I can't update my app.
I thought updating the version number might help, but I had no luck with this.
Any ideas? Thanks.
Are you deploying the same version (as specified in appengine-web.xml) as the default version that is running on your app? If not, you'll have to access your new deployment at http://newversion.appname.appspot.com, or change your default version in app engine to your newly deployed version.
I have had the same problems too, especially when the changes concerned the static pages. Some little things to check:
If you have set an expiration date in your app.yaml, your browser cache could be holding the file.
If it’s specific to the online contents, it could be an intermediary cache (such as a squid server) serving the outdated contents, in which case you’d have to flush the cache to get the new version.
You could start by checking the log on the GAE console to see if the request is received by the server, that would help you debug.
Another trick, if you’re being served an outdated version of http://yourapp.appspot.com/index, try and pass a dummy argument to force the browser to update the version, for instance : http://yourapp.appspot.com/index?p=1