October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1828) Wildfly High Availability Guide: Load-balancing (LB) and mod_cluster write up

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1828?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1828: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Wildfly High Availability Guide: Load-balancing (LB) and mod_cluster write up > ----------------------------------------------------------------------------- > > Key: WFLY-1828 > URL: https://issues.jboss.org/browse/WFLY-1828 > Project: WildFly > Issue Type: Sub-task > Components: Clustering, Documentation > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.CR1 > > > https://docs.jboss.org/author/display/WFLY8/Load+Balancing -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1826) Wildfly High Availability Guide: Clustered Web Sessions write up

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1826?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1826: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Wildfly High Availability Guide: Clustered Web Sessions write up > ---------------------------------------------------------------- > > Key: WFLY-1826 > URL: https://issues.jboss.org/browse/WFLY-1826 > Project: WildFly > Issue Type: Sub-task > Components: Clustering, Documentation > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.CR1 > > > https://docs.jboss.org/author/display/WFLY8/Clustered+Web+Sessions -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1829) Wildfly High Availability Guide: EJB Services/Subsystem write up

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1829?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1829: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Wildfly High Availability Guide: EJB Services/Subsystem write up > ---------------------------------------------------------------- > > Key: WFLY-1829 > URL: https://issues.jboss.org/browse/WFLY-1829 > Project: WildFly > Issue Type: Sub-task > Components: Clustering, Documentation > Reporter: Radoslav Husar > Fix For: 8.0.0.CR1 > > > https://docs.jboss.org/author/display/WFLY8/EJB+Subsystem -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1858) Add RBAC sensitivity classification constraints to undertow subsystem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1858?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1858: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add RBAC sensitivity classification constraints to undertow subsystem > --------------------------------------------------------------------- > > Key: WFLY-1858 > URL: https://issues.jboss.org/browse/WFLY-1858 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Web (Undertow) > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Labels: RBAC-WF-only > Fix For: 8.0.0.CR1 > > > The current RBAC work updated the web subsystem but not undertow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1849) Provide complete model descriptions for undertow subsystem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1849?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1849: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Provide complete model descriptions for undertow subsystem > ---------------------------------------------------------- > > Key: WFLY-1849 > URL: https://issues.jboss.org/browse/WFLY-1849 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management, Web (Undertow) > Reporter: Heiko Braun > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1837) manual module testoutput is a bit disturbing NPE and dependencies missing

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1837?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1837: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > manual module testoutput is a bit disturbing NPE and dependencies missing > ------------------------------------------------------------------------- > > Key: WFLY-1837 > URL: https://issues.jboss.org/browse/WFLY-1837 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 8.0.0.Alpha3 > Reporter: Bartosz Baranowski > Assignee: JBoss SET > Fix For: 8.0.0.CR1 > > > Manual testmodule shows a lot of NPEs and dependency issues: > {noformat} > [org.jboss.as.ejb3] (EJB default - 2) JBAS014249: Error invoking method public abstract void org.jboss.as.test.manualmode.ejb.shutdown.RemoteLatch.testDone() on bean named LatchBean for appname modulename dep1 distinctname : java.lang.NullPointerException > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:322) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:70) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:203) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > 13:06:07,613 ERROR [org.jboss.as.ejb3] (EJB default - 2) JBAS014250: Could not write method invocation failure for method public abstract void org.jboss.as.test.manualmode.ejb.shutdown.RemoteLatch.testDone() on bean named LatchBean for appname modulename dep1 distinctname due to: java.io.IOException: Stream is closed > at org.xnio.streams.BufferPipeOutputStream.closed(BufferPipeOutputStream.java:58) [xnio-api-3.1.0.CR3.jar:3.1.0.CR3] > at org.xnio.streams.BufferPipeOutputStream.checkClosed(BufferPipeOutputStream.java:64) [xnio-api-3.1.0.CR3.jar:3.1.0.CR3] > at org.xnio.streams.BufferPipeOutputStream.write(BufferPipeOutputStream.java:90) [xnio-api-3.1.0.CR3.jar:3.1.0.CR3] > at org.jboss.remoting3.remote.OutboundMessage.write(OutboundMessage.java:252) > at java.io.DataOutputStream.write(DataOutputStream.java:107) [rt.jar:1.7.0_25] > at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler$1.write(AbstractMessageHandler.java:217) > at org.jboss.marshalling.OutputStreamByteOutput.write(OutputStreamByteOutput.java:56) > at org.jboss.marshalling.SimpleDataOutput.shallowFlush(SimpleDataOutput.java:328) > at org.jboss.marshalling.river.RiverMarshaller.writeString(RiverMarshaller.java:1451) > at org.jboss.marshalling.river.RiverMarshaller.writeNewSerializableClass(RiverMarshaller.java:1362) > at org.jboss.marshalling.river.RiverMarshaller.writeSerializableClass(RiverMarshaller.java:1345) > at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:883) > at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063) > at org.jboss.marshalling.river.RiverObjectOutputStream.defaultWriteObject(RiverObjectOutputStream.java:159) > at java.lang.Throwable.writeObject(Throwable.java:984) [rt.jar:1.7.0_25] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25] > at org.jboss.marshalling.reflect.SerializableClass.callWriteObject(SerializableClass.java:180) > at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1007) > at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:998) > at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:998) > at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:998) > at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885) > at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62) > at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119) > at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler.writeException(AbstractMessageHandler.java:112) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$400(MethodInvocationMessageHandler.java:70) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:213) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > Caused by: an exception which occurred: > in field suppressedExceptions > in object java.lang.NullPointerException@18e5c476 > {noformat} > {noformat} > 13:01:23,032 ERROR [org.jboss.as.controller.management-operation] (pool-2-thread-1) JBAS014612: Operation ("add") failed - address: ([ > ("host" => "master"), > ("core-service" => "management"), > ("management-interface" => "http-interface") > ]): java.lang.NullPointerException > at org.jboss.as.host.controller.operations.HttpManagementAddHandler.installHttpManagementServices(HttpManagementAddHandler.java:137) [wildfly-host-controller-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-SNAPSHOT] > at org.jboss.as.host.controller.operations.HttpManagementAddHandler.performRuntime(HttpManagementAddHandler.java:97) [wildfly-host-controller-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-SNAPSHOT] > at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:75) [wildfly-controller-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4-SNAPSHOT] > {noformat} > {noformat} > 13:01:23,493 ERROR [org.jboss.as.controller.management-operation] (pool-2-thread-1) JBAS014613: Operation ("add") failed - address: ([ > ("core-service" => "management"), > ("management-interface" => "native-interface") > ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => [ > "jboss.remoting.authentication_provider.management is missing [jboss.server.path.\"jboss.server.temp.dir\"]", > "jboss.remoting.endpoint.management.management.operation.handler is missing [jboss.as.server-controller]", > "jboss.remoting.endpoint.management.channel.management is missing [jboss.remoting.endpoint.management.shutdown.executor]", > "jboss.remoting.server.management is missing [jboss.binding.management-native, jboss.socket-binding-manager]" > ]} > 13:01:23,494 INFO [org.jboss.as.controller] (pool-2-thread-1) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.as.server-controller (missing) dependents: [service jboss.remoting.endpoint.management.management.operation.handler] > service jboss.binding.management-native (missing) dependents: [service jboss.remoting.server.management] > service jboss.remoting.endpoint.management.shutdown.executor (missing) dependents: [service jboss.remoting.endpoint.management.channel.management] > service jboss.server.path."jboss.server.temp.dir" (missing) dependents: [service jboss.remoting.authentication_provider.management] > service jboss.socket-binding-manager (missing) dependents: [service jboss.remoting.server.management] > 13:01:23,495 INFO [org.jboss.as.server] (pool-2-thread-1) JBAS015888: Creating http management service using socket-binding (management-http) > 13:01:23,496 ERROR [org.jboss.as.controller.management-operation] (pool-2-thread-1) JBAS014612: Operation ("add") failed - address: ([ > ("core-service" => "management"), > ("management-interface" => "http-interface") > ]): org.jboss.msc.service.ServiceNotFoundException: Service service jboss.server.environment not found > at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:668) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationContextImpl.java:1068) [wildfly-controller-8.0.0.Alpha4-SNAPSHOT.jar:8.0.0.Alpha4- > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1836) manual module SSLEJBRemoteClientTestCase keeps freezing

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1836?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1836: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > manual module SSLEJBRemoteClientTestCase keeps freezing > ------------------------------------------------------- > > Key: WFLY-1836 > URL: https://issues.jboss.org/browse/WFLY-1836 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha3 > Reporter: Bartosz Baranowski > Assignee: JBoss SET > Fix For: 8.0.0.CR1 > > > CI job keeps freezing on this test. In local run, it does not fail however: > execution in batch: 102s+ > standalone : ~45s -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1832) Wildfly High Availability Guide: Migration and Changes From Previous Versions write up

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1832?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1832: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Wildfly High Availability Guide: Migration and Changes From Previous Versions write up > --------------------------------------------------------------------------------------- > > Key: WFLY-1832 > URL: https://issues.jboss.org/browse/WFLY-1832 > Project: WildFly > Issue Type: Sub-task > Components: Clustering, Documentation > Reporter: Radoslav Husar > Fix For: 8.0.0.CR1 > > > https://docs.jboss.org/author/display/WFLY8/Changes+From+Previous+Versions -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1873) mod_cluster ISE on shutdown

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1873?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1873: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > mod_cluster ISE on shutdown > --------------------------- > > Key: WFLY-1873 > URL: https://issues.jboss.org/browse/WFLY-1873 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.Alpha4 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.CR1 > > > 16:45:28,305 ERROR [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (MSC service thread 1-2) Error [MEM: MEM: Can't read node: {4}] sending command DISABLE-APP to proxy localhost/127.0.0.1:6666, configuration will be reset > 16:45:28,315 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017521: Undertow AJP listener ajp suspending > 16:45:28,319 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017520: Undertow AJP listener ajp stopped, was bound to /127.0.0.1:8009 > 16:45:28,336 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010418: Stopped Driver service with driver-name = h2 > 16:45:28,344 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017521: Undertow HTTP listener default suspending > 16:45:28,349 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017520: Undertow HTTP listener default stopped, was bound to /127.0.0.1:8080 > 16:45:38,307 WARN [org.jboss.modcluster.ModClusterService] (MSC service thread 1-2) Failed to drain pending requests from context [org.wildfly.mod_cluster.undertow.UndertowContext@1906d941] within specified timeout: 10 seconds > 16:45:38,308 WARN [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000004: Failure during stop of service jboss.undertow.deployment.default-host./clusterbench-ee6-web: java.lang.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.wildfly.mod_cluster.undertow.UndertowEventHandlerAdapter.onDeploymentStop(UndertowEventHandlerAdapter.java:137) > at org.wildfly.extension.undertow.Host$2.invoke(Host.java:138) > at org.wildfly.extension.undertow.UndertowService.fireEvent(UndertowService.java:168) > at org.wildfly.extension.undertow.Host.unregisterDeployment(Host.java:135) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:104) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:94) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2052) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2013) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1902) jconsole.sh fails when JAVA_HOME is not set

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1902?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1902: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > jconsole.sh fails when JAVA_HOME is not set > ------------------------------------------- > > Key: WFLY-1902 > URL: https://issues.jboss.org/browse/WFLY-1902 > Project: WildFly > Issue Type: Feature Request > Components: Scripts > Affects Versions: 8.0.0.Alpha4 > Environment: RHEL#/Fedora/Debian RPM > Reporter: Aleksandar Kostadinov > Assignee: Aleksandar Kostadinov > Labels: jconsole > Fix For: 8.0.0.CR1 > > > In most standard linux distros JAVA_HOME is never set no matter if any JVM is installed or not. This breaks jconsole.sh > {code} > # /usr/share/jbossas/bin/jconsole.sh > JAVA_HOME is not set. Unable to locate the jars needed to run jconsole. > {code} > jconsole.sh needs to try finding a suitable java installation before failing with an error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2013