[JBoss JIRA] (WFLY-13512) Duplicated classes in META-INF folder
by Richard Opalka (Jira)
[ https://issues.redhat.com/browse/WFLY-13512?page=com.atlassian.jira.plugi... ]
Richard Opalka commented on WFLY-13512:
---------------------------------------
Hi [~antferna] this is new feature introduced in JDK9.
When Java Platform Module System was introduced,
together with it was introduced also so called
"multirelease jar file" that is a jar file that may contain
classes with different behaviour on different JDK versions.
Classes in META-INF/version subfolder are targeting
particular JDKs. It is not an error or packaging issue.
I suggest you to upgrade the enforcer maven plugin -
newer versions should be familiar with this JDK feature.
> Duplicated classes in META-INF folder
> -------------------------------------
>
> Key: WFLY-13512
> URL: https://issues.redhat.com/browse/WFLY-13512
> Project: WildFly
> Issue Type: Quality Risk
> Reporter: Antonio Fernandez Alhambra
> Priority: Major
> Labels: reported-by-qe
> Attachments: Screenshot from 2020-05-14 17-20-16.png
>
>
> There are duplicated classes inside the org.wildfly.common:wildfly-common file.
> So whenever the enforcer maven plugin is used for building, if there is a dependency in the pom.xml, enforcer plugin will fail complaining about this jar due to these duplicated jar files.
> {noformat}
> Duplicate classes found:
> Found in:
> org.kie.server:kie-server-router-proxy:jar:7.38.0-SNAPSHOT:compile
> org.wildfly.common:wildfly-common:jar:1.5.1.Final:compile
> Duplicate classes:
> META-INF/versions/9/org/wildfly/common/lock/JDKSpecific.class
> META-INF/versions/9/org/wildfly/common/os/ProcessRedirect.class
> META-INF/versions/9/org/wildfly/common/lock/Substitutions$Target_PauseNode.class
> META-INF/versions/9/org/wildfly/common/os/GetProcessInfoAction.class
> META-INF/versions/9/org/wildfly/common/lock/JDKSpecific$1.class
> META-INF/versions/9/org/wildfly/common/lock/Substitutions.class
> META-INF/versions/9/org/wildfly/common/lock/Substitutions$Target_JDKSpecific.class
> META-INF/versions/11/org/wildfly/common/archive/JDKSpecific.class
> META-INF/versions/9/org/wildfly/common/cpu/ProcessorInfo.class
> {noformat}
> Seems these duplicated classes are bundled in the jar since version 1.4.x onwards.
> These duplicated classes are located in the META-INF/versions folders inside the jar.
> Attached a screenshot of the same.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (WFLY-13514) Huge memory leak in WildFly
by Konrad Bak (Jira)
Konrad Bak created WFLY-13514:
---------------------------------
Summary: Huge memory leak in WildFly
Key: WFLY-13514
URL: https://issues.redhat.com/browse/WFLY-13514
Project: WildFly
Issue Type: Bug
Components: CDI / Weld, JSF
Affects Versions: 20.0.0.Beta1, 19.1.0.Final, 18.0.1.Final
Reporter: Konrad Bak
Assignee: Matěj Novotný
https://github.com/konbk/bug-report-wildfly-oome
The project shows a huge memory leak introduced in recent WildFly versions that can crash a real-world Java EE application in a matter of hours.
When a JSF page contains any component bound to page variable, all CDI beans (regardless of scope) used on that page stay in memory.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (DROOLS-1003) incongruous security granularity in kie-server
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-1003?page=com.atlassian.jira.plug... ]
Mario Fusco reassigned DROOLS-1003:
-----------------------------------
Assignee: Toshiya Kobayashi (was: Maciej Swiderski)
> incongruous security granularity in kie-server
> ----------------------------------------------
>
> Key: DROOLS-1003
> URL: https://issues.redhat.com/browse/DROOLS-1003
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 6.3.0.Final
> Reporter: David Ward
> Assignee: Toshiya Kobayashi
> Priority: Major
> Attachments: web.xml
>
>
> The KIE Server provides two endpoints: HTTP/REST and JMS. By default, there is a "kie-server" role that one must have to perform operations through either endpoint. But by having this role, you can do *anything* in a very coarse-grained fashion.
> Luckily, the HTTP/REST endpoint can be modified by changing the kie-server.war/WEB-INF/web.xml, and adding/modifying the security constraints. For OpenShift purposes, this has been done to disallow creating and disposing containers, while still allowing for reading status and executing rules. This is because REST url-patterns can be filtered per various operations and also with different http-methods. (See attached web.xml for an example.)
> However, the JMS endpoint has no such capability. There is only one request queue with appserver security on it on a coarse-grained level, and no way to filter the messages as can be done via the HTTP/REST endpoint.
> I have an idea that might help? Clients invoke the server via serializing and sending in Command objects, and those objects themselves are fine-grained (they are named things like "CallContainerCommand" and "DisposeContainerCommand"). If the incoming messages could propagate some kind of property of who the caller was, then the server-side could do a isCallerInRole/isUserInRole to determine if that user is authorized to invoke that particular command before doing so. Just a brainstorming idea.
> Here is an example of the server handling the commands:
> https://github.com/droolsjbpm/droolsjbpm-integration/blob/6.2.x/kie-serve...
> The desired goal would be that developers (like myself) would not have to edit the kie-server.war/WEB-INF/web.xml, and that the same level of security granularity would already be available out-of-the-box for both the HTTP/REST and JMS interfaces. All that would be left for us would be to grant users the appropriate roles.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (DROOLS-1004) classloading errors in kie-server
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-1004?page=com.atlassian.jira.plug... ]
Mario Fusco reassigned DROOLS-1004:
-----------------------------------
Assignee: Toshiya Kobayashi (was: Maciej Swiderski)
> classloading errors in kie-server
> ---------------------------------
>
> Key: DROOLS-1004
> URL: https://issues.redhat.com/browse/DROOLS-1004
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 6.3.0.Final
> Reporter: David Ward
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> There appear to be some classloading errors in kie-server.war 6.3.0.Final-redhat-5 being deployed on JBoss EAP 6.4.4.
> *First, you get multiple jaxb and parser warnings like this:*
> {code}
> 11:58:47,603 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxb-api.jar in /opt/eap/standalone/deployments/kie-server.war/WEB-INF/lib/jaxb-core-2.2.11.jar does not point to a valid jar for a Class-Path reference.
> 11:58:47,606 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxb-core.jar in /opt/eap/standalone/deployments/kie-server.war/WEB-INF/lib/jaxb-impl-2.2.11.jar does not point to a valid jar for a Class-Path reference.
> 11:58:47,644 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxb-core.jar in /opt/eap/standalone/deployments/kie-server.war/WEB-INF/lib/jaxb-xjc-2.2.11.jar does not point to a valid jar for a Class-Path reference.
> 11:58:47,644 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxb-impl.jar in /opt/eap/standalone/deployments/kie-server.war/WEB-INF/lib/jaxb-xjc-2.2.11.jar does not point to a valid jar for a Class-Path reference.
> 11:58:47,713 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
> {code}
> The above was noticed as part of CLOUD-421. Please refer to the jira issue and note Kev's comment, {quote}"The jaxb jars are duplicates that are unnecessary in the EAP deployments however the upstream war file contains all dependencies. Removing the jaxb jars from within the kie-server.war/WEB-INF/lib directory will likely work however I'm loathed to do this since we would need to verify this through the BRMS QE team.
> The warning about the parser is caused by the kie-server.war/WEB-INF/lib/xpp3_min-1.1.4c.jar"{quote}
> *Second, there can be missing osgi classes:*
> If kjar model classes contain certain annotations, it seems to trigger the kie-server to try to load osgi classes. For example, annotating kjar model classes with Position, PropertyReactive, and Remotable as per this test case:
> http://git.app.eng.bos.redhat.com/git/xpaas-qe.git/tree/test-brms/src/tes...
> , you end up with errors like this in the log when the KieContainer is being installed:
> {code}
> Caused by: java.lang.NoClassDefFoundError: org/osgi/util/tracker/ServiceTrackerCustomizer
> at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.8.0_65]
> at java.lang.ClassLoader.defineClass(ClassLoader.java:760) [rt.jar:1.8.0_65]
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:361) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:482) [jboss-modules.jar:1.3.7.Final-redhat-1]
> ... 77 more
> Caused by: java.lang.ClassNotFoundException: org.osgi.util.tracker.ServiceTrackerCustomizer from [Module "deployment.kie-server.war:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.7.Final-redhat-1]
> ... 81 more
> {code}
> The above was noticed as part of CLOUD-418. To get around this issue, I had to add a kie-server.war/WEB-INF/jboss-deployment-structure.xml like so:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure>
> <deployment>
> <dependencies>
> <module name="org.osgi.core"/>
> <module name="org.osgi.enterprise"/>
> </dependencies>
> </deployment>
> </jboss-deployment-structure>
> {code}
> The jboss-bpmsuite-6.2.0.GA-redhat-1-deployable-eap6.x.zip file (from which we extract the kie-sever.war) is seemingly an EAP-specific build (thus the -eap6.x suffix). So perhaps the fix would be to have the kie-server.war already come pre-configured to contain (or better yet, depend upon the existing modules) jars in EAP for both the above problems (incorrect jaxb/xmlpull references, and missing osgi dependencies).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (DROOLS-1661) KIE-Server-Client needs to be more light-weight
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-1661?page=com.atlassian.jira.plug... ]
Mario Fusco reassigned DROOLS-1661:
-----------------------------------
Assignee: Mario Fusco (was: Maciej Swiderski)
> KIE-Server-Client needs to be more light-weight
> -----------------------------------------------
>
> Key: DROOLS-1661
> URL: https://issues.redhat.com/browse/DROOLS-1661
> Project: Drools
> Issue Type: Enhancement
> Components: kie server
> Affects Versions: 7.1.0.Beta3
> Reporter: Duncan Doyle
> Assignee: Mario Fusco
> Priority: Major
>
> KIE-Server-Client currently drags in a ton of dependencies. A {{mnv dependency:tree}} gives this output:
> {code}
> +- org.kie.server:kie-server-client:jar:7.1.0-SNAPSHOT:compile
> [INFO] | +- org.apache.commons:commons-lang3:jar:3.4:compile
> [INFO] | +- org.kie:kie-api:jar:7.1.0-SNAPSHOT:compile
> [INFO] | | \- org.uberfire:uberfire-maven-support:jar:1.1.0-SNAPSHOT:compile
> [INFO] | +- org.kie:kie-internal:jar:7.1.0-SNAPSHOT:compile
> [INFO] | +- org.optaplanner:optaplanner-core:jar:7.1.0-SNAPSHOT:compile
> [INFO] | | +- org.drools:drools-compiler:jar:7.1.0-SNAPSHOT:compile
> [INFO] | | | +- org.antlr:antlr-runtime:jar:3.5:compile
> [INFO] | | | +- org.eclipse.jdt.core.compiler:ecj:jar:4.4.2:compile
> [INFO] | | | \- com.google.protobuf:protobuf-java:jar:2.6.0:compile
> [INFO] | | +- org.apache.commons:commons-math3:jar:3.4.1:compile
> [INFO] | | +- com.google.guava:guava:jar:20.0:compile
> [INFO] | | +- org.reflections:reflections:jar:0.9.10:compile
> [INFO] | | | \- com.google.code.findbugs:annotations:jar:2.0.1:compile
> [INFO] | | \- com.thoughtworks.xstream:xstream:jar:1.4.9:compile
> [INFO] | | +- xmlpull:xmlpull:jar:1.1.3.1:compile
> [INFO] | | \- xpp3:xpp3_min:jar:1.1.4c:compile
> [INFO] | +- org.drools:drools-core:jar:7.1.0-SNAPSHOT:compile
> [INFO] | | +- org.mvel:mvel2:jar:2.3.0.Final:compile
> [INFO] | | \- commons-codec:commons-codec:jar:1.10:compile
> [INFO] | +- org.kie:kie-dmn-api:jar:7.1.0-SNAPSHOT:compile
> [INFO] | | \- org.kie:kie-dmn-model:jar:7.1.0-SNAPSHOT:compile
> [INFO] | +- org.kie.server:kie-server-api:jar:7.1.0-SNAPSHOT:compile
> [INFO] | | +- org.optaplanner:optaplanner-persistence-xstream:jar:7.1.0-SNAPSHOT:compile
> [INFO] | | | \- org.optaplanner:optaplanner-persistence-common:jar:7.1.0-SNAPSHOT:compile
> [INFO] | | +- org.optaplanner:optaplanner-persistence-jaxb:jar:7.1.0-SNAPSHOT:compile
> [INFO] | | | +- org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec:jar:1.0.4.Final:compile
> [INFO] | | | \- javax.activation:activation:jar:1.1.1:compile
> [INFO] | | +- com.fasterxml.jackson.core:jackson-annotations:jar:2.6.2:compile
> [INFO] | | +- com.fasterxml.jackson.core:jackson-core:jar:2.6.2:compile
> [INFO] | | +- com.fasterxml.jackson.core:jackson-databind:jar:2.6.2:compile
> [INFO] | | \- com.fasterxml.jackson.module:jackson-module-jaxb-annotations:jar:2.6.2:compile
> [INFO] | +- org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_2.0_spec:jar:1.0.0.Final:compile
> [INFO] | +- org.kie.server:kie-server-common:jar:7.1.0-SNAPSHOT:compile
> [INFO] | +- org.codehaus.jackson:jackson-xc:jar:1.9.13:compile
> [INFO] | | \- org.codehaus.jackson:jackson-core-asl:jar:1.9.13:compile
> [INFO] | +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.13:compile
> [INFO] | +- org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:jar:1.0.0.Final:compile
> [INFO] | +- com.sun.xml.bind:jaxb-core:jar:2.2.11:compile
> [INFO] | +- com.sun.xml.bind:jaxb-impl:jar:2.2.11:compile
> [INFO] | \- org.slf4j:jcl-over-slf4j:jar:1.7.7:runtime
> {code}
> So, if we're just creating a simple DMN KIE-Server Client, we are dragging in all sorts of {{drools-core}}, {{optaplanner-persistence-xstream}}, etc. into our project. Obviously we can start excluding theses dependencies, but that's not really that user friendly IMO.
> It would be nice if we could make this a bit more modular.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (DROOLS-2289) The response time jump add in stability test
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-2289?page=com.atlassian.jira.plug... ]
Mario Fusco reassigned DROOLS-2289:
-----------------------------------
Assignee: Toshiya Kobayashi (was: Maciej Swiderski)
> The response time jump add in stability test
> ---------------------------------------------
>
> Key: DROOLS-2289
> URL: https://issues.redhat.com/browse/DROOLS-2289
> Project: Drools
> Issue Type: Quality Risk
> Components: kie server
> Affects Versions: 7.5.0.Final
> Environment: tomcat version:8.5.24 jmeter version：jakarta-jmeter-2.5.1 Drools version：7.5.0.Final
> cpu：2x6 x86_64， memory：32G， sysOS：CentOS release 6.3
> Reporter: LIANG LIU
> Assignee: Toshiya Kobayashi
> Priority: Major
> Attachments: InputFact.java, image-2018-02-02-14-51-31-166.png, screenshot-1.png, tomcat8_test.jmx
>
>
> !image-2018-02-02-14-51-31-166.png|thumbnail!
> Stability test the response time jump add! Figure ; En,there are 20 rules,like:
> rule "1"
> salience 9999
> when
> $inputFact:InputFact(stateless_data["black_test"]== 1)
> then
> result.put(drools.getRule().getName(),1);
> end
> It's a problem I use or some parameters need to be set？
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (DROOLS-3075) Set XStream mode via http header
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-3075?page=com.atlassian.jira.plug... ]
Mario Fusco reassigned DROOLS-3075:
-----------------------------------
Assignee: Toshiya Kobayashi (was: Mario Fusco)
> Set XStream mode via http header
> --------------------------------
>
> Key: DROOLS-3075
> URL: https://issues.redhat.com/browse/DROOLS-3075
> Project: Drools
> Issue Type: Feature Request
> Components: kie server
> Affects Versions: 7.11.0.Final
> Reporter: Giovanni Martano
> Assignee: Toshiya Kobayashi
> 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.13.8#713008)
5 years, 11 months
[JBoss JIRA] (DROOLS-4510) Kie Client returns 500 when using kie spring boot drools
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-4510?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-4510:
--------------------------------
Sprint: 2020 Week 22-24 (from May 25)
> Kie Client returns 500 when using kie spring boot drools
> ---------------------------------------------------------
>
> Key: DROOLS-4510
> URL: https://issues.redhat.com/browse/DROOLS-4510
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 7.8.0.Final
> Reporter: Minal Bhalodi
> Assignee: Mario Fusco
> Priority: Major
>
> kie server returns 500 to kie client when using kie-server-spring-boot-starter-drools
> 2019-09-08 21:51:45.643 INFO 11763 --- [0.1-8081-exec-1] o.k.s.api.marshalling.MarshallerFactory : Marshaller extensions init
> 2019-09-08 21:53:01.971 ERROR 11763 --- [0.1-8081-exec-1] o.a.c.c.C.[.[.[/].[servletContainer] : Servlet.service() for servlet [servletContainer] in context with path [] threw exception [org.glassfish.jersey.server.ContainerException: java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.SerializationConfig.with(Lcom/fasterxml/jackson/databind/AnnotationIntrospector;)Lcom/fasterxml/jackson/databind/SerializationConfig;] with root cause
> java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.SerializationConfig.with(Lcom/fasterxml/jackson/databind/AnnotationIntrospector;)Lcom/fasterxml/jackson/databind/SerializationConfig;
> at org.kie.server.api.marshalling.json.JSONMarshaller.configureMarshaller(JSONMarshaller.java:155) ~[kie-server-api-7.9.0.Final.jar:7.9.0.Final]
> at org.kie.server.api.marshalling.json.JSONMarshaller.<init>(JSONMarshaller.java:128) ~[kie-server-api-7.9.0.Final.jar:7.9.0.Final]
> at org.kie.server.api.marshalling.BaseMarshallerBuilder.build(BaseMarshallerBuilder.java:43) ~[kie-server-api-7.9.0.Final.jar:7.9.0.Final]
> at org.kie.server.api.marshalling.MarshallerFactory.getMarshaller(MarshallerFactory.java:52) ~[kie-server-api-7.9.0.Final.jar:7.9.0.Final]
> at org.kie.server.services.impl.marshal.MarshallerHelper.marshal(MarshallerHelper.java:79) ~[kie-server-services-common-7.9.0.Final.jar:7.9.0.Final]
> at org.kie.server.remote.rest.common.util.RestUtils.createCorrectVariant(RestUtils.java:55) ~[kie-server-rest-common-7.9.0.Final.jar:7.9.0.Final]
> at org.kie.server.remote.rest.common.util.RestUtils.createCorrectVariant(RestUtils.java:44) ~[kie-server-rest-common-7.9.0.Final.jar:7.9.0.Final]
> at org.kie.server.remote.rest.common.resource.KieServerRestImpl.getInfo(KieServerRestImpl.java:94) ~[kie-server-rest-common-7.9.0.Final.jar:7.9.0.Final]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_152]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_152]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_152]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_152]
> at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory.lambda$static$0(ResourceMethodInvocationHandlerFactory.java:76) ~[jersey-server-2.26.jar:na]
> at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:148) ~[jersey-server-2.26.jar:na]
> at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:191) ~[jersey-server-2.26.jar:na]
> at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:200) ~[jersey-server-2.26.jar:na]
> at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:103) ~[jersey-server-2.26.jar:na]
> at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:493) ~[jersey-server-2.26.jar:na]
> at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:415) ~[jersey-server-2.26.jar:na]
> at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:104) ~[jersey-server-2.26.jar:na]
> at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:277) ~[jersey-server-2.26.jar:na]
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:272) ~[jersey-common-2.26.jar:na]
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:268) ~[jersey-common-2.26.jar:na]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:316) ~[jersey-common-2.26.jar:na]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:298) ~[jersey-common-2.26.jar:na]
> at org.glassfish.jersey.internal.Errors.process(Errors.java:268) ~[jersey-common-2.26.jar:na]
> at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:289) ~[jersey-common-2.26.jar:na]
> at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:256) ~[jersey-server-2.26.jar:na]
> at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:703) ~[jersey-server-2.26.jar:na]
> at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:416) ~[jersey-container-servlet-core-2.26.jar:na]
> at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:370) ~[jersey-container-servlet-core-2.26.jar:na]
> at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:389) ~[jersey-container-servlet-core-2.26.jar:na]
> at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:342) ~[jersey-container-servlet-core-2.26.jar:na]
> at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:229) ~[jersey-container-servlet-core-2.26.jar:na]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) ~[tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) ~[tomcat-embed-websocket-8.5.39.jar:8.5.39]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:320) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:127) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:91) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:119) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:137) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:111) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:170) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:63) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:215) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) ~[spring-web-5.0.13.RELEASE.jar:5.0.13.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:116) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.header.HeaderWriterFilter.doFilterInternal(HeaderWriterFilter.java:74) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) ~[spring-web-5.0.13.RELEASE.jar:5.0.13.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:105) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter.doFilterInternal(WebAsyncManagerIntegrationFilter.java:56) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) ~[spring-web-5.0.13.RELEASE.jar:5.0.13.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:215) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:178) ~[spring-security-web-5.0.12.RELEASE.jar:5.0.12.RELEASE]
> at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:357) ~[spring-web-5.0.13.RELEASE.jar:5.0.13.RELEASE]
> at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:270) ~[spring-web-5.0.13.RELEASE.jar:5.0.13.RELEASE]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99) ~[spring-web-5.0.13.RELEASE.jar:5.0.13.RELEASE]
> at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) ~[spring-web-5.0.13.RELEASE.jar:5.0.13.RELEASE]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:109) ~[spring-web-5.0.13.RELEASE.jar:5.0.13.RELEASE]
> at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) ~[spring-web-5.0.13.RELEASE.jar:5.0.13.RELEASE]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.springframework.web.filter.HiddenHttpMethodFilter.doFilterInternal(HiddenHttpMethodFilter.java:93) ~[spring-web-5.0.13.RELEASE.jar:5.0.13.RELEASE]
> at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) ~[spring-web-5.0.13.RELEASE.jar:5.0.13.RELEASE]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:200) ~[spring-web-5.0.13.RELEASE.jar:5.0.13.RELEASE]
> at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) ~[spring-web-5.0.13.RELEASE.jar:5.0.13.RELEASE]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199) ~[tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:493) [tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) [tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81) [tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) [tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:798) [tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) [tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:806) [tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498) [tomcat-embed-core-8.5.39.jar:8.5.39]
> at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-8.5.39.jar:8.5.39]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_152]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_152]
> at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-8.5.39.jar:8.5.39]
> at java.lang.Thread.run(Thread.java:748) [na:1.8.0_152]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (DROOLS-3075) Set XStream mode via http header
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-3075?page=com.atlassian.jira.plug... ]
Mario Fusco reassigned DROOLS-3075:
-----------------------------------
Assignee: Mario Fusco (was: Maciej Swiderski)
> Set XStream mode via http header
> --------------------------------
>
> Key: DROOLS-3075
> URL: https://issues.redhat.com/browse/DROOLS-3075
> Project: Drools
> Issue Type: Feature Request
> Components: kie server
> Affects Versions: 7.11.0.Final
> Reporter: Giovanni Martano
> Assignee: Mario Fusco
> 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.13.8#713008)
5 years, 11 months