[JBoss JIRA] (JASSIST-162) Correction introduced in JASSIST-127 raises AbstractMethodError on call site
by Brice Dutheil (JIRA)
Brice Dutheil created JASSIST-162:
-------------------------------------
Summary: Correction introduced in JASSIST-127 raises AbstractMethodError on call site
Key: JASSIST-162
URL: https://issues.jboss.org/browse/JASSIST-162
Project: Javassist
Issue Type: Bug
Affects Versions: 3.16.1-GA
Environment: OSX, JDK 1.6.0_29
Reporter: Brice Dutheil
Assignee: Shigeru Chiba
The proposed solution in JASSIST-127 doesn't work, the JVM raises an {{AbstractMethodError}} on the call site.
What happen is that in {{getMethods}} the code now discard method with same name / same arguments as the return type is not taken into account when generating the key.
Reverting this patch will raises a {{DuplicateMemberException}}, the reason is that {{ClassFile.isDuplicated}} don't see either of the possible duplicate method as bridge.
I've created a patch that detect methods with covariant type and mark forwarding methods as bridge if relevant.
Note that the effect is only for method calls that have the very same arguments, as Javassist don't see duplicate methods if the arguments differ, e.g. proxying ({{StringList extends List<String>}}) will see {{add(Object)}} and {{add(String)}}, though the first one is not marked as bridge in the generated bytecode.
Also, I'm not sure of that one, but the patch also adds a boolean to enable the {{MethodHandler}} to intercept bridge methods.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (AS7-4200) NPE in CoreGroupCommunicationService$ClusterNodeFactoryImpl.getClusterNode()
by Paul Ferraro (JIRA)
Paul Ferraro created AS7-4200:
---------------------------------
Summary: NPE in CoreGroupCommunicationService$ClusterNodeFactoryImpl.getClusterNode()
Key: AS7-4200
URL: https://issues.jboss.org/browse/AS7-4200
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.1.Final, 7.1.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 7.1.2.Final
2012/03/15 13:17:24,568 INFO
[org.jboss.as.clustering.impl.CoreGroupCommunicationService.web]
(VERIFY_SUSPECT.TimerThread,web,c9fc3ab485-bdecoste8.dev.rhcloud.com/web) JBAS010254:
Suspected member: 7c4425909e-bdecoste8.dev.rhcloud.com/web
2012/03/15 13:17:25,327 ERROR
[org.jboss.as.clustering.impl.CoreGroupCommunicationService.web]
(Incoming-6,null) JBAS010245: ViewAccepted failed:
java.lang.NullPointerException
at
org.jboss.as.clustering.impl.CoreGroupCommunicationService$ClusterNodeFactoryImpl.getClusterNode(CoreGroupCommunicationService.java:1643)
[jboss-as-clustering-impl-7.1.0.Final.jar:7.1.0.Final]
at
org.jboss.as.clustering.impl.CoreGroupCommunicationService.translateAddresses(CoreGroupCommunicationService.java:1268)
[jboss-as-clustering-impl-7.1.0.Final.jar:7.1.0.Final]
at
org.jboss.as.clustering.impl.CoreGroupCommunicationService$GroupView.<init>(CoreGroupCommunicationService.java:1359)
[jboss-as-clustering-impl-7.1.0.Final.jar:7.1.0.Final]
at
org.jboss.as.clustering.impl.CoreGroupCommunicationService.processViewChange(CoreGroupCommunicationService.java:1168)
[jboss-as-clustering-impl-7.1.0.Final.jar:7.1.0.Final]
at
org.jboss.as.clustering.impl.CoreGroupCommunicationService$MembershipListenerImpl.viewAccepted(CoreGroupCommunicationService.java:1717)
[jboss-as-clustering-impl-7.1.0.Final.jar:7.1.0.Final]
at
org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUpEvent(MessageDispatcher.java:506)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at
org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:545)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at
org.jboss.as.clustering.jgroups.ClassLoaderAwareUpHandler.up(ClassLoaderAwareUpHandler.java:56)
[jboss-as-clustering-jgroups-7.1.0.Final.jar:7.1.0.Final]
at
org.jgroups.blocks.mux.MuxUpHandler.passToAllHandlers(MuxUpHandler.java:156)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.blocks.mux.MuxUpHandler.up(MuxUpHandler.java:123)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at
org.jboss.as.clustering.jgroups.MuxChannel$ClassLoaderAwareMuxUpHandler.up(MuxChannel.java:64)
[jboss-as-clustering-jgroups-7.1.0.Final.jar:7.1.0.Final]
at org.jgroups.JChannel.up(JChannel.java:716)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1026)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.protocols.FRAG2.up(FRAG2.java:181)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.protocols.FlowControl.up(FlowControl.java:418)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.protocols.FlowControl.up(FlowControl.java:418)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.protocols.pbcast.GMS.installView(GMS.java:625)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at
org.jgroups.protocols.pbcast.CoordGmsImpl.handleViewChange(CoordGmsImpl.java:247)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.protocols.pbcast.GMS.up(GMS.java:784)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:244)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.protocols.UNICAST2.up(UNICAST2.java:383)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at
org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:730)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:559)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.protocols.BARRIER.up(BARRIER.java:126)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:140)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.protocols.FD.up(FD.java:273)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.protocols.MERGE2.up(MERGE2.java:205)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.protocols.Discovery.up(Discovery.java:354)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.stack.Protocol.up(Protocol.java:358)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.protocols.TP.passMessageUp(TP.java:1174)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at org.jgroups.protocols.TP$4.run(TP.java:1097)
[jgroups-3.0.4.Final.jar:3.0.4.Final]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[rt.jar:1.6.0_22]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[rt.jar:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_22]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (AS7-4140) Change distribution of -Dmcast through testsuite
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/AS7-4140?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar updated AS7-4140:
--------------------------------
Summary: Change distribution of -Dmcast through testsuite (was: Change distributtion of -Dmcast through testsuite)
> Change distribution of -Dmcast through testsuite
> ------------------------------------------------
>
> Key: AS7-4140
> URL: https://issues.jboss.org/browse/AS7-4140
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Test Suite
> Affects Versions: 7.1.1.Final
> Reporter: Pavel Janousek
> Assignee: Ondrej Zizka
> Priority: Blocker
> Fix For: 7.1.2.Final
>
>
> Please change present behavior.
> We need to define only one property -Dmcast (for ex., the name doesn't matter now) as command line parameter - this multicast address is needed to be distributed to every subsystem which manages any multicast communication. It is needed to be unique in every subsystem - JGroups, HornetQ etc. because we must avoid to interfere each other => port assignation must be unique for every a such component.
> This change is needed in both - IPV4 and IPv6...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month