December 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9391) EJB3.1 spec 4.8.4: destroying singleton because of error during initialization is not honored

by Pierre Kobylanski (JIRA)

EJB3.1 spec 4.8.4: destroying singleton because of error during initialization is not honored --------------------------------------------------------------------------------------------- Key: JBAS-9391 URL: https://issues.jboss.org/browse/JBAS-9391 Project: Legacy JBoss Application Server 6 Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB Affects Versions: 6.0.0.Final Environment: $ uname -a Linux tumlatum 2.6.38-2-686-bigmem #1 SMP Sun May 8 15:43:39 UTC 2011 i686 GNU/Linux Reporter: Pierre Kobylanski Assignee: Carlo de Wolf ejb 3.1 spec [4.8.4 Singleton Error Handling] says that "Errors occurring during Singleton initialization are considered fatal and must result in the discarding of the Singleton instance." I tried to raise a system exception in the @PostConstruct method of a singleton bean. Logs show the deployment error. But I then can access and call the singleton methods. -- Full paragraph 4.8.4: ----------------------------- Errors occurring during Singleton initialization are considered fatal and must result in the discarding of the Singleton instance. Possible initialization errors include injection failure, a system exception thrown from a PostConstruct method, or the failure of a PostConstruct method container-managed transaction to successfully commit. If a singleton fails to initialize, attempted invocations on the Singleton result in an exception as defined by Section 3.4.3 and Section 3.4.4. ------------------------------------------------------ I tested to raise a system exception (throw new RuntimeException()) in the @PostConstruct method. -- Logs show the error ------------------------------- ERROR [AbstractKernelController] Error installing to Start: name=startup-singleton-initiator:topLevelUnit=ts.ear,unit=testSingletonEjb.jar,bean=counter aliases=[startup-singleton-initiator:bean=counter,topLevelUnit=ts.ear,unit=testSingletonEjb.jar] state=Create: java.lang.RuntimeException: Could not invoke PostConstruct on the newly created bean instance at org.jboss.ejb3.singleton.impl.container.SingletonEJBInstanceManagerImpl.create(SingletonEJBInstanceManagerImpl.java:137) [:1.0.0-alpha-28] ... Caused by: testsingleton.exn.SE // class SE extends RuntimeException{} at testsingleton.ejb.CounterEjb.pc(CounterEjb.java:28) DEPLOYMENTS IN ERROR: Deployment "startup-singleton-initiator:topLevelUnit=ts.ear,unit=testSingletonEjb.jar,bean=counter" is in error due to the following reason(s): testsingleton.exn.SE at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1228) [:2.2.0.GA] ------------------------------------------------------ However, it is after that possible to access the singleton through a JNDI lookup and successfully call its methods. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2255) @SecurityDomain has no equivalent for <security-domain/>

by Richard Kennard (JIRA)

@SecurityDomain has no equivalent for <security-domain/> -------------------------------------------------------- Key: EJBTHREE-2255 URL: https://issues.jboss.org/browse/EJBTHREE-2255 Project: EJB 3.0 Issue Type: Bug Environment: JBoss 6.0.0.Final Reporter: Richard Kennard Test case attached. We have found it useful to turn off the security-domain for certain EJBs so that they can be accessed from unauthenticated clients. We can do this in jboss.xml using <security-domain /> but not, it seems, from an EJB using the @SessionDomain annotation. A @SessionDomain( "" ) is simply ignored. We're not a big fan of hard-coding security domain names inside EJBs, but it seems fine to be able to say 'this EJB has no security domain at all'. Should the annotation work for this? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1642) The <security-domain> tag included in <container-configuration> in the jboss.xml file is ignored

by John Gonon (JIRA)

