[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections
by Jan-Willem Gmelig Meyling (Jira)
[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ]
Jan-Willem Gmelig Meyling commented on WFLY-10531:
--------------------------------------------------
Thanks for providing a test! I'll have a look at your test case as well, I am very interested what to find during debugging. As indicated on your PR, I've built your changes locally and rolled them out to my staging server and the issue is in fact gone for me!
> Wildfly leaks ActiveMQ connections
> ----------------------------------
>
> Key: WFLY-10531
> URL: https://issues.jboss.org/browse/WFLY-10531
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Environment: openjdk 8 / openjdk 9, Linux
> Reporter: Marcel Šebek
> Assignee: Jeff Mesnil
> Priority: Major
> Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip
>
>
> After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on
> IJ000453: Unable to get managed connection for java:/JmsXA
> and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log:
> WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69)
> Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time.
> It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3075) Set XStream mode via http header
by Geoffrey De Smet (Jira)
[ https://issues.jboss.org/browse/DROOLS-3075?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-3075:
-------------------------------------
Description:
Currently kie-server only supports XPath references in XStream. Add a http header to make kie-server's XStream marshaller call:
{code}
xStream.setMode(XStream.ID_REFERENCES);
{code}
Motivation by community user:
It's very usefull for projects developed via kie-wb to set XStream mode (ID or ID_REFERENCES) similar to how there's a http parameter to switch between xstream xml, jaxb xml and jackson json.
Actually when submit to kie-server an xml body to post for solution (optaplanner feature) an error *com.thoughtworks.xstream.converters.ConversionException: Invalid reference* is raised by kie-server, if the xml have reference to facts using id's instead of XPath.
XML with XPath reference is very hard to read for users and to produce dinamically for app that post/get xml data via rest api.
was:
Currently kie-server only supports XPath references in XStream. Add a http parameter to make kie-server's XStream marshaller call:
{code}
xStream.setMode(XStream.ID_REFERENCES);
{code}
Motivation by community user:
It's very usefull for projects developed via kie-wb to set XStream mode (ID or ID_REFERENCES) similar to how there's a http parameter to switch between xstream xml, jaxb xml and jackson json.
Actually when submit to kie-server an xml body to post for solution (optaplanner feature) an error *com.thoughtworks.xstream.converters.ConversionException: Invalid reference* is raised by kie-server, if the xml have reference to facts using id's instead of XPath.
XML with XPath reference is very hard to read for users and to produce dinamically for app that post/get xml data via rest api.
> Set XStream mode via http header
> --------------------------------
>
> Key: DROOLS-3075
> URL: https://issues.jboss.org/browse/DROOLS-3075
> Project: Drools
> Issue Type: Feature Request
> Components: kie server
> Affects Versions: 7.11.0.Final
> Reporter: Giovanni Martano
> Assignee: Maciej Swiderski
> Priority: Minor
>
> Currently kie-server only supports XPath references in XStream. Add a http header to make kie-server's XStream marshaller call:
> {code}
> xStream.setMode(XStream.ID_REFERENCES);
> {code}
> Motivation by community user:
> It's very usefull for projects developed via kie-wb to set XStream mode (ID or ID_REFERENCES) similar to how there's a http parameter to switch between xstream xml, jaxb xml and jackson json.
> Actually when submit to kie-server an xml body to post for solution (optaplanner feature) an error *com.thoughtworks.xstream.converters.ConversionException: Invalid reference* is raised by kie-server, if the xml have reference to facts using id's instead of XPath.
> XML with XPath reference is very hard to read for users and to produce dinamically for app that post/get xml data via rest api.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3075) Set XStream mode via http header
by Geoffrey De Smet (Jira)
[ https://issues.jboss.org/browse/DROOLS-3075?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-3075:
-------------------------------------
Description:
Currently kie-server only supports XPath references in XStream. Add a http parameter to make kie-server's XStream marshaller call:
{code}
xStream.setMode(XStream.ID_REFERENCES);
{code}
Motivation by community user:
It's very usefull for projects developed via kie-wb to set XStream mode (ID or ID_REFERENCES) similar to how there's a http parameter to switch between xstream xml, jaxb xml and jackson json.
Actually when submit to kie-server an xml body to post for solution (optaplanner feature) an error *com.thoughtworks.xstream.converters.ConversionException: Invalid reference* is raised by kie-server, if the xml have reference to facts using id's instead of XPath.
XML with XPath reference is very hard to read for users and to produce dinamically for app that post/get xml data via rest api.
was:
Currently kie-server only supports XPath references in XStream. Add a http parameter to make kie-server's XStream marshaller call:
{code}
xStream.setMode(XStream.ID_REFERENCES);
{code}
Motivation:
It's very usefull for projects developed via kie-wb to set XStream mode (ID or ID_REFERENCES) similar to how there's a http parameter to switch between xstream xml, jaxb xml and jackson json.
Actually when submit to kie-server an xml body to post for solution (optaplanner feature) an error *com.thoughtworks.xstream.converters.ConversionException: Invalid reference* is raised by kie-server, if the xml have reference to facts using id's instead of XPath.
XML with XPath reference is very hard to read for users and to produce dinamically for app that post/get xml data via rest api.
> Set XStream mode via http header
> --------------------------------
>
> Key: DROOLS-3075
> URL: https://issues.jboss.org/browse/DROOLS-3075
> Project: Drools
> Issue Type: Feature Request
> Components: kie server
> Affects Versions: 7.11.0.Final
> Reporter: Giovanni Martano
> Assignee: Maciej Swiderski
> Priority: Minor
>
> Currently kie-server only supports XPath references in XStream. Add a http parameter to make kie-server's XStream marshaller call:
> {code}
> xStream.setMode(XStream.ID_REFERENCES);
> {code}
> Motivation by community user:
> It's very usefull for projects developed via kie-wb to set XStream mode (ID or ID_REFERENCES) similar to how there's a http parameter to switch between xstream xml, jaxb xml and jackson json.
> Actually when submit to kie-server an xml body to post for solution (optaplanner feature) an error *com.thoughtworks.xstream.converters.ConversionException: Invalid reference* is raised by kie-server, if the xml have reference to facts using id's instead of XPath.
> XML with XPath reference is very hard to read for users and to produce dinamically for app that post/get xml data via rest api.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3075) Set XStream mode via http header
by Geoffrey De Smet (Jira)
[ https://issues.jboss.org/browse/DROOLS-3075?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-3075:
-------------------------------------
Description:
Currently kie-server only supports XPath references in XStream. Add a http parameter to make kie-server's XStream marshaller call:
{code}
xStream.setMode(XStream.ID_REFERENCES);
{code}
It's very usefull for projects developed via kie-wb to set XStream mode (ID or ID_REFERENCES) similar to how there's a http parameter to switch between xstream xml, jaxb xml and jackson json.
Actually when submit to kie-server an xml body to post for solution (optaplanner feature) an error *com.thoughtworks.xstream.converters.ConversionException: Invalid reference* is raised by kie-server, if the xml have reference to facts using id's instead of XPath.
XML with XPath reference is very hard to read for users and to produce dinamically for app that post/get xml data via rest api.
was:
It's very usefull for projects developed via kie-wb to set XStream mode (ID or ID_REFERENCES) similar to how there's a http parameter to switch between xstream xml, jaxb xml and jackson json.
Actually when submit to kie-server an xml body to post for solution (optaplanner feature) an error *com.thoughtworks.xstream.converters.ConversionException: Invalid reference* is raised by kie-server, if the xml have reference to facts using id's instead of XPath.
XML with XPath reference is very hard to read for users and to produce dinamically for app that post/get xml data via rest api.
> Set XStream mode via http header
> --------------------------------
>
> Key: DROOLS-3075
> URL: https://issues.jboss.org/browse/DROOLS-3075
> Project: Drools
> Issue Type: Feature Request
> Components: kie server
> Affects Versions: 7.11.0.Final
> Reporter: Giovanni Martano
> Assignee: Maciej Swiderski
> Priority: Minor
>
> Currently kie-server only supports XPath references in XStream. Add a http parameter to make kie-server's XStream marshaller call:
> {code}
> xStream.setMode(XStream.ID_REFERENCES);
> {code}
> It's very usefull for projects developed via kie-wb to set XStream mode (ID or ID_REFERENCES) similar to how there's a http parameter to switch between xstream xml, jaxb xml and jackson json.
> Actually when submit to kie-server an xml body to post for solution (optaplanner feature) an error *com.thoughtworks.xstream.converters.ConversionException: Invalid reference* is raised by kie-server, if the xml have reference to facts using id's instead of XPath.
> XML with XPath reference is very hard to read for users and to produce dinamically for app that post/get xml data via rest api.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3075) Set XStream mode via http header
by Geoffrey De Smet (Jira)
[ https://issues.jboss.org/browse/DROOLS-3075?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-3075:
-------------------------------------
Description:
Currently kie-server only supports XPath references in XStream. Add a http parameter to make kie-server's XStream marshaller call:
{code}
xStream.setMode(XStream.ID_REFERENCES);
{code}
Motivation:
It's very usefull for projects developed via kie-wb to set XStream mode (ID or ID_REFERENCES) similar to how there's a http parameter to switch between xstream xml, jaxb xml and jackson json.
Actually when submit to kie-server an xml body to post for solution (optaplanner feature) an error *com.thoughtworks.xstream.converters.ConversionException: Invalid reference* is raised by kie-server, if the xml have reference to facts using id's instead of XPath.
XML with XPath reference is very hard to read for users and to produce dinamically for app that post/get xml data via rest api.
was:
Currently kie-server only supports XPath references in XStream. Add a http parameter to make kie-server's XStream marshaller call:
{code}
xStream.setMode(XStream.ID_REFERENCES);
{code}
It's very usefull for projects developed via kie-wb to set XStream mode (ID or ID_REFERENCES) similar to how there's a http parameter to switch between xstream xml, jaxb xml and jackson json.
Actually when submit to kie-server an xml body to post for solution (optaplanner feature) an error *com.thoughtworks.xstream.converters.ConversionException: Invalid reference* is raised by kie-server, if the xml have reference to facts using id's instead of XPath.
XML with XPath reference is very hard to read for users and to produce dinamically for app that post/get xml data via rest api.
> Set XStream mode via http header
> --------------------------------
>
> Key: DROOLS-3075
> URL: https://issues.jboss.org/browse/DROOLS-3075
> Project: Drools
> Issue Type: Feature Request
> Components: kie server
> Affects Versions: 7.11.0.Final
> Reporter: Giovanni Martano
> Assignee: Maciej Swiderski
> Priority: Minor
>
> Currently kie-server only supports XPath references in XStream. Add a http parameter to make kie-server's XStream marshaller call:
> {code}
> xStream.setMode(XStream.ID_REFERENCES);
> {code}
> Motivation:
> It's very usefull for projects developed via kie-wb to set XStream mode (ID or ID_REFERENCES) similar to how there's a http parameter to switch between xstream xml, jaxb xml and jackson json.
> Actually when submit to kie-server an xml body to post for solution (optaplanner feature) an error *com.thoughtworks.xstream.converters.ConversionException: Invalid reference* is raised by kie-server, if the xml have reference to facts using id's instead of XPath.
> XML with XPath reference is very hard to read for users and to produce dinamically for app that post/get xml data via rest api.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-2735) [DMN Editor] Function change breaks column layout
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2735?page=com.atlassian.jira.plugi... ]
Jozef Marko closed DROOLS-2735.
-------------------------------
Fix Version/s: 7.13.0.Final
Resolution: Cannot Reproduce
> [DMN Editor] Function change breaks column layout
> -------------------------------------------------
>
> Key: DROOLS-2735
> URL: https://issues.jboss.org/browse/DROOLS-2735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
> Fix For: 7.13.0.Final
>
> Attachments: Screenshot from 2018-07-13 10-21-15.png, Screenshot from 2018-07-13 10-21-28.png
>
>
> If user changes function definition in the context entry, while context grid contains multiple entries, then the layout of the context grid is broken.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-2735) [DMN Editor] Function change breaks column layout
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2735?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-2735:
-------------------------------------
[~manstis] Sweet as a nut, thanks for spotting, closing this.
> [DMN Editor] Function change breaks column layout
> -------------------------------------------------
>
> Key: DROOLS-2735
> URL: https://issues.jboss.org/browse/DROOLS-2735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
> Fix For: 7.13.0.Final
>
> Attachments: Screenshot from 2018-07-13 10-21-15.png, Screenshot from 2018-07-13 10-21-28.png
>
>
> If user changes function definition in the context entry, while context grid contains multiple entries, then the layout of the context grid is broken.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-8713) ISPN000136: Error executing command PutKeyValueCommand, writing keys
by Anton Skolznev (Jira)
[ https://issues.jboss.org/browse/WFLY-8713?page=com.atlassian.jira.plugin.... ]
Anton Skolznev commented on WFLY-8713:
--------------------------------------
I'm having the same problem on 12.0.0.Final. Probably should be resolved in infinispan itself.
> ISPN000136: Error executing command PutKeyValueCommand, writing keys
> --------------------------------------------------------------------
>
> Key: WFLY-8713
> URL: https://issues.jboss.org/browse/WFLY-8713
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.0.0.Final
> Environment: Linux
> Reporter: Divey Gupta
> Assignee: Jason Greene
> Priority: Major
>
> We have a cluster of 6 wildfly all running 10.0.0. There was a network blip for few minutes so the connectivity between the members of the cluster got affected.
> After that one of the members started throwing the following error on login.
> ERROR [InvocationContextInterceptor] (default task-51) ISPN000136: Error executing command PutKeyValueCommand, writing keys [SessionCreationMetaDataKey(k1XmyfLfE8KInACteyuTXQLCki9jq-HKL2-Ayo6G)]: org.infinispan.util.concurrent.TimeoutException: Timed out waiting for topology 27
> at org.infinispan.statetransfer.StateTransferLockImpl.reportErrorAfterWait(StateTransferLockImpl.java:159) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.statetransfer.StateTransferLockImpl.waitForTransactionData(StateTransferLockImpl.java:98) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.interceptors.base.BaseStateTransferInterceptor.waitForTransactionData(BaseStateTransferInterceptor.java:97) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.statetransfer.StateTransferInterceptor.handleNonTxWriteCommand(StateTransferInterceptor.java:366) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.statetransfer.StateTransferInterceptor.handleWriteCommand(StateTransferInterceptor.java:281) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.statetransfer.StateTransferInterceptor.visitPutKeyValueCommand(StateTransferInterceptor.java:107) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:78) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:114) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:83) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:43) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:78) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:99) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:113) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:43) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:78) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:335) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.cache.impl.CacheImpl.executeCommandAndCommitIfNeeded(CacheImpl.java:1672) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.cache.impl.CacheImpl.putIfAbsentInternal(CacheImpl.java:1163) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.cache.impl.CacheImpl.putIfAbsent(CacheImpl.java:1151) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.cache.impl.DecoratedCache.putIfAbsent(DecoratedCache.java:508) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at org.infinispan.cache.impl.AbstractDelegatingCache.putIfAbsent(AbstractDelegatingCache.java:246) [infinispan-core-8.2.4.Final.jar:8.2.4.Final]
> at java.util.concurrent.ConcurrentMap.computeIfAbsent(ConcurrentMap.java:325) [rt.jar:1.8.0_72]
> at org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.createValue(InfinispanSessionMetaDataFactory.java:53)
> at org.wildfly.clustering.web.infinispan.session.InfinispanSessionMetaDataFactory.createValue(InfinispanSessionMetaDataFactory.java:36)
> at org.wildfly.clustering.web.infinispan.session.InfinispanSessionFactory.createValue(InfinispanSessionFactory.java:52)
> at org.wildfly.clustering.web.infinispan.session.InfinispanSessionFactory.createValue(InfinispanSessionFactory.java:38)
> at org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager.createSession(InfinispanSessionManager.java:257)
> at org.wildfly.clustering.web.undertow.session.DistributableSessionManager.createSession(DistributableSessionManager.java:110)
> at io.undertow.servlet.spec.ServletContextImpl.getSession(ServletContextImpl.java:787) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.spec.ServletContextImpl.getSession(ServletContextImpl.java:802) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler$SecurityNotificationReceiver.handleNotification(CachedAuthenticatedSessionHandler.java:104) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.security.impl.AbstractSecurityContext.sendNoticiation(AbstractSecurityContext.java:131) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.security.impl.AbstractSecurityContext.authenticationComplete(AbstractSecurityContext.java:88) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.security.impl.AbstractSecurityContext.authenticationComplete(AbstractSecurityContext.java:80) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.security.impl.FormAuthenticationMechanism.runFormAuth(FormAuthenticationMechanism.java:126) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.security.impl.FormAuthenticationMechanism.authenticate(FormAuthenticationMechanism.java:96) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:245) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:263) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:231) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:125) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:99) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:92) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:53) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:59) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) [undertow-servlet-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:805) [undertow-core-1.4.0.Final.jar:1.4.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_72]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_72]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_72]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-2709) Revise and align visual presentation of tables (DMN, scenario, DT)
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-2709?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2709:
----------------------------------------
[~danielezonca] Seems reasonable enough; however it'll probably only work for the _styling_ requirements mentioned [here|https://issues.jboss.org/browse/DROOLS-2709?focusedCommentId=1364300...]. The _behavioural_ requirements will need changes in {{uberfire-wires-code-grids}} for sure (or somewhere else _common_ to all the uses of the grids).
> Revise and align visual presentation of tables (DMN, scenario, DT)
> -------------------------------------------------------------------
>
> Key: DROOLS-2709
> URL: https://issues.jboss.org/browse/DROOLS-2709
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor, Scenario Simulation and Testing, Test Scenarios Editor
> Reporter: Liz Clayton
> Assignee: Michael Anstis
> Priority: Major
> Labels: UX, UXTeam, VisualDesign, drools-tools
>
> As a practitioner I need a clear and consistent presentation of table styles, so that I can learn the visual cues once for all tables in the application suite.
> When possible, iteratively update visual styles for tables using the following proposed options: https://redhat.invisionapp.com/share/RXLG7XB2TCW
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months