July 2009 - jboss-jira - Jboss List Archives

[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

15 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-4078) DeploymentManager.getAvailableModules() returns null

by Libor Kotouc (JIRA)

DeploymentManager.getAvailableModules() returns null ---------------------------------------------------- Key: JBAS-4078 URL: http://jira.jboss.com/jira/browse/JBAS-4078 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta2 Environment: JBoss 5.0.0.beta2 trunk build 20070206, JDK 1.5.0_08 Reporter: Libor Kotouc Assigned To: Dimitris Andreadis Priority: Critical This issue blocks an integration of JBoss AS 5 into NetBeans IDE. Steps to reproduce the behavior: 1. create a simple web application and copy the .war file into the deploy directory (I used the 'default' server) 2. start JBoss server (./run.sh) 3. run the following code from a J2SE application (I added JBoss jars to the classpath): public class Main { public static void main(String[] args) { try { javax.enterprise.deploy.spi.factories.DeploymentFactory df = new org.jboss.deployment.spi.factories.DeploymentFactoryImpl(); javax.enterprise.deploy.spi.DeploymentManager dm; dm = df.getDeploymentManager("http://org.jboss.deployment/jsr88", null, null); javax.enterprise.deploy.spi.Target[] targets = dm.getTargets(); javax.enterprise.deploy.spi.TargetModuleID[] modules; modules = dm.getAvailableModules(javax.enterprise.deploy.shared.ModuleType.WAR, targets); System.out.println(targets.length + " " + targets[0]); System.out.println(modules); } catch (javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException ex) { } catch (javax.enterprise.deploy.spi.exceptions.TargetException ex) { } } } The output of System.out.println statements is: 1 org.jboss.deployment.spi.JMXTarget@161d36b null I expect the module representing the web application, but null is returned. -- 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, 6 months

4
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1791) Create ejb3-metadata-spi

by jaikiran pai (JIRA)

Create ejb3-metadata-spi ------------------------ Key: EJBTHREE-1791 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1791 Project: EJB 3.0 Issue Type: Task Reporter: jaikiran pai Assignee: jaikiran pai The ejb3-metadata-spi acts as an adapter over the JBossMetadata. This would allow us to extend the JBossMetadata as per our new needs for EJB3.1. -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1847) Fix logging of irrelevant (for end users) message about WebService context property

by jaikiran pai (JIRA)

Fix logging of irrelevant (for end users) message about WebService context property ------------------------------------------------------------------------------------- Key: EJBTHREE-1847 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1847 Project: EJB 3.0 Issue Type: Task Components: core Affects Versions: 1.1.6 Reporter: jaikiran pai Assignee: jaikiran pai We currently log this message [StatelessBeanContext] EJBTHREE-1337: do not get WebServiceContext property from stateless bean context, it should already have been injected which is of no relevance to the end user. We need to fix this. Please see referenced forum thread for details. -- 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, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1711) Create a profile3_1 component

by jaikiran pai (JIRA)

Create a profile3_1 component ----------------------------- Key: EJBTHREE-1711 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1711 Project: EJB 3.0 Issue Type: Task Affects Versions: 1.0.0-GA Reporter: jaikiran pai Assignee: jaikiran pai As mentioned in the referenced forum thread: The goal of this component is to provide an EJB 3.1 profile configuration for use in JBoss Reloaded. To get off the ground fast we're going to use JBoss Bootstrap and hardcoded 1 profile in the bootstrap. This will allow us to create a set of integration tests within this component and quickly establish a baseline. -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBREM-1074) Config Guide should clarify the HTTP transport vs Servlet

by Andrew Oliver (JIRA)

Config Guide should clarify the HTTP transport vs Servlet --------------------------------------------------------- Key: JBREM-1074 URL: https://jira.jboss.org/jira/browse/JBREM-1074 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Andrew Oliver http://docs.jboss.org/jbossas/unified_invoker/UnifiedInvoker_guide.html describes changing to use HTTP as a transport. Meaning JBoss remoting launches its own HTTP server. This is probably a pretty esoteric configuration and most people are probably looking for this: http://www.jboss.org/community/docs/DOC-9632 instead. The guide should clarify WHAT that is and where to find what you're probably REALLY looking for. (you probably don't want to run on some weird port if you're using HTTP and most installs probably run WITH tomcat which means you need to run through TC or have a totally separate IP which is pretty hard to do in most environments) -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBREM-1144) Extend connection identity to server side

by Ron Sigal (JIRA)

