August 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1706) Deploying with force an unmanaged deployment makes it managed

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1706?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet reassigned WFCORE-1706: ----------------------------------------- Assignee: ehsavoie Hugonnet (was: Alexey Loubyansky) > Deploying with force an unmanaged deployment makes it managed > ------------------------------------------------------------- > > Key: WFCORE-1706 > URL: https://issues.jboss.org/browse/WFCORE-1706 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Alpha4 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > For an unmanaged deployment if you replace it using the CLI deploy command it becomes managed. > To reproduce: > {code:java} > deploy /home/ehsavoie/dev/wildfly/quickstart/kitchensink-ear/ear/target/wildfly-kitchensink-ear.ear --unmanaged > deploy /home/ehsavoie/dev/wildfly/quickstart/kitchensink-ear/ear/target/wildfly-kitchensink-ear.ear --unmanaged --force > {code} > After the second command the deployment is managed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6926) TimeoutException: Replication timeout when handling request with DIST cache

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-6926?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-6926: ------------------------------- Fix Version/s: 10.1.0.Final > TimeoutException: Replication timeout when handling request with DIST cache > --------------------------------------------------------------------------- > > Key: WFLY-6926 > URL: https://issues.jboss.org/browse/WFLY-6926 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.CR1 > Reporter: Michal Vinkler > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 10.1.0.Final > > > Seen in http-session scenarios with *DIST* cache only. REPL cache scenarios seem not to be affected. > TimeoutExceptions occur right away after sending first request and definitely result in client getting 500: > {code} > [JBossINF] [0m[31m04:31:39,033 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (default task-1) ISPN000136: Error executing command GetKeyValueCommand, writing keys []: org.infinispan.util.concurrent.TimeoutException: Replication timeout for perf19 > [JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:801) > [JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$1(JGroupsTransport.java:642) > [JBossINF] at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602) > [JBossINF] at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577) > [JBossINF] at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) > [JBossINF] at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962) > [JBossINF] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.staggeredProcessNext(CommandAwareRpcDispatcher.java:375) > [JBossINF] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.lambda$processCallsStaggered$3(CommandAwareRpcDispatcher.java:357) > [JBossINF] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:266) > [JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > [JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > [JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [JBossINF] at java.lang.Thread.run(Thread.java:745) > {code} > Client: > {code} > 2016/08/08 04:31:39:068 EDT [WARN ][Runner - 4] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: Internal Server Error> > org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: Internal Server Error > at org.jboss.smartfrog.loaddriver.http.HttpRequestProcessorFactoryImpl$HttpRequestProcessor.processRequest(HttpRequestProcessorFactoryImpl.java:163) > at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52) > at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103) > at java.lang.Thread.run(Thread.java:745) > {code} > I was able to reproduce it even with a very small load of 30 sessions. > Server link (run with 30 sessions): > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mvinkler_eap-7x-failo... > Client link (run with 30 sessions): > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mvinkler_eap-7x-failo... > This issue occurs under different conditions than JBEAP-3779 (which is similar), that's why I opened new issue. > Number of occurrences of TimeoutExceptions is very high. The server logs are full of them. > This issue makes clustering with *DIST* cache unusable, thus giving blocker priority. > Also, there is a issue with shutting down the servers in the end of the test, I don't know if it can be related, but I am hitting it constantly in the http-session DIST scenarios. > The server shutdown usually gets stuck on this command: > {code} > [JBossINF] [0m[0m04:38:51,694 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000082: Stopping the RpcDispatcher for channel web > {code} > *EDIT:* > Also ejb-remote tests with *DIST* cache are affected (even if only 20 sessions are created). > Server log for ejb-remote run: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mvinkler_eap-7x-failo... > Client log for ejb-remote run: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mvinkler_eap-7x-failo... > *EDIT #2:* > Can be very easily reproduced locally. Just start a cluster of at least 3 servers with clusterbench deployed. Then do few requests to various nodes until you get 500 as a response. Also notice, when shutting down a node, which logged TimeoutException before, the node won't stop and get stuck during the shutdown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1705) A system dependency sun/security/provider/certpath is missing from wildfly's module.xml

