January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2898) Broken JGroups in clustering RuntimeException: class for magic number 22551 not found

by Radoslav Husar (Created) (JIRA)

Broken JGroups in clustering RuntimeException: class for magic number 22551 not found ------------------------------------------------------------------------------------- Key: AS7-2898 URL: https://issues.jboss.org/browse/AS7-2898 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: No Release Environment: eaebc8a0041e2c7bd9b7de93ea2d2bf87701abff Reporter: Radoslav Husar Assignee: Paul Ferraro {code} [JBossINF] 09:28:49,124 SEVERE [org.jgroups.protocols.UDP] (Incoming-9,null) failed handling incoming message: java.lang.RuntimeException: class for magic number 22551 not found [JBossINF] at org.jgroups.util.Util.readOtherAddress(Util.java:847) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.util.Util.readAddress(Util.java:811) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.util.Util.readAddresses(Util.java:896) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.protocols.pbcast.GMS$GmsHeader.readFrom(GMS.java:1163) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.Message.readHeader(Message.java:837) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.Message.readFrom(Message.java:727) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.protocols.TP.readMessage(TP.java:1326) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1690) [jgroups-3.0.0.Final.jar:] [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29] [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29] [JBossINF] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29] [JBossINF] [JBossINF] 09:28:55,674 WARNING [org.jgroups.protocols.pbcast.NAKACK] (Incoming-11,null) perf20/web: dropped message 1 from perf21/web (sender not in table [perf20/web, perf01/web, perf03/web]), view=[perf01/web|12] [perf01/web, perf03/web, perf20/web] [JBossINF] 09:28:56,666 SEVERE [org.jgroups.protocols.UDP] (OOB-18,null) failed handling incoming message: java.io.IOException: length has to be 4 or 16 bytes (was 1 bytes) [JBossINF] at org.jgroups.stack.IpAddress.readFrom(IpAddress.java:190) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.util.Util.readAddress(Util.java:808) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.util.Util.readAddresses(Util.java:896) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.protocols.PingData.readFrom(PingData.java:162) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.util.Util.readStreamable(Util.java:936) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.protocols.PingHeader.readFrom(PingHeader.java:88) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.Message.readHeader(Message.java:837) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.Message.readFrom(Message.java:727) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.protocols.TP.readMessage(TP.java:1326) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1690) [jgroups-3.0.0.Final.jar:] [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29] [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29] [JBossINF] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29] [JBossINF] [JBossINF] 09:28:56,666 SEVERE [org.jgroups.protocols.UDP] (OOB-17,null) failed handling incoming message: java.io.IOException: length has to be 4 or 16 bytes (was 1 bytes) [JBossINF] at org.jgroups.stack.IpAddress.readFrom(IpAddress.java:190) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.util.Util.readAddress(Util.java:808) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.util.Util.readAddresses(Util.java:896) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.protocols.PingData.readFrom(PingData.java:162) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.util.Util.readStreamable(Util.java:936) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.protocols.PingHeader.readFrom(PingHeader.java:88) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.Message.readHeader(Message.java:837) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.Message.readFrom(Message.java:727) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.protocols.TP.readMessage(TP.java:1326) [jgroups-3.0.0.Final.jar:] [JBossINF] at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1690) [jgroups-3.0.0.Final.jar:] [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29] [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29] [JBossINF] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29] {code} -- 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

12 years, 8 months

5
5
0 / 0

[JBoss JIRA] (JGRP-1418) Avoid outoboxing on org.jgroups.stack.AckSenderWindow.get(long)

by Sanne Grinovero (JIRA)

Sanne Grinovero created JGRP-1418: ------------------------------------- Summary: Avoid outoboxing on org.jgroups.stack.AckSenderWindow.get(long) Key: JGRP-1418 URL: https://issues.jboss.org/browse/JGRP-1418 Project: JGroups Issue Type: Enhancement Reporter: Sanne Grinovero Assignee: Bela Ban In certain scenarios the org.jgroups.stack.AckSenderWindow.get(long) method is invoked frequently, and each long is converted in a Long, becoming an allocation hotspot. I'm wondering if the ConcurrentNavigableMap used in AckSenderWindow could be converted in a more primitive-friendly collection. -- 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

