December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (SECURITY-27) Container Task:JBoss 4.2.x related Tasks for Security 2.0

by Anil Saldhana (JIRA)

Container Task:JBoss 4.2.x related Tasks for Security 2.0 --------------------------------------------------------- Key: SECURITY-27 URL: http://jira.jboss.com/jira/browse/SECURITY-27 Project: JBoss Security Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 Container task for all 4.2.x related tasks that need to be performed for the 5.x releases of JBAS. -- 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

15 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (SECURITY-28) JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass

by Anil Saldhana (JIRA)

JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass ---------------------------------------------------------------------------------------- Key: SECURITY-28 URL: http://jira.jboss.com/jira/browse/SECURITY-28 Project: JBoss Security Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 JBAS-1824 -- 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

15 years, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1459) portal:service=TreeCache,type=hibernate should define ClusterConfig

by Galder Zamarreno (JIRA)

portal:service=TreeCache,type=hibernate should define ClusterConfig ------------------------------------------------------------------- Key: JBPORTAL-1459 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1459 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6.CR1, 2.6.CR2, 2.4.1 SP1, 2.4.1 Final Reporter: Galder Zamarreno portal:service=TreeCache,type=hibernate omits ClusterConfig which can lead to confusion when trying to separate different AS + Portal clusters. Here's, bearing in mind the status of the JBC/HB integration, a good starting point: <attribute name="ClusterConfig"> <config> <UDP mcast_addr="${portal.hibernate.cache.udpGroup:224.0.0.36}" mcast_port="${portal.hibernate.cache.udpPort:55566}" ip_ttl="8" ip_mcast="true" mcast_send_buf_size="150000" mcast_recv_buf_size="80000" ucast_send_buf_size="150000" ucast_recv_buf_size="80000" loopback="false" up_thread="false" down_thread="false" /> <PING timeout="2000" num_initial_members="3" up_thread="false" down_thread="false" /> <MERGE2 min_interval="10000" max_interval="20000" up_thread="false" down_thread="false" /> <FD_SOCK up_thread="false" down_thread="false" /> <FD shun="true" timeout="20000" max_tries="5" up_thread="false" down_thread="false" /> <VERIFY_SUSPECT timeout="1500" up_thread="false" down_thread="false"/> <pbcast.NAKACK gc_lag="50" retransmit_timeout="600,1200,2400,4800" max_xmit_size="8192" discard_delivered_msgs="true" up_thread="false" down_thread="false"/> <UNICAST timeout="600,1200,2400" window_size="100" min_threshold="10" up_thread="false" down_thread="false"/> <pbcast.STABLE desired_avg_gossip="20000" up_thread="false" down_thread="false"/> <pbcast.GMS join_timeout="5000" join_retry_timeout="2000" shun="true" print_local_addr="true" up_thread="false" down_thread="false"/> <FRAG2 frag_size="8192" up_thread="false" down_thread="false"/> <pbcast.STATE_TRANSFER up_thread="false" down_thread="false"/> </config> </attribute> It'd be interesting to change the ClusterName as well: <attribute name="ClusterName">${portal.hibernate.cache.partition.name:portal.hibernate}</attribute> This configuration works and should be much better than the default one provided by JBossCache. -- 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

15 years, 11 months

4
4
0 / 0

[JBoss JIRA] Created: (SECURITY-61) Use JBossSubject rather than JAAS Subject

by Anil Saldhana (JIRA)

Use JBossSubject rather than JAAS Subject ----------------------------------------- Key: SECURITY-61 URL: http://jira.jboss.com/jira/browse/SECURITY-61 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX, Security SPI Affects Versions: 2.0.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 The JAAS Subject is quite inflexible. There is a need for a customized Subject. Let us call it JBossSubject which can internally hold a Jaas Subject. -- 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

15 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-46) SASL Implementation

by Anil Saldhana (JIRA)

SASL Implementation --------------------- Key: SECURITY-46 URL: http://jira.jboss.com/jira/browse/SECURITY-46 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX, JEMS Integration Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 Need to get an implementation of SASL for client/server kind of setup for JBoss AS. This will work off of the Security Client implementation and then security managers on the server side. -- 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

15 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1016) Refactoring EJB 3

by Carlo de Wolf (JIRA)

Refactoring EJB 3 ----------------- Key: EJBTHREE-1016 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1016 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD -- 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

15 years, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (JGRP-594) Intermittently, a Null pointer exception is thrown when trying to remove non-existent entry in ReplicatedHashMap

by Dipak Kothari (JIRA)