by Peter Nalyvayko (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1705?page=com.atlassian.jira.plugi... ] Peter Nalyvayko updated WFCORE-1705: ------------------------------------ Description: There is a system dependency path "sun/security/provider/certpath" missing from modules\system\layers\base\sun\jdk\main\module.xml. This is causing class def not found exception when attempting to create an instance of a class from that namespace. The module contents (abbreviated) are shown below. Notice that the path to "sun/security/provider/certpath" is not listed in there: {{<module xmlns="urn:jboss:module:1.3" name="sun.jdk"> <resources>  <resource-root path="service-loader-resources"/> </resources> <dependencies> <module name="sun.scripting" export="true"/> <system export="true"> <paths> ... <path name="sun/security/action"/> <path name="sun/security/pkcs"/> <path name="sun/security/x509"/> <path name="sun/security"/> <path name="sun/security/util"/> <path name="sun/security/krb5"/> <path name="sun/security/krb5/internal"/> <path name="sun/security/pkcs11"/> <path name="sun/security/provider"/> ... </paths> <exports> <include-set> <path name="META-INF/services"/> </include-set> </exports> </system> </dependencies> </module> }}Manually adding the missing system dependency path fixes the issue. was: There is a system dependency path "sun/security/provider/certpath" missing from modules\system\layers\base\sun\jdk\main\module.xml. This is causing class def not found exception when attempting to create an instance of a class from that namespace. The module contents (abbreviated) are shown below. Notice that the path to "sun/security/provider/certpath" is not listed in there: <module xmlns="urn:jboss:module:1.3" name="sun.jdk"> <resources>  <resource-root path="service-loader-resources"/> </resources> <dependencies> <module name="sun.scripting" export="true"/> <system export="true"> <paths> ... <path name="sun/security/action"/> <path name="sun/security/pkcs"/> <path name="sun/security/x509"/> <path name="sun/security"/> <path name="sun/security/util"/> <path name="sun/security/krb5"/> <path name="sun/security/krb5/internal"/> <path name="sun/security/pkcs11"/> <path name="sun/security/provider"/> ... </paths> <exports> <include-set> <path name="META-INF/services"/> </include-set> </exports> </system> </dependencies> </module> Manually adding the missing system dependency path fixes the issue. > A system dependency sun/security/provider/certpath is missing from wildfly's module.xml > --------------------------------------------------------------------------------------- > > Key: WFCORE-1705 > URL: https://issues.jboss.org/browse/WFCORE-1705 > Project: WildFly Core > Issue Type: Feature Request > Components: Modules > Affects Versions: 2.2.0.Final > Reporter: Peter Nalyvayko > Assignee: David Lloyd > > There is a system dependency path "sun/security/provider/certpath" missing from modules\system\layers\base\sun\jdk\main\module.xml. This is causing class def not found exception when attempting to create an instance of a class from that namespace. The module contents (abbreviated) are shown below. Notice that the path to "sun/security/provider/certpath" is not listed in there: > {{<module xmlns="urn:jboss:module:1.3" name="sun.jdk"> > <resources> >  > <resource-root path="service-loader-resources"/> > </resources> > <dependencies> > <module name="sun.scripting" export="true"/> > <system export="true"> > <paths> > ... > <path name="sun/security/action"/> > <path name="sun/security/pkcs"/> > <path name="sun/security/x509"/> > <path name="sun/security"/> > <path name="sun/security/util"/> > <path name="sun/security/krb5"/> > <path name="sun/security/krb5/internal"/> > <path name="sun/security/pkcs11"/> > <path name="sun/security/provider"/> > ... > </paths> > <exports> > <include-set> > <path name="META-INF/services"/> > </include-set> > </exports> > </system> > </dependencies> > </module> > }}Manually adding the missing system dependency path fixes the issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1705) A system dependency sun/security/provider/certpath is missing from wildfly's module.xlm

by Peter Nalyvayko (JIRA)