12 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-8135) By default use a common identifier anywhere a server "id" notion is exposed in the configuration

by Brian Stansberry (JIRA)

By default use a common identifier anywhere a server "id" notion is exposed in the configuration ------------------------------------------------------------------------------------------------ Key: JBAS-8135 URL: https://jira.jboss.org/browse/JBAS-8135 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.M1 This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: >> * JBoss Transactions, jvm-route, jboss messaging all require a >> unique identifier for them to behave properly in a clustered >> environment. I would like one unique identifier for each server >> configuration and for all services that need a unique identifier >> to reference it by default. Then I don't have to worry about >> unique identifiers when creating new servers. (The jboss messaging bit is out of date with respect to AS 7, which will use HornetQ and thus has no ServerPeerId configuration required. But the basic point is spot-on.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
14
0 / 0

[JBoss JIRA] (AS7-2604) Http API : jndi-view and dump-services operations showing errors, browser waiting indefinitely - need to return a proper error message

by Vimal Kansal (Created) (JIRA)

Http API : jndi-view and dump-services operations showing errors, browser waiting indefinitely - need to return a proper error message -------------------------------------------------------------------------------------------------------------------------------------- Key: AS7-2604 URL: https://issues.jboss.org/browse/AS7-2604 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Vimal Kansal Assignee: Brian Stansberry Yes please report this as a bug that we do not return a proper error message. As to custom operations, for security reasons we have to make sure that GET can never mutate production state, since browsers operate on that assumption. For this reason we have limited GET to our universal read operations, and do not have support for custom operations. We could support an arbitrary runtime operation, but only IF we had a special flag that reported it as being read-only. On 11/11/11 3:01 AM, Vimal Kansal wrote: > So you mean to say, if I try executing a subsystem specific > operation(i.e a get) on any other subsystem, I should get a similar > error? Moreover, even with this jndi-view operation, browser just seems > to be waiting for response to come back, it does not show any error > message. I think we need a clear indication of what is supported and > what is not supported. In our doc also we should try to clarify it that > Http API is not an exact replica of what we can achieve through CLI. > Ideally I would have loved to be able to do whatever I can do with CLI. > > On 11/11/2011 7:20 PM, Darran Lofthouse wrote: >> Yes I don't think this is invalid, although I do see some problems >> regarding how we could implement this. At the moment it is literally >> just the global operations that we allow to be called but operations >> like this are subsystem specific. >> >> Maybe get a feature request raised for this to be further considered. >> >> Regards, >> Darran Lofthouse. >> >> >> On 11/11/2011 08:15 AM, Vimal Kansal wrote: >>> Thanks Darran. Semantically, don't you think dump-services is really a >>> get(i.e read) operation? >>> >>> On 11/11/2011 7:13 PM, Darran Lofthouse wrote: >>>> Hi Vimal, >>>> >>>> Using GET requests only a small subset of the read only operations are >>>> available, this operation would need to be invoked as a POST request >>>> from an external client. >>>> >>>> Regards, >>>> Darran Lofthouse. >>>> >>>> >>>> On 11/11/2011 04:20 AM, Vimal Kansal wrote: >>>>> Hi, >>>>> >>>>> I am trying to use Http API to display the JNDI view (which I am ble to >>>>> get via CLI alright) by pointing my browser as >>>>> http://localhost:9990/management/subsystem/naming?operation=jndi-view >>>>> and I get the following error : >>>>> >>>>> 15:16:53,086 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> Exception in thread "HttpManagementService-threads - 1" >>>>> java.lang.ExceptionInInitializerError >>>>> 15:16:53,087 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> at >>>>> org.jboss.as.domain.http.server.DomainApiHandler.convertGetRequest(DomainApiHandler.java:422) >>>>> 15:16:53,088 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> at >>>>> org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:263) >>>>> 15:16:53,089 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> at >>>>> org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:191) >>>>> 15:16:53,091 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) >>>>> 15:16:53,093 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:69) >>>>> 15:16:53,095 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81) >>>>> 15:16:53,096 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> at >>>>> org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:689) >>>>> 15:16:53,097 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) >>>>> 15:16:53,098 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:661) >>>>> 15:16:53,099 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >>>>> 15:16:53,100 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >>>>> 15:16:53,101 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> at java.lang.Thread.run(Thread.java:662) >>>>> 15:16:53,102 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> at org.jboss.threads.JBossThread.run(JBossThread.java:122) >>>>> 15:16:53,103 ERROR [stderr] (HttpManagementService-threads - 1) Caused >>>>> by: java.lang.IllegalArgumentException: Invalid bundle interface >>>>> org.jboss.as.domain.http.server.HttpServerMessages (implementati >>>>> on not found) >>>>> 15:16:53,103 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> at org.jboss.logging.Messages.getBundle(Messages.java:81) >>>>> 15:16:53,104 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> at org.jboss.logging.Messages.getBundle(Messages.java:46) >>>>> 15:16:53,105 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> at >>>>> org.jboss.as.domain.http.server.HttpServerMessages.<clinit>(HttpServerMessages.java:39) >>>>> 15:16:53,106 ERROR [stderr] (HttpManagementService-threads - 1) >>>>> ... 13 more >>>>> >>>>> Thx >>>>> >>>>> Vimal >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> jboss-as7-dev mailing list >>>>> jboss-as7-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >>>> _______________________________________________ >>>> jboss-as7-dev mailing list >>>> jboss-as7-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >>> _______________________________________________ >>> jboss-as7-dev mailing list >>> jboss-as7-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev -- Jason T. Greene JBoss AS Lead / EAP Platform Architect JBoss, a division of Red Hat -- 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

