May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Deleted: (JBMESSAGING-967) Clustered EJB SmokeTest/Example

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-967?page=all ] Clebert Suconic deleted JBMESSAGING-967: ---------------------------------------- > Clustered EJB SmokeTest/Example > ------------------------------- > > Key: JBMESSAGING-967 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-967 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Clebert Suconic > Assigned To: Clebert Suconic > > We should create a smoke test using a clustered ejb > a) Deploy stateless clustered ejb into farm > b) Deploy clustered queue/topic into farm > c) invoke method on ejb. this causes a message to be send to destination > d) Consume message from destination - verify is received > e) The example should use HAJNDI to lookup ejb and destination -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-967) Clustered EJB SmokeTest/Example

by Clebert Suconic (JIRA)

Clustered EJB SmokeTest/Example ------------------------------- Key: JBMESSAGING-967 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-967 Project: JBoss Messaging Issue Type: Feature Request Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.2.0.SP2 -- 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

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-706) Editor widgets to report "dirty" flat when editied

by Michael Neale (JIRA)

Editor widgets to report "dirty" flat when editied -------------------------------------------------- Key: JBRULES-706 URL: http://jira.jboss.com/jira/browse/JBRULES-706 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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

19 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBFORUMS-233) Clear up sources from useless files

by Ryszard Kozmik (JIRA)

Clear up sources from useless files ----------------------------------- Key: JBFORUMS-233 URL: http://jira.jboss.com/jira/browse/JBFORUMS-233 Project: JBoss Forums Issue Type: Task Components: Portlet Productization Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.0 GA, 1.0.1 RC There are quite many files that are no longer used, like JSPs, template files etc. Those need to be removed. -- 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

19 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBFORUMS-204) building sources

by Luca Stancapiano (JIRA)

building sources ---------------- Key: JBFORUMS-204 URL: http://jira.jboss.com/jira/browse/JBFORUMS-204 Project: JBoss Forums Issue Type: Bug Components: Portlet Productization Affects Versions: 1.0.0 RC Environment: all Reporter: Luca Stancapiano Assigned To: Ryszard Kozmik Fix For: 1.0.0 GA hi......I try to build sources of forums applicattion (taken from http://anonsvn.labs.jboss.com/labs/jbossforums/trunk). Apparently it is ok but when I deploy jboss-forums.ear, I have the error that portal-forums-authz-plugin.sar is lost. Inside jboss-forums.ear infact it is not added. I added in build.xml row 162 of authz-jaae-plugin project theese rows: <copy todir="${forums.root}/resources/portal-forums-ear"> <fileset dir="${authz-jaae-plugin.lib}" includes="portal-forums-authz-plugin.sar"/> </copy> <jar jarfile="${forums.lib}/jboss-forums.ear"> <fileset dir="${forums.root}/resources/portal-forums-ear" includes="**/*"/> </jar> so, when target output of forums is executed, portal-forums-authz-plugin.sar is added automatically into jboss-forums.ear -- 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

19 years, 2 months

2
9
0 / 0

[JBoss JIRA] Created: (JGRP-516) UDP: mcast_sock is not binding to bind_addr for reception of packets

by Bela Ban (JIRA)

UDP: mcast_sock is not binding to bind_addr for reception of packets -------------------------------------------------------------------- Key: JGRP-516 URL: http://jira.jboss.com/jira/browse/JGRP-516 Project: JGroups Issue Type: Task Affects Versions: 2.4.1 SP3, 2.4.1 SP2, 2.4.1 SP1, 2.4.1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 mcast_sock only bind to a NIC for *sending* of messages, but not for reception: it actually receives multicast packets on *all* interfaces (wildcard address 0.0.0.0). Code is UDP.createSockets(): mcast_sock=new MulticastSocket(mcast_port); We should change this to: SocketAddress saddr=new InetSocketAddress(bind_addr, mcast_port); mcast_sock=new MulticastSocket(saddr); -- 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

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBFORUMS-193) Change attachments view

by Ryszard Kozmik (JIRA)

Change attachments view ----------------------- Key: JBFORUMS-193 URL: http://jira.jboss.com/jira/browse/JBFORUMS-193 Project: JBoss Forums Issue Type: Sub-task Components: Forum View Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC Attachments view have to be rewritten to new L&F. -- 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

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-928) filter missing in hibernate mapping for ProcessDefinition

by Britt Miner (JIRA)

filter missing in hibernate mapping for ProcessDefinition --------------------------------------------------------- Key: JBPM-928 URL: http://jira.jboss.com/jira/browse/JBPM-928 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2, jBPM 3.1.2 Reporter: Britt Miner Assigned To: Tom Baeyens Symptom: processDefinition.findNode(), getNode(), getNodeList(), and getNodesMap() (basically all node related methods on ProcessDefinition) fail to properly find or return all Nodes when SuperStates are present. Cause: Hibernate mapping for ProcessDefinition does not recognize that NODEINDEXCOLLECTION_ on the jbpm_node table may have duplicated values per ProcessDefinition (members of a SuperState comprise a separate node collection in this column) and only picks up the last Node with a given NODEINDEXCOLLECTION_ value. The list-index line is the problem: <list name="nodes" cascade="all"> <cache usage="nonstrict-read-write"/> <key column="PROCESSDEFINITION_" /> <list-index column="NODECOLLECTIONINDEX_" /> <one-to-many class="org.jbpm.graph.def.Node" /> </list> Solution: Perhaps usage of a Set instead of a list would solve the problem (Sets don't use 'list-index'), or a Hibernate Bag collection would allow usage of a List in the object without the requirement of list-index (with an associated performance hit). Or perhaps some type of Hibernate filter could be used. -- 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

19 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JGRP-514) GroupRequest adjusts timeout improperly in doExecute

by Bryan Lanoue (JIRA)

GroupRequest adjusts timeout improperly in doExecute ---------------------------------------------------- Key: JGRP-514 URL: http://jira.jboss.com/jira/browse/JGRP-514 Project: JGroups Issue Type: Bug Affects Versions: 2.5 Environment: Linux/Windows Reporter: Bryan Lanoue Assigned To: Bela Ban Priority: Minor Fix For: 2.5 Attachments: GroupRequestTest.java As GroupRequests are alerted to new responses, the total timeout to receive all responses decreases. This makes GroupRequests return from execute() without waiting for all responses within the true timeout. I think this can be fixed by (in the doExecute() method ) by adding start_time = System.currentTimeMillis(); timeout_time = start_time + timeout; and replacing timeout = timeout - (System.currentTimeMillis() - start_time); with timeout = timeout_time - System.currentTimeMillis(); -- 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

19 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-364) Update wiki page(s) about snapshots and releases.

by Paul Gier (JIRA)

Update wiki page(s) about snapshots and releases. ------------------------------------------------- Key: JBBUILD-364 URL: http://jira.jboss.com/jira/browse/JBBUILD-364 Project: JBoss Build System Issue Type: Feature Request Reporter: Paul Gier Assigned To: Paul Gier Fix For: MavenBuild 2.0 Adrian brought up a few things that should be included on the wiki pages about how to release jboss projects. * the version policy (how do you decide what the next version is) * move the pom.xml onto the next release/snapshot when finished? * tagging (how the maven version relates to SVN tags) * a release cannot depend on snapshots (how to resolve when it does) * all tests must pass (QA approved release?). * all JIRA issues should be closed * JIRA needs updating to move along the released project * Notifying product support about the new release (where relevant) * Agreement from project lead The old wiki pages about releases should also be checked to see what other information should be included. -- 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

19 years, 2 months

1
2
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 May 2007