March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1148) IronJacamar 1.0.24.Final

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1148?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1148. ------------------------------------ Resolution: Done > IronJacamar 1.0.24.Final > ------------------------ > > Key: JBJCA-1148 > URL: https://issues.jboss.org/browse/JBJCA-1148 > Project: IronJacamar > Issue Type: Release > Components: Build > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.24.Final > > > Release notes: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310691&versi... -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1148) IronJacamar 1.0.24.Final

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1148: -------------------------------------- Summary: IronJacamar 1.0.24.Final Key: JBJCA-1148 URL: https://issues.jboss.org/browse/JBJCA-1148 Project: IronJacamar Issue Type: Release Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.24.Final Release notes: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310691&versi... -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1138) TransactionSynchronizer leaks memory and causes deadlocks in jacorb

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1138?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1138: ----------------------------------- Fix Version/s: (was: 1.0.24.Final) Priority: Major (was: Blocker) > TransactionSynchronizer leaks memory and causes deadlocks in jacorb > ------------------------------------------------------------------- > > Key: JBJCA-1138 > URL: https://issues.jboss.org/browse/JBJCA-1138 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.23.Final > Reporter: Andrey Smirnov > Assignee: Jesper Pedersen > > Seems like TransactionSynchronizer has been rolled back to state it was in August. I think this was caused by little typo in commit 469b4c303dd0d5c39f3476a5972556d8b9537b44 > 296: Record record = records.get(tx); > But 'records' map uses TransactionKey as key and above line should be written as > 296:TransactionKey key = new TransactionKey(tx); > 297: Record record = records.get(key); > I've checked 1.0.22 containing applied fix and mem-leaks and deadlocks are all gone -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1802) OverlappingUnicastMergeTest

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created JGRP-1802: ----------------------------------------- Summary: OverlappingUnicastMergeTest Key: JGRP-1802 URL: https://issues.jboss.org/browse/JGRP-1802 Project: JGroups Issue Type: Bug Affects Versions: 3.2.13 Environment: Solaris, RHEL Reporter: Richard Achmatowicz Assignee: Bela Ban Fix For: 3.2.13 OverlappingUnicastMergeTest does the following: - set up three channels a,b,c with the layers MERGE2, VERIFY_SUSPECT and FC removed - the receiver of each channel will look at all incoming messages: if mcast, ignore it; if unicast, add to the list of messages received - inject some new view into the channels which represents a view configuration which should be recovered from - send messages to the channels and check that the messages are received, despite the injected view OverlappingUnicastMergeTest this test is failing in a number of ways (i.e. many of the test methods are failing within the test class on multiple platforms. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1802) OverlappingUnicastMergeTest

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/JGRP-1802?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on JGRP-1802: ------------------------------------------- Here are links to some of the example failures: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-JGro... > OverlappingUnicastMergeTest > --------------------------- > > Key: JGRP-1802 > URL: https://issues.jboss.org/browse/JGRP-1802 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.13 > Environment: Solaris, RHEL > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Fix For: 3.2.13 > > > OverlappingUnicastMergeTest does the following: > - set up three channels a,b,c with the layers MERGE2, VERIFY_SUSPECT and FC removed > - the receiver of each channel will look at all incoming messages: if mcast, ignore it; if unicast, add to the list of messages received > - inject some new view into the channels which represents a view configuration which should be recovered from > - send messages to the channels and check that the messages are received, despite the injected view > OverlappingUnicastMergeTest this test is failing in a number of ways (i.e. many of the test methods are failing within the test class on multiple platforms. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3053) BootstrapImpl#bootstrap result is inherently racy

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3053?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3053: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1071934 > BootstrapImpl#bootstrap result is inherently racy > ------------------------------------------------- > > Key: WFLY-3053 > URL: https://issues.jboss.org/browse/WFLY-3053 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Reporter: David Lloyd > Assignee: Jason Greene > Fix For: 8.0.1.Final > > > The boostrap code presently installs a stability monitor and awaits stability before returning. It then probes the state of the root service. There is a window of time in which the root service may be stopped or removed, resulting in big exception traces being logged. To atomically get the result of the operation, the service container must somehow be frozen until the root service is completely read. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3053) BootstrapImpl#bootstrap result is inherently racy

by David Lloyd (JIRA)

David Lloyd created WFLY-3053: --------------------------------- Summary: BootstrapImpl#bootstrap result is inherently racy Key: WFLY-3053 URL: https://issues.jboss.org/browse/WFLY-3053 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Server Reporter: David Lloyd Assignee: Jason Greene Fix For: 8.0.1.Final The boostrap code presently installs a stability monitor and awaits stability before returning. It then probes the state of the root service. There is a window of time in which the root service may be stopped or removed, resulting in big exception traces being logged. To atomically get the result of the operation, the service container must somehow be frozen until the root service is completely read. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3051) JMX connection to remote server-instances is not happening in wildfly 8.0.0.Final in domain mode

by Rituraj Sinha (JIRA)

