[JBoss JIRA] (WFLY-9370) Fix failing SingletonTunnelTestCase(ASYNC-tunnel)#testSingletonService
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9370?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-9370:
--------------------------------------
Meanwhile opened WFLY-9377 as moving the test to do management operations directly rather than XSLT will fail.
> Fix failing SingletonTunnelTestCase(ASYNC-tunnel)#testSingletonService
> -----------------------------------------------------------------------
>
> Key: WFLY-9370
> URL: https://issues.jboss.org/browse/WFLY-9370
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.CR1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> The problem is that this test is not run as part of regular CI execution thus is destined to be broken. The test should be moved to the right location and renamed (i.e. drop tunnel since that has nothing to do with what it is testing).
> {noformat}
> [0m[31m04:44:19,235 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "singleton.war")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.clustering.group.default"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.test1.service.default is missing [jboss.clustering.group.default]",
> "jboss.test2.service.default is missing [jboss.clustering.group.default]"
> ],
> "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => [
> "jboss.deployment.discovery.\"singleton.war\"",
> "jboss.deployment.unit.\"singleton.war\".CdiValidatorFactoryService",
> "jboss.deployment.unit.\"singleton.war\".WeldStartService",
> "jboss.deployment.unit.\"singleton.war\".component.TopologyChangeListenerBean.JndiBindingsService",
> "jboss.deployment.unit.\"singleton.war\".component.TopologyChangeListenerBean.START",
> "jboss.deployment.unit.\"singleton.war\".component.TopologyChangeListenerBean.VIEW.\"org.jboss.as.test.clustering.TopologyChangeListener\".REMOTE",
> "jboss.deployment.unit.\"singleton.war\".component.TopologyChangeListenerBean.WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.TopologyChangeListenerBean.WeldInterceptorBindingsService",
> "jboss.deployment.unit.\"singleton.war\".component.\"com.sun.faces.config.ConfigureListener\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"com.sun.faces.config.ConfigureListener\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.\"javax.faces.webapp.FacetTag\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"javax.faces.webapp.FacetTag\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.as.test.clustering.TopologyChangeListenerServlet\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.as.test.clustering.TopologyChangeListenerServlet\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.as.test.clustering.cluster.singleton.service.NodeServiceServlet\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.as.test.clustering.cluster.singleton.service.NodeServiceServlet\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.as.test.clustering.cluster.singleton.service.ValueServiceServlet\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.as.test.clustering.cluster.singleton.service.ValueServiceServlet\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.weld.servlet.WeldInitialListener\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.weld.servlet.WeldInitialListener\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.weld.servlet.WeldTerminalListener\".START",
> "jboss.deployment.unit.\"singleton.war\".component.\"org.jboss.weld.servlet.WeldTerminalListener\".WeldInstantiator",
> "jboss.deployment.unit.\"singleton.war\".deploymentCompleteService",
> "jboss.deployment.unit.\"singleton.war\".ejb3.client-context.registration-service",
> "jboss.deployment.unit.\"singleton.war\".jndiDependencyService",
> "jboss.deployment.unit.\"singleton.war\".moduleDeploymentRuntimeInformation",
> "jboss.deployment.unit.\"singleton.war\".moduleDeploymentRuntimeInformationStart",
> "jboss.naming.context.java.app.singleton.singleton.TopologyChangeListenerBean",
> "jboss.naming.context.java.app.singleton.singleton.\"TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener\"",
> "jboss.naming.context.java.global.singleton.TopologyChangeListenerBean",
> "jboss.naming.context.java.global.singleton.\"TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener\"",
> "jboss.naming.context.java.module.singleton.singleton.TopologyChangeListenerBean",
> "jboss.naming.context.java.module.singleton.singleton.\"TopologyChangeListenerBean!org.jboss.as.test.clustering.TopologyChangeListener\"",
> "jboss.undertow.deployment.default-server.default-host./singleton",
> "jboss.undertow.deployment.default-server.default-host./singleton.UndertowDeploymentInfoService"
> ],
> "Services that may be the cause:" => [
> "jboss.clustering.group.default",
> "org.wildfly.network.socket-binding.undefined"
> ]
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-9377) Reloading fails with BindException when TUNNEL protocol is configured with socket-binding
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9377?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-9377:
--------------------------------------
Requires jgroups upgrade 3.6.15.
> Reloading fails with BindException when TUNNEL protocol is configured with socket-binding
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-9377
> URL: https://issues.jboss.org/browse/WFLY-9377
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.CR1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> {noformat}
> 15:58:16,189 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool – 68) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee: java.net.BindException: Address already in use (Bind failed)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:104)
> at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.net.BindException: Address already in use (Bind failed)
> at java.net.PlainDatagramSocketImpl.bind0(Native Method)
> at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:93)
> at java.net.DatagramSocket.bind(DatagramSocket.java:392)
> at java.net.DatagramSocket.<init>(DatagramSocket.java:242)
> at java.net.DatagramSocket.<init>(DatagramSocket.java:299)
> at org.jgroups.util.DefaultSocketFactory.createDatagramSocket(DefaultSocketFactory.java:62)
> at org.jgroups.protocols.TUNNEL.init(TUNNEL.java:142)
> at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861)
> at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:831)
> at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:108)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:102)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JGRP-2221) TUNNEL does not close its sock in #destroy()
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2221?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2221:
---------------------------
Fix Version/s: 4.0.7
> TUNNEL does not close its sock in #destroy()
> --------------------------------------------
>
> Key: JGRP-2221
> URL: https://issues.jboss.org/browse/JGRP-2221
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.12
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 3.6.15, 4.0.7
>
>
> Noticed when reloading the server.
> 15:58:16,189 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 68) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee: java.net.BindException: Address already in use (Bind failed)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:104)
> at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.net.BindException: Address already in use (Bind failed)
> at java.net.PlainDatagramSocketImpl.bind0(Native Method)
> at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:93)
> at java.net.DatagramSocket.bind(DatagramSocket.java:392)
> at java.net.DatagramSocket.<init>(DatagramSocket.java:242)
> at java.net.DatagramSocket.<init>(DatagramSocket.java:299)
> at org.jgroups.util.DefaultSocketFactory.createDatagramSocket(DefaultSocketFactory.java:62)
> at org.jgroups.protocols.TUNNEL.init(TUNNEL.java:142)
> at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861)
> at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:831)
> at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:108)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:102)
> ... 5 more
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-9377) Reloading fails with BindException when TUNNEL protocol is configured with socket-binding
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9377?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-9377:
--------------------------------------
Issue is cause by JGroups issue, see JGRP-2221 and the PR.
> Reloading fails with BindException when TUNNEL protocol is configured with socket-binding
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-9377
> URL: https://issues.jboss.org/browse/WFLY-9377
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.CR1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> {noformat}
> 15:58:16,189 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool – 68) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee: java.net.BindException: Address already in use (Bind failed)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:104)
> at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.net.BindException: Address already in use (Bind failed)
> at java.net.PlainDatagramSocketImpl.bind0(Native Method)
> at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:93)
> at java.net.DatagramSocket.bind(DatagramSocket.java:392)
> at java.net.DatagramSocket.<init>(DatagramSocket.java:242)
> at java.net.DatagramSocket.<init>(DatagramSocket.java:299)
> at org.jgroups.util.DefaultSocketFactory.createDatagramSocket(DefaultSocketFactory.java:62)
> at org.jgroups.protocols.TUNNEL.init(TUNNEL.java:142)
> at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861)
> at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:831)
> at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:108)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:102)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JGRP-2221) TUNNEL does not close its sock in #destroy()
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2221?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2221:
---------------------------
Fix Version/s: 3.6.15
> TUNNEL does not close its sock in #destroy()
> --------------------------------------------
>
> Key: JGRP-2221
> URL: https://issues.jboss.org/browse/JGRP-2221
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.12
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 3.6.15
>
>
> Noticed when reloading the server.
> 15:58:16,189 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 68) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee: java.net.BindException: Address already in use (Bind failed)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:104)
> at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.net.BindException: Address already in use (Bind failed)
> at java.net.PlainDatagramSocketImpl.bind0(Native Method)
> at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:93)
> at java.net.DatagramSocket.bind(DatagramSocket.java:392)
> at java.net.DatagramSocket.<init>(DatagramSocket.java:242)
> at java.net.DatagramSocket.<init>(DatagramSocket.java:299)
> at org.jgroups.util.DefaultSocketFactory.createDatagramSocket(DefaultSocketFactory.java:62)
> at org.jgroups.protocols.TUNNEL.init(TUNNEL.java:142)
> at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861)
> at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:831)
> at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:108)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:102)
> ... 5 more
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-9377) Reloading fails with BindException when TUNNEL protocol is configured with socket-binding
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-9377:
------------------------------------
Summary: Reloading fails with BindException when TUNNEL protocol is configured with socket-binding
Key: WFLY-9377
URL: https://issues.jboss.org/browse/WFLY-9377
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 11.0.0.CR1
Reporter: Radoslav Husar
Assignee: Radoslav Husar
{noformat}
15:58:16,189 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool – 68) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee: java.net.BindException: Address already in use (Bind failed)
at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:104)
at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.net.BindException: Address already in use (Bind failed)
at java.net.PlainDatagramSocketImpl.bind0(Native Method)
at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:93)
at java.net.DatagramSocket.bind(DatagramSocket.java:392)
at java.net.DatagramSocket.<init>(DatagramSocket.java:242)
at java.net.DatagramSocket.<init>(DatagramSocket.java:299)
at org.jgroups.util.DefaultSocketFactory.createDatagramSocket(DefaultSocketFactory.java:62)
at org.jgroups.protocols.TUNNEL.init(TUNNEL.java:142)
at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861)
at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:831)
at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:108)
at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:102)
... 5 more
{noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JGRP-2221) TUNNEL does not close its sock in #destroy()
by Radoslav Husar (JIRA)
Radoslav Husar created JGRP-2221:
------------------------------------
Summary: TUNNEL does not close its sock in #destroy()
Key: JGRP-2221
URL: https://issues.jboss.org/browse/JGRP-2221
Project: JGroups
Issue Type: Bug
Affects Versions: 3.6.12
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Noticed when reloading the server.
15:58:16,189 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 68) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee: java.net.BindException: Address already in use (Bind failed)
at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:104)
at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.net.BindException: Address already in use (Bind failed)
at java.net.PlainDatagramSocketImpl.bind0(Native Method)
at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:93)
at java.net.DatagramSocket.bind(DatagramSocket.java:392)
at java.net.DatagramSocket.<init>(DatagramSocket.java:242)
at java.net.DatagramSocket.<init>(DatagramSocket.java:299)
at org.jgroups.util.DefaultSocketFactory.createDatagramSocket(DefaultSocketFactory.java:62)
at org.jgroups.protocols.TUNNEL.init(TUNNEL.java:142)
at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861)
at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:831)
at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:108)
at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:102)
... 5 more
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JASSIST-269) javassist.CannotCompileException: by java.lang.LinkageError when Application deployment on Java 8 Server
by vinay kp (JIRA)
[ https://issues.jboss.org/browse/JASSIST-269?page=com.atlassian.jira.plugi... ]
vinay kp updated JASSIST-269:
-----------------------------
Description:
With javassit 3.12.0.GA and JDK 1.6 , I can able to deploy .EAR application successfully . After changing to *Java 8 support* with * javassit 3.19.0-GA* , i am getting some_ IllegalStateException: javassist.CannotCompileException: by java.lang.LinkageError_
Please find the attached error log . I tried different scenarios to solve this problem like .
* Changing parent class first /last property .
* I have added asm , cglib dependency in POM,xml file .
I think this is due to class loader issue . Can you please check this ?
was:
With javassit 3.12.0.GA and JDK 1.6 , I can able to deploy .EAR application successfully . After changing to *Java 8 support* with * javassit 3.19.0-GA* , i am getting some_ IllegalStateException: javassist.CannotCompileException: by java.lang.LinkageError_
Please find the attached error log . I tried different scenarios to solve this problem like
* Changing parent class first /last property
* I have added asm , cglib dependency in POM,xml file
I think this is due to class loader issue . Can you please check this ?
> javassist.CannotCompileException: by java.lang.LinkageError when Application deployment on Java 8 Server
> --------------------------------------------------------------------------------------------------------
>
> Key: JASSIST-269
> URL: https://issues.jboss.org/browse/JASSIST-269
> Project: Javassist
> Issue Type: Bug
> Affects Versions: 3.19.0-GA
> Environment: JDK 8 , Java 8
> Reporter: vinay kp
> Assignee: Shigeru Chiba
> Priority: Critical
> Attachments: error_logs.txt, java file.txt
>
>
> With javassit 3.12.0.GA and JDK 1.6 , I can able to deploy .EAR application successfully . After changing to *Java 8 support* with * javassit 3.19.0-GA* , i am getting some_ IllegalStateException: javassist.CannotCompileException: by java.lang.LinkageError_
> Please find the attached error log . I tried different scenarios to solve this problem like .
> * Changing parent class first /last property .
> * I have added asm , cglib dependency in POM,xml file .
> I think this is due to class loader issue . Can you please check this ?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months