June 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4917) paths need to allow expressions in its 'path' attribute

by Tom Fonteyne (JIRA)

Tom Fonteyne created AS7-4917: --------------------------------- Summary: paths need to allow expressions in its 'path' attribute Key: AS7-4917 URL: https://issues.jboss.org/browse/AS7-4917 Project: Application Server 7 Issue Type: Feature Request Components: Logging Affects Versions: 7.1.2.Final (EAP) Reporter: Tom Fonteyne Assignee: Brian Stansberry The "paths" section should allow expressions for "path" elements Rationale is the fact that customers often want the log files to be send to another directory "outside" of the JBoss directory. <periodic-rotating-file-handler name="FILE"> ... <file relative-to="jboss.server.log.dir" path="server.log"/> You can change the above and hardcode to : <file path="/logs/jboss/server.log"/> but that means that as soon as you have two servers on the same machine, using the same profile, they will write to a single logfile. The "file"s "path" attribute does not allow expressions; this RFE is however not for this attribute. As relative-to="jboss.server.log.dir" can use self-defined names paths, we looked at the "paths" section. <paths> <path name="my.log" path="/logs/jboss/${my.system.propery}"/> </paths> but as it turns out, the "path" attribute of the "path" tag also does not allow expressions, and the above entry fails. Hence: please allow the "path" attribute of the "path" tag to allow expressions so that the above "paths" example works. Note that we consider this "Major" as customer do/want this functionality often. -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] (AS7-4931) configuration history length and the number of days they are kept is hardcoded - this needs to be configurable

by Tom Fonteyne (JIRA)

Tom Fonteyne created AS7-4931: --------------------------------- Summary: configuration history length and the number of days they are kept is hardcoded - this needs to be configurable Key: AS7-4931 URL: https://issues.jboss.org/browse/AS7-4931 Project: Application Server 7 Issue Type: Feature Request Components: ConfigAdmin Affects Versions: 7.1.2.Final (EAP) Reporter: Tom Fonteyne Assignee: David Bosschaert Priority: Minor Currently 100 configuration settings are kept for 30 days. These settings are hard-coded in org/ jboss/ as/ controller/ persistence/ ConfigurationFile.java 057 private static final int CURRENT_HISTORY_LENGTH = 100; 058 private static final int HISTORY_DAYS = 30; Please make these configurable settings. -- 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, 9 months

4
4
0 / 0

[JBoss JIRA] (AS7-3959) SerializingCloner can't clone primitive data types

by Sebastian Woeste (JIRA)

Sebastian Woeste created AS7-3959: ------------------------------------- Summary: SerializingCloner can't clone primitive data types Key: AS7-3959 URL: https://issues.jboss.org/browse/AS7-3959 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.0.Final Reporter: Sebastian Woeste Assignee: jaikiran pai If i try to invoke a method remote the arguments will be cloned by org.jboss.marshalling.cloner.SerializingCloner. The SerializingCloner calls the ClassLoaderClassCloner.clone(final Class<?> original) method where an exception will be thrown if the argument is a primitive data type. See the forum reference for some more details. -- 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, 9 months

4
13
0 / 0

[JBoss JIRA] (JASSIST-171) Calling SignatureAttribute$MethodSignature.toString results in RuntimeException: bad descriptor

by ami tabak (JIRA)

ami tabak created JASSIST-171: --------------------------------- Summary: Calling SignatureAttribute$MethodSignature.toString results in RuntimeException: bad descriptor Key: JASSIST-171 URL: https://issues.jboss.org/browse/JASSIST-171 Project: Javassist Issue Type: Feature Request Affects Versions: 3.16.1-GA Reporter: ami tabak Assignee: Shigeru Chiba When attempting to instrument "org.apache.hadoop.examples.WordCount$TokenizerMapper" Am getting the following error: Exception in thread "main" java.lang.RuntimeException: bad descriptor: o at javassist.bytecode.Descriptor.toClassName(Descriptor.java:105) at javassist.bytecode.SignatureAttribute$BaseType.toString(SignatureAttribute.java:450) at java.lang.String.valueOf(Unknown Source) at java.lang.StringBuffer.append(Unknown Source) at javassist.bytecode.SignatureAttribute$Type.toString(SignatureAttribute.java:419) at javassist.bytecode.SignatureAttribute$MethodSignature.toString(SignatureAttribute.java:275) at java.lang.String.valueOf(Unknown Source) at java.lang.StringBuilder.append(Unknown Source) at com.optier.bug.report.Test.main(Test.java:50) -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] (AS7-4928) Upgrade Hibernate to 4.1.4

by Júlio Cezar Santos Pires (JIRA)

