[JBoss JIRA] (WFCORE-3127) standalone.bat script does not parse JAVA_OPTS containing '|' symbol properly
by Radovan Stancel (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3127?page=com.atlassian.jira.plugi... ]
Radovan Stancel commented on WFCORE-3127:
-----------------------------------------
As code was changed a lot, fix for WFCORE-99 is no more valid.
> standalone.bat script does not parse JAVA_OPTS containing '|' symbol properly
> -----------------------------------------------------------------------------
>
> Key: WFCORE-3127
> URL: https://issues.jboss.org/browse/WFCORE-3127
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 3.0.0.Beta30
> Reporter: Radovan Stancel
> Assignee: Radovan Stancel
> Labels: downstream_dependency
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> ======================
> Scenario-1)
> ============ With the following line of JAVA_OPTS in "standalone.bat.conf" file
> set "JAVA_OPTS=%JAVA_OPTS% -Dhttp.nonProxyHosts=localhost|127.0.0.1|10.10.10.*"
> {code}
> Error while starting EAP 6.1.1
> C:\jboss-eap-6.1.1\bin>standalone.bat
> Calling "C:\jboss-eap-6.1.1\bin\standalone.conf.bat"
> Setting JAVA property to "C:\JDKs\jdk1.7.0_67\bin\java"
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> {code}
> Scenario-2)
> ============ In Windows "^" sign is the escape character so we tried altering the JAVA_OPTS as following in the "standalone.bat.conf" file:
> set "JAVA_OPTS=%JAVA_OPTS% -Dhttp.nonProxyHosts=localhost^|127.0.0.1^|10.10.10.*"
> Now EAP 6.1.1 server starts but still we see the following messages in windows console:
> {code}
> C:\jboss-eap-6.1.1\bin>standalone.bat
> Calling "C:\jboss-eap-6.1.1\bin\standalone.conf.bat"
> Setting JAVA property to "C:\JDKs\jdk1.7.0_67\bin\java"
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3127) standalone.bat script does not parse JAVA_OPTS containing '|' symbol properly
by Radovan Stancel (JIRA)
Radovan Stancel created WFCORE-3127:
---------------------------------------
Summary: standalone.bat script does not parse JAVA_OPTS containing '|' symbol properly
Key: WFCORE-3127
URL: https://issues.jboss.org/browse/WFCORE-3127
Project: WildFly Core
Issue Type: Bug
Components: Scripts
Affects Versions: 3.0.0.Beta30
Reporter: Radovan Stancel
Assignee: Radovan Stancel
======================
Scenario-1)
============ With the following line of JAVA_OPTS in "standalone.bat.conf" file
set "JAVA_OPTS=%JAVA_OPTS% -Dhttp.nonProxyHosts=localhost|127.0.0.1|10.10.10.*"
{code}
Error while starting EAP 6.1.1
C:\jboss-eap-6.1.1\bin>standalone.bat
Calling "C:\jboss-eap-6.1.1\bin\standalone.conf.bat"
Setting JAVA property to "C:\JDKs\jdk1.7.0_67\bin\java"
'127.0.0.1' is not recognized as an internal or external command,
operable program or batch file.
{code}
Scenario-2)
============ In Windows "^" sign is the escape character so we tried altering the JAVA_OPTS as following in the "standalone.bat.conf" file:
set "JAVA_OPTS=%JAVA_OPTS% -Dhttp.nonProxyHosts=localhost^|127.0.0.1^|10.10.10.*"
Now EAP 6.1.1 server starts but still we see the following messages in windows console:
{code}
C:\jboss-eap-6.1.1\bin>standalone.bat
Calling "C:\jboss-eap-6.1.1\bin\standalone.conf.bat"
Setting JAVA property to "C:\JDKs\jdk1.7.0_67\bin\java"
'127.0.0.1' is not recognized as an internal or external command,
operable program or batch file.
'127.0.0.1' is not recognized as an internal or external command,
operable program or batch file.
'127.0.0.1' is not recognized as an internal or external command,
operable program or batch file.
'127.0.0.1' is not recognized as an internal or external command,
operable program or batch file.
'127.0.0.1' is not recognized as an internal or external command,
operable program or batch file.
'127.0.0.1' is not recognized as an internal or external command,
operable program or batch file.
'127.0.0.1' is not recognized as an internal or external command,
operable program or batch file.
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (WFLY-9096) JMS client fails to connect with SSL on IBM JDK 8
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-9096?page=com.atlassian.jira.plugin.... ]
Jan Kalina commented on WFLY-9096:
----------------------------------
Blocking *ARTEMIS-1299* resolved for *org.apache.activemq.artemis 2.3.0* - defaults can be fixed after artemis tagging and upgrade in wildfly (not sure if possible/acceptable in short-term, as wildfly currently use very old version 1.5.5).
> JMS client fails to connect with SSL on IBM JDK 8
> -------------------------------------------------
>
> Key: WFLY-9096
> URL: https://issues.jboss.org/browse/WFLY-9096
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Security
> Affects Versions: 11.0.0.Alpha1
> Environment: IBM JDK 8:
> {code}
> $ java -version
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxi3280sr4fp2-20170322_01(SR4 FP2))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux x86-32 20170314_340265 (JIT enabled, AOT enabled)
> J9VM - R28_20170314_2309_B340265
> JIT - tr.r14.java.green_20170314_134138
> GC - R28_20170314_2309_B340265
> J9CL - 20170314_340265)
> JCL - 20170318_01 based on Oracle jdk8u121-b13
> {code}
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Critical
> Labels: eap7.1-risks-mitigation
>
> If server is configured to authenticate JMS client with SSL configured using Elytron SSLContext then if client is using IBM JDK 8, authentication fails with:
> {code}
> ERROR: AMQ214016: Failed to create netty connection
> java.nio.channels.ClosedChannelException
> at io.netty.handler.ssl.SslHandler.channelInactive(...)(Unknown Source)
> Producer got exception and ended:javax.jms.JMSException: Failed to create session factory
> javax.jms.JMSException: Failed to create session factory
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:757)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:265)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:260)
> at ProducerTransSession.run(ProducerTransSession.java:75)
> Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.]
> at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:787)
> at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:755)
> ... 3 more
> {code}
> If client uses Oracle JDK 8 or SSL authentication is configured on http listener using PicketBox then client connects successfully.
> Issue is under investigation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (DROOLS-1511) NullPointerException when running sample projects
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1511?page=com.atlassian.jira.plugi... ]
Kris Verlaenen commented on DROOLS-1511:
----------------------------------------
[~tomasdavidorg] I believe it was related to this fix:
https://github.com/kiegroup/droolsjbpm-tools/commit/381e7fc9bda075d0b086a...
> NullPointerException when running sample projects
> -------------------------------------------------
>
> Key: DROOLS-1511
> URL: https://issues.jboss.org/browse/DROOLS-1511
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Environment: DevStudio 10 + IS 10.3.0.CR2
> Eclipse Neon + Drools plugin 7.0.0.CR3
> Drools Runtime 7.x
> Reporter: Tomas David
> Assignee: Kris Verlaenen
> Priority: Blocker
> Labels: reported-by-qe
> Fix For: 7.1.0.Final
>
>
> NullPointerException is thrown when running sample project using Drools and Java Runtime classes because KieSession is not created.
> Eclipse log:
> !SESSION 2017-04-04 12:39:38.638 -----------------------------------------------
> eclipse.buildId=4.6.3.M20170301-0400
> java.version=1.8.0_121
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
> !ENTRY org.drools.eclipse 4 120 2017-04-04 12:41:31.737
> !MESSAGE Internal error in Drools Plugin:
> !STACK 1
> Java Model Exception: Java Model Status [Build path contains duplicate entry: 'DROOLS/Drools' for project 'TestProject']
> at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:786)
> at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3097)
> at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3059)
> at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3112)
> at org.drools.eclipse.util.DroolsRuntimeManager.addBuilder(DroolsRuntimeManager.java:122)
> at org.drools.eclipse.action.ConvertToDroolsProjectAction.run(ConvertToDroolsProjectAction.java:45)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:247)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5227)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4561)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4151)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> !SUBENTRY 1 org.eclipse.jdt.core 4 977 2017-04-04 12:41:31.739
> !MESSAGE Build path contains duplicate entry: 'DROOLS/Drools' for project 'TestProject'
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3126) Cannot start EAP - MALLOC_ARENA_MAX=1: is not an identifier
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3126?page=com.atlassian.jira.plugi... ]
Tomaz Cerar moved JBEAP-12435 to WFCORE-3126:
---------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-3126 (was: JBEAP-12435)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Scripts
(was: Scripts)
Affects Version/s: 3.0.0.Beta30
(was: 7.1.0.ER3)
Affects Testing: (was: Regression,Blocks Testing)
> Cannot start EAP - MALLOC_ARENA_MAX=1: is not an identifier
> ------------------------------------------------------------
>
> Key: WFCORE-3126
> URL: https://issues.jboss.org/browse/WFCORE-3126
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 3.0.0.Beta30
> Environment: {noformat}
> $ uname -a
> SunOS 5.10 Generic_150400-51 sun4v sparc SUNW,SPARC-Enterprise-T1000
> {noformat}
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Priority: Blocker
>
> JBEAP-11565 add the following line into the EAP launching scripts:
> {noformat}
> export MALLOC_ARENA_MAX="${MALLOC_ARENA_MAX:-1}"
> {noformat}
> This is problematic on *Solaris 10 sparc*
> {noformat}
> $ ./standalone.sh
> ./standalone.sh: MALLOC_ARENA_MAX=1: is not an identifier
> $ ./domain.sh
> ./domain.sh: MALLOC_ARENA_MAX=1: is not an identifier
> {noformat}
> See https://issues.apache.org/jira/browse/MNG-5829 description:
> {noformat}
> The $(cmd) idiom is used extensively in bin/mvn from lines 199-220, but this is not supported by older incarnations of /bin/sh (used on the shebang line). The `cmd` idiom is slightly more portable, and looks like it can probably be directly substituted.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3042) It is not possible to add new Elytron policy after adding and removing it first
by Martin Stefanko (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3042?page=com.atlassian.jira.plugi... ]
Martin Stefanko reassigned WFCORE-3042:
---------------------------------------
Assignee: Martin Stefanko
> It is not possible to add new Elytron policy after adding and removing it first
> -------------------------------------------------------------------------------
>
> Key: WFCORE-3042
> URL: https://issues.jboss.org/browse/WFCORE-3042
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Jan Kašík
> Assignee: Martin Stefanko
>
> Adding new Elytron policy fails if it was previously added and then removed. Next adding fails [1] and with exception [2] in server.log.
> [1]
> {code}
> [standalone@localhost:9990 /] /subsystem=elytron/policy=jacc:add(jacc-policy=[{name => jacc}])
> {
> "outcome" => "failed",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> },
> "failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.policy" => "Failed to start service
> Caused by: java.lang.RuntimeException: Failed to set policy [org.wildfly.security.authz.jacc.JaccDelegatingPolicy@502d9a84]
> Caused by: java.lang.SecurityException: ELY03018: Cannot add permissions to a read-only permission collection"}},
> "rolled-back" => true
> }
> {code}
> [2]
> {code}
> 2017-06-29 11:08:35,700 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service org.wildfly.security.policy: org.jboss.msc.service.StartException in service org.wildfly.security.policy: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.RuntimeException: Failed to set policy [org.wildfly.security.authz.jacc.JaccDelegatingPolicy@502d9a84]
> at org.wildfly.extension.elytron.PolicyDefinitions$1$1.start(PolicyDefinitions.java:177)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> ... 3 more
> Caused by: java.lang.SecurityException: ELY03018: Cannot add permissions to a read-only permission collection
> at org.wildfly.security.authz.jacc.JaccDelegatingPolicy$1.add(JaccDelegatingPolicy.java:126)
> at java.security.Policy.addStaticPerms(Policy.java:686)
> at java.security.Policy.getPermissions(Policy.java:673)
> at org.jboss.security.jacc.DelegatingPolicy.getPermissions(DelegatingPolicy.java:125)
> at java.security.Policy.initPolicy(Policy.java:327)
> at java.security.Policy.setPolicy(Policy.java:270)
> at org.wildfly.extension.elytron.PolicyDefinitions$1$1.lambda$setPolicyAction$0(PolicyDefinitions.java:201)
> at org.wildfly.extension.elytron.PolicyDefinitions$1$1.setPolicy(PolicyDefinitions.java:195)
> at org.wildfly.extension.elytron.PolicyDefinitions$1$1.start(PolicyDefinitions.java:173)
> ... 5 more
> 2017-06-29 11:08:35,701 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("policy" => "jacc")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.policy" => "Failed to start service
> Caused by: java.lang.RuntimeException: Failed to set policy [org.wildfly.security.authz.jacc.JaccDelegatingPolicy@502d9a84]
> Caused by: java.lang.SecurityException: ELY03018: Cannot add permissions to a read-only permission collection"}}
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (DROOLS-1186) Setting the planning variable nullable in nurserostering examples causes Drools NPE
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1186?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet commented on DROOLS-1186:
------------------------------------------
[~code4dc] If this was fixed after 6.5.0.Final community went out, then it's fixed only in a product release for the 6.x series. Of course, it's also fixed in community on master, so for 7.0.0.Final. If this was fixed before 6.5.0.Final community went out, it's probably fixed in there too.
See item "Backport bugfixes to maintenance branches" in the comparison here:
https://www.optaplanner.org/community/product.html
> Setting the planning variable nullable in nurserostering examples causes Drools NPE
> -----------------------------------------------------------------------------------
>
> Key: DROOLS-1186
> URL: https://issues.jboss.org/browse/DROOLS-1186
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final, 6.3.0.Final
> Environment: Windows 7 x 64, JDK 8u66, IDE netbeans 8.0.1.
> Reporter: Julio Bellon Aguilera
> Assignee: Mario Fusco
> Priority: Critical
> Fix For: 7.0.0.Beta1
>
> Attachments: PLANNER_488.patch
>
>
> If you set the planning variable to "nullable=true", firstable, causes a IllegalStateException.
> fixed that, causes the first NPE, and fixed that, causes other NPE unfixed:
> Exception in thread "AWT-EventQueue-0" java.lang.IllegalStateException:
> Caused by: java.lang.NullPointerException
> at org.drools.core.phreak.RuleNetworkEvaluator.deleteChildLeftTuple(RuleNetworkEvaluator.java:778)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months