[JBoss JIRA] (WFCORE-1395) Deprecate /host=master/core-service=management/access=authorization
by ehsavoie Hugonnet (JIRA)
ehsavoie Hugonnet created WFCORE-1395:
-----------------------------------------
Summary: Deprecate /host=master/core-service=management/access=authorization
Key: WFCORE-1395
URL: https://issues.jboss.org/browse/WFCORE-1395
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 2.1.0.CR1
Reporter: ehsavoie Hugonnet
Assignee: ehsavoie Hugonnet
Priority: Minor
Fix For: 3.0.0.Alpha1
The /host=master/core-service=management/access=authorization is odd. It should be deprecated and made non-functional in WF 11.
Non-functional meaning the add / remove / write-attribute handlers log a WARN and do nothing
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFCORE-1394) default maxPermgen is added when jvm isn't configured
by Martin Simka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1394?page=com.atlassian.jira.plugi... ]
Martin Simka moved JBEAP-3458 to WFCORE-1394:
---------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1394 (was: JBEAP-3458)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Domain Management
(was: Domain Management)
Target Release: (was: 7.backlog.GA)
Affects Version/s: 2.1.0.CR1
(was: 7.0.0.ER5)
> default maxPermgen is added when jvm isn't configured
> ------------------------------------------------------
>
> Key: WFCORE-1394
> URL: https://issues.jboss.org/browse/WFCORE-1394
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.1.0.CR1
> Reporter: Martin Simka
> Assignee: Brian Stansberry
>
> Default maxPermgen size is added when {{jvm}} element isn't specified in domain.xml/host.xml and warning is logged.
> {code:xml}
> <server-group name="main-server-group" profile="default">
> <!--
> <jvm name="default">
> <heap size="64m" max-size="512m"/>
> </jvm>
> -->
> <socket-binding-group ref="standard-sockets"/>
> </server-group>
> {code}
> {noformat}
> WFLYHC0011: Ignoring <permgen> for jvm 'SUN' type jvm: null
> {noformat}
> It happens because default is defined in [JvmElement.java#L76|https://github.com/wildfly/wildfly-core/blob/master/h...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6106) Exception is thrown during access, setting of cache in Infinispan in cluster with two nodes
by Serg Jakean19019 (JIRA)
[ https://issues.jboss.org/browse/WFLY-6106?page=com.atlassian.jira.plugin.... ]
Serg Jakean19019 commented on WFLY-6106:
----------------------------------------
thanks.
such answer oft - could You try-reproduce in new version is no used. earlier version 9.01.Final was adviced.
> Exception is thrown during access, setting of cache in Infinispan in cluster with two nodes
> -------------------------------------------------------------------------------------------
>
> Key: WFLY-6106
> URL: https://issues.jboss.org/browse/WFLY-6106
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 9.0.1.Final
> Reporter: Serg Jakean19019
> Assignee: Paul Ferraro
> Attachments: logErrorsInfiniSpan.txt
>
>
> Exception is thrown during access and setting of cache in Infinispan. The error occurs not immediately.
> Konfiguration des CacheContainer:
> <cache-container name="customCache" default-cache="cachedb">
> <transport lock-timeout="60000"/>
> <replicated-cache name="cachedb" mode="SYNC">
> <locking isolation="READ_COMMITTED" striping="false" acquire-timeout="60000" concurrency-level="1000"/>
> <transaction mode="BATCH"/>
> <expiration lifespan="15000"/>
> </replicated-cache>
> </cache-container>
> Access of cache from Java:
> @Resource(lookup = "java:jboss/infinispan/container/customCache")
> private CacheContainer cc;
> private Map<String, Object> cache;
> public void setInInfiniSpan(String name, Object object) {
> Cache<Object,Object> cache = cc.getCache();
> TransactionManager tm = cache.getAdvancedCache().getTransactionManager();
> try {
> cache.startBatch();
> cache.put(name, object);
> cache.endBatch(true);
> } catch (SecurityException e) {
> // TODO Auto-generated catch block
> logger.error("SecurityException: "+e.getMessage(), e);
> } catch (IllegalStateException e) {
> // TODO Auto-generated catch block
> logger.error("IllegalStateException: "+e.getMessage(), e);
> }
> }
> Logs:
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (DROOLS-1048) Change github url from github.com/droolsjbpm/ to github.com/kiegroup/
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1048?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet edited comment on DROOLS-1048 at 2/17/16 6:27 AM:
-------------------------------------------------------------------
Extra requirement: *All repository names must match the artifactId of the root pom.*
- repo droolsjbpm-knowledge must be renamed to ...
- -pom drools-multiproject must be renamed to drools (to match rep drools)-
etc
This is important for automated scripts such as xmvn (which builds RPM's), as well as to adhere to maven standards (which are relied upon by maven site etc).
was (Author: ge0ffrey):
Extra requirement: *All repository names must match the artifactId of the root pom.*
- repo droolsjbpm-knowledge must be renamed to ...
- pom drools-multiproject must be renamed to drools (to match rep drools)
etc
This is important for automated scripts such as xmvn (which builds RPM's), as well as to adhere to maven standards (which are relied upon by maven site etc).
> Change github url from github.com/droolsjbpm/ to github.com/kiegroup/
> ---------------------------------------------------------------------
>
> Key: DROOLS-1048
> URL: https://issues.jboss.org/browse/DROOLS-1048
> Project: Drools
> Issue Type: Task
> Components: build
> Reporter: Geoffrey De Smet
> Assignee: Petr Široký
> Priority: Critical
>
> [~mark.proctor] asked me to make an inventory of what would need to happen if we ever migrate from github.com/droolsjbpm/ to github.com/kiegroup/. Technically this issue is very simply (just change it in GitHub), but organizationally this issue is difficult and dangerous: it needs to be done with care.
> Preparation:
> 1) Get some experience
> - Make a dummy repository in droolsjbpm, add some files and a few branches, fork it to your user account, add a PR on it, clone it 2 times:
> -- Once from droolsjbpm
> -- Once from your user account with droolsjbpm addes as upstream ("git remote add upstream ...github.com/droolsjbpm/...")
> - Add some local changes on both dirs.
> - On GitHub, go into the repository settings, in the danger zone and move it from droolsjbpm to kiegroup.
> - Try using it from your 2 local clones ("git pull --rebase" or "git fetch upstream"). Copy paste the error messages for later use.
> -- Fix it locally without recloning, without losing the local changes, etc. Record these steps clearly in a recipe to share with everyone else later.
> -- Once it's fixed, see if you can do git operations without having to specify origin for the direct droolsjbpm clone. See also the git option "-u" - you'll likely have to add in the recipe as an extra step.
> -- What happened to the open PR?
> 2) Clean up our repositories in droolsjbpm. There are a few dead ones that we should not be moving.
> 3) Set up roles and users of github.com/kiegroup.
> 4) Reach out
> - Talk to each type of person involved:
> -- R&D developer
> -- QA
> -- Productization
> -- Product docs
> -- Community
> - Make an inventory of references to "github.com/droolsjbpm"
> -- Do a find in path on all our files for "github.com/droolsjbpm")
> -- Which webapps reference it?
> --- jenkins
> --- jira
> --- www.openhub.net
> --- gitter
> --- stackoverflow
> --- google forums / mailing lists
> --- ...
> - Set a date when you'll be moving the first repository.
> -- Clearly communicate on all channels to let everyone know. This includes:
> --- Public mailing lists and fora: Drools, OptaPlanner, jBPM, ...
> --- Internal mailing lists: sme-brms, pm lists, bsig, etc
> --- IRC channel topics
> --- Social media (Twitter accounts etc)
> --- ...
> - Clearly communicate:
> -- What you'll do
> -- When you'll do it
> -- How strong the freeze is: Can they make local changes meanwhile? Will they lose the open PR's? How will this affect their forks and branches? Answer all these questions proactively, based on your experience. Cropped screenshots are good!
> -- A recipe: What they need to do - step by step for dummies - after the merge is done.
> -- Get someone to review this mail before it goes out.
> - You can't overcommunicate this, but you can undercommunicate it. And there's always going to be 1 person who complains he wasn't told about it and it messes up his work.
> 5) Do it:
> - You can do one repository at a time, or do multiple at the same time.
> -- I'd recommend to start with just 1 to get a feel for it.
> - Do them in reverse order of the repository-list.txt!
> - DELETE THE OLD REPOSITORY. DO NOT COPY IT, BUT MOVE IT.
> -- After the move, we want anyone that's trying to pull from droolsjbpm to clearly *fail* pulling, but without losing local changes.
> -- Some people will not have read your mail, they need to fail when pulling, otherwise they'll find themselves asking in 5 months why we haven't done any changes in 5 months.
> - In droolsjbpm, create a repository called all_repositories_have_moved_to_github_com_kiegroup and make sure it's on the top of the list of the droolsjbpm repositories. Add a link in it's readme.adoc. This is for people who follow dead links from stackoverflow etc.
> - Migrations like this should really happen during the weekend to reduce the impact on the rest of the team, ask your manager to swap a weekday for a weekend day.
> 6) Clean up the fallout
> - Go through your inventory and replace the references as far as humanly reasonable (stackoverflow is likely to be unreasonably, but openhub is not).
> Anyway, that's my 2 cents (from my experience when moving svn to Git and splitting up the monastical build 5 years ago). Do this right and this will be almost a non-event (5 years ago it went pretty well on the engineering side, but less on the product side). Mess this up and this can be a disaster that will antagonize a lot of people...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-5566) org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase#testPutToBackupNotRelayed
by Ivan Straka (JIRA)
[ https://issues.jboss.org/browse/WFLY-5566?page=com.atlassian.jira.plugin.... ]
Ivan Straka commented on WFLY-5566:
-----------------------------------
Thank you. I just was not sure about that idea.
> org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase#testPutToBackupNotRelayed
> --------------------------------------------------------------------------------
>
> Key: WFLY-5566
> URL: https://issues.jboss.org/browse/WFLY-5566
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Test Suite
> Affects Versions: 10.0.0.CR2
> Reporter: Ivan Straka
> Assignee: Radoslav Husar
>
> There is org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase#testPutToBackupNotRelayed failing with exception:
> {code:java}
> Error Message
> expected:<500> but was:<200>
> Stacktrace
> java.lang.AssertionError: expected:<500> but was:<200>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutToBackupNotRelayed(XSiteSimpleTestCase.java:202)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (DROOLS-1048) Change github url from github.com/droolsjbpm/ to github.com/kiegroup/
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1048?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet edited comment on DROOLS-1048 at 2/17/16 5:50 AM:
-------------------------------------------------------------------
Extra requirement: *All repository names must match the artifactId of the root pom.*
- repo droolsjbpm-knowledge must be renamed to ...
- pom drools-multiproject must be renamed to drools (to match rep drools)
etc
This is important for automated scripts such as xmvn (which builds RPM's), as well as to adhere to maven standards (which are relied upon by maven site etc).
was (Author: ge0ffrey):
Extra requirement: *All repository names must match the artifactId of the root pom.*
- repo droolsjbpm-knowledge must be renamed to ...
- pom drools-multiproject must be renamed to drools (to match rep drools)
etc
This is important for automated scripts such as xmvn (which builds RPM's) etc.
> Change github url from github.com/droolsjbpm/ to github.com/kiegroup/
> ---------------------------------------------------------------------
>
> Key: DROOLS-1048
> URL: https://issues.jboss.org/browse/DROOLS-1048
> Project: Drools
> Issue Type: Task
> Components: build
> Reporter: Geoffrey De Smet
> Assignee: Petr Široký
> Priority: Critical
>
> [~mark.proctor] asked me to make an inventory of what would need to happen if we ever migrate from github.com/droolsjbpm/ to github.com/kiegroup/. Technically this issue is very simply (just change it in GitHub), but organizationally this issue is difficult and dangerous: it needs to be done with care.
> Preparation:
> 1) Get some experience
> - Make a dummy repository in droolsjbpm, add some files and a few branches, fork it to your user account, add a PR on it, clone it 2 times:
> -- Once from droolsjbpm
> -- Once from your user account with droolsjbpm addes as upstream ("git remote add upstream ...github.com/droolsjbpm/...")
> - Add some local changes on both dirs.
> - On GitHub, go into the repository settings, in the danger zone and move it from droolsjbpm to kiegroup.
> - Try using it from your 2 local clones ("git pull --rebase" or "git fetch upstream"). Copy paste the error messages for later use.
> -- Fix it locally without recloning, without losing the local changes, etc. Record these steps clearly in a recipe to share with everyone else later.
> -- Once it's fixed, see if you can do git operations without having to specify origin for the direct droolsjbpm clone. See also the git option "-u" - you'll likely have to add in the recipe as an extra step.
> -- What happened to the open PR?
> 2) Clean up our repositories in droolsjbpm. There are a few dead ones that we should not be moving.
> 3) Set up roles and users of github.com/kiegroup.
> 4) Reach out
> - Talk to each type of person involved:
> -- R&D developer
> -- QA
> -- Productization
> -- Product docs
> -- Community
> - Make an inventory of references to "github.com/droolsjbpm"
> -- Do a find in path on all our files for "github.com/droolsjbpm")
> -- Which webapps reference it?
> --- jenkins
> --- jira
> --- www.openhub.net
> --- gitter
> --- stackoverflow
> --- google forums / mailing lists
> --- ...
> - Set a date when you'll be moving the first repository.
> -- Clearly communicate on all channels to let everyone know. This includes:
> --- Public mailing lists and fora: Drools, OptaPlanner, jBPM, ...
> --- Internal mailing lists: sme-brms, pm lists, bsig, etc
> --- IRC channel topics
> --- Social media (Twitter accounts etc)
> --- ...
> - Clearly communicate:
> -- What you'll do
> -- When you'll do it
> -- How strong the freeze is: Can they make local changes meanwhile? Will they lose the open PR's? How will this affect their forks and branches? Answer all these questions proactively, based on your experience. Cropped screenshots are good!
> -- A recipe: What they need to do - step by step for dummies - after the merge is done.
> -- Get someone to review this mail before it goes out.
> - You can't overcommunicate this, but you can undercommunicate it. And there's always going to be 1 person who complains he wasn't told about it and it messes up his work.
> 5) Do it:
> - You can do one repository at a time, or do multiple at the same time.
> -- I'd recommend to start with just 1 to get a feel for it.
> - Do them in reverse order of the repository-list.txt!
> - DELETE THE OLD REPOSITORY. DO NOT COPY IT, BUT MOVE IT.
> -- After the move, we want anyone that's trying to pull from droolsjbpm to clearly *fail* pulling, but without losing local changes.
> -- Some people will not have read your mail, they need to fail when pulling, otherwise they'll find themselves asking in 5 months why we haven't done any changes in 5 months.
> - In droolsjbpm, create a repository called all_repositories_have_moved_to_github_com_kiegroup and make sure it's on the top of the list of the droolsjbpm repositories. Add a link in it's readme.adoc. This is for people who follow dead links from stackoverflow etc.
> - Migrations like this should really happen during the weekend to reduce the impact on the rest of the team, ask your manager to swap a weekday for a weekend day.
> 6) Clean up the fallout
> - Go through your inventory and replace the references as far as humanly reasonable (stackoverflow is likely to be unreasonably, but openhub is not).
> Anyway, that's my 2 cents (from my experience when moving svn to Git and splitting up the monastical build 5 years ago). Do this right and this will be almost a non-event (5 years ago it went pretty well on the engineering side, but less on the product side). Mess this up and this can be a disaster that will antagonize a lot of people...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months