July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8384) Passivation of a @Stateful session bean with an @Inject'ed @Stateless session bean fails with not-serializable error.

by Ken Britton (JIRA)

Passivation of a @Stateful session bean with an @Inject'ed @Stateless session bean fails with not-serializable error. --------------------------------------------------------------------------------------------------------------------- Key: JBAS-8384 URL: https://jira.jboss.org/browse/JBAS-8384 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.M4 Environment: Mac OS 10.6.4, Java6 Reporter: Ken Britton If a @Stateful session bean has an injected @Stateless session bean it cannot be passivated. -- 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, 4 months

4
8
0 / 0

[JBoss JIRA] (AS7-5255) Deployed log4j.properties does not affect non log4j logging systems

by Patrick Ruckstuhl (JIRA)

Patrick Ruckstuhl created AS7-5255: -------------------------------------- Summary: Deployed log4j.properties does not affect non log4j logging systems Key: AS7-5255 URL: https://issues.jboss.org/browse/AS7-5255 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.1.2.Final (EAP) Reporter: Patrick Ruckstuhl Assignee: James Perkins If I create the file my.ear/META-INF/log4j.properties with log4j.rootLogger=DEBUG, FA log4j.appender.FA=org.apache.log4j.FileAppender log4j.appender.FA.File=/tmp/my.log log4j.appender.FA.layout=org.apache.log4j.PatternLayout log4j.appender.FA.layout.ConversionPattern= %-4r [%t] %-5p %c %x - %m%n this results in nothing in the server.log and an empty /tmp/my.log but if I create a my.ear/META-INF/logging.properties this results in everything beeing logged to /tmp/my.log We're using SLF4J in our application and also using a library that uses COMMONS-LOGGING I also did a test with doing an additional log statement using the log4j api directly and this one (and only this one) did get logged to /tmp/my.log -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
15
0 / 0

[JBoss JIRA] (AS7-4127) Intermittent failure in RemotingSubsystemTestCase.testSubsystemWithConnectorPropertyChange()

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-4127: --------------------------------- Summary: Intermittent failure in RemotingSubsystemTestCase.testSubsystemWithConnectorPropertyChange() Key: AS7-4127 URL: https://issues.jboss.org/browse/AS7-4127 Project: Application Server 7 Issue Type: Bug Reporter: Ondrej Zizka Spotted in https://hudson.qa.jboss.com/hudson/view/ESSC/job/AS7-TS-valid-default/las... {code} junit.framework.AssertionFailedError: expected not same at junit.framework.Assert.fail(Assert.java:50) at junit.framework.Assert.failSame(Assert.java:276) at junit.framework.Assert.assertNotSame(Assert.java:262) at junit.framework.Assert.assertNotSame(Assert.java:269) at org.jboss.as.remoting.RemotingSubsystemTestCase$CurrentConnectorAndController.checkStatus(RemotingSubsystemTestCase.java:333) at org.jboss.as.remoting.RemotingSubsystemTestCase$CurrentConnectorAndController.updateCurrentConnector(RemotingSubsystemTestCase.java:327) at org.jboss.as.remoting.RemotingSubsystemTestCase.testSubsystemWithConnectorPropertyChange(RemotingSubsystemTestCase.java:186) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
12
0 / 0

[JBoss JIRA] (AS7-3632) Re-enable RemotingSubsystemTestCase.testSubsystemWithBadConnectorProperty

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-3632: -------------------------------- Summary: Re-enable RemotingSubsystemTestCase.testSubsystemWithBadConnectorProperty Key: AS7-3632 URL: https://issues.jboss.org/browse/AS7-3632 Project: Application Server 7 Issue Type: Task Affects Versions: 7.1.0.Final Environment: jenkins Reporter: Tomaz Cerar Assignee: Tomaz Cerar testSubsystemWithBadConnectorProperty test randomly fails on some enviroments. until this is resolved test is marked as @Ignored -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
2
0 / 0

[JBoss JIRA] (JBRULES-3389) OSGi-fy drools-spring and drools-camel modules