[ https://issues.jboss.org/browse/WFLY-3051?page=com.atlassian.jira.plugin.... ] Rituraj Sinha commented on WFLY-3051: ------------------------------------- Thanks for replying Darran ...will wait for your response ... > JMX connection to remote server-instances is not happening in wildfly 8.0.0.Final in domain mode > ------------------------------------------------------------------------------------------------ > > Key: WFLY-3051 > URL: https://issues.jboss.org/browse/WFLY-3051 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMX, Remoting > Affects Versions: 8.0.0.Final > Reporter: Rituraj Sinha > Assignee: Darran Lofthouse > Fix For: 8.0.1.Final > > > i have gone through the below link for JMX subsystem for wildfly 8 as > https://docs.jboss.org/author/display/WFLY8/JMX+subsystem+configuration > > but unable to connect to server-instances running remotely ...i have posted my question there as well and pasting it here now ... > can someone please give us the steps to configure JMX through jconsole...? > changes done on the domain.xml are the same as stated above > <subsystem xmlns="urn:jboss:domain:jmx:1.3"> > <expose-resolved-model/> > <expose-expression-model/> > <remoting-connector use-management-endpoint="false"/> > </subsystem> > <subsystem xmlns="urn:jboss:domain:jmx:1.3"> > <expose-resolved-model/> > <expose-expression-model/> > <remoting-connector use-management-endpoint="false"/> > </subsystem> > as per the jboss-as-jmx_1_3.xsd its like > <xs:attribute name="use-management-endpoint" type="xs:boolean" default="true" use="optional" > > <xs:annotation> > <xs:documentation> > If true then this connector will use the management endpoint, otherwise it will use the > remoting subsystem endpoint. > </xs:documentation> > </xs:annotation> > </xs:attribute> > now if we are making it false then it should be using the remoting endpoint ...now remoting subsystem by default uses ApplicatoinRealm > i have created application-user and password for the same but when i am trying to connect to remote server-instances its not connecting it.... > below is what i am able to connect to > service:jmx:http-remoting-jmx://remote_hostA:9990 -- > Unknown macro: {host A is where my domain_controller is running} > how can i access the server-instances running on domain_controller > Unknown macro: {there are three server_instanaces running on HostA with a port offset of 100 each} > i am trying to connect with the below url as > service:jmx:http-remoting-jmx://lremote_hostA:8180 > let me know if something is missing from my side... > Thanks -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1752) Concurrent message headers modification causes that message is never sent

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/JGRP-1752?page=com.atlassian.jira.plugin.... ] Mircea Markus updated JGRP-1752: -------------------------------- Labels: 621 (was: ) > Concurrent message headers modification causes that message is never sent > ------------------------------------------------------------------------- > > Key: JGRP-1752 > URL: https://issues.jboss.org/browse/JGRP-1752 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.1 > Reporter: Radim Vansa > Assignee: Bela Ban > Labels: 621 > Fix For: 3.4.2, 3.5 > > > Under some circumstances the TP protocol may try to add the TP header to message twice concurrently. > This happens for example when the stable message triggers retransmission while the message has been sent right now. > This may result in ArrayOutOfBoundException in Headers._putHeader and/or subsequent NullPointerException in Headers.size(). The retransmission attempt always fails, the message is never delivered. Moreover, keeping this (and possibly following) messages in the transmission table can lead to OOME. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3051) JMX connection to remote server-instances is not happening in wildfly 8.0.0.Final in domain mode

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3051?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-3051: ---------------------------------------- I have scheduled this issue so that I can investigate it further, at this point I have no further information. > JMX connection to remote server-instances is not happening in wildfly 8.0.0.Final in domain mode > ------------------------------------------------------------------------------------------------ > > Key: WFLY-3051 > URL: https://issues.jboss.org/browse/WFLY-3051 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMX, Remoting > Affects Versions: 8.0.0.Final > Reporter: Rituraj Sinha > Assignee: Darran Lofthouse > Fix For: 8.0.1.Final > > > i have gone through the below link for JMX subsystem for wildfly 8 as > https://docs.jboss.org/author/display/WFLY8/JMX+subsystem+configuration > > but unable to connect to server-instances running remotely ...i have posted my question there as well and pasting it here now ... > can someone please give us the steps to configure JMX through jconsole...? > changes done on the domain.xml are the same as stated above > <subsystem xmlns="urn:jboss:domain:jmx:1.3"> > <expose-resolved-model/> > <expose-expression-model/> > <remoting-connector use-management-endpoint="false"/> > </subsystem> > <subsystem xmlns="urn:jboss:domain:jmx:1.3"> > <expose-resolved-model/> > <expose-expression-model/> > <remoting-connector use-management-endpoint="false"/> > </subsystem> > as per the jboss-as-jmx_1_3.xsd its like > <xs:attribute name="use-management-endpoint" type="xs:boolean" default="true" use="optional" > > <xs:annotation> > <xs:documentation> > If true then this connector will use the management endpoint, otherwise it will use the > remoting subsystem endpoint. > </xs:documentation> > </xs:annotation> > </xs:attribute> > now if we are making it false then it should be using the remoting endpoint ...now remoting subsystem by default uses ApplicatoinRealm > i have created application-user and password for the same but when i am trying to connect to remote server-instances its not connecting it.... > below is what i am able to connect to > service:jmx:http-remoting-jmx://remote_hostA:9990 -- > Unknown macro: {host A is where my domain_controller is running} > how can i access the server-instances running on domain_controller > Unknown macro: {there are three server_instanaces running on HostA with a port offset of 100 each} > i am trying to connect with the below url as > service:jmx:http-remoting-jmx://lremote_hostA:8180 > let me know if something is missing from my side... > Thanks -- 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

11 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2014