[JBoss JIRA] (WFLY-2839) Remote Naming communication exception should be thrown on ConnectException
by Brad Maxwell (JIRA)
Brad Maxwell created WFLY-2839:
----------------------------------
Summary: Remote Naming communication exception should be thrown on ConnectException
Key: WFLY-2839
URL: https://issues.jboss.org/browse/WFLY-2839
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Naming
Affects Versions: 8.0.0.CR1
Reporter: Brad Maxwell
Assignee: Brad Maxwell
Remote Naming communication exception should be thrown on ConnectException, a remoting bug fix showed that a ConnectException can be thrown to remoting and we should throw this as a CommunicationException instead of generic NamingException. This is related to WFLY-2198
--
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
12 years, 5 months
[JBoss JIRA] (WFLY-2838) Revisit default mod_cluster metric for WildFly 8
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-2838:
------------------------------------
Summary: Revisit default mod_cluster metric for WildFly 8
Key: WFLY-2838
URL: https://issues.jboss.org/browse/WFLY-2838
Project: WildFly
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: 8.0.0.CR1
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Priority: Blocker
Fix For: 8.0.0.Final
Since the threading aspects of Undertow in WildFly are completely different from JBoss Web's in the previous versions of AS, we should reconsider the default metric for WildFly.
Currently, busyness requires explicit capacity to be useful which would require further tweaking by users.
Metric "cpu" is also a good candidate since it doesn't need explicit capacity..
--
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
12 years, 5 months
[JBoss JIRA] (WFLY-2836) http-listener requires 'https' socket-binding
by dfisher (JIRA)
[ https://issues.jboss.org/browse/WFLY-2836?page=com.atlassian.jira.plugin.... ]
dfisher commented on WFLY-2836:
-------------------------------
I need multiple http-listeners, so I renamed the listeners and the socket-bindings in the default config to be representative of their purpose in our environment.
That's how I discovered this dependency on a socket-binding named 'https'.
> http-listener requires 'https' socket-binding
> ---------------------------------------------
>
> Key: WFLY-2836
> URL: https://issues.jboss.org/browse/WFLY-2836
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.CR1
> Reporter: dfisher
> Assignee: Tomaz Cerar
> Priority: Minor
> Fix For: 8.0.0.Final
>
>
> Using a http-listener without the redirect-socket attribute requires the configuration to define a socket-binding with name "https".
> The following error is produced attempting to configure wildfly without https:
> {code}
> ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("http-listener" => "default")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]}
> {code}
> I believe this constant is defined in ListenerResourceDefinition on line 80.
> If this is the desired behavior, the undertow schema should probably be updated to make redirect-socket required or at least document the dependency.
--
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
12 years, 5 months
[JBoss JIRA] (WFLY-2816) Favour jboss-persistence.xml if present
by Christopher Klein (JIRA)
[ https://issues.jboss.org/browse/WFLY-2816?page=com.atlassian.jira.plugin.... ]
Christopher Klein commented on WFLY-2816:
-----------------------------------------
I put a message on the mailing list. Let's see what the reactions are.
> Favour jboss-persistence.xml if present
> ---------------------------------------
>
> Key: WFLY-2816
> URL: https://issues.jboss.org/browse/WFLY-2816
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JPA / Hibernate, Server
> Reporter: Christopher Klein
> Assignee: Scott Marlow
> Priority: Minor
>
> For developing for different target application servers (e.g. JBoss and WebSphere) it would be nice if WildFly favours a jboss-persistence.xml instead of the original persistence.xml.
> The jboss-persistence.xml is specific for the deployment inside WildFly, the persistence.xml would be the fallback/default for other application servers.
--
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
12 years, 5 months
[JBoss JIRA] (WFLY-2836) http-listener requires 'https' socket-binding
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-2836?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-2836:
-----------------------------------
In default configs we ship https socket binding, to help with exactly this kind of things...
you didn't start with provided configuration files?
> http-listener requires 'https' socket-binding
> ---------------------------------------------
>
> Key: WFLY-2836
> URL: https://issues.jboss.org/browse/WFLY-2836
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.CR1
> Reporter: dfisher
> Assignee: Tomaz Cerar
> Priority: Minor
> Fix For: 8.0.0.Final
>
>
> Using a http-listener without the redirect-socket attribute requires the configuration to define a socket-binding with name "https".
> The following error is produced attempting to configure wildfly without https:
> {code}
> ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("http-listener" => "default")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]}
> {code}
> I believe this constant is defined in ListenerResourceDefinition on line 80.
> If this is the desired behavior, the undertow schema should probably be updated to make redirect-socket required or at least document the dependency.
--
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
12 years, 5 months
[JBoss JIRA] (WFLY-2836) http-listener requires 'https' socket-binding
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-2836?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-2836:
------------------------------
Fix Version/s: 8.0.0.Final
> http-listener requires 'https' socket-binding
> ---------------------------------------------
>
> Key: WFLY-2836
> URL: https://issues.jboss.org/browse/WFLY-2836
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.CR1, 8.0.0.Final
> Reporter: dfisher
> Assignee: Tomaz Cerar
> Priority: Minor
> Fix For: 8.0.0.Final
>
>
> Using a http-listener without the redirect-socket attribute requires the configuration to define a socket-binding with name "https".
> The following error is produced attempting to configure wildfly without https:
> {code}
> ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("http-listener" => "default")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]}
> {code}
> I believe this constant is defined in ListenerResourceDefinition on line 80.
> If this is the desired behavior, the undertow schema should probably be updated to make redirect-socket required or at least document the dependency.
--
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
12 years, 5 months
[JBoss JIRA] (WFLY-2836) http-listener requires 'https' socket-binding
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-2836?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-2836:
------------------------------
Affects Version/s: (was: 8.0.0.Final)
> http-listener requires 'https' socket-binding
> ---------------------------------------------
>
> Key: WFLY-2836
> URL: https://issues.jboss.org/browse/WFLY-2836
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.CR1
> Reporter: dfisher
> Assignee: Tomaz Cerar
> Priority: Minor
> Fix For: 8.0.0.Final
>
>
> Using a http-listener without the redirect-socket attribute requires the configuration to define a socket-binding with name "https".
> The following error is produced attempting to configure wildfly without https:
> {code}
> ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("http-listener" => "default")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]}
> {code}
> I believe this constant is defined in ListenerResourceDefinition on line 80.
> If this is the desired behavior, the undertow schema should probably be updated to make redirect-socket required or at least document the dependency.
--
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
12 years, 5 months
[JBoss JIRA] (WFLY-2836) http-listener requires 'https' socket-binding
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-2836?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-2836:
---------------------------------
Assignee: Tomaz Cerar (was: Stuart Douglas)
> http-listener requires 'https' socket-binding
> ---------------------------------------------
>
> Key: WFLY-2836
> URL: https://issues.jboss.org/browse/WFLY-2836
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.CR1, 8.0.0.Final
> Reporter: dfisher
> Assignee: Tomaz Cerar
> Priority: Minor
>
> Using a http-listener without the redirect-socket attribute requires the configuration to define a socket-binding with name "https".
> The following error is produced attempting to configure wildfly without https:
> {code}
> ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("http-listener" => "default")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]}
> {code}
> I believe this constant is defined in ListenerResourceDefinition on line 80.
> If this is the desired behavior, the undertow schema should probably be updated to make redirect-socket required or at least document the dependency.
--
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
12 years, 5 months
[JBoss JIRA] (WFLY-2837) "UT015005: Error invoking method requestDestroyed on listener class ..." on clean shutdown with session draining
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-2837:
------------------------------------
Summary: "UT015005: Error invoking method requestDestroyed on listener class ..." on clean shutdown with session draining
Key: WFLY-2837
URL: https://issues.jboss.org/browse/WFLY-2837
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (Undertow)
Affects Versions: 8.0.0.CR1
Reporter: Radoslav Husar
Assignee: Stuart Douglas
When using mod_cluster session draining and shutting down, draining for 10 seconds results in problem with invoking requestDestroyed listener event.
Seems to me like dependency orchestration problem on shutdown..
{noformat}
19:01:31,978 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment null (runtime-name: clusterbench-ee7-ejb-1.1.0-SNAPSHOT.jar) in 437ms
19:01:31,978 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment null (runtime-name: clusterbench-ee7-web-1.1.0-SNAPSHOT.war) in 462ms
19:01:31,981 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment clusterbench-ee7.ear (runtime-name: clusterbench-ee7.ear) in 441ms
19:01:35,505 INFO [org.jboss.test.clusterbench.web.load.AverageSystemLoadServlet] (default task-2) DONE, I was stressing CPU with 4 evil threads for 5027 milliseconds (including warm-up).
19:01:35,510 ERROR [io.undertow.servlet.request] (default task-2) UT015005: Error invoking method requestDestroyed on listener class com.sun.faces.config.ConfigureListener: java.lang.RuntimeException: javax.servlet.ServletException: UT010013: Could not instantiate com.sun.faces.config.ConfigureListener
at io.undertow.servlet.core.ManagedListener.instance(ManagedListener.java:77) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.servlet.core.ApplicationListeners.get(ApplicationListeners.java:297) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.servlet.core.ApplicationListeners.requestDestroyed(ApplicationListeners.java:225) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:283) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:685) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: javax.servlet.ServletException: UT010013: Could not instantiate com.sun.faces.config.ConfigureListener
at io.undertow.servlet.core.ManagedListener.start(ManagedListener.java:50) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.servlet.core.ManagedListener.instance(ManagedListener.java:75) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
... 11 more
Caused by: java.lang.IllegalStateException
at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
at org.jboss.as.ee.component.ComponentStartService.getValue(ComponentStartService.java:97)
at org.jboss.as.ee.component.ComponentStartService.getValue(ComponentStartService.java:41)
at org.jboss.msc.service.ServiceControllerImpl.getValue(ServiceControllerImpl.java:1158)
at org.jboss.as.ee.component.ComponentRegistry$ComponentManagedReferenceFactory.getReference(ComponentRegistry.java:149)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$5.createInstance(UndertowDeploymentInfoService.java:1132)
at io.undertow.servlet.core.ManagedListener.start(ManagedListener.java:48) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
... 12 more
19:01:35,513 ERROR [io.undertow.servlet.request] (default task-2) UT015005: Error invoking method requestDestroyed on listener class org.jboss.weld.servlet.WeldInitialListener: java.lang.RuntimeException: javax.servlet.ServletException: UT010013: Could not instantiate org.jboss.weld.servlet.WeldInitialListener
at io.undertow.servlet.core.ManagedListener.instance(ManagedListener.java:77) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.servlet.core.ApplicationListeners.get(ApplicationListeners.java:297) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.servlet.core.ApplicationListeners.requestDestroyed(ApplicationListeners.java:225) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:283) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:685) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: javax.servlet.ServletException: UT010013: Could not instantiate org.jboss.weld.servlet.WeldInitialListener
at io.undertow.servlet.core.ManagedListener.start(ManagedListener.java:50) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
at io.undertow.servlet.core.ManagedListener.instance(ManagedListener.java:75) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
... 11 more
Caused by: java.lang.IllegalStateException
at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
at org.jboss.as.ee.component.ComponentStartService.getValue(ComponentStartService.java:97)
at org.jboss.as.ee.component.ComponentStartService.getValue(ComponentStartService.java:41)
at org.jboss.msc.service.ServiceControllerImpl.getValue(ServiceControllerImpl.java:1158)
at org.jboss.as.ee.component.ComponentRegistry$ComponentManagedReferenceFactory.getReference(ComponentRegistry.java:149)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$5.createInstance(UndertowDeploymentInfoService.java:1132)
at io.undertow.servlet.core.ManagedListener.start(ManagedListener.java:48) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33]
... 12 more
19:01:41,578 INFO [org.jboss.modcluster] (MSC service thread 1-6) MODCLUSTER000021: All pending requests drained from default-host:/clusterbench in 10.0 seconds
19:01:41,580 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 60) MODCLUSTER000002: Initiating mod_cluster shutdown
19:01:41,580 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017521: Undertow AJP listener ajp suspending
19:01:41,582 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017520: Undertow AJP listener ajp stopped, was bound to /127.0.0.1:8009
19:01:41,583 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017506: Undertow 1.0.0.Beta33 stopping
19:01:41,586 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015950: WildFly 8.0.0.Final-SNAPSHOT "WildFly" stopped in 10026ms
{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
12 years, 5 months