Extend connection identity to server side ----------------------------------------- Key: JBREM-1144 URL: https://jira.jboss.org/jira/browse/JBREM-1144 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.3, 2.5.1 (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2 (Flounder), 2.2.3.SP1 In JBREM-1128 "Introduce connection identity concept" and JBREM-1132 "CLONE [JBREM-1128] - Introduce connection identity concept", the server was equipped to recognized when a client had been replaced by another client. In other words, clients were assigned an identity. This concept should be extended to the server side, so that ConnectionValidator can detect that a server has been replaced. -- 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, 6 months

1
9
0 / 0

[JBoss JIRA] Created: (JBAS-7013) Seam Booking IOException with JSF2 Beta1 on AS5

by Stan Silvert (JIRA)

Seam Booking IOException with JSF2 Beta1 on AS5 ----------------------------------------------- Key: JBAS-7013 URL: https://jira.jboss.org/jira/browse/JBAS-7013 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JSF Affects Versions: JBossAS-5.1.0.GA Reporter: Stan Silvert Assignee: Stan Silvert I drop-in replaced JSF in AS5.1 with JSF 2 Beta 1. With the Seam Booking demo, I bundle the old facelets and have: <context-param> <param-name>javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER</param-name> <param-value>true</param-value> </context-param> I get the stack trace below. Though it doesn't seem to affect the application, I need to figure out why this is happening. 13:38:34,463 ERROR [compiler] Error Loading Library: vfszip:/C:/jboss-5.1.0.GA/s erver/default/deploy/jbossweb.sar/jsf-libs/jsf-impl.jar/META-INF/mojarra_ext.tag lib.xml java.io.IOException: Error parsing [vfszip:/C:/jboss-5.1.0.GA/server/default/dep loy/jbossweb.sar/jsf-libs/jsf-impl.jar/META-INF/mojarra_ext.taglib.xml]: at com.sun.facelets.compiler.TagLibraryConfig.create(TagLibraryConfig.ja va:410) at com.sun.facelets.compiler.TagLibraryConfig.loadImplicit(TagLibraryCon fig.java:431) at com.sun.facelets.compiler.Compiler.initialize(Compiler.java:87) at com.sun.facelets.compiler.Compiler.compile(Compiler.java:104) at com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFace letFactory.java:218) at com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFacelet Factory.java:149) at com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFacelet Factory.java:100) at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java :517) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.jav a:567) at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWra pper.java:108) at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.j ava:216) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePha se.java:124) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:103) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:311) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter .java:83) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter .java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter .java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter .java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter .java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter .java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter .java:69) at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter .java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi lter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV alve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV alve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit yAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv e.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.proce ss(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invok e(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j ava:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j ava:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedC onnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal ve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav a:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java :829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce ss(Http11Protocol.java:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44 7) at java.lang.Thread.run(Thread.java:619) Caused by: org.xml.sax.SAXException: Error Handling [vfszip:/C:/jboss-5.1.0.GA/s erver/default/deploy/jbossweb.sar/jsf-libs/jsf-impl.jar/META-INF/mojarra_ext.tag lib.xml@42,29] at com.sun.facelets.compiler.TagLibraryConfig$LibraryHandler.error(TagLi braryConfig.java:376) at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.rootElementSpecified(Unkno wn Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Sourc e) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElemen t(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanR ootElementHook(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent Dispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un known Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Sour ce) at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(SAXParser.java:198) at com.sun.facelets.compiler.TagLibraryConfig.create(TagLibraryConfig.ja va:407) ... 54 more Caused by: org.xml.sax.SAXParseException: Document root element "facelet-taglib" , must match DOCTYPE root "null". at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Un known Source) ... 73 more -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1828) Deprecated usage of runtime components during dependency resolve

by Carlo de Wolf (JIRA)

Deprecated usage of runtime components during dependency resolve ---------------------------------------------------------------- Key: EJBTHREE-1828 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1828 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Carlo de Wolf Assignee: Carlo de Wolf Fix For: 1.1.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

15 years, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (JGRP-641) Explore data center failover for clusters at the JGroups level

by Jimmy Wilson (JIRA)

Explore data center failover for clusters at the JGroups level -------------------------------------------------------------- Key: JGRP-641 URL: http://jira.jboss.com/jira/browse/JGRP-641 Project: JGroups Issue Type: Task Affects Versions: 2.x Reporter: Jimmy Wilson Assigned To: Bela Ban Priority: Minor Explore the possibility of using a JGroups protocol (or other mechanism) to provide data center fail over. Possible use cases: * Primary/Backup * Loadbalancing w/ sticky sessions * Rolling updates * Shared data Wiki generated from this discussion (was JBossCache-specific): http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheAcrossDataCentres The forum discussion has been associated with this JIRA as well. -- 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, 7 months

2
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 2009