April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9254) Crashed/killed server not detected

by Heiko Rupp (JIRA)

Crashed/killed server not detected ----------------------------------- Key: JBAS-9254 URL: https://issues.jboss.org/browse/JBAS-9254 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Reporter: Heiko Rupp Start domain mode. This brings up server-one and -two and -three as disabled. Kill from the shell server-two hrupp 56191 0,1 1,0 1058416 81580 s003 S+ 11:50am 0:54.69 /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java -Xms64m -Xmx256m -Dorg.jboss.boot.log.file=domain/servers/server-two/log/boot.log -Dlogging.configuration=file:/devel/jbas7/jboss-as/build/target/jboss-7.0.0.Beta3-SNAPSHOT/domain/configuration/logging.properties -jar jboss-modules.jar -mp modules -logmodule org.jboss.logmanager -jaxpmodule javax.xml.jaxp-provider org.jboss.as.server snert:/im/rhq/modules/plugins/jboss-as-7 hrupp$ kill 56191 snert:/im/rhq/modules/plugins/jboss-as-7 hrupp$ ps auxw|grep server-two snert:/im/rhq/modules/plugins/jboss-as-7 hrupp$ Hostcontroller log shows: [Server:server-two] 16:39:29,310 INFO [org.jboss.as.logging] (MSC service thread 1-1) Restored bootstrap log handlers [Server:server-two] 16:39:29,314 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) Removed JDBC Data-source [java:/H2DS] [Server:server-two] 16:39:29,315 ERROR [org.jboss.as.management] (Read thread for /0.0.0.0:9999) java.net.SocketException: Socket closed [Server:server-two] 16:39:29,317 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-2) ARJUNA-32018 Destroying TransactionManagerService [Server:server-two] 16:39:29,317 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-2) ARJUNA-32014 Stopping transaction recovery manager [Server:server-two] 16:39:29,317 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-4) JMX remote connector stopped [Server:server-two] 16:39:29,326 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) HornetQ Server version 2.1.2.Final (Colmeia, 120) stopped [Server:server-two] 16:39:29,328 INFO [org.jboss.as] (MSC service thread 1-2) JBoss AS 7.0.0.Beta3-SNAPSHOT "TBD" stopped in 30ms 16:39:29,661 INFO [org.jboss.as.process.Server:server-two.status] (reaper for Server:server-two) Process 'Server:server-two' finished with an exit status of 143 Now go to e.g. the CLI [localhost:9999 /] cd /host=local/server-config=server-two [localhost:9999 server-two] :read-attribute(name=status) { "outcome" => "success", "result" => "STARTED", "compensating-operation" => undefined } Note that the server is still considered as running. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
1
0 / 0

