[JBoss JIRA] (WFLY-3264) When Wildfly fails with JBAS015810: failed to resolve interface management, it should terminate.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3264?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-3264:
----------------------------------------
Interesting. The boot actually consists of two batches of operations, where a failure in the first should trigger an abort, while a failure in the second should not. I'm pretty certain my intent was the 'management' interface failure would cause the first set to fail, triggering abort. Not sure why it doesn't.
The first set gets the core services, particularly the management interfaces, running. Without those you can't administer and correct any problem, so the server aborts. The second set brings in all the subsystems and deployments.
The 'public' interface wouldn't be used until the second set. Triggering abort on that second set would need to be in some way configurable. I'm pretty sure there's a JIRA about that out there somewhere.
> When Wildfly fails with JBAS015810: failed to resolve interface management, it should terminate.
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-3264
> URL: https://issues.jboss.org/browse/WFLY-3264
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.1.0.CR1
> Reporter: Jay Kumar SenSharma
> Assignee: Brian Stansberry
>
> - When Wildfly fails with **JBAS015810: failed to resolve interface management**, it should terminate rather than dangling.
> - When starting the Wildfly with an IP address which is non-existent, you get the error 'JBAS015810: failed to resolve interface management'.
> -The server starts, but with the error message :
> {code}
> 10:41:15,390 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: JBAS015810: failed to resolve interface public
> at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:96) [wildfly-server-8.1.0.CR1.jar:8.1.0.CR1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> 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]
> 10:41:15,390 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management
> at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:96) [wildfly-server-8.1.0.CR1.jar:8.1.0.CR1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> 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]
> {code}
> - Since the server could not bind to the given address and port, and neither the cli nor the admin console are enabled, the server is as good as dead. The server should exit instead of starting up with errors when this of error is seen .
--
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, 2 months
[JBoss JIRA] (WFLY-3079) Wildfly JDK 8
by Aliaksei Lahachou (JIRA)
[ https://issues.jboss.org/browse/WFLY-3079?page=com.atlassian.jira.plugin.... ]
Aliaksei Lahachou commented on WFLY-3079:
-----------------------------------------
Are you starting WildFly from Eclipse? I had the same problem:
* After installing JDK 8, I configured JRE in Eclipse.
* I switched JRE in JBoss Runtime configuration from Default JRE for JavaSE-1.7 to jdk1.8.0_05.
* When I tried to start WildFly, I've got the same exception.
The problem was that runtime configuration does not remove old entry for JDK from classpath. When I looked into launch configuration for WildFly, there were both jdk1.7.0_55 and jdk1.8.0_05 in classpath. When I removed the jdk1.7.0_55 entry, WildFly started without problems.
> Wildfly JDK 8
> -------------
>
> Key: WFLY-3079
> URL: https://issues.jboss.org/browse/WFLY-3079
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Security, Server
> Affects Versions: 8.0.0.Final
> Reporter: Otávio Garcia
> Assignee: Tomaz Cerar
> Labels: jdk8, wildfly
>
> When I start wildfly in standalone mode I got this error.
> {noformat}
> 02:55:28,938 ERROR [org.xnio.listener] (XNIO-1 I/O-2) XNIO001007: A channel event listener threw an exception: java.lang.NoClassDefFoundError: Could not initialize class sun.security.ec.CurveDB
> at sun.security.ec.SunECEntries.putEntries(SunECEntries.java:72)
> at sun.security.ec.SunEC.<init>(SunEC.java:76)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.8.0]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) [rt.jar:1.8.0]
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.8.0]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:408) [rt.jar:1.8.0]
> at java.lang.Class.newInstance(Class.java:433) [rt.jar:1.8.0]
> at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:221) [rt.jar:1.8.0]
> at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:206) [rt.jar:1.8.0]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0]
> at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:206) [rt.jar:1.8.0]
> at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:187) [rt.jar:1.8.0]
> at sun.security.jca.ProviderList.loadAll(ProviderList.java:282) [rt.jar:1.8.0]
> at sun.security.jca.ProviderList.removeInvalid(ProviderList.java:299) [rt.jar:1.8.0]
> at sun.security.jca.Providers.getFullProviderList(Providers.java:173) [rt.jar:1.8.0]
> at java.security.Security.getProviders(Security.java:452) [rt.jar:1.8.0]
> at org.xnio.sasl.SaslUtils.getFactories(SaslUtils.java:121) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at org.xnio.sasl.SaslUtils.getSaslServerFactories(SaslUtils.java:75) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.initialiseCapabilities(ServerConnectionOpenListener.java:165) [jboss-remoting-4.0.0.Final.jar:4.0.0.Final]
> at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.sendCapabilities(ServerConnectionOpenListener.java:413) [jboss-remoting-4.0.0.Final.jar:4.0.0.Final]
> at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.handleEvent(ServerConnectionOpenListener.java:260) [jboss-remoting-4.0.0.Final.jar:4.0.0.Final]
> at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.handleEvent(ServerConnectionOpenListener.java:139) [jboss-remoting-4.0.0.Final.jar:4.0.0.Final]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:196) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:110) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at org.xnio.ChannelListeners$DelegatingChannelListener.handleEvent(ChannelListeners.java:1092) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:531)
> 02:55:34,171 ERROR [org.xnio.listener] (XNIO-1 I/O-1) XNIO001007: A channel event listener threw an exception: java.lang.NoClassDefFoundError: Could not initialize class sun.security.ec.CurveDB
> at sun.security.ec.SunECEntries.putEntries(SunECEntries.java:72)
> at sun.security.ec.SunEC.<init>(SunEC.java:76)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.8.0]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) [rt.jar:1.8.0]
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.8.0]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:408) [rt.jar:1.8.0]
> at java.lang.Class.newInstance(Class.java:433) [rt.jar:1.8.0]
> at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:221) [rt.jar:1.8.0]
> at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:206) [rt.jar:1.8.0]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0]
> at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:206) [rt.jar:1.8.0]
> at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:187) [rt.jar:1.8.0]
> at sun.security.jca.ProviderList.loadAll(ProviderList.java:282) [rt.jar:1.8.0]
> at sun.security.jca.ProviderList.removeInvalid(ProviderList.java:299) [rt.jar:1.8.0]
> at sun.security.jca.Providers.getFullProviderList(Providers.java:173) [rt.jar:1.8.0]
> at java.security.Security.getProviders(Security.java:452) [rt.jar:1.8.0]
> at org.xnio.sasl.SaslUtils.getFactories(SaslUtils.java:121) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at org.xnio.sasl.SaslUtils.getSaslServerFactories(SaslUtils.java:75) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.initialiseCapabilities(ServerConnectionOpenListener.java:165) [jboss-remoting-4.0.0.Final.jar:4.0.0.Final]
> at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.sendCapabilities(ServerConnectionOpenListener.java:413) [jboss-remoting-4.0.0.Final.jar:4.0.0.Final]
> at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.handleEvent(ServerConnectionOpenListener.java:260) [jboss-remoting-4.0.0.Final.jar:4.0.0.Final]
> at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.handleEvent(ServerConnectionOpenListener.java:139) [jboss-remoting-4.0.0.Final.jar:4.0.0.Final]
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.2.0.Final.jar:3.2.0.Final]
> {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, 2 months
[JBoss JIRA] (JBJMX-116) Jconsole doesn't connect JBOSS server 6.1.0 locally
by Rajan Chaturvedi (JIRA)
Rajan Chaturvedi created JBJMX-116:
--------------------------------------
Summary: Jconsole doesn't connect JBOSS server 6.1.0 locally
Key: JBJMX-116
URL: https://issues.jboss.org/browse/JBJMX-116
Project: JBoss JMX
Issue Type: Bug
Environment: Windows , JDK 1.6_21
Reporter: Rajan Chaturvedi
Hi
We are moving application from JBOSS 4.X to JBOSS EAP 6.1.0.
We are unable to connect JMS console . Every time we got follwoing
error at JCONSOLE
Exception in thread "AWT-EventQueue-0" java.lang.RuntimeException: Error connecting to JBoss AS.
at org.jboss.as.cli.gui.JConsoleCLIPlugin.getTabs(JConsoleCLIPlugin.java:80)
at sun.tools.jconsole.VMPanel.createPluginTabs(VMPanel.java:641)
at sun.tools.jconsole.VMPanel.propertyChange(VMPanel.java:315)
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339)
at javax.swing.event.SwingPropertyChangeSupport.firePropertyChange(SwingPropertyChangeSupport.java:75)
at javax.swing.event.SwingPropertyChangeSupport$1.run(SwingPropertyChangeSupport.java:80)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: java.lang.NullPointerException
at org.jboss.as.cli.gui.JConsoleCLIPlugin.connectCommandContext(JConsoleCLIPlugin.java:109)
at org.jboss.as.cli.gui.JConsoleCLIPlugin.getTabs(JConsoleCLIPlugin.java:77)
... 13 more
This Error is coming after adding jline-0.9.94-redhat-1.jar.
at %JBOSS_MODULEPATH%\jline\main\jline-0.9.94-redhat-1.jar.
Note that we are doing custom deployment hence written new bat file to start server which set few paths and then calls standalone.bat.
Please provide solution ASAP.
--
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, 2 months
[JBoss JIRA] (WFLY-3274) connector values are not available like "requestCount , maxTime, bytesReceived etc " in wildfly (domain mode) 8.0.0.Final
by Rituraj Sinha (JIRA)
[ https://issues.jboss.org/browse/WFLY-3274?page=com.atlassian.jira.plugin.... ]
Rituraj Sinha updated WFLY-3274:
--------------------------------
Issue Type: Task (was: Bug)
Priority: Major (was: Critical)
> connector values are not available like "requestCount , maxTime, bytesReceived etc " in wildfly (domain mode) 8.0.0.Final
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3274
> URL: https://issues.jboss.org/browse/WFLY-3274
> Project: WildFly
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JMX, Web (Undertow)
> Affects Versions: 8.0.0.Final
> Reporter: Rituraj Sinha
> Assignee: Kabir Khan
>
> while using jboss 7.2.0 we were able to fetch above values from the cli command as
> [domain@test.com:9999 subsystem=web] ls
> configuration valve default-virtual-server=default-host native=false
> connector virtual-server instance-id=${jboss.node.name}
> [domain@test.com:9999 connector] ls
> ajp http
> [domain@test.com:9999 connector] cd http
> [domain@test.com:9999 connector] pwd
> /profile=ha/subsystem=web/connector=http
> [domain@test.com:9999 connector=http] ls
> configuration max-connections=undefined proxy-port=undefined
> ssl max-post-size=2097152 redirect-port=443
> bytesReceived= max-save-post-size=4096 requestCount=
> bytesSent= maxTime= scheme=http
> enable-lookups=false name=http secure=false
> enabled=true processingTime= socket-binding=http
> errorCount= protocol=HTTP/1.1 virtual-server=undefined
> executor=undefined proxy-name=undefined
>
> Now we have moved to wildfly8 and trying to look for the same values in underetow( as there is no "web" subsystem in wildfly8)
> as below
> [domain@test2.com:9990 subsystem=undertow] ls
> buffer-cache server default-servlet-container=default statistics-enabled=false (Here there is no connector attribute available as this was in jboss 7.2.0 )
> configuration servlet-container default-virtual-host=default-host
> error-page default-server=default-server instance-id=${jboss.node.name}
>
> but the listners(HTTP, AJP and HTTPS ) are defined in the server attribute...hence going into server attribute we get the below as
> [domain@test2.com:9990 server=default-server] ls
> ajp-listener host http-listener https-listener default-host=default-host servlet-container=default
> after getting into http-listener we get the below
> [domain@test2.com:9990 http-listener=default] ls
> allow-encoded-slash=false certificate-forwarding=false max-cookies=200 max-post-size=10485760 socket-binding=http
> always-set-keep-alive=true decode-url=true max-header-size=51200 proxy-address-forwarding=false url-charset=UTF-8
> buffer-pipelined-data=true enabled=true max-headers=200 record-request-start-time=false worker=default
> buffer-pool=default max-buffered-request-size=16384 max-parameters=1000 redirect-socket=https
>
> Can someone please look into it ..?
--
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, 2 months
[JBoss JIRA] (WFLY-3274) connector values are not available like "requestCount , maxTime, bytesReceived etc " in wildfly (domain mode) 8.0.0.Final
by Rituraj Sinha (JIRA)
Rituraj Sinha created WFLY-3274:
-----------------------------------
Summary: connector values are not available like "requestCount , maxTime, bytesReceived etc " in wildfly (domain mode) 8.0.0.Final
Key: WFLY-3274
URL: https://issues.jboss.org/browse/WFLY-3274
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX, Web (Undertow)
Affects Versions: 8.0.0.Final
Reporter: Rituraj Sinha
Assignee: Kabir Khan
Priority: Critical
while using jboss 7.2.0 we were able to fetch above values from the cli command as
[domain@test.com:9999 subsystem=web] ls
configuration valve default-virtual-server=default-host native=false
connector virtual-server instance-id=${jboss.node.name}
[domain@test.com:9999 connector] ls
ajp http
[domain@test.com:9999 connector] cd http
[domain@test.com:9999 connector] pwd
/profile=ha/subsystem=web/connector=http
[domain@test.com:9999 connector=http] ls
configuration max-connections=undefined proxy-port=undefined
ssl max-post-size=2097152 redirect-port=443
bytesReceived= max-save-post-size=4096 requestCount=
bytesSent= maxTime= scheme=http
enable-lookups=false name=http secure=false
enabled=true processingTime= socket-binding=http
errorCount= protocol=HTTP/1.1 virtual-server=undefined
executor=undefined proxy-name=undefined
Now we have moved to wildfly8 and trying to look for the same values in underetow( as there is no "web" subsystem in wildfly8)
as below
[domain@test2.com:9990 subsystem=undertow] ls
buffer-cache server default-servlet-container=default statistics-enabled=false (Here there is no connector attribute available as this was in jboss 7.2.0 )
configuration servlet-container default-virtual-host=default-host
error-page default-server=default-server instance-id=${jboss.node.name}
but the listners(HTTP, AJP and HTTPS ) are defined in the server attribute...hence going into server attribute we get the below as
[domain@test2.com:9990 server=default-server] ls
ajp-listener host http-listener https-listener default-host=default-host servlet-container=default
after getting into http-listener we get the below
[domain@test2.com:9990 http-listener=default] ls
allow-encoded-slash=false certificate-forwarding=false max-cookies=200 max-post-size=10485760 socket-binding=http
always-set-keep-alive=true decode-url=true max-header-size=51200 proxy-address-forwarding=false url-charset=UTF-8
buffer-pipelined-data=true enabled=true max-headers=200 record-request-start-time=false worker=default
buffer-pool=default max-buffered-request-size=16384 max-parameters=1000 redirect-socket=https
Can someone please look into it ..?
--
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, 2 months