Intermittently, a Null pointer exception is thrown when trying to remove non-existent entry in ReplicatedHashMap ---------------------------------------------------------------------------------------------------------------- Key: JGRP-594 URL: http://jira.jboss.com/jira/browse/JGRP-594 Project: JGroups Issue Type: Bug Affects Versions: 2.5 Environment: Linux Reporter: Dipak Kothari Assigned To: Bela Ban Intermittently, when an entry is removed from a ReplicatedHashMap (where the entry does not exist) the following exception is thrown: java.lang.RuntimeException: remove(APMExample.Services.examples.ServerA09) failed at org.jgroups.blocks.ReplicatedHashMap.remove(ReplicatedHashMap.java:405) at com.ubs.apm.control.service.nameservice.jgroup.JGroupNameService.unRegisterService(JGroupNameService.java:132) at com.ubs.apm.control.sensors.ControlSensorManager.cleanup(ControlSensorManager.java:468) at com.ubs.apm.control.sensors.ControlSensorManager.<init>(ControlSensorManager.java:125) at com.ubs.apm.control.sensors.ControlSensorManager.<init>(ControlSensorManager.java:106) at com.ubs.apm.control.example.ManagedServer.init(ManagedServer.java:20) at com.ubs.apm.control.example.ManagedServer.main(ManagedServer.java:45) Caused by: java.lang.RuntimeException: failed executing request [req_id=1189617222436 caller=14.64.61.201:6825 14.64.61.201:6838: sender=14.64.61.201:6838, retval=null, received=false, suspected=false .... many such lines ... 14.64.61.201:6860: sender=14.64.61.201:6860, retval=null, received=false, suspected=false 14.64.61.201:6847: sender=14.64.61.201:6847, retval=null, received=false, suspected=false request_msg: [dst: <null>, src: 14.64.61.201:6825 (2 headers), size=143 bytes] rsp_mode: GET_NONE done: true timeout: 5000 expected_mbrs: 0 ([14.64.61.201:6815, 14.64.61.201:6816, 14.64.61.201:6824, 14.64.61.201:6825, 14.64.61.201:6826, 14.64.61.201:6827, 14.64.61.201:6828, 14.64.61.201:6829, 14.64.61.201:6830, 14.64.61.201:6831, 14.64.61.201:6833, 14.64.61.201:6834, 14.64.61.201:6835, 14.64.61.201:6836, 14.64.61.201:6837, 14.64.61.201:6838, 14.64.61.201:6839, 14.64.61.201:6842, 14.64.61.201:6843, 14.64.61.201:6844, 14.64.61.201:6845, 14.64.61.201:6846, 14.64.61.201:6847, 14.64.61.201:6848, 14.64.61.201:6849, 14.64.61.201:6850, 14.64.61.201:6851, 14.64.61.201:6852, 14.64.61.201:6853, 14.64.61.201:6854, 14.64.61.201:6855, 14.64.61.201:6856, 14.64.61.201:6857, 14.64.61.201:6858, 14.64.61.201:6859, 14.64.61.201:6860, 14.64.61.201:6861, 14.64.61.201:6862, 14.64.61.201:6863, 14.64.61.201:6864, 14.64.61.201:6865, 14.64.61.201:6866])] at org.jgroups.blocks.MessageDispatcher.castMessage(MessageDispatcher.java:433) at org.jgroups.blocks.RpcDispatcher.callRemoteMethods(RpcDispatcher.java:199) at org.jgroups.blocks.RpcDispatcher.callRemoteMethods(RpcDispatcher.java:167) at org.jgroups.blocks.RpcDispatcher.callRemoteMethods(RpcDispatcher.java:163) at org.jgroups.blocks.ReplicatedHashMap.remove(ReplicatedHashMap.java:402) ... 6 more Caused by: java.lang.RuntimeException: failure adding msg [dst: <null>, src: 14.64.61.201:6825 (2 headers), size=143 bytes] to the retransmit table for 14.64.61.201:6825 at org.jgroups.protocols.pbcast.NAKACK.send(NAKACK.java:636) at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:438) at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:317) at org.jgroups.protocols.pbcast.GMS.down(GMS.java:782) at org.jgroups.protocols.pbcast.STATE_TRANSFER.down(STATE_TRANSFER.java:221) at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:339) at org.jgroups.JChannel.downcall(JChannel.java:1240) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.down(MessageDispatcher.java:752) at org.jgroups.blocks.RequestCorrelator.sendRequest(RequestCorrelator.java:301) at org.jgroups.blocks.GroupRequest.doExecute(GroupRequest.java:440) at org.jgroups.blocks.GroupRequest.execute(GroupRequest.java:190) at org.jgroups.blocks.MessageDispatcher.castMessage(MessageDispatcher.java:430) ... 10 more Caused by: java.lang.NullPointerException at org.jgroups.protocols.pbcast.NAKACK.send(NAKACK.java:632) ... 21 more -- 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

15 years, 11 months

2
10
0 / 0

[JBoss JIRA] Created: (JBAOP-388) Allow specification of the exception for after-throwing bindings

by Flavia Rainone (JIRA)

Allow specification of the exception for after-throwing bindings ---------------------------------------------------------------- Key: JBAOP-388 URL: http://jira.jboss.com/jira/browse/JBAOP-388 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 2.0.0.alpha4 Reporter: Flavia Rainone Assigned To: Flavia Rainone Priority: Minor Fix For: 2.0.0.alpha5 We need to provide an optional attribute to the throwing tag (and to the corrersponding annotation, if it has already been implemented JBAOP-386), so the user can specify an exception type. This task includes updating: - advice validation algorithm - overloaded advice selection algorithm - documentation (tutorial, reference manual, etc) -- 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

15 years, 11 months

2
23
0 / 0

[JBoss JIRA] Created: (EJBTHREE-788) Default SFSB timeout should be longer than the default tomcat HttpSession timeout.

by Gavin King (JIRA)

Default SFSB timeout should be longer than the default tomcat HttpSession timeout. ---------------------------------------------------------------------------------- Key: EJBTHREE-788 URL: http://jira.jboss.com/jira/browse/EJBTHREE-788 Project: EJB 3.0 Issue Type: Bug Reporter: Gavin King Priority: Critical This bites every user who tries to use Seam. -- 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

15 years, 11 months

6
18
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1155) Allow for discovery of N Local/Remote interfaces through Home create() methods

by Andrew Lee Rubinger (JIRA)

Allow for discovery of N Local/Remote interfaces through Home create() methods ------------------------------------------------------------------------------ Key: EJBTHREE-1155 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1155 Project: EJB 3.0 Issue Type: Bug Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.Beta3 Presently, the Local/Remote interface may be discovered via reflection from the return type of the first "create" method in the Home interface. Allow discovery of an N number of Local/Remote interfaces from the return types of Home.create(). -- 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

15 years, 11 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007