The <security-domain> tag included in <container-configuration> in the jboss.xml file is ignored ------------------------------------------------------------------------------------------------ Key: EJBTHREE-1642 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1642 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: HEAD Environment: Windows XP JDK 1.6.build10 JBOSS 5.0.0.GA Reporter: John Gonon Priority: Minor The <security-domain> tag included in <container-configuration> in the jboss.xml file is ignored. I have tracked were the problem seems to be (at least as I saw it). In the class "org.jboss.ejb3.security.bridge.SecurityDomainMetaDataBridge" there are those lines: //TODO: How to get the merged meta data? Is the following line correct? if(securityDomain == null) securityDomain = beanMetaData.getJBossMetaData().getSecurityDomain(); I replaced them with: if (securityDomain == null) { JBossMetaData metaData = beanMetaData.getJBossMetaData(); securityDomain = metaData.getContainerConfiguration(beanMetaData.determineConfigurationName()) .getSecurityDomain(); if (securityDomain == null) securityDomain = metaData.getSecurityDomain(); } As I understand it, if no "SecurityDomain" annotation is found, then we finish in this class and we do in order: 1. seek for a security domain in the bean's metadata (I guess it is in the EJB declaration) 2. seek for the one in "jboss-app.xml" I inserted between them some code returning the one comming from the container's configuration I hope this helps ... Best regards, Please keep me informed, I hope to remove my "modified" jar with an official one soon. John -- 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

12 years, 2 months

2
5
0 / 0

[JBoss JIRA] (AS7-2516) Arquillian throws OutOfMemoryError: PermGen space after deploying several big wars on JBoss 7

by Geoffrey De Smet (Created) (JIRA)

Arquillian throws OutOfMemoryError: PermGen space after deploying several big wars on JBoss 7 --------------------------------------------------------------------------------------------- Key: AS7-2516 URL: https://issues.jboss.org/browse/AS7-2516 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.0.2.Final Reporter: Geoffrey De Smet Assignee: Andrew Rubinger Priority: Minor Here's the proof (that build is saved forever): https://hudson.qa.jboss.com/hudson/view/Drools%20jBPM/job/guvnor/1161/con... Our war is apparently so big, that the 3th deployment fails with PermGen. A few tests later it even hangs forever (until it times out) {code} 10:41:56,393 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/dc25ad71-9358-412e-8a90-c4471cb3422f].[ArquillianServletRunner]] (http--127.0.0.1-8080-2) Servlet.service() for servlet ArquillianServletRunner threw exception: java.lang.OutOfMemoryError: PermGen space {code} How to reproduce? ================= git clone git@github.com:droolsjbpm/guvnor.git guvnor cd guvnor mvn clean install -DskipTests cd guvnor-webapp gedit src/test/resources/arquillian.xml // remove the maxTestClassesBeforeRestart property mvn test Using arquillian 1.0.0.CR5 and jboss 7.0.2. Workaround: use maxTestClassesBeforeRestart = 1. -- 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

12 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-6326) InterruptedException on shutdown

by Jeff Yu (JIRA)

InterruptedException on shutdown -------------------------------- Key: JBAS-6326 URL: https://jira.jboss.org/jira/browse/JBAS-6326 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.2.GA Reporter: Jeff Yu Assignee: Jeff Zhang Priority: Minor I see the following exception on shutdown with either default, all, production servers (using all's log4j configuration). I'm not sure it is necessary for users to see. Probably needs to be changed to DEBUG level if really not relevant. 09:07:59,647 WARN [NewMsgsWorker] Interrupted waiting for new msg check java.lang.InterruptedException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:474) at EDU.oswego.cs.dl.util.concurrent.Semaphore.acquire(Semaphore.java:108) at EDU.oswego.cs.dl.util.concurrent.SemaphoreControlledChannel.take(SemaphoreControlledChannel.java:131) at org.jboss.resource.adapter.mail.inflow.NewMsgsWorker.run(NewMsgsWorker.java:75) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756) at java.lang.Thread.run(Thread.java:595) -- 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

12 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBVFS-170) Support for -Djboss.vfs.forceCaseSensitive=true

by Jean-Frederic Clere (JIRA)