[JBoss JIRA] Deleted: (JGRP-140) Backwards compatibility for marshalling

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-140?page=com.atlassian.jira.plugin.s... ] Bela Ban deleted JGRP-140: -------------------------- > Backwards compatibility for marshalling > --------------------------------------- > > Key: JGRP-140 > URL: https://issues.jboss.org/browse/JGRP-140 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > > New versions of JGroups are backwards-compatible to previous versions. > Solution: > - Maintain a hashmap of version numbers (keys) with Marshallers (values), e.g. > 2.2.7: Marshaller-2.2.7 > 2.2.8: Marshaller-2.2.8 > 2.2.9: Marshaller-2.2.9 > We send with each msg a version ID (this is done already). The version ID is the lookup key for unmarshalling a message, so we fetch the right Marsaller -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Deleted: (JGRP-43) Use persistent storage to store results of initial discovery

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-43?page=com.atlassian.jira.plugin.sy... ] Bela Ban deleted JGRP-43: ------------------------- > Use persistent storage to store results of initial discovery > ------------------------------------------------------------ > > Key: JGRP-43 > URL: https://issues.jboss.org/browse/JGRP-43 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Deleted: (JGRP-81) Look into Apache APR to use in transport protocols (UDP, TCP)

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-81?page=com.atlassian.jira.plugin.sy... ] Bela Ban deleted JGRP-81: ------------------------- > Look into Apache APR to use in transport protocols (UDP, TCP) > ------------------------------------------------------------- > > Key: JGRP-81 > URL: https://issues.jboss.org/browse/JGRP-81 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > > Potential speedup. Mladen is thinking about porting java.net to APR, then we would just need to prepend the LD_LIBRARY_PATH with apx.so > Email from Mladen: > Couple of extra notes... > With additional transport protocols (NT pipes and unix domain sockets) > beside standard TCP you can also use additional interface that > can take a NIO direct ByteBuffers. > Only that gives the 5-10% overall speed improvement over > standard implementation, because it lowers the JNI function > calls compared with standard java.net > Also since the JGroups is mostly packet based, having a poller > for input events will give you the chance to lower the worker > thread count, without the need to change the entire processing > logic to NIO bullshit. For example APR/AJP protocol in JBossWeb > can easily handle 10000 connections with only 100 threads with > negligible performance impact. > When you guys are ready to dig into APR, I'll help you with > the implementation and API usage. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Deleted: (JGRP-98) Bounded retransmission time for NAKACK

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-98?page=com.atlassian.jira.plugin.sy... ] Bela Ban deleted JGRP-98: ------------------------- > Bounded retransmission time for NAKACK > -------------------------------------- > > Key: JGRP-98 > URL: https://issues.jboss.org/browse/JGRP-98 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > > Guarantee a max time after which a message must be delivered. If it was lost, and > we can't get a retransmission within n milliseconds, simply discard the message. > ==> This changes the usual QoS guarantees in that message gaps (lost msgs) are now alllowed -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Deleted: (JGRP-134) Emission of JMX notifications on membership changes

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-134?page=com.atlassian.jira.plugin.s... ] Bela Ban deleted JGRP-134: -------------------------- > Emission of JMX notifications on membership changes > --------------------------------------------------- > > Key: JGRP-134 > URL: https://issues.jboss.org/browse/JGRP-134 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Vladimir Blagojevic > > Moved to 2.x -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Deleted: (JGRP-1197) ConnectionTable: trash it

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1197?page=com.atlassian.jira.plugin.... ] Bela Ban deleted JGRP-1197: --------------------------- > ConnectionTable: trash it > ------------------------- > > Key: JGRP-1197 > URL: https://issues.jboss.org/browse/JGRP-1197 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > > This class isn't used anymore; we use ConnectionMap instead -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1046) FC: change semantics of min_threshold

by Bela Ban (JIRA)

FC: change semantics of min_threshold ------------------------------------- Key: JGRP-1046 URL: https://jira.jboss.org/jira/browse/JGRP-1046 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 FC.max_credits=1000000,min_threshold=0.2: This means that when a receiver's credits for a sender drop below 800'000 bytes, the receiver will send 200'000 bytes to the sender. This can be misleading because one might think min_threshold means the number of bytes *remaining* after which to send new credits. We need to either change the semantics of min_threshold, or introduce a new property. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] Deleted: (JGRP-930) Provide hooks for scopes

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-930?page=com.atlassian.jira.plugin.s... ] Bela Ban deleted JGRP-930: -------------------------- > Provide hooks for scopes > ------------------------ > > Key: JGRP-930 > URL: https://issues.jboss.org/browse/JGRP-930 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > > Just implement the scope field in a Message (a header?) and provide the impl later -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Deleted: (JGRP-905) PING: remove gossip_host/port

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-905?page=com.atlassian.jira.plugin.s... ] Bela Ban deleted JGRP-905: -------------------------- > PING: remove gossip_host/port > ----------------------------- > > Key: JGRP-905 > URL: https://issues.jboss.org/browse/JGRP-905 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Vladimir Blagojevic > > This is redundant functionality: gossip_host/gossip_port can be replaced by using TCPGOSSIP -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2011