This is usually caused by an un-tuned IP stack in your OS. These
symptoms usually occur when you have hit the max sockets. You
generally hit this limit because your socket timeouts are set too high
(it can be 30-60 seconds by default before the socket is released back
to the OS).
I
Build produces invalid jar file
---
Key: DIRMINA-673
URL: https://issues.apache.org/jira/browse/DIRMINA-673
Project: MINA
Issue Type: Bug
Affects Versions: 2.0.0-M4
Reporter: Chris Custine
The
[
https://issues.apache.org/jira/browse/DIRMINA-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12682213#action_12682213
]
Chris Custine commented on DIRMINA-673:
---
The main cause of this is the use of the
[
https://issues.apache.org/jira/browse/DIRMINA-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Custine updated DIRMINA-673:
--
Attachment: DIRMINA-673.patch
Build produces invalid jar file
Mina xbean module requires mina-core for compile scope
--
Key: DIRMINA-674
URL: https://issues.apache.org/jira/browse/DIRMINA-674
Project: MINA
Issue Type: Bug
Affects Versions:
[
https://issues.apache.org/jira/browse/DIRMINA-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12682214#action_12682214
]
Chris Custine commented on DIRMINA-674:
---
Yeah, I know... this is a dumb patch but
[
https://issues.apache.org/jira/browse/DIRMINA-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Custine updated DIRMINA-674:
--
Attachment: DIRMINA-674.patch
Mina xbean module requires mina-core for compile scope
