April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-627) Response headers do not propagate through the domain

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-627: --------------------------------------- Summary: Response headers do not propagate through the domain Key: WFCORE-627 URL: https://issues.jboss.org/browse/WFCORE-627 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 1.0.0.Beta2 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 1.0.0.CR1 There's no access-control response header here: {code} [domain@localhost:9999 /] /host=master/server=server-one/subsystem=datasources/data-source=ExampleDS:read-resource{roles=Monitor} { "outcome" => "success", "result" => { .... } } {code} ProxyStepHandler needs to pass through response-header data. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-626) Global list-get operation can inadvertently create list elements

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFCORE-626?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFCORE-626: -------------------------------- Summary: Global list-get operation can inadvertently create list elements (was: Global list-get operation can inadvertently create list elements.) > Global list-get operation can inadvertently create list elements > ---------------------------------------------------------------- > > Key: WFCORE-626 > URL: https://issues.jboss.org/browse/WFCORE-626 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Beta2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 1.0.0.CR1 > > > Consider the following sequence of operations: > # :list-clear(name=attribute) > # :list-get(name=attribute, index=0) > # :list-add(name=attribute, value=test) > # :list-get(name=attribute, index=0) > #2 will return <undefined> as expected. The expected result of #4 is "test". However, it returns <undefined>. This is because #2 will create the missing element at index 0 causing #3 to operate on index 1. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-626) Global list-get operation can inadvertently create list elements.

by Paul Ferraro (JIRA)

Paul Ferraro created WFCORE-626: ----------------------------------- Summary: Global list-get operation can inadvertently create list elements. Key: WFCORE-626 URL: https://issues.jboss.org/browse/WFCORE-626 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 1.0.0.Beta2 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 1.0.0.CR1 Consider the following sequence of operations: # :list-clear(name=attribute) # :list-get(name=attribute, index=0) # :list-add(name=attribute, value=test) # :list-get(name=attribute, index=0) #2 will return <undefined> as expected. The expected result of #4 is "test". However, it returns <undefined>. This is because #2 will create the missing element at index 0 causing #3 to operate on index 1. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1259) Tracer improvements

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1259?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1259: ----------------------------------- Description: Add the following events: * PUSH_CCM_CONTEXT * POP_CCM_CONTEXT * REGISTER_CCM_CONNECTION * UNREGISTER_CCM_CONNECTION * CCM_USER_TRANSACTION * UNKNOWN_CCM_CONNECTION * CLOSE_CCM_CONNECTION * VERSION Add 2nd payload field Create reports for CCM interaction Add -ignore-tracking command line option Reference guides for connections, connection listeners and managed connection pools was: Add the following events: * PUSH_CCM_CONTEXT * POP_CCM_CONTEXT * REGISTER_CCM_CONNECTION * UNREGISTER_CCM_CONNECTION * CCM_USER_TRANSACTION * UNKNOWN_CCM_CONNECTION * CLOSE_CCM_CONNECTION * VERSION Add 2nd payload field Create reports for CCM interaction Add -ignore-tracking command line option > Tracer improvements > ------------------- > > Key: JBJCA-1259 > URL: https://issues.jboss.org/browse/JBJCA-1259 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.2.4.Final > > > Add the following events: > * PUSH_CCM_CONTEXT > * POP_CCM_CONTEXT > * REGISTER_CCM_CONNECTION > * UNREGISTER_CCM_CONNECTION > * CCM_USER_TRANSACTION > * UNKNOWN_CCM_CONNECTION > * CLOSE_CCM_CONNECTION > * VERSION > Add 2nd payload field > Create reports for CCM interaction > Add -ignore-tracking command line option > Reference guides for connections, connection listeners and managed connection pools -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4486) When i try to stop the wildfly server using services its not stopping, status is always in stopping state.

by masthan shaik (JIRA)

