January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2337) Big performance issue caused by Task entity and I18N

by Julien Cheype (JIRA)

Big performance issue caused by Task entity and I18N ---------------------------------------------------- Key: JBRULES-2337 URL: https://jira.jboss.org/jira/browse/JBRULES-2337 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-process-task Reporter: Julien Cheype Assignee: Mark Proctor There is a big performance issue with the Task entity, for example query to TasksAssignedAsPotentialOwner can take more than 2 seconds for returning less than 20 records using a MySql server Correction consist in adding mappedBy="id" to subjects, names and description attributes -- 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

13 years, 11 months

4
7
0 / 0

[JBoss JIRA] Created: (JGRP-1268) Allow 0.0.0.0 as bind address

by Bela Ban (JIRA)

Allow 0.0.0.0 as bind address ----------------------------- Key: JGRP-1268 URL: https://issues.jboss.org/browse/JGRP-1268 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.12 Currently, bind_addr has to be a valid interface and the wildcard (0.0.0.0) address is not permitted. The reason is that bind_addr determines the physical address of a node, e.g. 192.168.1.5:46537, and using 0.0.0.0:46537 wouldn't allow us to identify the node in order to send it a message. To allow for TCP and UDP sockets to bind to the wildcard address, we could either use a bind_addr of 0.0.0.0 and introduce an additional property to pick the physical address (e.g. physical_addr="192.168.1.5" / physical_addr="GLOBAL"), or continue using bind_addr to determine the physical address and add a property (bind_to_wild_card_addr="true") to make the UDP and TCP sockets bind to the wildcard address (if true). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-7049) tests-jacc-securitymgr test server fails to start with OpenJDK 6

by Shelly McGowan (JIRA)

tests-jacc-securitymgr test server fails to start with OpenJDK 6 ---------------------------------------------------------------- Key: JBAS-7049 URL: https://jira.jboss.org/jira/browse/JBAS-7049 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Reporter: Shelly McGowan Assignee: Anil Saldhana Fix For: JBossAS-5.2.0.Beta1 This test server runs with security manager and a server.policy file. The test target boots fine with Sun JDK 6. -- 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

13 years, 11 months

4
17
0 / 0

[JBoss JIRA] Created: (JBWEB-196) Version 0 cookies support

by Mike Millson (JIRA)

Version 0 cookies support ------------------------- Key: JBWEB-196 URL: https://issues.jboss.org/browse/JBWEB-196 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Affects Versions: JBossWeb-7.0.0.Beta1 Reporter: Mike Millson Assignee: Jean-Frederic Clere Version 0 cookies support. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-5345) New instance of resources injected on every onMessage MDB call

by Dok Tora (JIRA)

New instance of resources injected on every onMessage MDB call -------------------------------------------------------------- Key: JBAS-5345 URL: http://jira.jboss.com/jira/browse/JBAS-5345 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA, JBossAS-4.0.5.GA Environment: Java version: 1.5.0_13,Apple Computer, Inc. OS-System: Mac OS X 10.4.11,i386 Reporter: Dok Tora Assigned To: Adrian Brock Priority: Critical A new instance of an injected bean is created every time the onMessage() method of an MDB is called. Details with sample code modifications to EJBTrailBlazer for reproduction can be found here: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=132331 Problem was replicated in 4.0.5.GA, 4.2.1 and 4.2.2 -- 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

13 years, 11 months

5
11
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1945) RunAsIdentity is not propagated correctly

by Anton Kolmakov (JIRA)

RunAsIdentity is not propagated correctly ----------------------------------------- Key: EJBTHREE-1945 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1945 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: Plugin 1.0.17 Reporter: Anton Kolmakov I have one message driven bean A and two stateless beans B and C. A annotated with @RunAs, @RunAsPrincipal and @SecurityDomain. B and C annotated with @SecurityDomain. A receives message and calls B which calls C. RunAsPrincipal is propagated to B only but not to C. Why? Is it expected behavior? I expect propagation of RunAsPrinciapl to all beans in execution chain after bean with @RunAsPrincipal annotation. -- 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

13 years, 11 months

6
11
0 / 0

[JBoss JIRA] Created: (JBAS-3816) Wildcard handling in "org.jboss.metadata.MethodAttributes.patternMatches()" isn't correct (or documentation problem)

by Anders Welen (JIRA)

Wildcard handling in "org.jboss.metadata.MethodAttributes.patternMatches()" isn't correct (or documentation problem) -------------------------------------------------------------------------------------------------------------------- Key: JBAS-3816 URL: http://jira.jboss.com/jira/browse/JBAS-3816 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Reporter: Anders Welen Priority: Minor Attachments: JBossBug.tgz The method "patternMatches" in "org.jboss.metadata.MethodAttributes" just stops at the first wildcard ("*") found and assumes that match is ok. Either this is a bug or the documentation ("http://docs.jboss.com/jbossas/guides/j2eeguide/r2/en/html_single/#d0e11084") should be changed and clearly inform that the wildcard must be the last character. If you specify for example "*get*" than all methods will be matched.... -- 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

13 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-8443) BaseClassLoader leaks instances on redeploy

by Stan Silvert (JIRA)

BaseClassLoader leaks instances on redeploy ------------------------------------------- Key: JBAS-8443 URL: https://jira.jboss.org/browse/JBAS-8443 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: 6.0.0.M4 Reporter: Stan Silvert Assignee: Ales Justin The instance count for org.jboss.classloader.spi.base.BaseClassLoader grows by one with each redeploy. These instances are not GC'd, and they eventually cause OOM PermGen errors if you undeploy/deploy several times. -- 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

13 years, 11 months

4
7
0 / 0

[JBoss JIRA] Created: (SECURITY-344) Error decrypting datasource password with SecureIdentityLoginModule

by Marcus Moyses (JIRA)

Error decrypting datasource password with SecureIdentityLoginModule ------------------------------------------------------------------- Key: SECURITY-344 URL: https://jira.jboss.org/jira/browse/SECURITY-344 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.2.SP3 Reporter: Marcus Moyses Assignee: Marcus Moyses Fix For: 2.0.2.SP5 During password decryption using SecureIdentityLoginModule there could be an error due to missing leading zeros for certain passwords. This error might appear in the log: [SecureIdentityLoginModule] Failed to decode password javax.crypto.IllegalBlockSizeException: Input length must be multiple of 8 when decrypting with padded cipher at com.sun.crypto.provider.SunJCE_h.b(DashoA12275) at com.sun.crypto.provider.SunJCE_h.b(DashoA12275) at com.sun.crypto.provider.BlowfishCipher.engineDoFinal(DashoA12275) at javax.crypto.Cipher.doFinal(DashoA12275) at org.jboss.resource.security.SecureIdentityLoginModule.decode(SecureIdentityLoginModule.java:173) at org.jboss.resource.security.SecureIdentityLoginModule.commit(SecureIdentityLoginModule.java:114) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) -- 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

13 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (SECURITY-530) Implement a TOTP Login Module

by Anil Saldhana (JIRA)

Implement a TOTP Login Module ----------------------------- Key: SECURITY-530 URL: https://jira.jboss.org/browse/SECURITY-530 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_v3_0_CR1 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v3_0_CR2 It should be possible for an user to enter a TOTP value from any handheld device into a text box in the login form of a web application. This login module can then validate the totp entered. -- 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

13 years, 11 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2011