[JBoss JIRA] (WFCORE-3269) [GSS](7.2.0) module defined in jboss-deployment-structure.xml with fails to parse when annotations=true
by Brad Maxwell (JIRA)
Brad Maxwell created WFCORE-3269:
------------------------------------
Summary: [GSS](7.2.0) module defined in jboss-deployment-structure.xml with fails to parse when annotations=true
Key: WFCORE-3269
URL: https://issues.jboss.org/browse/WFCORE-3269
Project: WildFly Core
Issue Type: Bug
Components: Server
Affects Versions: 3.0.2.CR1
Reporter: Brad Maxwell
Assignee: Brad Maxwell
{code}
21:15:06,004 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "application-exception-using-dynamic-module.ear")]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"jboss.deployment.subunit.\"application-exception-using-dynamic-module.ear\".\"application-exception-client-singleton.jar\".PARSE is missing [jboss.module.service.\"deployment.application-exception-api\".main]",
"jboss.deployment.subunit.\"application-exception-using-dynamic-module.ear\".\"application-exception-ejb.jar\".PARSE is missing [jboss.module.service.\"deployment.application-exception-api\".main]"
]}
21:15:06,027 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "application-exception-using-dynamic-module.ear" (runtime-name : "application-exception-using-dynamic-module.ear")
21:15:06,028 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.module.service."deployment.application-exception-api".main (missing) dependents: [service jboss.deployment.subunit."application-exception-using-dynamic-module.ear"."application-exception-ejb.jar".PARSE, service jboss.deployment.subunit."application-exception-using-dynamic-module.ear"."application-exception-client-singleton.jar".PARSE]
{code}
{code}
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
<module name="deployment.application-exception-api">
<resources>
<resource-root path="application-exception-api.jar"/>
</resources>
<dependencies>
<module name="javaee.api" export="true"/>
<module name="javax.api" export="true"/>
</dependencies>
</module>
<sub-deployment name="application-exception-ejb.jar">
<dependencies>
<module name="deployment.application-exception-api" annotations="true" meta-inf="export"/>
</dependencies>
</sub-deployment>
</jboss-deployment-structure>
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3270) [GSS](7.1.z) module defined in jboss-deployment-structure.xml with fails to parse when annotations=true
by Brad Maxwell (JIRA)
Brad Maxwell created WFCORE-3270:
------------------------------------
Summary: [GSS](7.1.z) module defined in jboss-deployment-structure.xml with fails to parse when annotations=true
Key: WFCORE-3270
URL: https://issues.jboss.org/browse/WFCORE-3270
Project: WildFly Core
Issue Type: Bug
Components: Server
Affects Versions: 3.0.2.CR1
Reporter: Brad Maxwell
Assignee: Brad Maxwell
{code}
21:15:06,004 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "application-exception-using-dynamic-module.ear")]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"jboss.deployment.subunit.\"application-exception-using-dynamic-module.ear\".\"application-exception-client-singleton.jar\".PARSE is missing [jboss.module.service.\"deployment.application-exception-api\".main]",
"jboss.deployment.subunit.\"application-exception-using-dynamic-module.ear\".\"application-exception-ejb.jar\".PARSE is missing [jboss.module.service.\"deployment.application-exception-api\".main]"
]}
21:15:06,027 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "application-exception-using-dynamic-module.ear" (runtime-name : "application-exception-using-dynamic-module.ear")
21:15:06,028 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.module.service."deployment.application-exception-api".main (missing) dependents: [service jboss.deployment.subunit."application-exception-using-dynamic-module.ear"."application-exception-ejb.jar".PARSE, service jboss.deployment.subunit."application-exception-using-dynamic-module.ear"."application-exception-client-singleton.jar".PARSE]
{code}
{code}
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
<module name="deployment.application-exception-api">
<resources>
<resource-root path="application-exception-api.jar"/>
</resources>
<dependencies>
<module name="javaee.api" export="true"/>
<module name="javax.api" export="true"/>
</dependencies>
</module>
<sub-deployment name="application-exception-ejb.jar">
<dependencies>
<module name="deployment.application-exception-api" annotations="true" meta-inf="export"/>
</dependencies>
</sub-deployment>
</jboss-deployment-structure>
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3268) module defined in jboss-deployment-structure.xml with fails to parse when annotations=true
by Brad Maxwell (JIRA)
Brad Maxwell created WFCORE-3268:
------------------------------------
Summary: module defined in jboss-deployment-structure.xml with fails to parse when annotations=true
Key: WFCORE-3268
URL: https://issues.jboss.org/browse/WFCORE-3268
Project: WildFly Core
Issue Type: Bug
Components: Server
Affects Versions: 3.0.2.CR1
Reporter: Brad Maxwell
Assignee: Brad Maxwell
{code}
21:15:06,004 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "application-exception-using-dynamic-module.ear")]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"jboss.deployment.subunit.\"application-exception-using-dynamic-module.ear\".\"application-exception-client-singleton.jar\".PARSE is missing [jboss.module.service.\"deployment.application-exception-api\".main]",
"jboss.deployment.subunit.\"application-exception-using-dynamic-module.ear\".\"application-exception-ejb.jar\".PARSE is missing [jboss.module.service.\"deployment.application-exception-api\".main]"
]}
21:15:06,027 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "application-exception-using-dynamic-module.ear" (runtime-name : "application-exception-using-dynamic-module.ear")
21:15:06,028 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.module.service."deployment.application-exception-api".main (missing) dependents: [service jboss.deployment.subunit."application-exception-using-dynamic-module.ear"."application-exception-ejb.jar".PARSE, service jboss.deployment.subunit."application-exception-using-dynamic-module.ear"."application-exception-client-singleton.jar".PARSE]
{code}
{code}
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
<module name="deployment.application-exception-api">
<resources>
<resource-root path="application-exception-api.jar"/>
</resources>
<dependencies>
<module name="javaee.api" export="true"/>
<module name="javax.api" export="true"/>
</dependencies>
</module>
<sub-deployment name="application-exception-ejb.jar">
<dependencies>
<module name="deployment.application-exception-api" annotations="true" meta-inf="export"/>
</dependencies>
</sub-deployment>
</jboss-deployment-structure>
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9326) Elytron SSO causes distributed session lock timeouts if request contains obsolete SSO cookie
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-9326?page=com.atlassian.jira.plugin.... ]
Paul Ferraro moved JBEAP-13093 to WFLY-9326:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9326 (was: JBEAP-13093)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Clustering
(was: Clustering)
Affects Version/s: 11.0.0.CR1
(was: 7.1.0.CR1)
> Elytron SSO causes distributed session lock timeouts if request contains obsolete SSO cookie
> --------------------------------------------------------------------------------------------
>
> Key: WFLY-9326
> URL: https://issues.jboss.org/browse/WFLY-9326
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.CR1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Blocker
>
> This is easily reproducible if request contains cookie from previously active SSO session. Causes user session to be unusable.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JGRP-2034) SASLTest-functional and SASL_SimpleAuthorizingCallbackTest-functional fails on IBM jdk 1.8
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2034?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2034:
---------------------------
Fix Version/s: 4.0.7
> SASLTest-functional and SASL_SimpleAuthorizingCallbackTest-functional fails on IBM jdk 1.8
> ------------------------------------------------------------------------------------------
>
> Key: JGRP-2034
> URL: https://issues.jboss.org/browse/JGRP-2034
> Project: JGroups
> Issue Type: Bug
> Reporter: Ivan Straka
> Assignee: Tristan Tarrant
> Fix For: 3.6.14, 4.0.7
>
>
> We see these two tests failing on IBM jdk 1.8
> org.jgroups.protocols.SASLTest-functional
> org.jgroups.protocols.SASL_SimpleAuthorizingCallbackTest-functional
> This issue may be related to https://issues.jboss.org/browse/JGRP-1993 somehow.
> There is standard output of tests.
> {code}
> ------------- testSASLDigestMD5 -----------
> -------------------------------------------------------------------
> GMS: address=A, cluster=SaslTest
> -------------------------------------------------------------------
> 521823 [TRACE] GMS: A: no members discovered after 3000 ms: creating cluster as first member
> 521823 [DEBUG] GMS: A: installing view [A|0] (1) [A]
> 521823 [DEBUG] GMS: A: created cluster (first member). My view is [A|0], impl is org.jgroups.protocols.pbcast.CoordGmsImpl
> -------------------------------------------------------------------
> GMS: address=B, cluster=SaslTest
> -------------------------------------------------------------------
> 521825 [TRACE] GMS: B: discovery took 0 ms, members: 1 rsps (1 coords) [done]
> 521826 [DEBUG] GMS: B: sending JOIN(B) to A
> 521826 [TRACE] SASL: B: received CHALLENGE from A
> 521827 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 524826 [WARN] GMS: B: JOIN(B) sent to A timed out (after 3000 ms), on try 1
> 524827 [TRACE] GMS: B: discovery took 1 ms, members: 1 rsps (1 coords) [done]
> 524827 [DEBUG] GMS: B: sending JOIN(B) to A
> 524828 [TRACE] SASL: B: received CHALLENGE from A
> 524828 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 526826 [WARN] SASL: failed to validate SaslHeader from B, header: payload=[B@ad737f58
> ------------- testSASLDigestMD5Failure -----------
> -------------------------------------------------------------------
> GMS: address=A, cluster=SaslTest
> -------------------------------------------------------------------
> 529863 [TRACE] GMS: A: no members discovered after 3000 ms: creating cluster as first member
> 529864 [DEBUG] GMS: A: installing view [A|0] (1) [A]
> 529864 [DEBUG] GMS: A: created cluster (first member). My view is [A|0], impl is org.jgroups.protocols.pbcast.CoordGmsImpl
> -------------------------------------------------------------------
> GMS: address=B, cluster=SaslTest
> -------------------------------------------------------------------
> 529866 [TRACE] GMS: B: discovery took 1 ms, members: 1 rsps (1 coords) [done]
> 529866 [DEBUG] GMS: B: sending JOIN(B) to A
> 529867 [TRACE] SASL: B: received CHALLENGE from A
> 529867 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 532867 [WARN] GMS: B: JOIN(B) sent to A timed out (after 3000 ms), on try 1
> 532867 [TRACE] GMS: B: discovery took 0 ms, members: 1 rsps (1 coords) [done]
> 532867 [DEBUG] GMS: B: sending JOIN(B) to A
> 532868 [TRACE] SASL: B: received CHALLENGE from A
> 532869 [WARN] SASL: B: failed to validate CHALLENGE from A, token
> javax.security.sasl.SaslException: DIGEST-MD5: Error acquiring realm, authentication ID or password
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:380) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at com.ibm.security.sasl.digest.DigestMD5Client.evaluateChallenge(DigestMD5Client.java:236) ~[ibmsaslprovider.jar:8.0 build_20150506]
> at org.jgroups.auth.sasl.SaslClientContext.evaluateChallenge(SaslClientContext.java:119) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.addHeader(SaslClientContext.java:92) ~[classes/:?]
> at org.jgroups.auth.sasl.SaslClientContext.nextMessage(SaslClientContext.java:72) ~[classes/:?]
> at org.jgroups.protocols.SASL.up(SASL.java:239) [classes/:?]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) [classes/:?]
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) [classes/:?]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) [classes/:?]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [classes/:?]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:645) [classes/:?]
> at org.jgroups.protocols.Discovery.up(Discovery.java:296) [classes/:?]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1567) [classes/:?]
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1783) [classes/:?]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [?:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal]
> Caused by: java.io.IOException: Invalid realm A
> at org.jgroups.auth.sasl.SimpleAuthorizingCallbackHandler.handle(SimpleAuthorizingCallbackHandler.java:119) ~[classes/:?]
> at com.ibm.security.sasl.digest.DigestMD5Client.processChallenge(DigestMD5Client.java:353) ~[ibmsaslprovider.jar:8.0 build_20150506]
> ... 16 more
> 534867 [WARN] SASL: failed to validate SaslHeader from B, header: payload=[B@6f6c2511
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (DROOLS-1516) GAV names are not coming properly when running the tomcat as Service
by CasterJose CasterJose (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1516?page=com.atlassian.jira.plugi... ]
CasterJose CasterJose commented on DROOLS-1516:
-----------------------------------------------
The Jars are created in the the given location for "{color:red}C:\drools\repositories\kie{color}" fro my Global M2 repository directory, However i still get the undetermined under GAV.
I did some research and i found that the undetermined is thrown if there is an Exception in the MinimalPomParser.
If i click on the download button to download a jar i get a link path like "{color:red}http://localhost:8082/kie-server/maven2wb/{color:#14892c}om{color}/myteam/Waffle/1.0.0/Waffle-1.0.0.jar{color}" which give a HTTP 404 ERROR. However i do see something wrong with the link, the artifact is "{color:#14892c}com{color}" but in the link it is generated as "{color:#14892c}om{color}". If i change it to "{color:#14892c}com{color}" the download proceeds without a HTTP 404 error.
> GAV names are not coming properly when running the tomcat as Service
> --------------------------------------------------------------------
>
> Key: DROOLS-1516
> URL: https://issues.jboss.org/browse/DROOLS-1516
> Project: Drools
> Issue Type: Bug
> Components: build, kie server, tools
> Affects Versions: 6.5.0.Final
> Environment: Windows
> Reporter: Arunraj SRM
> Assignee: Toni Rikkola
> Priority: Critical
> Labels: Drools, GAV,, Maven
> Attachments: gav_issue.png
>
>
> Deploy Drools Work Bench and KIE Server in Tomcat Server configured with SSL and started via service. All the artifacts populated under the GAV are displaying as
> <undetermined>:<undetermined>:<undetermined>
> instead of actual path including the guvnor
> Start-up values:
> -Dcatalina.home=C:\apache-tomcat-9.0.0.M19
> -Dcatalina.base=C:\apache-tomcat-9.0.0.M19
> -Djava.io.tmpdir=C:\apache-tomcat-9.0.0.M19\temp
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> -Djava.util.logging.config.file=C:\apache-tomcat-9.0.0.M19\conf\logging.properties
> -Xmx256M
> -XX:MaxPermSize=2048m
> -Dbtm.root=C:\apache-tomcat-9.0.0.M19\
> -Dbitronix.tm.configuration=C:\apache-tomcat-9.0.0.M19\conf\btm-config.properties
> -Dbitronix.tm.resource.configuration=C:\apache-tomcat-9.0.0.M19\conf\resources.properties
> -Djbpm.tsr.jndi.lookup=java:comp/env/TransactionSynchronizationRegistry
> -Djava.security.auth.login.config=C:\apache-tomcat-9.0.0.M19\webapps\kie-wb\WEB-INF\classes\login.config
> -Dorg.jboss.logging.provider=jdk
> -Dorg.jbpm.cdi.bm=java:comp/env/BeanManager
> -Dorg.kie.server.persistence.ds=java:comp/env/jdbc/jbpm
> -Dorg.kie.server.persistence.tm=org.hibernate.service.jta.platform.internal.BitronixJtaPlatform
> -Dorg.uberfire.nio.git.dir=C:\drools\repositories\git\
> -Dorg.guvnor.m2repo.dir=C:\drools\repositories\kie\
> -Dorg.uberfire.metadata.index.dir=C:\drools\runtime\
> -Dorg.uberfire.nio.git.ssh.cert.dir=C:\drools\runtime\
> -Dorg.kie.demo=false
> -Dorg.kie.example=false
> -Dorg.kie.server.id=default-kieserver
> -Dorg.kie.server.location=https://localhost/kie-server/services/rest/server
> -Dorg.kie.server.controller=https://localhost/kie-wb/rest/controller
> -Dorg.jbpm.server.ext.disabled=true
> -Dorg.drools.server.filter.classes=true
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (DROOLS-1516) GAV names are not coming properly when running the tomcat as Service
by CasterJose CasterJose (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1516?page=com.atlassian.jira.plugi... ]
CasterJose CasterJose commented on DROOLS-1516:
-----------------------------------------------
Thanks for the Reply,
I'm using the latest 7.2 drools version with apache-tomcat-8.0.45
Here are the startup values:
09-Sep-2017 14:46:30.964 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.0.45
09-Sep-2017 14:46:30.966 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Jun 26 2017 20:06:07 UTC
09-Sep-2017 14:46:30.966 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.0.45.0
09-Sep-2017 14:46:30.966 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Windows 10
09-Sep-2017 14:46:30.966 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 10.0
09-Sep-2017 14:46:30.966 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd64
09-Sep-2017 14:46:30.967 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: C:\Program Files\Java\jdk1.8.0_101\jre
09-Sep-2017 14:46:30.967 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_101-b13
09-Sep-2017 14:46:30.967 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation
09-Sep-2017 14:46:30.967 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: C:\Tools\Server\drools72\kie-drools-wb
09-Sep-2017 14:46:30.967 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: C:\Tools\Server\drools72\kie-drools-wb
09-Sep-2017 14:46:30.968 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:\Tools\Server\drools72\kie-drools-wb\conf\logging.properties
09-Sep-2017 14:46:30.968 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
09-Sep-2017 14:46:30.968 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
09-Sep-2017 14:46:30.968 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
09-Sep-2017 14:46:30.969 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.endorsed.dirs=C:\Tools\Server\drools72\kie-drools-wb\endorsed
09-Sep-2017 14:46:30.972 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\Tools\Server\drools72\kie-drools-wb
09-Sep-2017 14:46:30.973 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\Tools\Server\drools72\kie-drools-wb
09-Sep-2017 14:46:30.973 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:\Tools\Server\drools72\kie-drools-wb\temp
> GAV names are not coming properly when running the tomcat as Service
> --------------------------------------------------------------------
>
> Key: DROOLS-1516
> URL: https://issues.jboss.org/browse/DROOLS-1516
> Project: Drools
> Issue Type: Bug
> Components: build, kie server, tools
> Affects Versions: 6.5.0.Final
> Environment: Windows
> Reporter: Arunraj SRM
> Assignee: Toni Rikkola
> Priority: Critical
> Labels: Drools, GAV,, Maven
> Attachments: gav_issue.png
>
>
> Deploy Drools Work Bench and KIE Server in Tomcat Server configured with SSL and started via service. All the artifacts populated under the GAV are displaying as
> <undetermined>:<undetermined>:<undetermined>
> instead of actual path including the guvnor
> Start-up values:
> -Dcatalina.home=C:\apache-tomcat-9.0.0.M19
> -Dcatalina.base=C:\apache-tomcat-9.0.0.M19
> -Djava.io.tmpdir=C:\apache-tomcat-9.0.0.M19\temp
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> -Djava.util.logging.config.file=C:\apache-tomcat-9.0.0.M19\conf\logging.properties
> -Xmx256M
> -XX:MaxPermSize=2048m
> -Dbtm.root=C:\apache-tomcat-9.0.0.M19\
> -Dbitronix.tm.configuration=C:\apache-tomcat-9.0.0.M19\conf\btm-config.properties
> -Dbitronix.tm.resource.configuration=C:\apache-tomcat-9.0.0.M19\conf\resources.properties
> -Djbpm.tsr.jndi.lookup=java:comp/env/TransactionSynchronizationRegistry
> -Djava.security.auth.login.config=C:\apache-tomcat-9.0.0.M19\webapps\kie-wb\WEB-INF\classes\login.config
> -Dorg.jboss.logging.provider=jdk
> -Dorg.jbpm.cdi.bm=java:comp/env/BeanManager
> -Dorg.kie.server.persistence.ds=java:comp/env/jdbc/jbpm
> -Dorg.kie.server.persistence.tm=org.hibernate.service.jta.platform.internal.BitronixJtaPlatform
> -Dorg.uberfire.nio.git.dir=C:\drools\repositories\git\
> -Dorg.guvnor.m2repo.dir=C:\drools\repositories\kie\
> -Dorg.uberfire.metadata.index.dir=C:\drools\runtime\
> -Dorg.uberfire.nio.git.ssh.cert.dir=C:\drools\runtime\
> -Dorg.kie.demo=false
> -Dorg.kie.example=false
> -Dorg.kie.server.id=default-kieserver
> -Dorg.kie.server.location=https://localhost/kie-server/services/rest/server
> -Dorg.kie.server.controller=https://localhost/kie-wb/rest/controller
> -Dorg.jbpm.server.ext.disabled=true
> -Dorg.drools.server.filter.classes=true
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3266) Simple permission mapper can't represent wildcards or spaces
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3266?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-3266:
-------------------------------------
Fix Version/s: (was: 3.0.2.CR1)
> Simple permission mapper can't represent wildcards or spaces
> ------------------------------------------------------------
>
> Key: WFCORE-3266
> URL: https://issues.jboss.org/browse/WFCORE-3266
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Jason Greene
> Assignee: Jason Greene
> Priority: Blocker
> Fix For: 3.0.2.Final
>
>
> The inability of the simple-permission-mapper to handle wildcards forces the user to utilize complex logical permission mapper chains to achieve common use cases. This makes simple changes, such as adding an additional permission to a user unnecessarily complex. In addition to construction complexity, modifications performed by non-experts are likely to lead to unintended behavior, including accidentally granting permissions to a user that should not have them.
> This is readily apparent by even our default configuration requiring the use of 3 permission mappers to handle the basic case of denying anonymous users and allowing everyone else.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3267) Authorization identity forwarding not exposed to configuration
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3267?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-3267:
-------------------------------------
Fix Version/s: (was: 3.0.2.CR1)
> Authorization identity forwarding not exposed to configuration
> --------------------------------------------------------------
>
> Key: WFCORE-3267
> URL: https://issues.jboss.org/browse/WFCORE-3267
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Jason Greene
> Assignee: Jason Greene
> Priority: Blocker
> Fix For: 3.0.2.Final
>
>
> As part of EAP7-284, Elytron was designed for and contains implementation to support trusted use of identities between peers in addition to credential forwarding. Cases in which one would prefer this approach include:
> * Scenarios where the user has requirements to not send passwords over the wire. Notably credential forwarding requires TLS and/or secure networks
> * Setups where an authentication type that does not support credential forwarding are used (credential forwarding is limited to Plain, Form, and OAuth, all other mechanisms, including the out of the box Digest auth of EAP are not)
> * Environments where its desired to limit which systems are allowed to receive requests which are propagated
> Due to an oversight this capability was not properly wired to the server configuration (nor a config method on the Elytron API).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months