12 years, 8 months

4
5
0 / 0

[JBoss JIRA] (AS7-3453) Upgrade JBoss Marshalling to 1.3.6.GA

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-3453: --------------------------------- Summary: Upgrade JBoss Marshalling to 1.3.6.GA Key: AS7-3453 URL: https://issues.jboss.org/browse/AS7-3453 Project: Application Server 7 Issue Type: Component Upgrade Affects Versions: 7.1.0.CR1b Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.0.Final -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-3452) Merge MemberListProducer.java and MemberResourceRESTService.java in the EE6 archetypes

by Burr Sutter (JIRA)

Burr Sutter created AS7-3452: -------------------------------- Summary: Merge MemberListProducer.java and MemberResourceRESTService.java in the EE6 archetypes Key: AS7-3452 URL: https://issues.jboss.org/browse/AS7-3452 Project: Application Server 7 Issue Type: Feature Request Reporter: Burr Sutter Assignee: Pete Muir The current implementation contains some very similar code like listAllMembers vs retrieveAllMembersOrderedByName. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1168) improve ds management operation test suite

by Stefano Maestri (JIRA)

improve ds management operation test suite ------------------------------------------ Key: AS7-1168 URL: https://issues.jboss.org/browse/AS7-1168 Project: Application Server 7 Issue Type: Task Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1204) test for properties exception sorter, valid & stale connection checkers aren't stored

by Stefano Maestri (JIRA)

test for properties exception sorter, valid & stale connection checkers aren't stored ------------------------------------------------------------------------------------- Key: AS7-1204 URL: https://issues.jboss.org/browse/AS7-1204 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Stefano Maestri Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
4
0 / 0

[JBoss JIRA] (AS7-2124) Fix or remove ignored RAR smoke tests

by Thomas Diesler (Created) (JIRA)

Fix or remove ignored RAR smoke tests -------------------------------------- Key: AS7-2124 URL: https://issues.jboss.org/browse/AS7-2124 Project: Application Server 7 Issue Type: Sub-task Reporter: Thomas Diesler Assignee: Stefano Maestri Fix For: 7.1.0.Beta1 -- 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

12 years, 8 months

6
6
0 / 0

[JBoss JIRA] (AS7-2440) Removing logging handlers should verify the handler is not assigned to a logger

by James Perkins (Created) (JIRA)

Removing logging handlers should verify the handler is not assigned to a logger ------------------------------------------------------------------------------- Key: AS7-2440 URL: https://issues.jboss.org/browse/AS7-2440 Project: Application Server 7 Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 7.1.0.Beta1 If the logging handler is assigned to a logger an error should be raised. -- 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

12 years, 8 months

4
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012