masthan shaik created WFLY-4486: ----------------------------------- Summary: When i try to stop the wildfly server using services its not stopping, status is always in stopping state. Key: WFLY-4486 URL: https://issues.jboss.org/browse/WFLY-4486 Project: WildFly Issue Type: Bug Components: Server Affects Versions: 8.1.0.Final, 8.0.0.Final Environment: windows 7 operating system,(64bit),Java,web services,jsp,servlets,flex,ejb Reporter: masthan shaik Assignee: Jason Greene Hi , i have installed wildfly server (version 8.1.0) as a service on win7 64 bit machine. When try to stop the service , it is not stopping properly , always status is in stopping state. manually i am killing the java .exe and wildfly-server.exe from task manager and then starting server again. please let me know how to resolve this isssue. Thanks mastan -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4485) Don't Expose JDT Compiler to Web Applications

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/WFLY-4485?page=com.atlassian.jira.plugin.... ] Philippe Marschall commented on WFLY-4485: ------------------------------------------ Is a regression > Don't Expose JDT Compiler to Web Applications > --------------------------------------------- > > Key: WFLY-4485 > URL: https://issues.jboss.org/browse/WFLY-4485 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Affects Versions: 9.0.0.Beta2 > Reporter: Philippe Marschall > Assignee: Stuart Douglas > Labels: classloading, jsp > > Currently the Eclipse JDT compiler is exposed to web applications because the undertow servlet module exposes all its dependencies. > This can break applications that ship their own version of the Eclipse JDT compiler like the Cocoon web framework. > This seems to be a regression. It was already fixed once in WFLY-1770 but seems to be an issue again since undertow JSP is now once again one instead of two modules. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4485) Don't Expose JDT Compiler to Web Applications

by Philippe Marschall (JIRA)

Philippe Marschall created WFLY-4485: ---------------------------------------- Summary: Don't Expose JDT Compiler to Web Applications Key: WFLY-4485 URL: https://issues.jboss.org/browse/WFLY-4485 Project: WildFly Issue Type: Enhancement Components: Web (Undertow) Affects Versions: 9.0.0.Beta2 Reporter: Philippe Marschall Assignee: Stuart Douglas Currently the Eclipse JDT compiler is exposed to web applications because the undertow servlet module exposes all its dependencies. This can break applications that ship their own version of the Eclipse JDT compiler like the Cocoon web framework. This seems to be a regression. It was already fixed once in WFLY-1770 but seems to be an issue again since undertow JSP is now once again one instead of two modules. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JASSIST-245) Javassist 3.19.0-GA causes compilation warnings with -Xlint:classfile

by David Carr (JIRA)

