[
https://issues.jboss.org/browse/JBIDE-15574?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-15574:
-------------------------------------
I did make a commit to update the the server jars to beta1, as that was needed for
integrations testing anyway (always stay on the top of the stream), but in reality, there
are still issues when using a java 6 jre to run eclipse and communicate with a wildfly
server. It appears the the NIO libraries have a requirement on API introduced in java7,
specifically a class named ReflectiveOperationException.
I think now it becomes basically a requirement to run eclipse with java7 if you expect to
be communicating with wildfly unless we can get the nio stuff fixed.
{code}
java.lang.NoClassDefFoundError: java/lang/ReflectiveOperationException
at org.xnio.ssl.JsseXnioSsl.<init>(JsseXnioSsl.java:81)
at org.xnio.Xnio.getSslProvider(Xnio.java:221)
at
org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:188)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:337)
at
org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:80)
at
org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:99)
at
org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
at
org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
at
org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204)
at
org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148)
at
org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)
at
org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115)
at
org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90)
at
org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
at
org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
at
org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
at
org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
at
org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.execute(Wildfly8Manager.java:316)
at
org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.getServerState(Wildfly8Manager.java:257)
at
org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8ManagerService.getServerState(Wildfly8ManagerService.java:142)
at
org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.getServerState(JBoss7ManagerServiceProxy.java:71)
{code}
Re-opening wildfly bug.
Wildfly management plugin getting unsupported class version unit test
errors
----------------------------------------------------------------------------
Key: JBIDE-15574
URL:
https://issues.jboss.org/browse/JBIDE-15574
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Alpha1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.2.0.Alpha1
This should be fixed in wildfly beta. There is nothing that tools can do to fix this. The
relevant server jars need to rebuilt with a lower class version.
https://issues.jboss.org/browse/WFLY-2072
We will switch our unit tests to beta1 as soon as it is available.
--
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