December 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1112) DataSource marked as Serializable

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1112?page=com.atlassian.jira.plugin... ] Paul Ferraro updated JBJCA-1112: -------------------------------- Forum Reference: https://community.jboss.org/message/848009 > DataSource marked as Serializable > --------------------------------- > > Key: JBJCA-1112 > URL: https://issues.jboss.org/browse/JBJCA-1112 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.21.Final, 1.1.1.Final > Reporter: Paul Ferraro > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.24.Final, 1.1.2.Final > > > See JBPAPP6-1762 for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1112) DataSource marked as Serializable

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1112?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on JBJCA-1112: ------------------------------------- Here is the forum post as requested: https://community.jboss.org/message/848009 > DataSource marked as Serializable > --------------------------------- > > Key: JBJCA-1112 > URL: https://issues.jboss.org/browse/JBJCA-1112 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.21.Final, 1.1.1.Final > Reporter: Paul Ferraro > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.24.Final, 1.1.2.Final > > > See JBPAPP6-1762 for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2597) Incorrect help message for add-user

by Arun Gupta (JIRA)

[ https://issues.jboss.org/browse/WFLY-2597?page=com.atlassian.jira.plugin.... ] Arun Gupta commented on WFLY-2597: ---------------------------------- Seems like there are three options with exact same text help: -s, --silent Activate the silent mode (no output to the console) -e, --enable Activate the silent mode (no output to the console) -d, --disable Activate the silent mode (no output to the console) > Incorrect help message for add-user > ----------------------------------- > > Key: WFLY-2597 > URL: https://issues.jboss.org/browse/WFLY-2597 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Arun Gupta > Priority: Minor > > add-user --help shows the following message: > -e, --enable Activate the silent mode (no output to > the console) > -d, --disable Activate the silent mode (no output to > the console) > Both the options provide the exact same help text. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2597) Incorrect help message for add-user

by Arun Gupta (JIRA)

Arun Gupta created WFLY-2597: -------------------------------- Summary: Incorrect help message for add-user Key: WFLY-2597 URL: https://issues.jboss.org/browse/WFLY-2597 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Arun Gupta Priority: Minor add-user --help shows the following message: -e, --enable Activate the silent mode (no output to the console) -d, --disable Activate the silent mode (no output to the console) Both the options provide the exact same help text. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1112) DataSource marked as Serializable

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1112?page=com.atlassian.jira.plugin... ] Paul Ferraro reopened JBJCA-1112: --------------------------------- > DataSource marked as Serializable > --------------------------------- > > Key: JBJCA-1112 > URL: https://issues.jboss.org/browse/JBJCA-1112 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.21.Final, 1.1.1.Final > Reporter: Paul Ferraro > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.24.Final, 1.1.2.Final > > > See JBPAPP6-1762 for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-367) CLONE - XML schema; use of elementFormDefault='unqualified'; cannot validate some documents

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBMETA-367?page=com.atlassian.jira.plugin... ] Viacheslav Kabanovich commented on JBMETA-367: ---------------------------------------------- https://github.com/wildfly/wildfly/pull/5560 > CLONE - XML schema; use of elementFormDefault='unqualified'; cannot validate some documents > ------------------------------------------------------------------------------------------- > > Key: JBMETA-367 > URL: https://issues.jboss.org/browse/JBMETA-367 > Project: JBoss Metadata > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Elias Ross > > When attempting to write a (seemingly) valid jboss-deployment-structure.xml using the schema in ./docs, my document fails to validate. > This is because of the settings used in the XSD. Have these XSDs been used to validate actual documents? By setting unqualified to 'qualified' then the documents will probably validate. > $ git grep elementFormDefault..unqualified > jboss-deployment-dependencies-1_0.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_0.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_1.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_2.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_0.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_1.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_2.xsd: elementFormDefault="unqualified" > jboss-jpa_1_0.xsd: elementFormDefault="unqualified" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2505) JGroups subsystem should REJECT relay configuration instead of DISCARD

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-2505?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on WFLY-2505: ------------------------------------------- Added test cases for testing transformation to legacy EAP versions. > JGroups subsystem should REJECT relay configuration instead of DISCARD > ---------------------------------------------------------------------- > > Key: WFLY-2505 > URL: https://issues.jboss.org/browse/WFLY-2505 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Richard Achmatowicz > Fix For: 8.0.0.CR1 > > > https://github.com/wildfly/wildfly/blob/master/clustering/jgroups/src/mai... > Richard is taking this on along new transformer API shift. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2596) JASPI Web layer problems

