February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6196) Tests fails in manualmode with security manager

by Fedor Gavrilov (JIRA)

[ https://issues.jboss.org/browse/WFLY-6196?page=com.atlassian.jira.plugin.... ] Fedor Gavrilov reassigned WFLY-6196: ------------------------------------ Assignee: Fedor Gavrilov > Tests fails in manualmode with security manager > ----------------------------------------------- > > Key: WFLY-6196 > URL: https://issues.jboss.org/browse/WFLY-6196 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Hynek Švábek > Assignee: Fedor Gavrilov > > *org.jboss.as.test.manualmode.weld.extension.BeforeShutdownJNDILookupTestCase#org.jboss.as.test.manualmode.weld.extension.BeforeShutdownJNDILookupTestCase* > *org.jboss.as.test.manualmode.weld.extension.BeforeShutdownJNDILookupTestCase#testTransactionJNDILookupDuringShutdownEvent* > {{./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.manualmode -Dts.noSmoke -Dtest=org.jboss.as.test.manualmode.weld.extension.BeforeShutdownJNDILookupTestCase > }} > Fail with: > {code} > ERROR [org.jboss.weld.Bootstrap] (MSC service thread 1-6) : java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "target" "read")" in code source "(vfs:/content/test.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.checkPermission(WildFlySecurityManager.java:175) > at java.lang.SecurityManager.checkRead(SecurityManager.java:888) > at org.wildfly.security.manager.WildFlySecurityManager.checkRead(WildFlySecurityManager.java:377) > at java.io.File.exists(File.java:814) > at org.jboss.as.test.manualmode.weld.extension.BeforeShutdownExtension.writeOutput(BeforeShutdownExtension.java:62) > at org.jboss.as.test.manualmode.weld.extension.BeforeShutdownExtension.lookupBeforeShutdown(BeforeShutdownExtension.java:37) > 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.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:88) > at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:78) > at org.jboss.weld.injection.MethodInvocationStrategy$SimpleMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:129) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:309) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:124) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:287) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:265) > at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:271) > at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:260) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:154) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:148) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:53) > at org.jboss.weld.bootstrap.events.BeforeShutdownImpl.fire(BeforeShutdownImpl.java:41) > at org.jboss.weld.bootstrap.events.BeforeShutdownImpl.fire(BeforeShutdownImpl.java:32) > at org.jboss.weld.bootstrap.WeldRuntime.shutdown(WeldRuntime.java:72) > at org.jboss.weld.bootstrap.WeldBootstrap.shutdown(WeldBootstrap.java:113) > at org.jboss.as.weld.WeldStartService.stop(WeldStartService.java:128) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > 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:745) > {code} > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1073) Option to bypass start task operation in REST/JMS

by Ivo Bek (JIRA)

Ivo Bek created DROOLS-1073: ------------------------------- Summary: Option to bypass start task operation in REST/JMS Key: DROOLS-1073 URL: https://issues.jboss.org/browse/DROOLS-1073 Project: Drools Issue Type: Enhancement Components: kie server Affects Versions: 6.3.0.Final Reporter: Ivo Bek Assignee: Ivo Bek Today, it takes 2 requests to complete a task. In web development every request costs some time and in many scenarios it's enough to start and complete a task in one request without any delay. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6280) Can not call "visibility" bridged methods

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-6280?page=com.atlassian.jira.plugin.... ] Farah Juma updated WFLY-6280: ----------------------------- Component/s: (was: JSF) > Can not call "visibility" bridged methods > ----------------------------------------- > > Key: WFLY-6280 > URL: https://issues.jboss.org/browse/WFLY-6280 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.2.Final, 10.0.0.Final > Reporter: Trond G. Ziarkowski > Assignee: Farah Juma > Labels: el > > After fix of WFLY-3456 all bridged methods are filtered which causes javax.el.MethodNotFoundException for "visibility" bridged methods. > This has been commented by [~bodist] in WFLY-3456, but nothing has been done to fix it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6280) Can not call "visibility" bridged methods

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-6280?page=com.atlassian.jira.plugin.... ] Farah Juma reassigned WFLY-6280: -------------------------------- Assignee: Tomaz Cerar (was: Farah Juma) > Can not call "visibility" bridged methods > ----------------------------------------- > > Key: WFLY-6280 > URL: https://issues.jboss.org/browse/WFLY-6280 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.2.Final, 10.0.0.Final > Reporter: Trond G. Ziarkowski > Assignee: Tomaz Cerar > Labels: el > > After fix of WFLY-3456 all bridged methods are filtered which causes javax.el.MethodNotFoundException for "visibility" bridged methods. > This has been commented by [~bodist] in WFLY-3456, but nothing has been done to fix it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6280) Can not call "visibility" bridged methods

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-6280?page=com.atlassian.jira.plugin.... ] Farah Juma updated WFLY-6280: ----------------------------- Labels: el (was: ) > Can not call "visibility" bridged methods > ----------------------------------------- > > Key: WFLY-6280 > URL: https://issues.jboss.org/browse/WFLY-6280 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 9.0.2.Final, 10.0.0.Final > Reporter: Trond G. Ziarkowski > Assignee: Farah Juma > Labels: el > > After fix of WFLY-3456 all bridged methods are filtered which causes javax.el.MethodNotFoundException for "visibility" bridged methods. > This has been commented by [~bodist] in WFLY-3456, but nothing has been done to fix it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1970) Make mod_cluster status interval configurable

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1970?page=com.atlassian.jira.plugin.... ] Radoslav Husar closed WFLY-1970. -------------------------------- > Make mod_cluster status interval configurable > --------------------------------------------- > > Key: WFLY-1970 > URL: https://issues.jboss.org/browse/WFLY-1970 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 8.0.0.Final, 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.Alpha1 > > > There is a TODO in UndertowEventHandlerAdapter.start(StartContext) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3575) Parameterize subsystem version in xsite/jgroups testsuite xslt stylesheet

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3575?page=com.atlassian.jira.plugin.... ] Radoslav Husar closed WFLY-3575. -------------------------------- > Parameterize subsystem version in xsite/jgroups testsuite xslt stylesheet > ------------------------------------------------------------------------- > > Key: WFLY-3575 > URL: https://issues.jboss.org/browse/WFLY-3575 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 8.1.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Fix For: 9.0.0.Alpha1 > > > I wasted a good couple of hours today trying to figure out why my changes broke the xsite tests. It turns out that the xslt scripts have the subsystem schema version hardcoded, and I had created a new schema version. > We should parameterize this, in the same way as the addCacheContainer.xsl stylesheet does. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6257) Allow Narayanas list of XAOrphanFilters to include a check of the transaction status manager

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-6257?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-6257: -------------------------------- Fix Version/s: 11.0.0.Alpha1 (was: 10.1.0.Final) > Allow Narayanas list of XAOrphanFilters to include a check of the transaction status manager > -------------------------------------------------------------------------------------------- > > Key: WFLY-6257 > URL: https://issues.jboss.org/browse/WFLY-6257 > Project: WildFly > Issue Type: Enhancement > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 11.0.0.Alpha1 > > > Narayana has added a check of the transaction status manager to check the status of the transaction with a transaction manager. This needs to be exposed in WildFly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6257) Allow Narayanas list of XAOrphanFilters to include a check of the transaction status manager

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-6257?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-6257: -------------------------------- Fix Version/s: 10.1.0.Final > Allow Narayanas list of XAOrphanFilters to include a check of the transaction status manager > -------------------------------------------------------------------------------------------- > > Key: WFLY-6257 > URL: https://issues.jboss.org/browse/WFLY-6257 > Project: WildFly > Issue Type: Enhancement > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 10.1.0.Final > > > Narayana has added a check of the transaction status manager to check the status of the transaction with a transaction manager. This needs to be exposed in WildFly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5857) HASingleton Stop is called in Node1 (Master) during down of Node2 in cluster, but start is not called in Node1 again after Node1 is selected Master again

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5857?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-5857: ------------------------------------ Please see the documentation for this feature here: https://docs.jboss.org/author/display/WFLY10/HA+Singleton+Features > HASingleton Stop is called in Node1 (Master) during down of Node2 in cluster, but start is not called in Node1 again after Node1 is selected Master again > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5857 > URL: https://issues.jboss.org/browse/WFLY-5857 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 9.0.1.Final > Environment: Wildfly-9.0.1.Final. Full HA Configuration. Cluster Full Ha > Reporter: Serg Jakean19019 > Assignee: Paul Ferraro > > HASingleton Stop is called in Node1 (Master) during down of Node2 in cluster, but Start is not called in Node1 again after Node1 is selected Master again. > If Node2 ist started again, than Start is called in Node1 again. > This Solution worked in 8.2.0.Final and was taken from GitHub > Part of Log after Stop in Singletone: > 2015-12-16 10:25:39,832 WARN [org.wildfly.clustering.server] (remote-thread--p8-t5) WFLYCLSV0007: Just reached required quorum of 1 for jboss.quickstart.ha.singleton.default service. If this cluster loses another member, no node will be chosen to provide this service. > 2015-12-16 10:25:39,832 INFO [org.wildfly.clustering.server] (remote-thread--p8-t5) WFLYCLSV0003: DevNode1 elected as the singleton provider of the jboss.quickstart.ha.singleton.default service > 2015-12-16 10:25:40,410 WARN [org.hornetq.core.client] (Thread-514 (HornetQ-client-global-threads-816000930)) HQ212037: Connection failure has been detected: HQ119015: The connection was disconnected because of server shutdown [code=DISCONNECTED] > 2015-12-16 10:25:40,424 WARN [org.hornetq.core.client] (Thread-515 (HornetQ-client-global-threads-816000930)) HQ212037: Connection failure has been detected: HQ119015: The connection was disconnected because of server shutdown [code=DISCONNECTED] > 2015-12-16 10:25:40,442 INFO [org.hornetq.core.server] (Thread-16 (HornetQ-server-HornetQServerImpl::serverUUID=5f62a17c-a33d-11e5-b968-cda4b2119720-1601129088)) HQ221029: stopped bridge sf.my-cluster.b27b8fc6-a33e-11e5-84b8-b7bbc6dfe24c > 2015-12-16 10:25:40,495 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-5,ee,DevNode1) ISPN000094: Received new cluster view for channel server: [Node1|2] (1) [DevNode1] > 2015-12-16 10:25:40,496 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-5,ee,DevNode1) ISPN000094: Received new cluster view for channel ejb: [Node1|2] (1) [DevNode1] > 2015-12-16 10:25:40,497 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-5,ee,DevNode1) ISPN000094: Received new cluster view for channel hibernate: [DevNode1|2] (1) [DevNode1] > 2015-12-16 10:25:57,010 WARNING [org.jgroups.protocols.UDP] (INT-1,hq-cluster,DevNode1) JGRP000012: discarded message from different cluster ee (our cluster is hq-cluster). Sender was DevNode1 (received 38 identical messages from DevNode1 in the last 63946 ms) > 2015-12-16 10:26:30,810 WARNING [org.jgroups.protocols.UDP] (Incoming-13,ee,DevNode1) JGRP000012: discarded message from different cluster hq-cluster (our cluster is ee). Sender was DevNode1 (received 80 identical messages from DevNode1 in the last 60008 ms) > This issue also in: > https://developer.jboss.org/thread/266831 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2016