February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4414) Non Standard SESSIONID not clustered

by Robert Smith (JIRA)

[ https://issues.jboss.org/browse/WFLY-4414?page=com.atlassian.jira.plugin.... ] Robert Smith commented on WFLY-4414: ------------------------------------ No we cannot. We are not on Wildfly 10, we are possibly moving to 9 in the near future. You should be able to test it pretty easily by creating a custom named session id in your web xml. > Non Standard SESSIONID not clustered > ------------------------------------ > > Key: WFLY-4414 > URL: https://issues.jboss.org/browse/WFLY-4414 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.1.0.Final > Reporter: Robert Smith > Assignee: Radoslav Husar > > We are using Wildfly 8.1.0-Final in domain mode with mod-cluster. > We use a non-standard session id in a web application as follows: > ... > <distributable /> > <session-config> > <cookie-config> > <name>VSOPSESSIONID</name> > </cookie-config> > </session-config> > ... > During testing of this we had our sticky set to JSESSIONID which caused requests to be forwarded to our 2 nodes alternatively. > In our 1st request we do: > request.getSession().setAttribute(KEY, value) > In our 2nd request we do: > request.getSession.getAttribute(KEY) > The second request always returns null. > When we remove the custom session id, the session data is avaliable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4414) Non Standard SESSIONID not clustered

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4414?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-4414: -------------------------------------- [~rsmith1] Can you please revalidate with wildfly 10.0.0.Final? > Non Standard SESSIONID not clustered > ------------------------------------ > > Key: WFLY-4414 > URL: https://issues.jboss.org/browse/WFLY-4414 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.1.0.Final > Reporter: Robert Smith > Assignee: Radoslav Husar > > We are using Wildfly 8.1.0-Final in domain mode with mod-cluster. > We use a non-standard session id in a web application as follows: > ... > <distributable /> > <session-config> > <cookie-config> > <name>VSOPSESSIONID</name> > </cookie-config> > </session-config> > ... > During testing of this we had our sticky set to JSESSIONID which caused requests to be forwarded to our 2 nodes alternatively. > In our 1st request we do: > request.getSession().setAttribute(KEY, value) > In our 2nd request we do: > request.getSession.getAttribute(KEY) > The second request always returns null. > When we remove the custom session id, the session data is avaliable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-925) Cannot deploy kie-server to Wildfly 10.0.0.CR1

by Martijn Burger (JIRA)

[ https://issues.jboss.org/browse/DROOLS-925?page=com.atlassian.jira.plugin... ] Martijn Burger commented on DROOLS-925: --------------------------------------- Problem also exists in WildFly 10.0.0.Final proposed (and declined) pull request does not even work for WildFly 10.0.0.Final > Cannot deploy kie-server to Wildfly 10.0.0.CR1 > ---------------------------------------------- > > Key: DROOLS-925 > URL: https://issues.jboss.org/browse/DROOLS-925 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.3.0.CR2 > Environment: Wildfly 10.0.0.CR1 > Reporter: Pokpitch Patcharadamrongkul > Assignee: Edson Tirelli > Priority: Critical > Fix For: 6.4.0.CR1 > > > Cannot deploy kie-server to Wildfly 10.0.0.CR1 (HornetQ is to be deprecated from Wildfly 10.x.x) Please fixed in kie-server-x.x-x.war/META-INF/kie-server-jms.xml > {color:red}Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file /opt/wildfly-10.0.0.CR1/standalone/tmp/vfs/temp/temp8eb8a1f894857057/content-c7b7cd6a0a56658e/META-INF/kie-server-jms.xml > at org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment' > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) > ... 6 more{color} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1395) Remove /host=master/core-service=management/access=authorization

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1395?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet updated WFCORE-1395: -------------------------------------- Description: The /host=master/core-service=management/access=authorization is odd. It should be removed in WF 11. (was: The /host=master/core-service=management/access=authorization is odd. It should be deprecated and made non-functional in WF 11. Non-functional meaning the add / remove / write-attribute handlers log a WARN and do nothing) Summary: Remove /host=master/core-service=management/access=authorization (was: Deprecate /host=master/core-service=management/access=authorization) > Remove /host=master/core-service=management/access=authorization > ---------------------------------------------------------------- > > Key: WFCORE-1395 > URL: https://issues.jboss.org/browse/WFCORE-1395 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.CR1 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Minor > Fix For: 3.0.0.Alpha1 > > > The /host=master/core-service=management/access=authorization is odd. It should be removed in WF 11. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1399) Failure when resolving an expression with the default value containing a '$' at the end

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1399?page=com.atlassian.jira.plugi... ] Alexey Loubyansky commented on WFCORE-1399: ------------------------------------------- Have you seen testDollarEscaping test in that testcase? Try escaping with '$'. > Failure when resolving an expression with the default value containing a '$' at the end > --------------------------------------------------------------------------------------- > > Key: WFCORE-1399 > URL: https://issues.jboss.org/browse/WFCORE-1399 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.CR1 > Reporter: Valentin Maechler > Assignee: ehsavoie Hugonnet > Attachments: ExpressionResolver.java, ExpressionResolverUnitTestCase.java > > > Can not add a JNDI / naming entry which contains a "$" sign at the end of its default value. > e.g. {code} > value="${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$}" > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-820) ClassLoader memory leak with MDB

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/WFLY-820?page=com.atlassian.jira.plugin.s... ] Stefano Maestri closed WFLY-820. -------------------------------- Resolution: Out of Date > ClassLoader memory leak with MDB > -------------------------------- > > Key: WFLY-820 > URL: https://issues.jboss.org/browse/WFLY-820 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Vlad Arkhipov > Assignee: Stefano Maestri > Priority: Critical > Attachments: leak.tar.gz > > > There are still some references to MDB class (NOT to the *instance*) if you undeploy an archive from the AS. Sooner or later it leads to OutOfMemory Permgen exception after multiple redeployments. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1065) ClasspathKieProject should not deal ".jar" always like a file

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1065?page=com.atlassian.jira.plugi... ] Petr Široký resolved DROOLS-1065. --------------------------------- Fix Version/s: 7.0.0.Final Resolution: Done > ClasspathKieProject should not deal ".jar" always like a file > ------------------------------------------------------------- > > Key: DROOLS-1065 > URL: https://issues.jboss.org/browse/DROOLS-1065 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.4.0.Beta1 > Reporter: Petr Široký > Assignee: Petr Široký > Fix For: 7.0.0.Final > > > Originally reported and fixed by David Santos (thanks!) via https://github.com/droolsjbpm/drools/pull/511 > Description: > Some containers allow deployments of artifacts in "expanded" mode (instead of a unique jar/ear/war/... file, al artifacts are deployed full decompressed, so they are directories). This is default with last JBoss Tools and Wildfly (unless you use compressed option for deployments). In that case drools fails to load jar contents. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1399) Failure when resolving an expression with the default value containing a '$' at the end

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1399?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet updated WFCORE-1399: -------------------------------------- Summary: Failure when resolving an expression with the default value containing a '$' at the end (was: CLI: failure when adding a JNDI entry with default value containing a '$' at the end) > Failure when resolving an expression with the default value containing a '$' at the end > --------------------------------------------------------------------------------------- > > Key: WFCORE-1399 > URL: https://issues.jboss.org/browse/WFCORE-1399 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.CR1 > Reporter: Valentin Maechler > Assignee: ehsavoie Hugonnet > Attachments: ExpressionResolver.java, ExpressionResolverUnitTestCase.java > > > Can not add a JNDI / naming entry which contains a "$" sign at the end of its default value. > e.g. {code} > value="${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$}" > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6239) CLI: failure when adding a JNDI entry with default value containing a '$' at the end

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-6239?page=com.atlassian.jira.plugin.... ] ehsavoie Hugonnet reassigned WFLY-6239: --------------------------------------- Assignee: ehsavoie Hugonnet (was: Alexey Loubyansky) > CLI: failure when adding a JNDI entry with default value containing a '$' at the end > ------------------------------------------------------------------------------------ > > Key: WFLY-6239 > URL: https://issues.jboss.org/browse/WFLY-6239 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 2.1.0.CR1 > Reporter: Valentin Maechler > Assignee: ehsavoie Hugonnet > Attachments: ExpressionResolver.java, ExpressionResolverUnitTestCase.java > > > Can not add a JNDI / naming entry which contains a "$" sign at the end of its default value. > e.g. {code} > value="${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$}" > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1399) CLI: failure when adding a JNDI entry with default value containing a '$' at the end

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1399?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet moved WFLY-6239 to WFCORE-1399: ------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1399 (was: WFLY-6239) Component/s: Domain Management (was: CLI) Affects Version/s: (was: 10.0.0.Final) > CLI: failure when adding a JNDI entry with default value containing a '$' at the end > ------------------------------------------------------------------------------------ > > Key: WFCORE-1399 > URL: https://issues.jboss.org/browse/WFCORE-1399 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Valentin Maechler > Assignee: ehsavoie Hugonnet > Attachments: ExpressionResolver.java, ExpressionResolverUnitTestCase.java > > > Can not add a JNDI / naming entry which contains a "$" sign at the end of its default value. > e.g. {code} > value="${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$}" > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

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 February 2016