October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1114) JBoss Remoting fails under load

by Tim Fox (JIRA)

JBoss Remoting fails under load ------------------------------- Key: JBMESSAGING-1114 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1114 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.GA Reporter: Tim Fox Assigned To: Tim Fox Priority: Critical Fix For: 1.4.0.SP1 JBoss Remoting fails with various different errors when under extreme load. To replicate this, set up two clustered server nodes, using a MySQL database. These can both be on the same machine, using ServiceBindingManager. On a second machine run Ovidiu's messkit toolki, first to send some messages: mess -stat send -size 10240 50000 And then to receive them back using 50 concurrent consumers: mess -stat -sessions 50 receive all You will notice that JBoss Remoting fails with errors: I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease? I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary. It also seems remoting is continually timing out and recreating connections - this could also be a source of error. How do we configure remoting so it does not do this? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

2
3
0 / 0

[JBoss JIRA] Closed: (JBAOP-265) Aspectize Java array

by Stale Pedersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-265?page=all ] Stale Pedersen closed JBAOP-265. -------------------------------- Resolution: Done committed and tested > Aspectize Java array > -------------------- > > Key: JBAOP-265 > URL: http://jira.jboss.com/jira/browse/JBAOP-265 > Project: JBoss AOP > Issue Type: Feature Request > Reporter: Ben Wang > Assigned To: Stale Pedersen > Fix For: 2.0.0.beta2 > > > For AOP, we haven't dealt with Java array. Is it possible to provide interception for array? This is required if we need to instrument Java Collection, for example, since they uses array list for internal fields. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBBUILD-414) Mavenize security project

by Paul Gier (JIRA)

Mavenize security project ------------------------- Key: JBBUILD-414 URL: http://jira.jboss.com/jira/browse/JBBUILD-414 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - App Server The pom of the security project should be updated to fit project standards. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBREM-63) Get rid of the legacy configuration that embeds xml parsing

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-63?page=comments#action_12383509 ] Ron Sigal commented on JBREM-63: -------------------------------- org.jboss.remoting.transport.remoting.Connector can now be configured by way of an org.jboss.remoting.ServerConfiguration. ServerConfiguration holds four components: 1. transport (supplied by constructor) 2. invokerLocatorParameters: the is a map of all parameter names and values that will go into the org.jboss.remoting.InvokerLocator 3. serverParameters: this is a map of parameter names and values that will be used by the server but will not go into the InvokerLocator 4. invocationHandlers: this is a map of invocation handlers. The key is the subsystem, or comma separated list of subsystems. Note that parameter values in invokerLocatorParameters override values in serverParameters, if a parameter appears in both. ServerConfiguration may be used programmatically, but it is primarily intended to be constructed from a jboss-beans.xml file by a microcontainer and injected into a Connector. Unit test: org.jboss.test.remoting.transport.config.POJOConfigurationTestCase. Waiting for cruisecontrol results. > Get rid of the legacy configuration that embeds xml parsing > ----------------------------------------------------------- > > Key: JBREM-63 > URL: http://jira.jboss.com/jira/browse/JBREM-63 > Project: JBoss Remoting > Issue Type: Task > Affects Versions: 1.0.1 beta > Reporter: Scott M Stark > Assigned To: Ron Sigal > Priority: Blocker > Fix For: 2.4.0.Beta1 (Pinto) > > > I see that the org.jboss.remoting.transport.Connector is using the legacy mechanism of using an Element configuration as an attribute and doing the xml parsing within the code. This needs to be removed and replaced with JBossXB constructs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4889) jboss-vfs 2.0.0.beta5

by Kabir Khan (JIRA)

jboss-vfs 2.0.0.beta5 --------------------- Key: JBAS-4889 URL: http://jira.jboss.com/jira/browse/JBAS-4889 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: JBossAS-5.0.0.Beta3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-418) Figure out why iiop and jmx do not build from the aggregate app server build.

by Paul Gier (JIRA)

Figure out why iiop and jmx do not build from the aggregate app server build. ----------------------------------------------------------------------------- Key: JBBUILD-418 URL: http://jira.jboss.com/jira/browse/JBBUILD-418 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - App Server Currently the jmx and iiop modules build fine by themselves, but do not build correctly during the aggregate build with all the modules. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
6
0 / 0

[JBoss JIRA] Created: (JBBUILD-423) Fix microcontainer poms and metatdata in maven repository

by Paul Gier (JIRA)

Fix microcontainer poms and metatdata in maven repository --------------------------------------------------------- Key: JBBUILD-423 URL: http://jira.jboss.com/jira/browse/JBBUILD-423 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - Maint 2007 The 2.0.0.Beta4 release of microcontainer is missing metadata files, and the tag has the incorrect version in a couple places. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-79) Principal Mapping Modules

by Anil Saldhana (JIRA)

Principal Mapping Modules ------------------------- Key: SECURITY-79 URL: http://jira.jboss.com/jira/browse/SECURITY-79 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.1-BETA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1-GA We need Principal Mapping Modules via the Mapping Manager. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBAS-1357) Support for massive mbean counts

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1357?page=all ] Dimitris Andreadis closed JBAS-1357. ------------------------------------ Resolution: Won't Fix Assignee: (was: Scott M Stark) Re-open if there is real interest for this. > Support for massive mbean counts > -------------------------------- > > Key: JBAS-1357 > URL: http://jira.jboss.com/jira/browse/JBAS-1357 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMX > Affects Versions: JBossAS-4.0.1 Final > Reporter: Scott M Stark > > Creating thousands of mbeans seems to incur a very large overhead in memory that needs to be investigated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-1402) Transaction Recovery

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1402?page=all ] Dimitris Andreadis reassigned JBAS-1402: ---------------------------------------- Assignee: Adrian Brock Adrian, can we close this whole task & subtasks out-of-date, or do we keep the JCA tasks as still current? > Transaction Recovery > -------------------- > > Key: JBAS-1402 > URL: http://jira.jboss.com/jira/browse/JBAS-1402 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transaction Manager > Affects Versions: JBossAS-4.0.1 Final > Reporter: Adrian Brock > Assigned To: Adrian Brock > > Implement optional transaction recovery > The simplest mechanism is to do this is with a local database > using the last resource gambit where during its "prepare" it logs the XID in a table. > If this last resource fails to commit, recovery will not find the transaction > in the table which means it will rollback the whole transaction. > This has limitations where a different local resource is required within the transaction > but not this local database used as the recovery log. > Another implementation is a local file. Though more complicated it should give superior > performance. > But, it does not work well with the last resource gambit, e.g. you cannot tell > whether the jdbc commit() suceeded or failed if it crashes just at the point of this invocation > before the result is returned from the db. > The other work required: > 1) Possibly, simplify the dependencies in the JCA module so we can run the recovery earlier. > Currently the RARs need the transaction manager at deployment time. The > recovery service needs to be an external service depending upon both the > tm and the managed connection factories. > At least this will require a GUID for the XID so we can avoid duplicates between > unrecovered XIDs and any new XIDs created before recovery is complete. > 2) JBossMQ needs to implement XAResource.recover() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007