Hi all,
Thanks for all your hard work! I'm currently working with MINA 1.1.x,
Spring, JMX and Maven 2. Recently, I introduced MXBeans into my project
while I found out that Spring doesn't support MXBean well until the 2.5
version. But Mina 1.1.x is depending on Spring 2.0.6, that really
Luis Neves wrote:
Hi,
Emmanuel Lecharny wrote:
You have plenty of tools to analyze a OOM. Either a commercial tool,
or free tools. Just googling for 'Memory leak java analyzer' will
bring a lot of those guys, like
http://www.manageability.org/blog/stuff/open-source-profilers-for-java.
I'm
OOps,
incorrectly accepted this message which has been sent to
[EMAIL PROTECTED] Forwarded to the correct ML...
On Dec 26, 2007 3:56 PM, sdivin [EMAIL PROTECTED] wrote:
i develop a socket serer based on mina , after run a long time ,when the
client send the request messsage to the server
can you help me ?
i develop a socket server based on the MINA, all the client
send the request message to the server ,the server will send the
response message to the client ,
but after run some days , when the client send the message to the
server ,the client can not receive the
Is there any reason to not be able to write a FileRegion to
ProtocolEncoderOutput in addition to an IoBuffer?
-geoff
NioProcessor.transferFile needs to catch IOException on Linux
-
Key: DIRMINA-503
URL: https://issues.apache.org/jira/browse/DIRMINA-503
Project: MINA
Issue Type: Bug
Did you get your problem fixed?
On Dec 22, 2007 12:36 AM, Steve Johns [EMAIL PROTECTED] wrote:
Try your own client with Sumup server and see if it works. If NOT,
something wrong with your client. If YES, try to find out what happens in
ExceptionCaught().Good luck!
On Dec 21, 2007 11:22 AM,
Are you saying Mina API Interface WriteFuture example is NOT a proper one?
Thanks.
On Dec 18, 2007 3:14 PM, Trustin Lee [EMAIL PROTECTED] wrote:
Hi Qi,
It's not a bug but a kind of dead lock caused by misuse of the API.
You are usually not supposed to call IoFuture.join() within an
Hey guys,
I was hoping to see if we could discuss some of the final qualifiers
on some of the methods in the AbstractIOSession. The reason I ask is it
would be cool to be able to override some of the methods such as:
public WriteFuture write(Object message)
public final int
I like it (the assert) ;-)
But I am not sure about having a completely different
AbstractIOMockSession since we would then be copying code to a certain
degree. I think it would just be cleaner to have the methods protected
so there is no need for code duplication ;-)
What do *you* think? ;-)
Jeff Genender wrote:
What do *you* think? ;-)
Beside the assert, which was a side effect of my quick glance at the
method you want to override, I think that dooming the final is sane.
If someone needs to protect this method, then the best solution would be
to define a super class with
Hi Jeff and Emmanuel,
You can add some hook for IoSession.write() by inserting an IoFilter,
so I am not sure about removing the final modifier from write().
Overriding getScheduledMessages and getScheduledBytes makes sense
though because they will always be 0 because messageSent event will be
On Dec 27, 2007 7:57 AM, Steve Johns [EMAIL PROTECTED] wrote:
Are you saying Mina API Interface WriteFuture example is NOT a proper one?
Well, it depends on situation. It is sometimes more convenient to use
WriteFuture.join() and it will work as long as you have inserted an
ExecutorFilter in
Hi Hefm,
In such a case, you need to try to use a packet capturing tool such as
wireshark or tcpdump to see if the server has sent the data really and
to see if the client is receiving the data.
HTH,
Trustin
On Dec 27, 2007 12:05 AM, hefm [EMAIL PROTECTED] wrote:
can you help me ?
i
On Dec 27, 2007 4:14 AM, Geoff Cadien [EMAIL PROTECTED] wrote:
Is there any reason to not be able to write a FileRegion to
ProtocolEncoderOutput in addition to an IoBuffer?
It's an API flaw. It should be fixed. Thanks for the heads up!
Trustin
--
what we call human nature is actually human
Alternatively, we could add a protected method in AbstractIoSession
and make write() method to call it before returning. However, it is
essentially the same with adding an IoFilter IMHO.
The implementation of IoSession and IoFilterChain is not so trivial so
creating another mock object is a kind
I agree...this makes sense...Filter is the way to go.
Jeff
Trustin Lee wrote:
Alternatively, we could add a protected method in AbstractIoSession
and make write() method to call it before returning. However, it is
essentially the same with adding an IoFilter IMHO.
The implementation of
Hi Steve,
Would you mind explain a bit more on heartbeat ?
Cheers,
Qi
Steve Johns-2 wrote:
Most likely, either client or server didn't detect the disconnection.
Please
use heartbeat.
On Dec 26, 2007 11:05 PM, hefm [EMAIL PROTECTED] wrote:
can you help me ?
i develop a socket
18 matches
Mail list logo
