[JBoss JIRA] (DROOLS-1006) License header: replace Jboss Inc by Red Hat, Inc. and/or its affiliates.
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1006?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-1006:
-------------------------------------
Description:
1) In java, drl and css files, replace in path this Case Sensitive Regular Expression in IntelliJ:
{code}
^/\*\n \* Copyright (\d{4}) JBoss Inc\n
{code}
by with this
{code}
/*\n * Copyright $1 Red Hat, Inc. and/or its affiliates.\n
{code}
To understand the regex, read this:
https://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html
Commit that already before starting step 2. I even recommend doing a separate commit per file type. (But wait with pushing until all are fixed.)
2) Then look for the string "JBoss Inc" in all files, case insensitive. Fix those too if applicable. Either by another smart regex find-replace or manually.
was:
1) In java and drl files, replace in path this Case Sensitive Regular Expression in IntelliJ:
{code}
^/\*\n \* Copyright (\d{4}) JBoss Inc\n
{code}
by with this
{code}
/*\n * Copyright $1 Red Hat, Inc. and/or its affiliates.\n
{code}
To understand the regex, read this:
https://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html
Commit that already before starting step 2. I even recommend doing a separate commit per file type. (But wait with pushing until all are fixed.)
2) Then look for the string "JBoss Inc" in all files, case insensitive. Fix those too if applicable. Either by another smart regex find-replace or manually.
> License header: replace Jboss Inc by Red Hat, Inc. and/or its affiliates.
> -------------------------------------------------------------------------
>
> Key: DROOLS-1006
> URL: https://issues.jboss.org/browse/DROOLS-1006
> Project: Drools
> Issue Type: Task
> Affects Versions: 6.3.0.Final
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
>
> 1) In java, drl and css files, replace in path this Case Sensitive Regular Expression in IntelliJ:
> {code}
> ^/\*\n \* Copyright (\d{4}) JBoss Inc\n
> {code}
> by with this
> {code}
> /*\n * Copyright $1 Red Hat, Inc. and/or its affiliates.\n
> {code}
> To understand the regex, read this:
> https://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html
> Commit that already before starting step 2. I even recommend doing a separate commit per file type. (But wait with pushing until all are fixed.)
> 2) Then look for the string "JBoss Inc" in all files, case insensitive. Fix those too if applicable. Either by another smart regex find-replace or manually.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (DROOLS-1006) License header: replace Jboss Inc by Red Hat, Inc. and/or its affiliates.
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1006?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-1006:
-------------------------------------
Description:
1) In java, drl, js and css files, replace in path this Case Sensitive Regular Expression in IntelliJ:
{code}
^/\*\n \* Copyright (\d{4}) JBoss Inc\n
{code}
by with this
{code}
/*\n * Copyright $1 Red Hat, Inc. and/or its affiliates.\n
{code}
To understand the regex, read this:
https://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html
Commit that already before starting step 2. I even recommend doing a separate commit per file type. (But wait with pushing until all are fixed.)
2) Then look for the string "JBoss Inc" in all files, case insensitive. Fix those too if applicable. Either by another smart regex find-replace or manually.
was:
1) In java, drl and css files, replace in path this Case Sensitive Regular Expression in IntelliJ:
{code}
^/\*\n \* Copyright (\d{4}) JBoss Inc\n
{code}
by with this
{code}
/*\n * Copyright $1 Red Hat, Inc. and/or its affiliates.\n
{code}
To understand the regex, read this:
https://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html
Commit that already before starting step 2. I even recommend doing a separate commit per file type. (But wait with pushing until all are fixed.)
2) Then look for the string "JBoss Inc" in all files, case insensitive. Fix those too if applicable. Either by another smart regex find-replace or manually.
> License header: replace Jboss Inc by Red Hat, Inc. and/or its affiliates.
> -------------------------------------------------------------------------
>
> Key: DROOLS-1006
> URL: https://issues.jboss.org/browse/DROOLS-1006
> Project: Drools
> Issue Type: Task
> Affects Versions: 6.3.0.Final
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
>
> 1) In java, drl, js and css files, replace in path this Case Sensitive Regular Expression in IntelliJ:
> {code}
> ^/\*\n \* Copyright (\d{4}) JBoss Inc\n
> {code}
> by with this
> {code}
> /*\n * Copyright $1 Red Hat, Inc. and/or its affiliates.\n
> {code}
> To understand the regex, read this:
> https://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html
> Commit that already before starting step 2. I even recommend doing a separate commit per file type. (But wait with pushing until all are fixed.)
> 2) Then look for the string "JBoss Inc" in all files, case insensitive. Fix those too if applicable. Either by another smart regex find-replace or manually.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (DROOLS-1006) License header: replace Jboss Inc by Red Hat, Inc. and/or its affiliates.
by Geoffrey De Smet (JIRA)
Geoffrey De Smet created DROOLS-1006:
----------------------------------------
Summary: License header: replace Jboss Inc by Red Hat, Inc. and/or its affiliates.
Key: DROOLS-1006
URL: https://issues.jboss.org/browse/DROOLS-1006
Project: Drools
Issue Type: Task
Affects Versions: 6.3.0.Final
Reporter: Geoffrey De Smet
Assignee: Michael Biarnes Kiefer
1) In java and drl files, replace in path this Case Sensitive Regular Expression in IntelliJ:
{code}
^/\*\n \* Copyright (\d{4}) JBoss Inc\n
{code}
by with this
{code}
/*\n * Copyright $1 Red Hat, Inc. and/or its affiliates.\n
{code}
To understand the regex, read this:
https://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html
Commit that already before starting step 2. I even recommend doing a separate commit per file type. (But wait with pushing until all are fixed.)
2) Then look for the string "JBoss Inc" in all files, case insensitive. Fix those too if applicable. Either by another smart regex find-replace or manually.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (WFCORE-1226) undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1226?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration updated WFCORE-1226:
--------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1280262
Bugzilla Update: Perform
> undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler
> -------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1226
> URL: https://issues.jboss.org/browse/WFCORE-1226
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.4.Final
> Reporter: Chao Wang
> Assignee: Chao Wang
>
> {noformat}
> 1. Start EAP 6.4.4 in domain mode and deploy application using following CLI command:
> ~~
> [domain@localhost:9999 /] deploy /Applications/WebApp-1.war --server-groups=main-server-group --name=WebApp-1.war --runtime-name=WebApp-1.war
> ~~~
> 2. Deploy next version of application in "disabled" state with same "runtime-name"
> ~~~
> [domain@localhost:9999 /] deploy /Applications/WebApp-2.war --disabled --name=WebApp-2.war --runtime-name=WebApp-1.war
> ~~~
> 3. Now use replace-deployment command to access latest version of application:
> ~~~
> [domain@localhost:9999 /] /server-group=main-server-group:replace-deployment(name=WebApp-2.war,to-replace=WebApp-1.war)
> ~~~
> its working fine,laest version of application is accessable.
> 4. Now try to undeploy old version of application
> ~~~
> /server-group=main-server-group/deployment=WebApp-1.war:undeploy()
> ~~~
> After undploying older version, we are not able to access(404) latest version of application(WebApp-2.war) as well.To access it we have to redeploy it.
> Same steps are working fine in Standalone mode.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (WFCORE-1226) undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1226?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on WFCORE-1226:
-------------------------------------------------
Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 1280262|https://bugzilla.redhat.com/show_bug.cgi?id=1280262] from NEW to ASSIGNED
> undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler
> -------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1226
> URL: https://issues.jboss.org/browse/WFCORE-1226
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.4.Final
> Reporter: Chao Wang
> Assignee: Chao Wang
>
> {noformat}
> 1. Start EAP 6.4.4 in domain mode and deploy application using following CLI command:
> ~~
> [domain@localhost:9999 /] deploy /Applications/WebApp-1.war --server-groups=main-server-group --name=WebApp-1.war --runtime-name=WebApp-1.war
> ~~~
> 2. Deploy next version of application in "disabled" state with same "runtime-name"
> ~~~
> [domain@localhost:9999 /] deploy /Applications/WebApp-2.war --disabled --name=WebApp-2.war --runtime-name=WebApp-1.war
> ~~~
> 3. Now use replace-deployment command to access latest version of application:
> ~~~
> [domain@localhost:9999 /] /server-group=main-server-group:replace-deployment(name=WebApp-2.war,to-replace=WebApp-1.war)
> ~~~
> its working fine,laest version of application is accessable.
> 4. Now try to undeploy old version of application
> ~~~
> /server-group=main-server-group/deployment=WebApp-1.war:undeploy()
> ~~~
> After undploying older version, we are not able to access(404) latest version of application(WebApp-2.war) as well.To access it we have to redeploy it.
> Same steps are working fine in Standalone mode.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (WFCORE-1226) undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler
by Chao Wang (JIRA)
Chao Wang created WFCORE-1226:
---------------------------------
Summary: undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler
Key: WFCORE-1226
URL: https://issues.jboss.org/browse/WFCORE-1226
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 2.0.4.Final
Reporter: Chao Wang
Assignee: Chao Wang
{noformat}
1. Start EAP 6.4.4 in domain mode and deploy application using following CLI command:
~~
[domain@localhost:9999 /] deploy /Applications/WebApp-1.war --server-groups=main-server-group --name=WebApp-1.war --runtime-name=WebApp-1.war
~~~
2. Deploy next version of application in "disabled" state with same "runtime-name"
~~~
[domain@localhost:9999 /] deploy /Applications/WebApp-2.war --disabled --name=WebApp-2.war --runtime-name=WebApp-1.war
~~~
3. Now use replace-deployment command to access latest version of application:
~~~
[domain@localhost:9999 /] /server-group=main-server-group:replace-deployment(name=WebApp-2.war,to-replace=WebApp-1.war)
~~~
its working fine,laest version of application is accessable.
4. Now try to undeploy old version of application
~~~
/server-group=main-server-group/deployment=WebApp-1.war:undeploy()
~~~
After undploying older version, we are not able to access(404) latest version of application(WebApp-2.war) as well.To access it we have to redeploy it.
Same steps are working fine in Standalone mode.
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JGRP-1992) GOOGLE_PING discovery fails if port 443 isn't used
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JGRP-1992?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JGRP-1992:
-----------------------------------------------
Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1290158|https://bugzilla.redhat.com/show_bug.cgi?id=1290158] from NEW to MODIFIED
> GOOGLE_PING discovery fails if port 443 isn't used
> --------------------------------------------------
>
> Key: JGRP-1992
> URL: https://issues.jboss.org/browse/JGRP-1992
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.6
> Reporter: Alan Field
> Assignee: Bela Ban
> Fix For: 3.6.7
>
>
> I was doing some testing with GCE, and I ran into the following issue. I have the following in my JGroups configuration file:
> <GOOGLE_PING access_key="access_key"
> secret_access_key="secret_access_key"
> location="jdg-cluster" />
> But I was getting the following exception when starting the JChannel:
> caused by: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
> at sun.security.ssl.InputRecord.handleUnknownRecord(InputRecord.java:710)
> at sun.security.ssl.InputRecord.read(InputRecord.java:527)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
> at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
> at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1513)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
> at org.jgroups.protocols.S3_PING$AWSAuthConnection.checkBucketExists(S3_PING.java:485)
> at org.jgroups.protocols.S3_PING.init(S3_PING.java:98)
> at org.jgroups.protocols.GOOGLE_PING.init(GOOGLE_PING.java:16)
> at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:860)
> at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:481)
> at org.jgroups.JChannel.init(JChannel.java:854)
> at org.jgroups.JChannel.<init>(JChannel.java:159)
> at org.jgroups.JChannel.<init>(JChannel.java:129)
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.buildChannel(JGroupsTransport.java:415)
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.initChannel(JGroupsTransport.java:316)
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.initChannelAndRPCDispatcher(JGroupsTransport.java:360)
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.start(JGroupsTransport.java:198)
> 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:497)
> at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:176)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:870)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:639)
> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:628)
> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:531)
> at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:238)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:583)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:549)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:420)
> at org.radargun.service.InfinispanEmbeddedService.startCaches(InfinispanEmbeddedService.java:119)
> at org.radargun.service.Infinispan51EmbeddedService.startCaches(Infinispan51EmbeddedService.java:100)
> at org.radargun.service.InfinispanLifecycle.start(InfinispanLifecycle.java:45)
> at org.radargun.service.InfinispanKillableLifecycle.start(InfinispanKillableLifecycle.java:51)
> at org.radargun.stages.lifecycle.LifecycleHelper.start(LifecycleHelper.java:59)
> at org.radargun.stages.lifecycle.ServiceStartStage.executeOnSlave(ServiceStartStage.java:83)
> at org.radargun.SlaveBase.scenarioLoop(SlaveBase.java:87)
> at org.radargun.SlaveBase$ScenarioRunner.run(SlaveBase.java:151)
> If I skip the check for the existence of the bucket, I get the same exception when trying to read or write the file. I worked around it by making GOOGLE_PING use the SSL port:
> <GOOGLE_PING access_key="access_key"
> secret_access_key="secret_access_key"
> location="jdg-cluster"
> port="443" />
> I have looked at the docs for migrating from S3 to Google Cloud Storage (https://cloud.google.com/storage/docs/migrating?hl=en), and they don't mention this requirement. I also verified that S3_PING works without any changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (WFCORE-1066) Parametr -Djboss.domain.log.dir does not have effect on HP-UX when directory does not exist
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1066?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet commented on WFCORE-1066:
-------------------------------------------
This is a script issue, since the directory doesn't exist `cd ${p#*=} ; pwd -P` will fail.
Either we can use awk or testing for directory existence before cding
> Parametr -Djboss.domain.log.dir does not have effect on HP-UX when directory does not exist
> -------------------------------------------------------------------------------------------
>
> Key: WFCORE-1066
> URL: https://issues.jboss.org/browse/WFCORE-1066
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 2.0.0.CR7
> Reporter: Ondřej Chaloupka
> Assignee: ehsavoie Hugonnet
> Priority: Minor
>
> If you run container in domain mode with explicitly specified log directory (by parameter {{jboss.domain.log.dir}}) then such settings does not take any effect if directory does not exist before server startup. This issue can be seen only on HP-UX (hpux jdk).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (WFCORE-1066) Parametr -Djboss.domain.log.dir does not have effect on HP-UX when directory does not exist
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1066?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet edited comment on WFCORE-1066 at 12/15/15 1:35 AM:
---------------------------------------------------------------------
This is a script issue, since the directory doesn't exist `cd ${p#*=} ; pwd -P` will fail.
Either we can use awk or testing for directory existence before cding
This should be also the case with standalone
was (Author: ehugonnet):
This is a script issue, since the directory doesn't exist `cd ${p#*=} ; pwd -P` will fail.
Either we can use awk or testing for directory existence before cding
> Parametr -Djboss.domain.log.dir does not have effect on HP-UX when directory does not exist
> -------------------------------------------------------------------------------------------
>
> Key: WFCORE-1066
> URL: https://issues.jboss.org/browse/WFCORE-1066
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 2.0.0.CR7
> Reporter: Ondřej Chaloupka
> Assignee: ehsavoie Hugonnet
> Priority: Minor
>
> If you run container in domain mode with explicitly specified log directory (by parameter {{jboss.domain.log.dir}}) then such settings does not take any effect if directory does not exist before server startup. This issue can be seen only on HP-UX (hpux jdk).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months