Júlio Cezar Santos Pires created AS7-4928: --------------------------------------------- Summary: Upgrade Hibernate to 4.1.4 Key: AS7-4928 URL: https://issues.jboss.org/browse/AS7-4928 Project: Application Server 7 Issue Type: Component Upgrade Components: JPA / Hibernate Reporter: Júlio Cezar Santos Pires Assignee: Scott Marlow New version of Hibernate has several fixes. Changelog: https://hibernate.onjira.com/secure/ReleaseNote.jspa?projectId=10031&vers... -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] (AS7-2534) JSF "View could not be restored" if cookies disabled in browser

by Marek Schmidt (Created) (JIRA)

JSF "View could not be restored" if cookies disabled in browser --------------------------------------------------------------- Key: AS7-2534 URL: https://issues.jboss.org/browse/AS7-2534 Project: Application Server 7 Issue Type: Bug Components: JSF Affects Versions: 7.1.0.Alpha1, 7.0.2.Final Environment: JBossAS 7.1.0.Alpha2-SNAPSHOT from 2011-11-07, firefox 3.6.23, Google Chrome 15.0.874.106 Reporter: Marek Schmidt Assignee: Stan Silvert Attachments: jboss-as-numberguess-nocdi.war A JSF application doesn't work if cookies are disabled in browser. The same WAR works on AS6. The generated front page of the app contains `action="/jboss-as-numberguess-nocdi/home.jsf"' attribute in the form element on AS7, while it does contain `/jboss-as-numberguess-nocdi/home.jsf;jsessionid=835F17A..."' on AS 6.1.0. Submitting a form in the app returns HTTP 500 and logs the following exception: 15:14:54,932 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/jboss-as-numberguess-nocdi].[Faces Servlet]] (http-localhost.localdomain-127.0.0.1-8080-2) Servlet.service() for servlet Faces Servlet threw exception: javax.faces.application.ViewExpiredException: viewId:/home.jsf - View /home.jsf could not be restored. at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:205) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.3-b02-jbossorg-2.jar:2.1.3-SNAPSHOT] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.0.0.Beta1.jar:2.0.0.Beta1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:155) [jboss-as-web-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at java.lang.Thread.run(Thread.java:636) [:1.6.0_20] -- 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, 9 months

5
7
0 / 0

[JBoss JIRA] (AS7-4969) Upgrade Mojarra to 2.1.9

by Juergen Zimmermann (JIRA)

Juergen Zimmermann created AS7-4969: --------------------------------------- Summary: Upgrade Mojarra to 2.1.9 Key: AS7-4969 URL: https://issues.jboss.org/browse/AS7-4969 Project: Application Server 7 Issue Type: Feature Request Components: JSF Affects Versions: 7.1.2.Final (EAP) Reporter: Juergen Zimmermann Assignee: Stan Silvert JBossAS 7.1.2 provides Mojarra 2.1.7. Meanwhile there is 2.1.9 at https://maven.java.net/content/repositories/releases/com/sun/faces/jsf-api and https://maven.java.net/content/repositories/releases/com/sun/faces/jsf-impl. IMHO, especially these 2 fixes are relevant: http://java.net/jira/browse/JAVASERVERFACES-2414 http://java.net/jira/browse/JAVASERVERFACES-2405 -- 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, 9 months

2
5
0 / 0

[JBoss JIRA] (AS7-3697) Intermittent failures in ModelControllerImplUnitTestCase

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-3697: ------------------------------------- Summary: Intermittent failures in ModelControllerImplUnitTestCase Key: AS7-3697 URL: https://issues.jboss.org/browse/AS7-3697 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.1.Final >From Jason: Failed tests: testRemoveDependentNonRecursive(org.jboss.as.controller.ModelControllerImplUnitTestCase): expected:<UP> but was:<DOWN> that one seems to fail semi-frequently (on lightning) semi being like every other day -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (SECURITY-129) Client Delegation

by Darran Lofthouse (JIRA)

Client Delegation ----------------- Key: SECURITY-129 URL: http://jira.jboss.com/jira/browse/SECURITY-129 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Web browser can delegate to the server being called so same credentials can be used for further calls. Delegation using GSSAPI, WS-Kerberos, credential propagation for EJB calls 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

13 years, 9 months

2
13
0 / 0

[JBoss JIRA] (AS7-3286) Regster InitialContextFactoryBuilder service the the OSGi layer to enable OSGi spec-compliant JNDI integration

by David Bosschaert (JIRA)

David Bosschaert created AS7-3286: ------------------------------------- Summary: Regster InitialContextFactoryBuilder service the the OSGi layer to enable OSGi spec-compliant JNDI integration Key: AS7-3286 URL: https://issues.jboss.org/browse/AS7-3286 Project: Application Server 7 Issue Type: Task Components: Naming Reporter: David Bosschaert Assignee: David Bosschaert Fix For: 7.1.0.Final In order to facilitate integration with the OSGi JNDI specification, an InitialContextFactoryBuilder needs to be registered as an MSC service. -- 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, 9 months

3
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 June 2012