[JBoss JIRA] (WFCORE-1274) CLI resolve-parameter-values set to true does not recognise vaulted strings
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1274?page=com.atlassian.jira.plugi... ]
Lin Gao closed WFCORE-1274.
---------------------------
Resolution: Rejected
> CLI resolve-parameter-values set to true does not recognise vaulted strings
> ---------------------------------------------------------------------------
>
> Key: WFCORE-1274
> URL: https://issues.jboss.org/browse/WFCORE-1274
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 2.0.5.Final
> Reporter: Lin Gao
> Assignee: Lin Gao
>
> When enabling
> <resolve-parameter-values>true</resolve-parameter-values>
> in "bin\jboss-cli.xml"
> vaulted string will get misinterpreted.
> Example, if a command has "${VAULT::tom::tom::1}" then
> the parser sees this as ${name:defaultValue} with
> name="VAULT"
> defaultValue=":tom::tom::1"
> Escaping the $ sign in various ways did not help. The only way is to switch <resolve-parameter-values> back to false.
> Ideally, the parser should recognize vaulted string and pass then in unchanged.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFCORE-1287) session.invalidate() throw NullPointerException on invalidated session with replication-granularity set to ATTRIBUTE
by Sammy Chu (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1287?page=com.atlassian.jira.plugi... ]
Sammy Chu updated WFCORE-1287:
------------------------------
Steps to Reproduce:
# Deploy session-invalidate-replication-attribute.war to Wildfly 8.
# Access http://localhost:8080/session-invalidate-replication-attribute/ , you should see the current session ID listed
# Click the "Invalidate It" link
# NullPointerExpcetion occurred
The expected result should be throwing IllegalStateException as others (session-invalidate-noreplication.war, session-invalidate-replication-session.war) does.
was:
# Deploy session-invalidate-replication-attribute.war to Wildfly 8.
# Access http://localhost:8080/session-invalidate-replication-attribute/ , you should see the current session listed
# Click the "Invalidate It" link
# NullPointerExpcetion occurred
The expected result should be throwing IllegalStateException as others (session-invalidate-noreplication.war, session-invalidate-replication-session.war) does.
> session.invalidate() throw NullPointerException on invalidated session with replication-granularity set to ATTRIBUTE
> --------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1287
> URL: https://issues.jboss.org/browse/WFCORE-1287
> Project: WildFly Core
> Issue Type: Bug
> Environment: Wildfly 8.2.1-Final
> JDK 1.8.0_66-b17
> Windows & Linux
> Reporter: Sammy Chu
> Attachments: session-invalidate-noreplication.war, session-invalidate-replication-attribute.war, session-invalidate-replication-session.war
>
>
> We suspected that calling session.invalidate() on an already invalidated session with replication-granularity set to "ATTRIBUTE" will throw a NullPointerException, but from the specification it should throw an IllegalStateException instead.
> Stack trace as below:
> {noformat}
> 13:12:35,554 ERROR [io.undertow.request] (default task-32) UT005023: Exception handling request to /<our system url>: java.lang.NullPointerException
> at org.wildfly.clustering.web.infinispan.session.fine.FineSessionFactory$1.invoke(FineSessionFactory.java:103)
> at org.wildfly.clustering.web.infinispan.session.fine.FineSessionFactory$1.invoke(FineSessionFactory.java:100)
> at org.jboss.as.clustering.infinispan.invoker.SimpleCacheInvoker.invoke(SimpleCacheInvoker.java:34)
> at org.jboss.as.clustering.infinispan.invoker.RetryingCacheInvoker.invoke(RetryingCacheInvoker.java:87)
> at org.wildfly.clustering.web.infinispan.session.fine.FineSessionFactory.remove(FineSessionFactory.java:109)
> at org.wildfly.clustering.web.infinispan.session.fine.FineSessionFactory.remove(FineSessionFactory.java:53)
> at org.wildfly.clustering.web.infinispan.session.InfinispanSession.invalidate(InfinispanSession.java:74)
> at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$SchedulableSession.invalidate(InfinispanSessionManager.java:359)
> at org.wildfly.clustering.web.undertow.session.DistributableSession.invalidate(DistributableSession.java:140)
> at io.undertow.servlet.spec.HttpSessionImpl.invalidate(HttpSessionImpl.java:199) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
> ... // our application code, just calling "session.invalidate()"
> {noformat}
> We also enclosed the simplified samples to reproduce this issue (session-invalidate-noreplication.war, session-invalidate-replication-attribute.war, session-invalidate-replication-session.war). In general they are the same except the replication-granularity (in jboss-web.xml => replication-granularity) settings.
> # session-invalidate-noreplication.war and session-invalidate-replication-session.war works correctly as they are throwing IllegalStateException.
> # session-invalidate-replication-attribute.war is buggy because it throw NullPointerException instead.
> For more information, please refer to https://developer.jboss.org/message/947295
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFCORE-1287) session.invalidate() throw NullPointerException on invalidated session with replication-granularity set to ATTRIBUTE
by Sammy Chu (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1287?page=com.atlassian.jira.plugi... ]
Sammy Chu updated WFCORE-1287:
------------------------------
Steps to Reproduce:
# Deploy session-invalidate-replication-attribute.war to Wildfly 8.
# Access http://localhost:8080/session-invalidate-replication-attribute/ , you should see the current session listed
# Click the "Invalidate It" link
# NullPointerExpcetion occurred
The expected result should be throwing IllegalStateException as others (session-invalidate-noreplication.war, session-invalidate-replication-session.war) does.
was:
# Deploy session-invalidate-replication-attribute.war to Wildfly 8.
# Access http://localhost:8080/session-invalidate-replication-attribute/ , you should see the # current session listed
# Click the "Invalidate It" link
# NullPointerExpcetion occurred
The expected result should be throwing IllegalStateException as others (session-invalidate-noreplication.war, session-invalidate-replication-session.war) does.
> session.invalidate() throw NullPointerException on invalidated session with replication-granularity set to ATTRIBUTE
> --------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1287
> URL: https://issues.jboss.org/browse/WFCORE-1287
> Project: WildFly Core
> Issue Type: Bug
> Environment: Wildfly 8.2.1-Final
> JDK 1.8.0_66-b17
> Windows & Linux
> Reporter: Sammy Chu
> Attachments: session-invalidate-noreplication.war, session-invalidate-replication-attribute.war, session-invalidate-replication-session.war
>
>
> We suspected that calling session.invalidate() on an already invalidated session with replication-granularity set to "ATTRIBUTE" will throw a NullPointerException, but from the specification it should throw an IllegalStateException instead.
> Stack trace as below:
> {noformat}
> 13:12:35,554 ERROR [io.undertow.request] (default task-32) UT005023: Exception handling request to /<our system url>: java.lang.NullPointerException
> at org.wildfly.clustering.web.infinispan.session.fine.FineSessionFactory$1.invoke(FineSessionFactory.java:103)
> at org.wildfly.clustering.web.infinispan.session.fine.FineSessionFactory$1.invoke(FineSessionFactory.java:100)
> at org.jboss.as.clustering.infinispan.invoker.SimpleCacheInvoker.invoke(SimpleCacheInvoker.java:34)
> at org.jboss.as.clustering.infinispan.invoker.RetryingCacheInvoker.invoke(RetryingCacheInvoker.java:87)
> at org.wildfly.clustering.web.infinispan.session.fine.FineSessionFactory.remove(FineSessionFactory.java:109)
> at org.wildfly.clustering.web.infinispan.session.fine.FineSessionFactory.remove(FineSessionFactory.java:53)
> at org.wildfly.clustering.web.infinispan.session.InfinispanSession.invalidate(InfinispanSession.java:74)
> at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$SchedulableSession.invalidate(InfinispanSessionManager.java:359)
> at org.wildfly.clustering.web.undertow.session.DistributableSession.invalidate(DistributableSession.java:140)
> at io.undertow.servlet.spec.HttpSessionImpl.invalidate(HttpSessionImpl.java:199) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
> ... // our application code, just calling "session.invalidate()"
> {noformat}
> We also enclosed the simplified samples to reproduce this issue (session-invalidate-noreplication.war, session-invalidate-replication-attribute.war, session-invalidate-replication-session.war). In general they are the same except the replication-granularity (in jboss-web.xml => replication-granularity) settings.
> # session-invalidate-noreplication.war and session-invalidate-replication-session.war works correctly as they are throwing IllegalStateException.
> # session-invalidate-replication-attribute.war is buggy because it throw NullPointerException instead.
> For more information, please refer to https://developer.jboss.org/message/947295
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFCORE-1287) session.invalidate() throw NullPointerException on invalidated session with replication-granularity set to ATTRIBUTE
by Sammy Chu (JIRA)
Sammy Chu created WFCORE-1287:
---------------------------------
Summary: session.invalidate() throw NullPointerException on invalidated session with replication-granularity set to ATTRIBUTE
Key: WFCORE-1287
URL: https://issues.jboss.org/browse/WFCORE-1287
Project: WildFly Core
Issue Type: Bug
Environment: Wildfly 8.2.1-Final
JDK 1.8.0_66-b17
Windows & Linux
Reporter: Sammy Chu
Attachments: session-invalidate-noreplication.war, session-invalidate-replication-attribute.war, session-invalidate-replication-session.war
We suspected that calling session.invalidate() on an already invalidated session with replication-granularity set to "ATTRIBUTE" will throw a NullPointerException, but from the specification it should throw an IllegalStateException instead.
Stack trace as below:
{noformat}
13:12:35,554 ERROR [io.undertow.request] (default task-32) UT005023: Exception handling request to /<our system url>: java.lang.NullPointerException
at org.wildfly.clustering.web.infinispan.session.fine.FineSessionFactory$1.invoke(FineSessionFactory.java:103)
at org.wildfly.clustering.web.infinispan.session.fine.FineSessionFactory$1.invoke(FineSessionFactory.java:100)
at org.jboss.as.clustering.infinispan.invoker.SimpleCacheInvoker.invoke(SimpleCacheInvoker.java:34)
at org.jboss.as.clustering.infinispan.invoker.RetryingCacheInvoker.invoke(RetryingCacheInvoker.java:87)
at org.wildfly.clustering.web.infinispan.session.fine.FineSessionFactory.remove(FineSessionFactory.java:109)
at org.wildfly.clustering.web.infinispan.session.fine.FineSessionFactory.remove(FineSessionFactory.java:53)
at org.wildfly.clustering.web.infinispan.session.InfinispanSession.invalidate(InfinispanSession.java:74)
at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager$SchedulableSession.invalidate(InfinispanSessionManager.java:359)
at org.wildfly.clustering.web.undertow.session.DistributableSession.invalidate(DistributableSession.java:140)
at io.undertow.servlet.spec.HttpSessionImpl.invalidate(HttpSessionImpl.java:199) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]
... // our application code, just calling "session.invalidate()"
{noformat}
We also enclosed the simplified samples to reproduce this issue (session-invalidate-noreplication.war, session-invalidate-replication-attribute.war, session-invalidate-replication-session.war). In general they are the same except the replication-granularity (in jboss-web.xml => replication-granularity) settings.
# session-invalidate-noreplication.war and session-invalidate-replication-session.war works correctly as they are throwing IllegalStateException.
# session-invalidate-replication-attribute.war is buggy because it throw NullPointerException instead.
For more information, please refer to https://developer.jboss.org/message/947295
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5970) Plain JMS clients don't fallback
by Yong Hao Gao (JIRA)
Yong Hao Gao created WFLY-5970:
----------------------------------
Summary: Plain JMS clients don't fallback
Key: WFLY-5970
URL: https://issues.jboss.org/browse/WFLY-5970
Project: WildFly
Issue Type: Bug
Components: EE
Affects Versions: 9.0.2.Final
Environment: all
Reporter: Yong Hao Gao
Assignee: Yong Hao Gao
Fix For: 9.x.x TBD
Plain JMS clients don't fallback when the Live server takes over
Version-Release number of selected component
messaging subsystem 1.4
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (ELY-403) Add permissive mode to WildflySecurityManager to log policy exceptions but not enforce them.
by Jason Shepherd (JIRA)
[ https://issues.jboss.org/browse/ELY-403?page=com.atlassian.jira.plugin.sy... ]
Jason Shepherd commented on ELY-403:
------------------------------------
Thanks David, works well for me.
> Add permissive mode to WildflySecurityManager to log policy exceptions but not enforce them.
> --------------------------------------------------------------------------------------------
>
> Key: ELY-403
> URL: https://issues.jboss.org/browse/ELY-403
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: Security Manager
> Affects Versions: 1.1.0.Beta3
> Reporter: Jason Shepherd
> Assignee: David Lloyd
>
> If you enable the security manager the any policies in force will halt the execution of your application at the first policy violation, making creating a policy tedious. With this feature enabled a developer can enable the security manager, but also set it to permissive mode. This will result in the required policy rules being logged, making policy generation possible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5519) Some clustering tests fails with security manager
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5519?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on WFLY-5519 at 1/10/16 5:59 PM:
---------------------------------------------------------------
Some permissions need to be granted for the test (e.g. to read property and WF server permissions for singleton service), see my branch [1]. See ISPN-6049 for Infinispan part of this and JBMAR-179 for JBoss Marshalling part.
[1] https://github.com/rhusar/wildfly/tree/WFLY-5519
was (Author: rhusar):
See ISPN-6049 for Infinispan part of this.
> Some clustering tests fails with security manager
> -------------------------------------------------
>
> Key: WFLY-5519
> URL: https://issues.jboss.org/browse/WFLY-5519
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Test Suite
> Affects Versions: 10.0.0.CR2
> Reporter: Marek Kopecký
> Assignee: Radoslav Husar
> Attachments: clustering.secman.zip
>
>
> *Description of problem:*
> Some clustering tests fails with security manager. Affected testcases:
> {noformat}org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover
> org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover
> org.jboss.as.test.clustering.cluster.dispatcher.CommandDispatcherTestCase(SYNC-tcp).test
> org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).failoverOnStop
> org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).nestedBeanFailover
> org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).connectionFactoryFailover
> org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).jmsConnectionFactoryFailover
> org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).noFailover
> org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).simpleFailover
> org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulTimeoutTestCase(SYNC-tcp).timeout
> org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testBasicXPC
> org.jboss.as.test.clustering.cluster.ejb.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testSecondLevelCache
> org.jboss.as.test.clustering.cluster.provider.ServiceProviderRegistrationTestCase(SYNC-tcp).test
> org.jboss.as.test.clustering.cluster.registry.RegistryTestCase(SYNC-tcp).test
> org.jboss.as.test.clustering.cluster.singleton.SingletonServiceTestCase(SYNC-tcp).testSingletonService
> org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase(SYNC-tcp).testFormAuthSingleSignOn
> org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testSerialized
> org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testSessionReplication
> org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testGracefulServeOnUndeploy
> org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testGracefulServeOnShutdown
> org.jboss.as.test.clustering.cluster.web.ExternalizerTestCase(SYNC-tcp).test
> org.jboss.as.test.clustering.cluster.web.ReplicationForNegotiationAuthenticatorTestCase(SYNC-tcp).testOneRequestSimpleFailover
> org.jboss.as.test.clustering.cluster.web.async.AsyncServletTestCase(SYNC-tcp).test
> org.jboss.as.test.clustering.cluster.web.context.InvalidateConversationTestCase(SYNC-tcp).testInvalidate
> org.jboss.as.test.clustering.cluster.web.expiration.CoarseSessionExpirationTestCase(SYNC-tcp).test
> org.jboss.as.test.clustering.cluster.web.expiration.FineSessionExpirationTestCase(SYNC-tcp).test
> org.jboss.as.test.clustering.cluster.web.passivation.CoarseSessionPassivationTestCase(SYNC-tcp).test
> org.jboss.as.test.clustering.cluster.web.passivation.FineSessionPassivationTestCase(SYNC-tcp).test
> org.jboss.as.test.clustering.cluster.web.shared.SharedSessionFailoverTestCase(SYNC-tcp).test
> org.jboss.as.test.clustering.single.registry.RegistryTestCase.org.jboss.as.test.clustering.single.registry.RegistryTestCase
> org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase.org.jboss.as.test.clustering.single.singleton.SingletonServiceTestCase{noformat}
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # ./integration-tests.sh -Dmaven.repo.local=$MAVEN_REPO_LOCAL -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -Dmcast=$MCAST_ADDR -Djboss.dist=$JBOSS_DIST -Dsecurity.manager -Dts.clustering -Dts.noSmoke
> *Actual results:*
> See attached logs
> *Expected results:*
> No errors
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months