[ https://issues.jboss.org/browse/JASSIST-245?page=com.atlassian.jira.plugi... ] David Carr updated JASSIST-245: ------------------------------- Steps to Reproduce: To reproduce, put the javassist JAR and DescribingHandlers.java (https://gist.github.com/davidmc24/17e120b67ce35831a07a) in a directory and run the following command: {code}javac -Werror -Xlint:classfile -classpath javassist-3.19.0-GA.jar DescribingHandlers.java{code} You should get something like the following output: {code} javassist-3.19.0-GA.jar(javassist/ClassPool.class): warning: [classfile] MethodParameters attribute introduced in version 52.0 class files is ignored in version 50.0 class files javassist-3.19.0-GA.jar(javassist/CtBehavior.class): warning: [classfile] MethodParameters attribute introduced in version 52.0 class files is ignored in version 50.0 class files javassist-3.19.0-GA.jar(javassist/CtClass.class): warning: [classfile] MethodParameters attribute introduced in version 52.0 class files is ignored in version 50.0 class files javassist-3.19.0-GA.jar(javassist/NotFoundException.class): warning: [classfile] MethodParameters attribute introduced in version 52.0 class files is ignored in version 50.0 class files javassist-3.19.0-GA.jar(javassist/bytecode/ClassFile.class): warning: [classfile] MethodParameters attribute introduced in version 52.0 class files is ignored in version 50.0 class files error: warnings found and -Werror specified javassist-3.19.0-GA.jar(javassist/CtMember.class): warning: [classfile] MethodParameters attribute introduced in version 52.0 class files is ignored in version 50.0 class files javassist-3.19.0-GA.jar(javassist/bytecode/MethodInfo.class): warning: [classfile] MethodParameters attribute introduced in version 52.0 class files is ignored in version 50.0 class files 1 error 7 warnings {code} was: To reproduce, put the javassist JAR the attached DescribingHandlers.java file in a directory and run the following command: {code}javac -Werror -Xlint:classfile -classpath javassist-3.19.0-GA.jar DescribingHandlers.java{code} You should get something like the following output: {code} javassist-3.19.0-GA.jar(javassist/ClassPool.class): warning: [classfile] MethodParameters attribute introduced in version 52.0 class files is ignored in version 50.0 class files javassist-3.19.0-GA.jar(javassist/CtBehavior.class): warning: [classfile] MethodParameters attribute introduced in version 52.0 class files is ignored in version 50.0 class files javassist-3.19.0-GA.jar(javassist/CtClass.class): warning: [classfile] MethodParameters attribute introduced in version 52.0 class files is ignored in version 50.0 class files javassist-3.19.0-GA.jar(javassist/NotFoundException.class): warning: [classfile] MethodParameters attribute introduced in version 52.0 class files is ignored in version 50.0 class files javassist-3.19.0-GA.jar(javassist/bytecode/ClassFile.class): warning: [classfile] MethodParameters attribute introduced in version 52.0 class files is ignored in version 50.0 class files error: warnings found and -Werror specified javassist-3.19.0-GA.jar(javassist/CtMember.class): warning: [classfile] MethodParameters attribute introduced in version 52.0 class files is ignored in version 50.0 class files javassist-3.19.0-GA.jar(javassist/bytecode/MethodInfo.class): warning: [classfile] MethodParameters attribute introduced in version 52.0 class files is ignored in version 50.0 class files 1 error 7 warnings {code} > Javassist 3.19.0-GA causes compilation warnings with -Xlint:classfile > --------------------------------------------------------------------- > > Key: JASSIST-245 > URL: https://issues.jboss.org/browse/JASSIST-245 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.19.0-GA > Reporter: David Carr > Assignee: Shigeru Chiba > > Tested using Oracle Java 1.8.0_40. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JASSIST-245) Javassist 3.19.0-GA causes compilation warnings with -Xlint:classfile

by David Carr (JIRA)

David Carr created JASSIST-245: ---------------------------------- Summary: Javassist 3.19.0-GA causes compilation warnings with -Xlint:classfile Key: JASSIST-245 URL: https://issues.jboss.org/browse/JASSIST-245 Project: Javassist Issue Type: Bug Affects Versions: 3.19.0-GA Reporter: David Carr Assignee: Shigeru Chiba Tested using Oracle Java 1.8.0_40. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4478) Server won't shutdown until batch threads are done executing

by Cheng Fang (JIRA)

[ https://issues.jboss.org/browse/WFLY-4478?page=com.atlassian.jira.plugin.... ] Cheng Fang commented on WFLY-4478: ---------------------------------- Calling JobOperator.stop(jobExecutionId) should be able to stop the running job execution, though it's a request to stop. JBeret calls the batchlet's stop() method to stop the batchlet, and a properly implemented batchlet should stop there; or stops the chunk stop execution as soon as the current chunk ends. > Server won't shutdown until batch threads are done executing > ------------------------------------------------------------ > > Key: WFLY-4478 > URL: https://issues.jboss.org/browse/WFLY-4478 > Project: WildFly > Issue Type: Bug > Components: Batch > Reporter: James Perkins > Assignee: James Perkins > > When the server is shutdown, even with {{SIGINT}}, the batch jobs keep running and the JVM will not exit until the batch jobs are complete. Ideally threads spawned from the {{BatchEnvironment}} will be daemon threads. At the least the thread should be interrupted. > Another option would be for JBeret to have a way to stop all running jobs. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
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 April 2015