|
Well , The flex.log file just
has this entries: 02/17 11:11:07 DEBUG
configuration service started. 02/17 11:11:07 DEBUG
logger services started. 02/17 11:11:07 INFO
License Service: Flex 2.0 Trial Edition enabled (beta period ends May 1, 2006) 02/17 11:11:07 DEBUG Flex:
License services started. 02/17 11:11:14 DEBUG
Initial setup: 453ms 02/17 11:11:17 DEBUG
Loaded 8 SWCs: 2438ms 02/17 11:11:17 DEBUG
License Service: Flex 2.0 Developer Edition enabled (beta period ends May 1,
2006) 02/17 11:11:17 DEBUG
Compiling... 02/17 11:11:48 DEBUG
Files: 626 Time: 31452ms 02/17 11:11:49 DEBUG
Linking... 297ms 02/17 11:11:54 DEBUG
Optimizing... 5484ms 02/17 11:11:55 DEBUG SWF
Encoding... 500ms In the server-out.log is
growing, even if the samples don’t update. (2 last calls, they are
all the same) [Flex] Executed command:
service=message-service commandMessage: Flex
Message (flex.messaging.messages.CommandMessage) operation: poll messageRefType:
flex.messaging.messages.AsyncMessage clientId:
1D421B33-9F0C-0EDC-A925-02830F909A2B correlationId: destination:
chat-topic-jms messageId:
F71EBDE9-8A26-43B2-6822FFFFFFFF5C11 timestamp:
1140177214653 timeToLive: 0 body: {} replyMessage: Flex
Message (flex.messaging.messages.AcknowledgeMessage) clientId: 1D421B33-9F0C-0EDC-A925-02830F909A2B correlationId:
F71EBDE9-8A26-43B2-6822FFFFFFFF5C11 destination: null messageId:
1DD977C7-DA1D-83A2-5AAA-2B26D07C5CD0 timestamp:
1140178779770 timeToLive: 0 body: null [Flex] Executed command:
service=message-service commandMessage: Flex
Message (flex.messaging.messages.CommandMessage) operation: poll messageRefType:
flex.messaging.messages.AsyncMessage clientId:
1D421B33-9F0C-0EDC-A925-02830F909A2B correlationId: destination:
chat-topic-jms messageId:
BC8D80AA-C434-6822-512DFFFFFFFFB570 timestamp:
1140177214653 timeToLive: 0 body: {} replyMessage: Flex
Message (flex.messaging.messages.AcknowledgeMessage) clientId: 1D421B33-9F0C-0EDC-A925-02830F909A2B correlationId:
BC8D80AA-C434-6822-512DFFFFFFFFB570 destination: null messageId:
1DD993F1-5310-9525-FF55-E99AC66A735B timestamp:
1140178782723 timeToLive: 0 body: null BTW, my java.args are java.args=-server
-Xmx512m -Dsun.io.useCanonCaches=false -XX:MaxPermSize=128m -XX:+UseParallelGC
-DJINTEGRA_NATIVE_MODE -DJINTEGRA_PREFETCH_ENUMS
-Dcoldfusion.rootDir={application.home}/ -Djmx.invoke.getters=true João Fernandes Programador
Informático From:
[email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Chotin May be a heap problem,
can you try turning on some of the debug logging in
flex-enterprise-services.xml and see if anything comes out when you hit it
after he idle? From:
[email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Dustin Mercer Sounds like a memory
issue… possibly… we were seeing the same types of odd issues until
we bumped the heap size up. Give that a try and see if it helps J Dustin Mercer From:
Hi there, I have deployed samples apps in a J2EE server
instance (/samples, /flex and /flex-admin). I opened the samples with no problem but after some
idle time, all the apps stopped to work. For example the dashboard, after this
idle time (+- 30 min) no message was sent.. Even if I refresh the application, it’s not
working. I have to restart the server instance to have them to work again. Is this a known issue? Regards, João Fernandes Programador
Informático
|
- RE: [flexcoders] Flex Enterprise Services (Messaging probl... João Fernandes
- RE: [flexcoders] Flex Enterprise Services (Messaging ... Matt Chotin
- RE: [flexcoders] Flex Enterprise Services (Messaging ... João Fernandes