Peter Nalyvayko created WFCORE-1705: --------------------------------------- Summary: A system dependency sun/security/provider/certpath is missing from wildfly's module.xlm Key: WFCORE-1705 URL: https://issues.jboss.org/browse/WFCORE-1705 Project: WildFly Core Issue Type: Feature Request Components: Modules Affects Versions: 2.2.0.Final Reporter: Peter Nalyvayko Assignee: David Lloyd There is a system dependency path "sun/security/provider/certpath" missing from modules\system\layers\base\sun\jdk\main\module.xml. This is causing class def not found exception when attempting to create an instance of a class from that namespace. The module contents (abbreviated) are shown below. Notice that the path to "sun/security/provider/certpath" is not listed in there: <module xmlns="urn:jboss:module:1.3" name="sun.jdk"> <resources>  <resource-root path="service-loader-resources"/> </resources> <dependencies> <module name="sun.scripting" export="true"/> <system export="true"> <paths> ... <path name="sun/security/action"/> <path name="sun/security/pkcs"/> <path name="sun/security/x509"/> <path name="sun/security"/> <path name="sun/security/util"/> <path name="sun/security/krb5"/> <path name="sun/security/krb5/internal"/> <path name="sun/security/pkcs11"/> <path name="sun/security/provider"/> ... </paths> <exports> <include-set> <path name="META-INF/services"/> </include-set> </exports> </system> </dependencies> </module> Manually adding the missing system dependency path fixes the issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1705) A system dependency sun/security/provider/certpath is missing from wildfly's module.xml

by Peter Nalyvayko (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1705?page=com.atlassian.jira.plugi... ] Peter Nalyvayko updated WFCORE-1705: ------------------------------------ Summary: A system dependency sun/security/provider/certpath is missing from wildfly's module.xml (was: A system dependency sun/security/provider/certpath is missing from wildfly's module.xlm) > A system dependency sun/security/provider/certpath is missing from wildfly's module.xml > --------------------------------------------------------------------------------------- > > Key: WFCORE-1705 > URL: https://issues.jboss.org/browse/WFCORE-1705 > Project: WildFly Core > Issue Type: Feature Request > Components: Modules > Affects Versions: 2.2.0.Final > Reporter: Peter Nalyvayko > Assignee: David Lloyd > > There is a system dependency path "sun/security/provider/certpath" missing from modules\system\layers\base\sun\jdk\main\module.xml. This is causing class def not found exception when attempting to create an instance of a class from that namespace. The module contents (abbreviated) are shown below. Notice that the path to "sun/security/provider/certpath" is not listed in there: > <module xmlns="urn:jboss:module:1.3" name="sun.jdk"> > <resources> >  > <resource-root path="service-loader-resources"/> > </resources> > <dependencies> > <module name="sun.scripting" export="true"/> > <system export="true"> > <paths> > ... > <path name="sun/security/action"/> > <path name="sun/security/pkcs"/> > <path name="sun/security/x509"/> > <path name="sun/security"/> > <path name="sun/security/util"/> > <path name="sun/security/krb5"/> > <path name="sun/security/krb5/internal"/> > <path name="sun/security/pkcs11"/> > <path name="sun/security/provider"/> > ... > </paths> > <exports> > <include-set> > <path name="META-INF/services"/> > </include-set> > </exports> > </system> > </dependencies> > </module> > Manually adding the missing system dependency path fixes the issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6906) Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated."

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-6906?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-6906: ------------------------------------ Effectively, our NONE mode becomes a synonym for MANUAL. > Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated." > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-6906 > URL: https://issues.jboss.org/browse/WFLY-6906 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Paul Ferraro > > Integrate MANUAL eviction strategy introduced in ISPN-6911. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6906) Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated."

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6906?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-6906: -------------------------------------- We will just make MANUAL mode the default. > Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated." > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-6906 > URL: https://issues.jboss.org/browse/WFLY-6906 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Paul Ferraro > > Integrate MANUAL eviction strategy introduced in ISPN-6911. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6906) Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated."

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6906?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-6906: --------------------------------- Comment: was deleted (was: We will just make MANUAL mode the default.) > Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated." > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-6906 > URL: https://issues.jboss.org/browse/WFLY-6906 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Paul Ferraro > > Integrate MANUAL eviction strategy introduced in ISPN-6911. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6906) Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated."

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6906?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-6906: -------------------------------------- Feature was introduced to master in https://github.com/infinispan/infinispan/pull/4472. > Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated." > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-6906 > URL: https://issues.jboss.org/browse/WFLY-6906 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Paul Ferraro > > Integrate MANUAL eviction strategy introduced in ISPN-6911. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6906) Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated."

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6906?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-6906: ------------------------------------ Assignee: Paul Ferraro (was: Radoslav Husar) > Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated." > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-6906 > URL: https://issues.jboss.org/browse/WFLY-6906 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Paul Ferraro > > Integrate MANUAL eviction strategy introduced in ISPN-6911. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2016