Support for -Djboss.vfs.forceCaseSensitive=true ----------------------------------------------- Key: JBVFS-170 URL: https://issues.jboss.org/browse/JBVFS-170 Project: JBoss VFS Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: windoze Reporter: Jean-Frederic Clere Assignee: John Bailey Priority: Minor For windoze Toto.class, TOTO.class, toto.class etc are the same file. When using JSP a class name Toto.class may hide a package toto. In AS5/6 it is fixed using -Djboss.vfs.forceCaseSensitive=true How is this handled in VFS3? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

7
15
0 / 0

[JBoss JIRA] Created: (AS7-1712) Implement an account lockout mechanism for domain management.

by Darran Lofthouse (JIRA)

Implement an account lockout mechanism for domain management. ------------------------------------------------------------- Key: AS7-1712 URL: https://issues.jboss.org/browse/AS7-1712 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta1 One issue to consider is that we are using realms to integrate with existing user stores so may not be able to update the remote store: - - Consider an option to update the remote store if possible. - If not cache a backlisted user until an admin unlocks that account -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (AS7-977) Dynamic Detection of SPNEGO auth method and adding of NegotiationAuthenticator

by Darran Lofthouse (JIRA)

Dynamic Detection of SPNEGO auth method and adding of NegotiationAuthenticator ------------------------------------------------------------------------------ Key: AS7-977 URL: https://issues.jboss.org/browse/AS7-977 Project: Application Server 7 Issue Type: Task Components: Security, Web Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Alpha1 Previously a mapping for the SPNEGO auth method and the authenticator had to be manually defined, this capability is not present in AS7 however it is suggested that alternatively we can detect the auth method ourselves and dynamically add the valve - this seems cleaner as it potentially allows SPNEGO to be added/removed from a server without manual configuration being required. It is suggested to look at the following code for an example where a valve has been added dynamically before: - org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor in the JPA subsystem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (AS7-777) Switchable Nonce Handling Strategy for HTTP DigestAuthenticator

by Darran Lofthouse (JIRA)

Switchable Nonce Handling Strategy for HTTP DigestAuthenticator --------------------------------------------------------------- Key: AS7-777 URL: https://issues.jboss.org/browse/AS7-777 Project: Application Server 7 Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.0.0.CR1 Allow the nonce strategy to be switchable: - 1 - Real 'Number Used Once' - i.e. new nonce for each request. 2 - Nonce per connection i.e. as long as a connection is kept alive allow re-use of nonce - new nonce on new connection. 3 - Timed nonce - Generate a nonce with a server secret and timestamp, nonce will be accepted for a validity period. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
8
0 / 0

[JBoss JIRA] (AS7-2771) ModelControllerClient operations don't fail on invalud username/password

by Thomas Diesler (Created) (JIRA)

ModelControllerClient operations don't fail on invalud username/password ------------------------------------------------------------------------ Key: AS7-2771 URL: https://issues.jboss.org/browse/AS7-2771 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JSR-88 Reporter: Thomas Diesler Assignee: Darran Lofthouse Priority: Critical Running org.jboss.as.test.smoke.jsr88.EnterpriseDeploymentTestCase Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 128.98 sec There should be a test failure with this {code} @Test public void testListAvailableModulesUnauthorized() throws Exception { DeploymentManager manager = getDeploymentManager("nobody", "nopass"); Target[] targets = manager.getTargets(); // [TODO] This should fail already TargetModuleID[] availableModules = manager.getAvailableModules(ModuleType.EAR, targets); assertNull(availableModules); ProgressObject progress = jsr88Deploy(manager, getEarArchive()); TargetModuleID[] targetModules = progress.getResultTargetModuleIDs(); try { availableModules = manager.getAvailableModules(ModuleType.EAR, targets); assertNotNull(availableModules); assertEquals(1, availableModules.length); TargetModuleID targetModuleID = availableModules[0]; String moduleID = targetModuleID.getModuleID(); assertTrue("Ends with deployment-app.ear", moduleID.endsWith("deployment-app.ear")); // [TODO] verify child modules } finally { jsr88Undeploy(manager, targetModules); } } {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

12 years, 3 months

7
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2011