[JBoss JIRA] (WFLY-9877) NAKACK, UNICAST2 and MERGE2 need to translate to their newer variants
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-9877?page=com.atlassian.jira.plugin.... ]
Kabir Khan commented on WFLY-9877:
----------------------------------
[~pkremens] I think you are correct in not creating a JBEAP for this one, as it is not a blocker for EAP CD12, as [~brian.stansberry] says "we don't use those protocols in standalone-openshift.xml and people bringing their own config migrated from 6.4 is not something I care about in a TP release". It is a blocker for EAP 7.2.0.GA though, and will get merged any time now.
CC [~msvehla]
> NAKACK, UNICAST2 and MERGE2 need to translate to their newer variants
> ---------------------------------------------------------------------
>
> Key: WFLY-9877
> URL: https://issues.jboss.org/browse/WFLY-9877
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 12.0.0.Beta1
> Reporter: Richard Janík
> Assignee: Paul Ferraro
> Priority: Blocker
>
> This is only an issue for EAP, which has different versions than WFLY, for that reason, all the versions mentioned here are EAP ones.
> After some discussion with people who test migrations, we found that these protocols that were deprecated in JGroups 3.6.x present in 7.1.0 and were removed in JGroups 4.0.10 present in 7.2.0 should be brought back in some form:
> {noformat}
> NAKACK --> NAKACK2
> UNICAST2 --> UNICAST3
> MERGE2 --> MERGE3
> {noformat}
> These are not in the default 7.0 or 7.1 configuration, so why do we need to translate these like we do it for NAKACK2? Because these protocols can be expected to be present in the 7.1 configuration due to migration from 6.x, where they are by default. Since, after migration from 6.x, these will work with the 7.1 configuration, and since there is a reason to expect them being used even if they are deprecated, we should not just silently remove these protocols with the JGroups upgrade that is in 7.2 - the configuration file from 7.1 should always work with 7.2.
> Cc [~msvehla] [~pkremens]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFCORE-1719) Wildfly 10.1.0.CR1 does not start as a windows service
by Nicklas Karlsson (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1719?page=com.atlassian.jira.plugi... ]
Nicklas Karlsson commented on WFCORE-1719:
------------------------------------------
I found it to work on some combination of WildFlys/Windows versions/start as users (the service doesn't always have the same environment variables at its disposal?)
> Wildfly 10.1.0.CR1 does not start as a windows service
> ------------------------------------------------------
>
> Key: WFCORE-1719
> URL: https://issues.jboss.org/browse/WFCORE-1719
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 2.2.0.Final
> Environment: Windows 8/Windows Server 2012
> Oracle Java 8
> Reporter: Anton Yudin
> Assignee: Tomaz Cerar
> Fix For: 3.0.0.Alpha6, 2.2.1.CR1
>
>
> Wildfly fails to start as a windows service.
> Installation works fine:
> {code}
> .\service.bat install
> Using the X86-64bit version of prunsrv
> "C:\applications\wildfly-10.1.0.CR1-test\bin\service\amd64\wildfly-service" install Wildfly --DisplayName=WildFly --Description=""WildFly Application Server"" --LogLevel=INFO --LogPath="C:\applications\wildfly-10.1.0.CR1-test\standalone\log" --LogPrefix=service --StdOutput=auto --StdError=auto --StartMode=exe --Startup=manual --StartImage=cmd.exe --StartPath="C:\applications\wildfly-10.1.0.CR1-test\bin" ++StartParams="/c#set#NOPAUSE=Y#&&#standalone.bat#-Djboss.server.base.dir=C:\applications\wildfly-10.1.0.CR1-test\standalone#--server-config=standalone.xml" --StopMode=exe --StopImage=cmd.exe --StopPath="C:\applications\wildfly-10.1.0.CR1-test\bin" ++StopParams="/c jboss-cli.bat --controller=localhost:9990 --connect --command=:shutdown"
> Service Wildfly installed
> {code}
> Windows reports this error:
> {quote}
> Windows could not start the Wildfly on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code1.
> {quote}
> {code}
> Event log report:
> The Wildfly service terminated with the following service-specific error:
> Incorrect function.
> <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> <System>
> <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager"/>
> <EventID Qualifiers="49152">7024</EventID>
> <Version>0</Version>
> <Level>2</Level>
> <Task>0</Task>
> <Opcode>0</Opcode>
> <Keywords>0x8080000000000000</Keywords>
> <TimeCreated SystemTime="2016-08-13T21:40:42.402218400Z"/>
> <EventRecordID>196500</EventRecordID>
> <Correlation/>
> <Execution ProcessID="668" ThreadID="10184"/>
> <Channel>System</Channel>
> <Computer>ITPC7.intra.rfgh.net</Computer>
> <Security/>
> </System>
> -
> <EventData>
> <Data Name="param1">Wildfly</Data>
> <Data Name="param2">%%1</Data>
> <Binary>570069006C00640066006C0079000000</Binary>
> </EventData>
> </Event>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-10046) Cannot create cluster with JGroups Gossip router
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10046?page=com.atlassian.jira.plugin... ]
Radoslav Husar commented on WFLY-10046:
---------------------------------------
Also, you are using a wrong socket binding..
> Cannot create cluster with JGroups Gossip router
> ------------------------------------------------
>
> Key: WFLY-10046
> URL: https://issues.jboss.org/browse/WFLY-10046
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 12.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Paul Ferraro
> Attachments: standalone-full-ha-gosship1.xml, standalone-full-ha-gosship2.xml
>
>
> I've used config from EAP 7.1.0/WF11 where gossip router was configured in udp stack like:
> {code}
> <stack name="udp">
> <transport type="UDP" shared="false" socket-binding="jgroups-udp"/>
> <protocol type="PING"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="TUNNEL">
> <property name="gossip_router_hosts">
> 0.0.0.0[12001]
> </property>
> </protocol>
> </stack>
> {code}
> Gossip router was started on localhost:
> {{java -cp $JBOSS_HOME//bin/client/jboss-client.jar org.jgroups.stack.GossipRouter -port 12001 -bindaddress 0.0.0.0}}
> but cluster does not form up. The same configuration works in EAP 7.1.
> Attaching xml config files for both of the servers.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-10046) Cannot create cluster with JGroups Gossip router
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10046?page=com.atlassian.jira.plugin... ]
Radoslav Husar commented on WFLY-10046:
---------------------------------------
Please don't create more confusion by calling the stack 'udp' while it has nothing to do with UDP whatsoever.
Why are you downgrading FRAG3 to FRAG2?
> Cannot create cluster with JGroups Gossip router
> ------------------------------------------------
>
> Key: WFLY-10046
> URL: https://issues.jboss.org/browse/WFLY-10046
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 12.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Paul Ferraro
> Attachments: standalone-full-ha-gosship1.xml, standalone-full-ha-gosship2.xml
>
>
> I've used config from EAP 7.1.0/WF11 where gossip router was configured in udp stack like:
> {code}
> <stack name="udp">
> <transport type="UDP" shared="false" socket-binding="jgroups-udp"/>
> <protocol type="PING"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="TUNNEL">
> <property name="gossip_router_hosts">
> 0.0.0.0[12001]
> </property>
> </protocol>
> </stack>
> {code}
> Gossip router was started on localhost:
> {{java -cp $JBOSS_HOME//bin/client/jboss-client.jar org.jgroups.stack.GossipRouter -port 12001 -bindaddress 0.0.0.0}}
> but cluster does not form up. The same configuration works in EAP 7.1.
> Attaching xml config files for both of the servers.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-10052) Provide XML schema for credential-reference
by Yeray Borges (JIRA)
[ https://issues.jboss.org/browse/WFLY-10052?page=com.atlassian.jira.plugin... ]
Yeray Borges moved JBEAP-8480 to WFLY-10052:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-10052 (was: JBEAP-8480)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Domain Management
JCA
JMS
Mail
Security
(was: Domain Management)
(was: JCA)
(was: JMS)
(was: Mail)
(was: Security)
Target Release: (was: 7.2.0.GA)
Affects Version/s: (was: 7.1.0.DR13)
(was: 7.1.0.DR18)
> Provide XML schema for credential-reference
> -------------------------------------------
>
> Key: WFLY-10052
> URL: https://issues.jboss.org/browse/WFLY-10052
> Project: WildFly
> Issue Type: Enhancement
> Components: Domain Management, JCA, JMS, Mail, Security
> Reporter: Jeff Mesnil
> Assignee: Yeray Borges
> Priority: Minor
> Labels: credential-reference, eap72
>
> With https://issues.jboss.org/browse/EAP7-538, all passwords references in the subsystems must support credential references.
> The model attribute is provided by wildlfy-controller module (including its XML parser and marshaller) but the corresponding XML element has been added directly to the subsystems XML schemas. This will become a maintenance issue when/if the credential references has to be updated and all the subsystems schema risk to be out of sync with the actual code reading/writing the credential reference.
> We should follow the same design than for threads attributes (provided by the willdfly-threads module): the wildlfy-controller module provides a XML schema for the credential-references with its own versioned namespace and any subsystem that requires it will just refer to it.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9961) [JDK9+] @WebListener and Spring WebApplicationInitializer not working (JDK8 OK!)
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9961?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar resolved WFLY-9961.
-------------------------------
Fix Version/s: 13.0.0.Beta1
Resolution: Done
WildFly Core 5.0.0.Alpha1 that has fixed version of jandex, was merged to WildFly.
> [JDK9+] @WebListener and Spring WebApplicationInitializer not working (JDK8 OK!)
> --------------------------------------------------------------------------------
>
> Key: WFLY-9961
> URL: https://issues.jboss.org/browse/WFLY-9961
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 12.0.0.Final
> Reporter: cnsgithub cnsgithub
> Assignee: Stuart Douglas
> Priority: Blocker
> Fix For: 13.0.0.Beta1
>
>
> After upgrading to WFLY 12 Final, the WebApplicationInitializer class residing in the *.war classes Folder is no longer being detected when built with JDK 9. However with JDK 1.8 it works as expected.
> With WFLY 11, both variants JDK9, and JDK1.8 Build were working.
> {code:java}
> package de.test;
> import javax.servlet.ServletContext;
> import javax.servlet.ServletException;
> import org.springframework.web.WebApplicationInitializer;
> public class MyWebApplicationInitializer implements WebApplicationInitializer {
> @Override
> public void onStartup(ServletContext container) throws ServletException {
> System.out.println("!!!!!!!!!!!!!! ;-) !!!!!!!!!!!!");
> }
> }
> {code}
> Maybe(!) related to this: https://issues.jboss.org/browse/WFLY-9081
> Even more serious: the @WebListener doesn't seem to be recognized with JDK9 as well:
> {code:java}
> package de.test;
> import javax.servlet.ServletContextEvent;
> import javax.servlet.ServletContextListener;
> import javax.servlet.annotation.WebListener;
> import javax.servlet.http.HttpSessionEvent;
> import javax.servlet.http.HttpSessionIdListener;
> import javax.servlet.http.HttpSessionListener;
> @WebListener
> public class MyWebListener implements ServletContextListener, HttpSessionIdListener, HttpSessionListener {
> @Override
> public void contextInitialized(ServletContextEvent event) {
> System.out.println("contextInitialized !!!!!!!! I'm only working when i was built with JDK8");
> }
>
> @Override
> public void sessionIdChanged(HttpSessionEvent arg0, String arg1) {
> // TODO Auto-generated method stub
>
> }
> }
> {code}
> The actual error seems to happen quite early: JBossWebMetaData
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2395) [DMN Designer] Invocation parameter and table output are not paired correctly
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2395?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2395:
--------------------------------
Description:
Invocation parameter is not updated if user updates output of the decision table output.
h2. Acceptance criteria
# Check invocation parameter and decision table output are paired (/)
## inv. parameter -> table (single) output
## table (single) output -> inv. parameter
## inv. parameter -> table (multi) output
## table (multi) output -> inv. parameter
# Check context entry and decision table output are paired (/)
## context entry -> table (single) output
## table (single) output -> context entry
## context entry -> table (multi) output
## table (multi) output -> context entry.
was:
Invocation parameter is not updated if user updates output of the decision table output.
h2. Acceptance criteria
# Check invocation parameter and decision table output are paired (x)
## inv. parameter -> table (single) output
## table (single) output -> inv. parameter
## inv. parameter -> table (multi) output
## table (multi) output -> inv. parameter
# Check context entry and decision table output are paired (x)
## context entry -> table (single) output
## table (single) output -> context entry
## context entry -> table (multi) output
## table (multi) output -> context entry.
> [DMN Designer] Invocation parameter and table output are not paired correctly
> -----------------------------------------------------------------------------
>
> Key: DROOLS-2395
> URL: https://issues.jboss.org/browse/DROOLS-2395
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Attachments: Screenshot from 2018-03-16 12-51-03.png, Screenshot from 2018-03-16 12-51-14.png, Screenshot from 2018-03-16 12-51-22.png, Screenshot from 2018-03-20 08-59-39.png, Screenshot from 2018-03-20 09-20-04.png
>
>
> Invocation parameter is not updated if user updates output of the decision table output.
> h2. Acceptance criteria
> # Check invocation parameter and decision table output are paired (/)
> ## inv. parameter -> table (single) output
> ## table (single) output -> inv. parameter
> ## inv. parameter -> table (multi) output
> ## table (multi) output -> inv. parameter
> # Check context entry and decision table output are paired (/)
> ## context entry -> table (single) output
> ## table (single) output -> context entry
> ## context entry -> table (multi) output
> ## table (multi) output -> context entry.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2395) [DMN Designer] Invocation parameter and table output are not paired correctly
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2395?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-2395:
-------------------------------------
New issue filed here: https://issues.jboss.org/browse/DROOLS-2402
> [DMN Designer] Invocation parameter and table output are not paired correctly
> -----------------------------------------------------------------------------
>
> Key: DROOLS-2395
> URL: https://issues.jboss.org/browse/DROOLS-2395
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Attachments: Screenshot from 2018-03-16 12-51-03.png, Screenshot from 2018-03-16 12-51-14.png, Screenshot from 2018-03-16 12-51-22.png, Screenshot from 2018-03-20 08-59-39.png, Screenshot from 2018-03-20 09-20-04.png
>
>
> Invocation parameter is not updated if user updates output of the decision table output.
> h2. Acceptance criteria
> # Check invocation parameter and decision table output are paired (x)
> ## inv. parameter -> table (single) output
> ## table (single) output -> inv. parameter
> ## inv. parameter -> table (multi) output
> ## table (multi) output -> inv. parameter
> # Check context entry and decision table output are paired (x)
> ## context entry -> table (single) output
> ## table (single) output -> context entry
> ## context entry -> table (multi) output
> ## table (multi) output -> context entry.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months