Re: unable to send multiple messages simontanously
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 would Google tuning IP stacks for your particular OS and concentrate on upping your allowed sockets and setting your socket timeout/wait to 1 second. If you are sending all these calls from a single client, you may need to do this on the client too. Jeff On Mar 14, 2009, at 7:53 AM, Nagesh wrote: Hi All, I am testing the server load by trying to send multiple messages simontanously. I am trying to create the 100 sessions and trying to write messages to those 100 session with a second gap. but it starts sending up to some time after that it does not give any exception and stops sending messages. can any one suggest me what might be the problem and possible solution to it. any help is highly appreciated. Thanks, Ajay.
[jira] Created: (DIRMINA-673) Build produces invalid jar file
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 build step for adding license files via the ant zip task produces invalid jar files because the manifest is not guaranteed to be the first file in the archive (part of the jar spec). This is affecting deployment in OSGi containers and any other code that uses JarInputStream to read the manifest prior to deployment because it expects the manifest to be the first file in the archive. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-673) Build produces invalid jar file
[ 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 ant zip task to explode and recreate the jar file. This patch removes the rather clunky ant task to move the ASL 2.0, jzlib, ognl, slf4j, and springframework into each jar file after it is built. I don't think these 3rd party license files are necessary in *each* jar file and should only be necessary in the larger assembly archives because that is the only download that includes them. This patch makes use of the remote-resources plugin that inserts all of the required ASL LICENSE and NOTICE files in the jars and just includes the 3rd party licenses in the assembly archive. This patch also creates mina-legal and mina-parent modules in order to work around some cyclic dependencies but this is very normal in many maven projects these days. This is a large patch so let me know if there is anything I can change to suit you. 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 Attachments: DIRMINA-673.patch The build step for adding license files via the ant zip task produces invalid jar files because the manifest is not guaranteed to be the first file in the archive (part of the jar spec). This is affecting deployment in OSGi containers and any other code that uses JarInputStream to read the manifest prior to deployment because it expects the manifest to be the first file in the archive. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRMINA-673) Build produces invalid jar file
[ 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 --- 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 Attachments: DIRMINA-673.patch The build step for adding license files via the ant zip task produces invalid jar files because the manifest is not guaranteed to be the first file in the archive (part of the jar spec). This is affecting deployment in OSGi containers and any other code that uses JarInputStream to read the manifest prior to deployment because it expects the manifest to be the first file in the archive. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DIRMINA-674) Mina xbean module requires mina-core for compile scope
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: 2.0.0-M4 Reporter: Chris Custine The mina-integration-xbean module has mina-core but scope is set to test even though there are classes required for compilation. This happens to work with Maven 2.0.x but I think it is coincidence. This will be broken with soon to be released Maven 2.1. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-674) Mina xbean module requires mina-core for compile scope
[ 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 what the heck. This will allow the entire build to work with Maven 2.1. 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: 2.0.0-M4 Reporter: Chris Custine Attachments: DIRMINA-674.patch The mina-integration-xbean module has mina-core but scope is set to test even though there are classes required for compilation. This happens to work with Maven 2.0.x but I think it is coincidence. This will be broken with soon to be released Maven 2.1. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRMINA-674) Mina xbean module requires mina-core for compile scope
[ 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 -- Key: DIRMINA-674 URL: https://issues.apache.org/jira/browse/DIRMINA-674 Project: MINA Issue Type: Bug Affects Versions: 2.0.0-M4 Reporter: Chris Custine Attachments: DIRMINA-674.patch The mina-integration-xbean module has mina-core but scope is set to test even though there are classes required for compilation. This happens to work with Maven 2.0.x but I think it is coincidence. This will be broken with soon to be released Maven 2.1. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
