January 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBUILD-544) Generate sar files directly instead of creating intermediate jar files.

by Paul Gier (JIRA)

Generate sar files directly instead of creating intermediate jar files. ----------------------------------------------------------------------- Key: JBBUILD-544 URL: https://jira.jboss.org/jira/browse/JBBUILD-544 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Assignee: Paul Gier Fix For: Maven Build - App Server (Phase 3) The assembly plugin can be used (with the jboss-packaging-maven-plugin 2.1) to generate files with a ".sar" extension. This would be better than first generating the "-sar.jar" files and then renaming, which currently happens in the varia module for example. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7591) client dir is missing profileservice-client jar

by Emanuel Muckenhuber (JIRA)

client dir is missing profileservice-client jar ----------------------------------------------- Key: JBAS-7591 URL: https://jira.jboss.org/jira/browse/JBAS-7591 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Emanuel Muckenhuber Assignee: Emanuel Muckenhuber Fix For: JBossAS-6.0.0.M2 -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMAN-94) ignore logger properties when creating meta types

by Emanuel Muckenhuber (JIRA)

ignore logger properties when creating meta types ------------------------------------------------- Key: JBMAN-94 URL: https://jira.jboss.org/jira/browse/JBMAN-94 Project: JBoss Managed Issue Type: Task Components: metatype Affects Versions: JBossMan.2.1.1.GA Reporter: Emanuel Muckenhuber Assignee: Emanuel Muckenhuber Fix For: JBossMan.2.1.1.SP1 When generating MetaTypes we should be ignoring logger properties, since this is failing in trunk when trying to serialize a composite values of a logger 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMETA-242) Allow "Singleton" session-type in ejb-jar.xml through the metadata binding classes

by jaikiran pai (JIRA)

Allow "Singleton" session-type in ejb-jar.xml through the metadata binding classes ----------------------------------------------------------------------------------- Key: JBMETA-242 URL: https://jira.jboss.org/jira/browse/JBMETA-242 Project: JBoss Metadata Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ejb Affects Versions: jboss-metadata-ejb-2.0.0-alpha-4 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: jboss-metadata-ejb-2.0.0-alpha-5 Right now, it only allows Stateless and Stateful. Using Singleton as session-type in the ejb-jar.xml leads to: Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Invalid value Singleton for {http://java.sun.com/xml/ns/javaee}session-typeType valid are [Stateful, Stateless] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREFLECT-89) AbstractClassPoolDomain.getCachedOrCreateFromPool calls getCachedOrCreateFromPoolParent unnecessarily

by Flavia Rainone (JIRA)

AbstractClassPoolDomain.getCachedOrCreateFromPool calls getCachedOrCreateFromPoolParent unnecessarily ----------------------------------------------------------------------------------------------------- Key: JBREFLECT-89 URL: https://jira.jboss.org/jira/browse/JBREFLECT-89 Project: JBoss Reflection Issue Type: Task Components: Class Pool Affects Versions: JBossReflection.2.2.0-Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: JBossReflection.2.2.0-Beta This results in overhead. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-501) JGroups demo hosted by jboss.org

by Bela Ban (JIRA)

JGroups demo hosted by jboss.org -------------------------------- Key: JGRP-501 URL: http://jira.jboss.com/jira/browse/JGRP-501 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Vladimir Blagojevic Priority: Minor Fix For: 2.5 Goal: users can download a minimal JGroups installation (either via WebStart or as an applet) and explore JGroups. The configuration would probably include TUNNEL and there would be a GossipRouter instance running, e.g. on labs.jboss.org. We could provide access to chat & whiteboard (org.jgroups.demos.wb.Whiteboard) This would also be a good test case for the new revamped GossipRouter. Plus, once we have redundant GossipRouters, we can test client failover. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (JGRP-860) GUI to test whether cluster nodes find each other ok

by Bela Ban (JIRA)

GUI to test whether cluster nodes find each other ok ---------------------------------------------------- Key: JGRP-860 URL: https://jira.jboss.org/jira/browse/JGRP-860 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 - New DiscoveryServer (GUI) which listens on a TCP socket at a given port - Then the nodes are started and connect to the DiscoveryServer via TCP - Connected nodes are shown in a listbox in the DiscoveryServer's GUI - The TCP connection between a node and the DS is the *control channel*, and is independent of JGroups (doesn't use a JGroups config) - The control channel is used to (a) register nodes and (b) send new JGroups configurations from the DS to the nodes - The GUI has 4 tabs: UDP, TCP dynamic (TCP:MPING config), TCP static (TCP:TCPPING) and External discovery (TCP:TCPGOSSIP). - Each tab has configuration specific options, e.g. for UDP we have - multicast address - multicast port - TTL - checkbox: use flush or not - checkbox: use state transfer or not - etc etc etc There are 2 actions buttons: "Discover" and "Save config". The latter saves the current configuration to a file (XML format). The "Discovery" button sends the current config to all nodes, via the control channel. Each node then creates a channel with the received config and connects to the cluster. The DiscoveryServer GUI (which also joins the same cluster) shows all nodes in a second listbox. When the number of nodes in the first and second listbox is the same, then this shows that the config works. In that case, the user can press "Save config" and use the generated config with all cluster nodes. - In case UDP doesn't work or a user wants a TCP based config from the onset, the user simply clicks on the TCP tab, fills in the required information and clicks on "Discover". - The initial config for each tab is provided by the corresponding default shipped with JGroups, e.g. UDP uses udp.xml In a second stage, we could also not just verify that the cluster can be established, but also run some perf tests over it. -- 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

16 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-903) Logical addresses: associate multiple physical addresses with one logical address

by Bela Ban (JIRA)

Logical addresses: associate multiple physical addresses with one logical address --------------------------------------------------------------------------------- Key: JGRP-903 URL: https://jira.jboss.org/jira/browse/JGRP-903 Project: JGroups Issue Type: Sub-task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 -- 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

16 years, 4 months

1
2
0 / 0

[JBoss JIRA] Assigned: (JGRP-253) List officially supported classes/API for JGroups

by Bela Ban (JIRA)

[ https://jira.jboss.org/jira/browse/JGRP-253?page=com.atlassian.jira.plugi... ] Bela Ban reassigned JGRP-253: ----------------------------- Assignee: Vladimir Blagojevic (was: Bela Ban) > List officially supported classes/API for JGroups > ------------------------------------------------- > > Key: JGRP-253 > URL: https://jira.jboss.org/jira/browse/JGRP-253 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 2.9 > > > List of APIs which are supported by JBoss, e.g. DistributedHashtable won't be supported -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-409) Channel bundling

by Bela Ban (JIRA)

Channel bundling ---------------- Key: JGRP-409 URL: http://jira.jboss.com/jira/browse/JGRP-409 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 We can distributed traffic across multiple sockets in the transport. E.g. if we have eth0 and eth1, and both are 100Mbps *full duplex*, then we should be able to send 100Mbps on eth0 and 100Mbps on eth1 *simultaneously*. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

3
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2010