I have been testing Atmosphere on WAS Liberty, and it is all working fine on Liberty 8.5.5.4.
When I try to upgrade to Liberty 8.5.5.5 or 8.5.5.6, there is a 1 min delay on the initial connection.
The problem can be easily replicated by downloading the atmosphere-chat-2.3.3.war from maven central. Rename to atmosphere-chat.war, change the application.js to have transport = 'long-polling'. Copy modified war in liberty dropins folder. Start server, go to http://localhost:9080/atmosphere-chat/
I think this might be a bug with async processing in Liberty, but maybe the Atmosphere or IBM guys know better. I can't quite figure it out, so I am staying on 8.5.5.4 for now.
If anyone can shed some light. It would be great.
Setting
AtmosphereConfig.PROPERTY_USE_STREAM=false
works around the issue for now.
Related
I have a meteor webapp that has been around for a few years. It hasn't been updated particularly often and thus the version is little bit old (Meteor 1.6.1.4), however it runs locally without an issue and I currently have a version of it it deployed without issue on a Digital Ocean droplet with Mongo on AtlasDB and the DNS on Cloudflare.
However I've been running into an issue deploying updates with the Meteor Up (MUP) tool. On my production server when I run mup deploy with my latest code the deployment works and validates successfully, however the live site now loops on page load. The page completes the load (including a call to Stripe API front end library) and the images load and as soon as that has happened the same page is loaded again over and over. This happens on each page of the webapp. There are no errors logged in the console.
I'm almost sure this isn't a codebase issue as I have a staging version of this same app running on an identical spec droplet which I can deploy to without issue. The only difference between the production and staging is that the staging uses a LetsEncrypt cert generated by MUP and production uses a Cloudflare issued cert. I can't remember exactly the reason for this as it was the outcome of my last round of troubleshooting, which did result in a successful deployment. The LetsEncrypt configuration with MUP seemed to be problematic when I last set everything up. Either way there is no obvious good reason why this error should occur.
So I think that the issue is most likely something to do with Cloudflare, however I don't have many clues as to what. I've tried clearing the full cache after deploying. I cannot disable the Cloudflare proxy as I get unsecure error.
For my next steps I'm thinking of setting up another staging droplet but with Cloudflare in front in the same way, to see if I can get a non-critical replicable version of the same error. From there I'm not sure what I would do to debug and fix. I was also wondering if configuring a load balancer for this webapp might be smart at this moment, though if in an SSL passthrough I wonder if it would not solve the underlying issue. This would also not necessarily be answering this question but rather just avoiding it. I'm also considering trying to update the version of the Meteor app as far as I can to see if there is any chance that codebase is part of the issue.
Any suggestions?
I have a widget and a page layout that are not working as they should on the development server. The development server is hosted on Azure. On my local machine, it is working properly. I'm at a lost on what the issue is.
Does anyone have any suggestions on what to check/test? Is there any way I could test/debug this better?
I reached out to Sitefinity to support and they pointed me in the right direction. I inadvertently had the wrong namespace in the widget. Unfortunately, the widget didn't display an error message. I had to go to the log files to find the issue.
Whew...ok, been wrestling with this for a while and I can't figure out what is going on.
I am new to Azure caching, but at this point I have read a good bit and I think I have it setup right, but something is obviously wrong so what do I know?
Ok, so first I setup a dedicated caching web worker role using this fine tutorial: http://berniecook.wordpress.com/2013/01/27/distributed-caching-in-azure-cache-worker-role/
I have an ASP.net MVC 4 website that is supposed to be using it.
I have my solution set to multiple starting projects with my cloud caching project set to start first, but no matter what I do, I get the "role discovery data is unavailable".
Sometimes in my output log I get that the Role Environment failed to initialize, but not very often. Most of the time the output log says that is succeeds. Regardless of that, I still get the error above.
I was thinking that maybe the issue was because I was running on local azure storage and compute emulators, so I reconfigured and published the Cloud Service to Azure to see if that helped.
It didn't...
The fun part is that there have been exactly 2 times when it suddenly worked (both when I was working locally). 2 times about of about 100. I didn't do anything different...just ran the debugger and poof, it all worked. This at least lends a bit of credit that it is actually setup correctly.
Needless to say, this is putting a huge damper on my productivity so any advice would be appreciated.
Update
Ok, I have figured out a workaround of sorts...I have learned that the reason that it consistently failed was because the development web server was holding onto a file which prevented the caching server to launch correctly.
The workaround is to stop the web server each and every time I want to recompile and run the code. This is obviously not ideal, so any ways to make this more reliable would be appreciated.
Thanks,
David
I don't know if this helps but I find that if I don't shut down the both the storage and compute emulator, I get weird errors, so after doing an F5 and closing the browser down, I manually shut down both emulators
This is with GF 3.1.1 build 12.
I have a JSF 2 web application that uses EclipseLink 2.3.0 as the back end JPA provider. You can see the deployment here.
When I use the admin console to redeploy, it uploads the WAR file just fine, then all hell breaks loose. As soon as someone accesses a page the log fills with exceptions usually related to attempting to do operations on a closed EntityManager. If I let it go on, GlassFish degenerates and pretty much crashes -- I can't get any response anymore on the admin port.
If I do a reload, then it seems to work OK. So my question is, what kind of application can do a redeploy without a reload? Is there something I can do to my application to let do a smooth transition from one version to the next?
I have this problem and did not find in the site a case like mine.
Here is the thing.
I created a TFS 2008 with the scrum template (Conchango). It was a clean install (a fresh OS, a fresh SQL Server, a fresh machine, etc…). So everything worked like a charm.
I created 3 Scrum repositories, assigned permissions, uploaded files and so on… 3 teams started working on them, and everything was super!
Up to this point the server only had 3 scrum repositories and nothing else.
Then, I had to create a new repository, but with the CMMi template (the one provided with TFS).
Again everything works (the Sharepoint site, the source control, documents..) … BUT…. Reports stopped refreshing!!!
Does anybody know how to fix it?
Any help will be really appreciated
Should you need more info please let me know
Found someone with the same problem, reports do stop working after adding CMMI project :)
The following link has an explaination of how to fix it:
http://blog.salvoz.com/2008/01/26/TFSWarehouseIssues.aspx
First of all, you didn't create a new repository. You created a new team project.
Secondly, the trick is to go find out why the reports stopped refreshing! There's no well-known bug, "reports stop refreshing when adding a CMMI Team Project: here's what to do". You'll need to go look on the database tier server and see if there are any problems listed in the event logs or the SQL Server logs. Then track it down.
I had one situation where Analysis Services crashed, restarted and crashed again - because I hadn't set up operator notification. It's necessary to look, in order to see.