|
Out of curiosity, was the server restarted
between the last time it didn’t work and the time it did an hour
later? If so, you may have some heap size issues (java could be running
out of memory) or connection pooling issues. I have had both of these
bring a server to its knees (no fault of FDS, just the way things work). Something
to also look for is the logging section in the services-config.mxml.
(below) . Main thing to look for here is if your logging level is set to
anything other than Error, maybe Info or Debug. I have seen this cause me
memory problems on WebSphere 6 when the heap size was only 128 min. I
bumped my heap up to 256 min and that helped a ton. You could also set
the logging back to Error, but that only bandaids the real issue, java loves
memory J You will probably end up having to increase the 128 default
eventually. GL! <logging>
<target class="flex.messaging.log.ConsoleTarget"
level="Error"> ...
</target> </logging> From:
[email protected] [mailto:[EMAIL PROTECTED] On Behalf Of ryan harlin Does
anyone know why (or has anyone had a similar -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com YAHOO! GROUPS LINKS
|
- [flexcoders] FDS sporadically works, but why? ryan harlin
- RE: [flexcoders] FDS sporadically works, but why? Dustin Mercer
- RE: [flexcoders] FDS sporadically works, but why? ryan harlin
- RE: [flexcoders] FDS sporadically works, but wh... Cathy Reilly

