JRun

[MAME]

Originally posted by: JasonClark
I've restarted the box that was dead. I've also written a .NET windows service that will check each server and restart it if there is an error. That should "fix" this until we move to fusetalk .NET version that they are releasing this summer.

uh....it still doesn't work



and it appears to only happen at night, why?

 

[Don Vito Corleone]

Originally posted by: MAME

and it appears to only happen at night, why?

In all fairness, it has been sucking hard since late afternoon in PDT.

 

[n0cmonkey]

Originally posted by: MAME

Originally posted by: JasonClark
I've restarted the box that was dead. I've also written a .NET windows service that will check each server and restart it if there is an error. That should "fix" this until we move to fusetalk .NET version that they are releasing this summer.

uh....it still doesn't work



and it appears to only happen at night, why?

Kids got out of school...

 

[Freewolf]

It's the worst I seen yet tonight

 

[ProviaFan]

I'm sorry, but this reboot script thing works about as well as watercooling your computer by sealing it with silicone sealant and filling it up with dihydrogen monoxide. :roll:

In other words, I'm now having to refresh on average of 60 to 80 times just to get any single freaking thing to load. :frown:

 

[ProviaFan]

I'm sorry, but this reboot script thing works about as well as watercooling your computer by sealing it with silicone sealant and filling it up with dihydrogen monoxide. :roll:

In other words, I'm now having to refresh on average of 60 to 80 times just to get any single freaking thing to load. :frown:

 

[MAME]

Originally posted by: Don_Vito

Originally posted by: MAME

and it appears to only happen at night, why?

In all fairness, it has been sucking hard since late afternoon in PDT.

ok, well afternoon to night

 

[ProviaFan]

Well, it seems that I'm only having to refresh 10 to 20 times to get stuff to work, as opposed to 300 or 400 (famous last words, I'm sure). :Q

 

[Jeff7181]

Just drop FuseTalk all together and use something with a more streamlined look. I don't think any of us ATer's care to have a "pretty" message board.

 

[Dennis Travis]

I am waiting patiently for someone here to blame the AMD Opterons for this problem or the Dual AMD's that run the forms. Come on, don't let me down. Blame it all on AMD and say if the Database and Forms servers had Intel with Faster Internet the Jrun would not happen. Come on, make my day and bash AMD and blame it all on the Opterons and say that AMD is unstable, will not run all apps and even has Silicon that deteriorates over time and goes slower and slower.

Anyone who does blame AMD should get out of computers and get out of the house more.

And come on, Jason is doing a great job. He put up test forms and told us to come check them out, this JRun issue did not show up there. I think it's all the load here on the forms. Give Jason a chance, it's some Macromedia bug that did not show up till it was installed here with so much activity. Give him a break, He will figure it out. Otherwise the new forms are first rate. I very much like the new interface. It's not Jason's fault this happened. The test forms he had up did not have the activity so this did not show up. Give the guy a break. He WILL solve it, that I am very confident.

Jesh, People.

 

[Sunner]

Originally posted by: n0cmonkey
Fusetalk tricked me. I got through 2 links without a JRUN error then F5ed for about 30 seconds.

Fusetalk is proving my point about how horrible Macromedia is.

Doesn't help the Windows guys make their arguments either.

No but stuff like this helps me whenever I feel like making fun of our Windows guy here at work

 

[n0cmonkey]

Originally posted by: Sunner

Originally posted by: n0cmonkey
Fusetalk tricked me. I got through 2 links without a JRUN error then F5ed for about 30 seconds.

Fusetalk is proving my point about how horrible Macromedia is.

Doesn't help the Windows guys make their arguments either.

No but stuff like this helps me whenever I feel like making fun of our Windows guy here at work

And AMD fanboys.


Disable OT, it might fix the problem.

 

[Adul]

jrun 1 - Forums 0

 

[WTT0001]

Jrun is back again with a vengence

 

[Amused]

This time it's worse than ever before! :|

 

[lobadobadingdong]

Originally posted by: JasonClark
Yeah its a random thing, might update the JVM and see what shakes.

I increased my security settings in IE and now I get them 4 or 5 times for every page I hit on the forums, strange thing though I lowered them again and no change.

 

[wischeez]

Help, I'm getting bombarded with JRUNS!!!! Does Imodium AD work for these????

 

[Jason Clark]

We're throwing some more memory in the forums today, which should alleviate the problem. It looks like we're running out of memory, and we're doing all we can to combat this.

1) this has nothing to do with fusetalk.
2) we're doing everything we can to combat the issue.
3) we're moving to fusetalk.net soon, we are tired of the JRUN issues as well.

Cheers.

 

[aphex]

Originally posted by: JasonClark
We're throwing some more memory in the forums today, which should alleviate the problem. It looks like we're running out of memory, and we're doing all we can to combat this.

1) this has nothing to do with fusetalk.
2) we're doing everything we can to combat the issue.
3) we're moving to fusetalk.net soon, we are tired of the JRUN issues as well.

Cheers.

Thanks for the update bro! Hope it all works out....

 

[RalfHutter]

I couldn't even get on the forums for a few hours this AM. Kept relaoding to no avail. Hope the extra memory helps this.

 

[Jason Clark]

It's just as frustrating here, trust me. I've spent countless hours debugging and looking at logs from JRUN. Not a single error, the only consistent thing is that memory is low when it dies. Why it doesn't release some, I don't know. Anyway another 512 is going in today.

 

[BDawg]

Originally posted by: JasonClark
It's just as frustrating here, trust me. I've spent countless hours debugging and looking at logs from JRUN. Not a single error, the only consistent thing is that memory is low when it dies. Why it doesn't release some, I don't know. Anyway another 512 is going in today.

Seems to be working now...that was a painful 12 hours.

 

[Don Vito Corleone]

Originally posted by: JasonClark
It's just as frustrating here, trust me. I've spent countless hours debugging and looking at logs from JRUN. Not a single error, the only consistent thing is that memory is low when it dies. Why it doesn't release some, I don't know. Anyway another 512 is going in today.

Thanks for your hard work in support of the forums! As I said above, I'm sure many members (including this one) would be happy to subscribe to help defray the costs, if the option were still offered.

Urge to kill fading . . . fading . . . fading . . .

 

[DurocShark]

Why are the new FuseTalk's system requirements so much higher than the last version's?

<---misses having to code for 64k Commodore machines.

 

[Jason Clark]

FuseTalk doesnt really have any higher requirements, but we were using CF5 before. FuseTalk is written for CFMX now as CF5 is gone, so we had to develop for the new platform. Our .NET version is 80% code complete, and so far is very very quick.. We're moving to it once it is released.