September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-415) Resource adapter deployer

by Jesper Pedersen (JIRA)

Resource adapter deployer ------------------------- Key: JBJCA-415 URL: https://jira.jboss.org/browse/JBJCA-415 Project: IronJacamar Issue Type: Task Components: Deployer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta2 Create a resource adapter deployer which can deploy an instance based on the resource-adapters.xsd format (-ra.xml) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-400) StAX based metadata model (ds.xml)

by Stefano Maestri (JIRA)

StAX based metadata model (ds.xml) ---------------------------------- Key: JBJCA-400 URL: https://jira.jboss.org/browse/JBJCA-400 Project: IronJacamar Issue Type: Task Components: Common Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 1.0.0.Beta2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBJCA-392) Arquillian 1.0.0.Alpha3

by Jesper Pedersen (JIRA)

Arquillian 1.0.0.Alpha3 ----------------------- Key: JBJCA-392 URL: https://jira.jboss.org/browse/JBJCA-392 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-410) JBoss Threads 2.0.0.CR5

by Jesper Pedersen (JIRA)

JBoss Threads 2.0.0.CR5 ----------------------- Key: JBJCA-410 URL: https://jira.jboss.org/browse/JBJCA-410 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-422) create test suite for Merger class

by Stefano Maestri (JIRA)

create test suite for Merger class ---------------------------------- Key: JBJCA-422 URL: https://jira.jboss.org/browse/JBJCA-422 Project: IronJacamar Issue Type: Task Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 1.0.0.Beta2 We need to verify default values and mandatory elements and attributes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBJCA-401) StAX based metadata model (resource-adapter.xml)

by Stefano Maestri (JIRA)

StAX based metadata model (resource-adapter.xml) ------------------------------------------------ Key: JBJCA-401 URL: https://jira.jboss.org/browse/JBJCA-401 Project: IronJacamar Issue Type: Task Components: Common Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 1.0.0.Beta2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-1104) Revisit critical path in NAKACK

by Vladimir Blagojevic (JIRA)

Revisit critical path in NAKACK ------------------------------- Key: JGRP-1104 URL: https://jira.jboss.org/jira/browse/JGRP-1104 Project: JGroups Issue Type: Task Affects Versions: 2.8 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 2.9 Revisit NAKACK#handleMessage and see if we can: a) lower contention on NRW lock by not attempting to propel up oob messages one-by-one I have no profiling data so I am speaking without a solid proof to back my claims. I am envisioning both oob and regular threads contending for a window as they push messages up the stack. oob threads are always going to attempt to lock per message (line 788). In an event that we received missing oob message in a series of oob messages we are going to repeatedly lock window per message traversed. Not good. We don't need this IMHO. I really like lock efficient removeMany algorithm. Let removeMany propel messages up the stack as much as possible, even oob messages. b) why are we propelling oob messages on a timer (line 833)? Is it to lower the workload of the current thread, or is there a more fundamental reason? c) undelivered_msgs is complicating things unnecessarily IMHO. Why don't we let oob threads go into removeMany code and remove as much messages as they can - both oob and regular and push them up rather than lock NRW per message? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
10
0 / 0

[JBoss JIRA] Created: (JGRP-1235) S3_PING: Allow Use of Pre-Signed URLs When Writing to Buckets

by Benjamin Browning (JIRA)

S3_PING: Allow Use of Pre-Signed URLs When Writing to Buckets ------------------------------------------------------------- Key: JGRP-1235 URL: https://jira.jboss.org/browse/JGRP-1235 Project: JGroups Issue Type: Feature Request Reporter: Benjamin Browning Assignee: Bela Ban Allowing pre-signed urls when writing and deleting from buckets will give us real write security without having to store AWS credentials in the config file. For this approach to work, buckets will need to be publicly readable and the user or their automated system will need to generate pre-signed urls for each node in the cluster. An example of the config entry: <S3_PING pre_signed_put_url="http://s3.amazonaws.com/ben-test/DemoCluster/thing1?AWSAccessKeyId=access..." pre_signed_delete_url="http://s3.amazonaws.com/ben-test/DemoCluster/thing1?AWSAccessKeyId=access..." timeout="2000" num_initial_members="3"/> The pre-signed urls need to be generated with no headers except "x-amz-acl" with a value of "public-read" for the PUT url. It would be a good idea to add some utility code to S3_Ping to generate these urls. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8430) Expose the name on SocketBinding

by Scott Stark (JIRA)

Expose the name on SocketBinding -------------------------------- Key: JBAS-8430 URL: https://jira.jboss.org/browse/JBAS-8430 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management services Affects Versions: 7.0.0.M1 Reporter: Scott Stark Assignee: Scott Stark Fix For: 7.0.0.M1 I need the name of the SocketBinding exposed on the class for the case where a single Injector is handling multiple SocketBindings and needs to route the binding to the correct usage. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8391) Update Deployment Module Loader to support unloading

by John Bailey (JIRA)

Update Deployment Module Loader to support unloading ---------------------------------------------------- Key: JBAS-8391 URL: https://jira.jboss.org/browse/JBAS-8391 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployers Reporter: John Bailey Assignee: Jason Greene Fix For: 7.0.0.M1 The DeploymentModuleLoader{Impl} needs to be updated to support unloading modules. This should be possible with https://jira.jboss.org/browse/MODULES-33. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2010