by István Tóth (JIRA)

István Tóth created WFLY-2596: --------------------------------- Summary: JASPI Web layer problems Key: WFLY-2596 URL: https://issues.jboss.org/browse/WFLY-2596 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Undertow) Affects Versions: 8.0.0.CR1 Environment: Fedora 19, x86_64 Reporter: István Tóth Assignee: Stuart Douglas I have found several problems in the current (master, trunk) Wildfly JASPI Web layer implementation Undertow related: ---------------------- * It does not support pre-emptive authentication: When the ServerAuthenticationModule returns AUTH_SUCCESS and null userPrincipal, it should let the request fall through unathenticated, instead it is rejected. * It does not call secureResponse when the authentication was unsuccessful * It does not populate the org.jboss.security.SecurityContext, only the undertow Account structure. * It does not support the wrapper feature (Spec 3.8.3.5 and B.9) The attached pull request aims to fix the first three issues. Credits: This patch is based on Arjan Tijms' analysis, and suggested patches for the Jboss 7.X valve based authentitactor. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2525) Atmosphere connection fails using long-polling transport (probable regression from WFLY-2416)

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-2525?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-2525. ---------------------------------- Fix Version/s: 8.0.0.CR1 Resolution: Done > Atmosphere connection fails using long-polling transport (probable regression from WFLY-2416) > --------------------------------------------------------------------------------------------- > > Key: WFLY-2525 > URL: https://issues.jboss.org/browse/WFLY-2525 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.CR1 > Environment: wildfly-8.0.0.Beta2-SNAPSHOT build #786 (undertow 1.0.0.beta23) > atmosphere chat-multiroom sample: > https://github.com/Atmosphere/atmosphere-samples/tree/master/samples/chat... > Reporter: John Teller > Assignee: Stuart Douglas > Fix For: 8.0.0.CR1 > > > In previous Atmosphere tests with undertow beta20, attempting to connect using websocket transport failed, then fell back successfully to long-polling. In latest test with undertow beta23, websocket transport now works correctly, but attempting to connect using long-polling transport now results in the following error: > 2013-11-17 21:57:32,857 ERROR [org.atmosphere.cpr.AtmosphereFramework] (default task-6) AtmosphereFramework exception: java.lang.IllegalStateException: UT010026: Async is not supported for this request, as not all filters or Servlets were marked as supporting async > at io.undertow.servlet.spec.HttpServletRequestImpl.startAsync(HttpServletRequestImpl.java:909) [undertow-servlet-1.0.0.Beta23.jar:1.0.0.Beta23] > at org.atmosphere.cpr.AtmosphereRequest.startAsync(AtmosphereRequest.java:503) [atmosphere-runtime-2.0.3.jar:2.0.3] > at org.atmosphere.container.Servlet30CometSupport.suspend(Servlet30CometSupport.java:128) [atmosphere-runtime-2.0.3.jar:2.0.3] > at org.atmosphere.container.Servlet30CometSupport.service(Servlet30CometSupport.java:103) [atmosphere-runtime-2.0.3.jar:2.0.3] > at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1684) [atmosphere-runtime-2.0.3.jar:2.0.3] > at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:198) [atmosphere-runtime-2.0.3.jar:2.0.3] > at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:184) [atmosphere-runtime-2.0.3.jar:2.0.3] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:114) [undertow-websockets-jsr-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:59) [undertow-servlet-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta23.jar:1.0.0.Beta23] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:81) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:239) [undertow-servlet-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:226) [undertow-servlet-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:72) [undertow-servlet-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:145) [undertow-servlet-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:139) [undertow-core-1.0.0.Beta23.jar:1.0.0.Beta23] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:637) [undertow-core-1.0.0.Beta23.jar:1.0.0.Beta23] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1112) DataSource marked as Serializable

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1112?page=com.atlassian.jira.plugin... ] Jesper Pedersen commented on JBJCA-1112: ---------------------------------------- Please, provide the information in the forum - https://community.jboss.org/en/ironjacamar > DataSource marked as Serializable > --------------------------------- > > Key: JBJCA-1112 > URL: https://issues.jboss.org/browse/JBJCA-1112 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.21.Final, 1.1.1.Final > Reporter: Paul Ferraro > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.24.Final, 1.1.2.Final > > > See JBPAPP6-1762 for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2013