[JBoss JIRA] (WFLY-8710) Auto-disable expiration/eviction configuration from distributed web/ejb caches
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-8710?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated WFLY-8710:
-------------------------------
Summary: Auto-disable expiration/eviction configuration from distributed web/ejb caches (was: Auto-remove expiration/eviction configuration from distributed web/ejb caches)
> Auto-disable expiration/eviction configuration from distributed web/ejb caches
> ------------------------------------------------------------------------------
>
> Key: WFLY-8710
> URL: https://issues.jboss.org/browse/WFLY-8710
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
>
> Setting expiration for cache-container ejb, does not trigger the @PreDestroy method.
> Request to remove the expiration configuration for internal ISPN we should have at least a WARN message that expiration for SFSB is not working.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8710) Auto-remove expiration/eviction configuration from distributed web/ejb caches
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-8710?page=com.atlassian.jira.plugin.... ]
Paul Ferraro moved JBEAP-10773 to WFLY-8710:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8710 (was: JBEAP-10773)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Clustering
(was: Clustering)
(was: EJB)
(was: JMS)
(was: Migration)
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.DR17)
> Auto-remove expiration/eviction configuration from distributed web/ejb caches
> -----------------------------------------------------------------------------
>
> Key: WFLY-8710
> URL: https://issues.jboss.org/browse/WFLY-8710
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
>
> Setting expiration for cache-container ejb, does not trigger the @PreDestroy method.
> Request to remove the expiration configuration for internal ISPN we should have at least a WARN message that expiration for SFSB is not working.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-6194) Tests fail with "java.util.PropertyPermission" with security manager enabled
by Ivo Studensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-6194?page=com.atlassian.jira.plugin.... ]
Ivo Studensky reopened WFLY-6194:
---------------------------------
Re-opened for another new issue.
> Tests fail with "java.util.PropertyPermission" with security manager enabled
> ----------------------------------------------------------------------------
>
> Key: WFLY-6194
> URL: https://issues.jboss.org/browse/WFLY-6194
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Hynek Švábek
> Assignee: Ivo Studensky
> Fix For: 11.0.0.Beta1
>
>
> *org.jboss.as.test.integration.ee.injection.support.websocket.WebSocketInjectionSupportTestCase#testWebSocketInjectionAndInterception*
> *org.jboss.as.test.integration.ee.suspend.EEConcurrencySuspendTestCase#testRequestInShutdown*
> {{./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.ee.injection.support.websocket.WebSocketInjectionSupportTestCase#testWebSocketInjectionAndInterception}}
> {{./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=org.jboss.as.test.integration.ee.suspend.EEConcurrencySuspendTestCase#testRequestInShutdown}}
> Fail with:
> {code}
> java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.util.PropertyPermission" "management.address" "read")" in code source "(vfs:/content/ee-suspend.war/WEB-INF/classes <no signer certificates>)" of "null")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:273)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPropertyAccess(WildFlySecurityManager.java:496)
> at java.lang.System.getProperty(System.java:717)
> at org.jboss.as.test.shared.TestSuiteEnvironment.getServerAddress(TestSuiteEnvironment.java:77)
> at org.jboss.as.test.integration.ee.suspend.EEConcurrencySuspendTestCase.testRequestInShutdown(EEConcurrencySuspendTestCase.java:77)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JGRP-2169) PDC.java can NPE when calling deleteFile
by Elias Ross (JIRA)
[ https://issues.jboss.org/browse/JGRP-2169?page=com.atlassian.jira.plugin.... ]
Elias Ross updated JGRP-2169:
-----------------------------
Description:
As seen in my logs:
{noformat}
[thread=jgroups-4,pv36d01ls-geo02042101-26405] [level=ERROR] [logger=unknown.jul.logger] - JGRP000027: failed passing message up
java.lang.NullPointerException: null
at org.jgroups.protocols.PDC.deleteFile(PDC.java:271) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
at org.jgroups.protocols.PDC.writeNodeToDisk(PDC.java:208) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
at org.jgroups.protocols.PDC.down(PDC.java:89) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
{noformat}
It seems that there are code paths where deleteFile can be called with a null parameter. For example:
{code:java}
protected File writeToTempFile(File dir, Address logical_addr, Address physical_addr, String logical_name) throws Exception {
DataOutputStream out=null;
File file=null;
String filename=null;
try {
file=File.createTempFile("temp", null, dir);
^^ If this fails, then file is null and delete is called with null
filename=file.getName();
...
}
catch(Exception e) {
Util.close(out);
log.error(Util.getMessage("FailedToWriteTemporaryFile") + filename, e);
deleteFile(file);
return null;
}
{code}
was:
As seen in my logs:
[thread=jgroups-4,pv36d01ls-geo02042101-26405] [level=ERROR] [logger=unknown.jul.logger] - JGRP000027: failed passing message up
java.lang.NullPointerException: null
at org.jgroups.protocols.PDC.deleteFile(PDC.java:271) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
at org.jgroups.protocols.PDC.writeNodeToDisk(PDC.java:208) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
at org.jgroups.protocols.PDC.down(PDC.java:89) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
It seems that there are code paths where deleteFile can be called with a null parameter. For example:
protected File writeToTempFile(File dir, Address logical_addr, Address physical_addr, String logical_name) throws Exception {
DataOutputStream out=null;
File file=null;
String filename=null;
try {
file=File.createTempFile("temp", null, dir);
^^ If this fails, then file is null and delete is called with null
filename=file.getName();
...
}
catch(Exception e) {
Util.close(out);
log.error(Util.getMessage("FailedToWriteTemporaryFile") + filename, e);
deleteFile(file);
return null;
}
> PDC.java can NPE when calling deleteFile
> ----------------------------------------
>
> Key: JGRP-2169
> URL: https://issues.jboss.org/browse/JGRP-2169
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.1
> Reporter: Elias Ross
> Assignee: Bela Ban
>
> As seen in my logs:
> {noformat}
> [thread=jgroups-4,pv36d01ls-geo02042101-26405] [level=ERROR] [logger=unknown.jul.logger] - JGRP000027: failed passing message up
> java.lang.NullPointerException: null
> at org.jgroups.protocols.PDC.deleteFile(PDC.java:271) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
> at org.jgroups.protocols.PDC.writeNodeToDisk(PDC.java:208) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
> at org.jgroups.protocols.PDC.down(PDC.java:89) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
> {noformat}
> It seems that there are code paths where deleteFile can be called with a null parameter. For example:
> {code:java}
> protected File writeToTempFile(File dir, Address logical_addr, Address physical_addr, String logical_name) throws Exception {
> DataOutputStream out=null;
> File file=null;
> String filename=null;
> try {
> file=File.createTempFile("temp", null, dir);
> ^^ If this fails, then file is null and delete is called with null
> filename=file.getName();
> ...
> }
> catch(Exception e) {
> Util.close(out);
> log.error(Util.getMessage("FailedToWriteTemporaryFile") + filename, e);
> deleteFile(file);
> return null;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JGRP-2169) PDC.java can NPE when calling deleteFile
by Elias Ross (JIRA)
[ https://issues.jboss.org/browse/JGRP-2169?page=com.atlassian.jira.plugin.... ]
Elias Ross updated JGRP-2169:
-----------------------------
Description:
[thread=jgroups-4,pv36d01ls-geo02042101-26405] [level=ERROR] [logger=unknown.jul.logger] - JGRP000027: failed passing message up
java.lang.NullPointerException: null
at org.jgroups.protocols.PDC.deleteFile(PDC.java:271) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
at org.jgroups.protocols.PDC.writeNodeToDisk(PDC.java:208) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
at org.jgroups.protocols.PDC.down(PDC.java:89) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
It seems that there are code paths where deleteFile can be called with a null parameter. For example:
{{
protected File writeToTempFile(File dir, Address logical_addr, Address physical_addr, String logical_name) throws Exception {
DataOutputStream out=null;
File file=null;
String filename=null;
try {
file=File.createTempFile("temp", null, dir);
^^ If this fails, then file is null and delete is called with null
filename=file.getName();
...
}
catch(Exception e) {
Util.close(out);
log.error(Util.getMessage("FailedToWriteTemporaryFile") + filename, e);
deleteFile(file);
return null;
}
}}
was:
[thread=jgroups-4,pv36d01ls-geo02042101-26405] [level=ERROR] [logger=unknown.jul.logger] - JGRP000027: failed passing message up
java.lang.NullPointerException: null
at org.jgroups.protocols.PDC.deleteFile(PDC.java:271) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
at org.jgroups.protocols.PDC.writeNodeToDisk(PDC.java:208) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
at org.jgroups.protocols.PDC.down(PDC.java:89) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
It seems that there are code paths where deleteFile can be called with a null parameter. For example:
{{ protected File writeToTempFile(File dir, Address logical_addr, Address physical_addr, String logical_name) throws Exception {
DataOutputStream out=null;
File file=null;
String filename=null;
try {
file=File.createTempFile("temp", null, dir);
^^ If this fails, then file is null and delete is called with null
filename=file.getName();
...
}
catch(Exception e) {
Util.close(out);
log.error(Util.getMessage("FailedToWriteTemporaryFile") + filename, e);
deleteFile(file);
return null;
}
}}
> PDC.java can NPE when calling deleteFile
> ----------------------------------------
>
> Key: JGRP-2169
> URL: https://issues.jboss.org/browse/JGRP-2169
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.1
> Reporter: Elias Ross
> Assignee: Bela Ban
>
> [thread=jgroups-4,pv36d01ls-geo02042101-26405] [level=ERROR] [logger=unknown.jul.logger] - JGRP000027: failed passing message up
> java.lang.NullPointerException: null
> at org.jgroups.protocols.PDC.deleteFile(PDC.java:271) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
> at org.jgroups.protocols.PDC.writeNodeToDisk(PDC.java:208) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
> at org.jgroups.protocols.PDC.down(PDC.java:89) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
> It seems that there are code paths where deleteFile can be called with a null parameter. For example:
> {{
> protected File writeToTempFile(File dir, Address logical_addr, Address physical_addr, String logical_name) throws Exception {
> DataOutputStream out=null;
> File file=null;
> String filename=null;
> try {
> file=File.createTempFile("temp", null, dir);
> ^^ If this fails, then file is null and delete is called with null
> filename=file.getName();
> ...
> }
> catch(Exception e) {
> Util.close(out);
> log.error(Util.getMessage("FailedToWriteTemporaryFile") + filename, e);
> deleteFile(file);
> return null;
> }
> }}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JGRP-2169) PDC.java can NPE when calling deleteFile
by Elias Ross (JIRA)
[ https://issues.jboss.org/browse/JGRP-2169?page=com.atlassian.jira.plugin.... ]
Elias Ross updated JGRP-2169:
-----------------------------
Description:
As seen in my logs:
[thread=jgroups-4,pv36d01ls-geo02042101-26405] [level=ERROR] [logger=unknown.jul.logger] - JGRP000027: failed passing message up
java.lang.NullPointerException: null
at org.jgroups.protocols.PDC.deleteFile(PDC.java:271) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
at org.jgroups.protocols.PDC.writeNodeToDisk(PDC.java:208) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
at org.jgroups.protocols.PDC.down(PDC.java:89) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
It seems that there are code paths where deleteFile can be called with a null parameter. For example:
protected File writeToTempFile(File dir, Address logical_addr, Address physical_addr, String logical_name) throws Exception {
DataOutputStream out=null;
File file=null;
String filename=null;
try {
file=File.createTempFile("temp", null, dir);
^^ If this fails, then file is null and delete is called with null
filename=file.getName();
...
}
catch(Exception e) {
Util.close(out);
log.error(Util.getMessage("FailedToWriteTemporaryFile") + filename, e);
deleteFile(file);
return null;
}
was:
[thread=jgroups-4,pv36d01ls-geo02042101-26405] [level=ERROR] [logger=unknown.jul.logger] - JGRP000027: failed passing message up
java.lang.NullPointerException: null
at org.jgroups.protocols.PDC.deleteFile(PDC.java:271) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
at org.jgroups.protocols.PDC.writeNodeToDisk(PDC.java:208) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
at org.jgroups.protocols.PDC.down(PDC.java:89) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
It seems that there are code paths where deleteFile can be called with a null parameter. For example:
{{
protected File writeToTempFile(File dir, Address logical_addr, Address physical_addr, String logical_name) throws Exception {
DataOutputStream out=null;
File file=null;
String filename=null;
try {
file=File.createTempFile("temp", null, dir);
^^ If this fails, then file is null and delete is called with null
filename=file.getName();
...
}
catch(Exception e) {
Util.close(out);
log.error(Util.getMessage("FailedToWriteTemporaryFile") + filename, e);
deleteFile(file);
return null;
}
}}
> PDC.java can NPE when calling deleteFile
> ----------------------------------------
>
> Key: JGRP-2169
> URL: https://issues.jboss.org/browse/JGRP-2169
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.1
> Reporter: Elias Ross
> Assignee: Bela Ban
>
> As seen in my logs:
> [thread=jgroups-4,pv36d01ls-geo02042101-26405] [level=ERROR] [logger=unknown.jul.logger] - JGRP000027: failed passing message up
> java.lang.NullPointerException: null
> at org.jgroups.protocols.PDC.deleteFile(PDC.java:271) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
> at org.jgroups.protocols.PDC.writeNodeToDisk(PDC.java:208) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
> at org.jgroups.protocols.PDC.down(PDC.java:89) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
> It seems that there are code paths where deleteFile can be called with a null parameter. For example:
> protected File writeToTempFile(File dir, Address logical_addr, Address physical_addr, String logical_name) throws Exception {
> DataOutputStream out=null;
> File file=null;
> String filename=null;
> try {
> file=File.createTempFile("temp", null, dir);
> ^^ If this fails, then file is null and delete is called with null
> filename=file.getName();
> ...
> }
> catch(Exception e) {
> Util.close(out);
> log.error(Util.getMessage("FailedToWriteTemporaryFile") + filename, e);
> deleteFile(file);
> return null;
> }
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JGRP-2169) PDC.java can NPE when calling deleteFile
by Elias Ross (JIRA)
Elias Ross created JGRP-2169:
--------------------------------
Summary: PDC.java can NPE when calling deleteFile
Key: JGRP-2169
URL: https://issues.jboss.org/browse/JGRP-2169
Project: JGroups
Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Elias Ross
Assignee: Bela Ban
[thread=jgroups-4,pv36d01ls-geo02042101-26405] [level=ERROR] [logger=unknown.jul.logger] - JGRP000027: failed passing message up
java.lang.NullPointerException: null
at org.jgroups.protocols.PDC.deleteFile(PDC.java:271) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
at org.jgroups.protocols.PDC.writeNodeToDisk(PDC.java:208) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
at org.jgroups.protocols.PDC.down(PDC.java:89) ~[org.jgroups-jgroups-4.0.1.Final.jar:4.0.1.Final]
It seems that there are code paths where deleteFile can be called with a null parameter. For example:
{{ protected File writeToTempFile(File dir, Address logical_addr, Address physical_addr, String logical_name) throws Exception {
DataOutputStream out=null;
File file=null;
String filename=null;
try {
file=File.createTempFile("temp", null, dir);
^^ If this fails, then file is null and delete is called with null
filename=file.getName();
...
}
catch(Exception e) {
Util.close(out);
log.error(Util.getMessage("FailedToWriteTemporaryFile") + filename, e);
deleteFile(file);
return null;
}
}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months