by Alexander Filipchik (JIRA)

Alexander Filipchik created JBRULES-3389: -------------------------------------------- Summary: OSGi-fy drools-spring and drools-camel modules Key: JBRULES-3389 URL: https://issues.jboss.org/browse/JBRULES-3389 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Components: drools-camel, drools-spring Affects Versions: 5.4.0.CR1 Reporter: Alexander Filipchik Assignee: Mark Proctor Fix For: 5.4.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

5
6
0 / 0

[JBoss JIRA] (AS7-3346) Security audit logging problem

by Jan Lanik (JIRA)

Jan Lanik created AS7-3346: ------------------------------ Summary: Security audit logging problem Key: AS7-3346 URL: https://issues.jboss.org/browse/AS7-3346 Project: Application Server 7 Issue Type: Bug Components: Security Affects Versions: 7.1.0.CR1b Reporter: Jan Lanik Assignee: Anil Saldhana I used the configuration setup + quick testing as documented here https://community.jboss.org/wiki/JBossAS7SecurityAuditing The audit.log file was created but no events was recorded in it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

8
27
0 / 0

[JBoss JIRA] (AS7-4680) Logout a remote client from server and clearing login module cache.

by Serkan Yıldırım (JIRA)

Serkan Yıldırım created AS7-4680: ------------------------------------ Summary: Logout a remote client from server and clearing login module cache. Key: AS7-4680 URL: https://issues.jboss.org/browse/AS7-4680 Project: Application Server 7 Issue Type: Feature Request Components: Remoting, Security, Server Affects Versions: 7.1.1.Final Environment: java 1.6 win 7 64 bit 4 gb ram Reporter: Serkan Yıldırım Assignee: David Lloyd Priority: Blocker I have a custom login module. I authenticate and authorize a user (creating roles) by using this custom module. When i close the remote application, i want to logout the user from server so that clear login module cache, i.e deleting principals and roles from the cache. I couldn't find a solution for this problem in forum. If it exists, could you please explain it, thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
5
0 / 0

[JBoss JIRA] (AS7-4679) Catching custom login module exceptions in remote client

by Serkan Yıldırım (JIRA)

Serkan Yıldırım created AS7-4679: ------------------------------------ Summary: Catching custom login module exceptions in remote client Key: AS7-4679 URL: https://issues.jboss.org/browse/AS7-4679 Project: Application Server 7 Issue Type: Feature Request Components: Remoting, Security, Server Affects Versions: 7.1.1.Final Environment: Win 7 64 Bit 4 GB RAM java 1.6 Reporter: Serkan Yıldırım Assignee: David Lloyd Priority: Critical This feature request is related with the discussion: https://community.jboss.org/message/732948#732948 I have custom login modules in JBOSS 7.1.2 Snapshot. They are working with no error, i can authenticate and authorize a user. However, when an exception occurs at the time of login, i.e. wrong password, i throw javax.security.auth.login.LoginException with my custom message. But i couldn't catch the exception in the remote client, how is it possible??? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] (AS7-4823) add-user has the ability to add a user and edit/replace a user - we should add delete a user

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4823: ------------------------------------- Summary: add-user has the ability to add a user and edit/replace a user - we should add delete a user Key: AS7-4823 URL: https://issues.jboss.org/browse/AS7-4823 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 For completeness the add-user utility should also support an option for deleting / disabling users. If we go for disabling rather than deleting we may then also want enabling - the re-writes of the properties files retain the comments so a disable / enable mechanism would be easiest to just comment out the disabled user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
2
0 / 0

[JBoss JIRA] (AS7-4049) Revisit the JBOSS_LOCAL_USER Mechanism

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4049: ------------------------------------- Summary: Revisit the JBOSS_LOCAL_USER Mechanism Key: AS7-4049 URL: https://issues.jboss.org/browse/AS7-4049 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse There are various points to reconsider: - - Implementation becoming quite embedded in the RealmSecurityProviderService - No local configuration within the realms - No http equivalent -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
3
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 July 2012