July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-91) BaseBusinessClass rename

by Mark Little (JIRA)

BaseBusinessClass rename ------------------------ Key: JBESB-91 URL: http://jira.jboss.com/jira/browse/JBESB-91 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Alpha 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 Beta 1 Do we want to rename this to be something more generic (for ESB). -- 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

18 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-97) Get docs for Nagios use

by Mark Little (JIRA)

Get docs for Nagios use ----------------------- Key: JBESB-97 URL: http://jira.jboss.com/jira/browse/JBESB-97 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Alpha 1 Reporter: Mark Little Assigned To: Daniel Brum Fix For: 4.0 Beta 1 -- 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

18 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3433) Canonical paths enforced inconsistently

by Ralph Apel (JIRA)

Canonical paths enforced inconsistently --------------------------------------- Key: JBAS-3433 URL: http://jira.jboss.com/jira/browse/JBAS-3433 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-4.0.4.GA Environment: Linux/Unix Reporter: Ralph Apel Assigned To: Dimitris Andreadis DeploymentInfo objects are created with file-URLs without previously canonicalizing the file's path. If the original URL wasn't canonical (e.g. with Linux/Unix symlinks involved), this discrepancy leads to failure of at least EjbUtil's resolution of ejb-link: The URL to be searched for among DeploymentInfos by the MBeanServer is constructed from the canonicalized path, but the DeploymentInfo which should be found has a non canonical file URL (i.e. without symlinks resolved). I have been able to provisionally solve this issue by patching EjbUtil to not invoke target = Strings.toURL(ourPath); (which directly or indirectly calls getCanonicalPath()) but a particular code fragment instead. This kind of solution surely isn't the right one. IMO, as the DeploymentInfo.url field is used as a key to the DeploymentInfo collections, this key should be always unique, i.e. canonicalized. My suggestion would be to change any DeploymentInfo instantiation AND any search for DeploymentInfo instances to use canonicalized file URLs. -- 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

18 years, 1 month

2
9
0 / 0

[JBoss JIRA] Created: (JBPM-711) Provide an arbitrary identifier for stored ProcessInstances

by Ryan Campbell (JIRA)

Provide an arbitrary identifier for stored ProcessInstances ----------------------------------------------------------- Key: JBPM-711 URL: http://jira.jboss.com/jira/browse/JBPM-711 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1 Reporter: Ryan Campbell Assigned To: Tom Baeyens Fix For: jBPM 3.1.2 When a process instance is created and then saved, an id is returned. If there is a server crash before that id is returned and saved, there is no way to know if the process was created. We would like to have mapping between our own arbitrary ids for a process instance so that we can recover a process instance. ie, recreate it if it was not created successfully. -- 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

18 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-704) Manifest/Documentation of 3rd Party Jars

by Ryan Campbell (JIRA)

Manifest/Documentation of 3rd Party Jars ---------------------------------------- Key: JBPM-704 URL: http://jira.jboss.com/jira/browse/JBPM-704 Project: JBoss jBPM Issue Type: Feature Request Components: Documentation Affects Versions: jBPM 3.1 Reporter: Ryan Campbell Assigned To: Tom Baeyens Fix For: jBPM 3.1.2 Provide a listing of 3rd pary jars shipped with jBPM. -- 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

18 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-703) Incompatibility with Sybase jConnect 5.5.latest

by Ryan Campbell (JIRA)

Incompatibility with Sybase jConnect 5.5.latest ----------------------------------------------- Key: JBPM-703 URL: http://jira.jboss.com/jira/browse/JBPM-703 Project: JBoss jBPM Issue Type: Sub-task Affects Versions: jBPM 3.1 Environment: Sybase 12.5 Reporter: Ryan Campbell Assigned To: Tom Baeyens Fix For: jBPM 3.1.2 When storing data in the jBPM context with size greater than 255 bytes, the data is truncated at some point. This issue only occurs with the jConnect 5.5 drivers, and not with the jTds opensource drivers. -- 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

18 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-93) Add unit tests for processors

by Mark Little (JIRA)

Add unit tests for processors ----------------------------- Key: JBESB-93 URL: http://jira.jboss.com/jira/browse/JBESB-93 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.0 Alpha 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 Beta 1 -- 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

18 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-260) Two subgroups don't merge when one of the hosts in TCPPING(intial_hosts=...) list is not accessible

by Tomasz Skutnik (JIRA)

Two subgroups don't merge when one of the hosts in TCPPING(intial_hosts=...) list is not accessible --------------------------------------------------------------------------------------------------- Key: JGRP-260 URL: http://jira.jboss.com/jira/browse/JGRP-260 Project: JGroups Issue Type: Bug Affects Versions: 2.2.9.2 Environment: Debian GNU/Linux 2.4.27, JDK 1.5.0_05 Reporter: Tomasz Skutnik Assigned To: Bela Ban Attachments: Test1.java When I run client program (see attachment) with following command: - on host h1: $ java -cp \ jgroups-all-2.2.9.2.jar:concurrent.jar:commons-logging-1.1.jar:\ classes test.Test1 "h1" "h1[7800],h3[7800]" - on host h2: $ java -cp \ jgroups-all-2.2.9.2.jar:concurrent.jar:commons-logging-1.1.jar:\ classes test.Test1 "h2" "h1[7800],h3[7800]" And host "h3" is known (listed in /etc/hosts) but physically turned off both hosts (h1 and h2) create two disjoint groups instead of one merged group. And on host "h2" following warnings/errors are logged: 2006-07-11 08:56:07 org.jgroups.protocols.pbcast.CoordGmsImpl$MergeTask run WARNING: merge responses from subgroup coordinators <= 1 ([sender=172.16.195.131:7800, view=[172.16.195.131:7800|0] [172.16.195.131:7800], digest=172.16.195.131:7800: [0 : 5]]). Cancelling merge 2006-07-11 08:56:52 org.jgroups.protocols.pbcast.CoordGmsImpl$MergeTask run WARNING: merge responses from subgroup coordinators <= 1 ([sender=172.16.195.131:7800, view=[172.16.195.131:7800|0] [172.16.195.131:7800], digest=172.16.195.131:7800: [0 : 7]]). Cancelling merge 2006-07-11 08:57:26 org.jgroups.protocols.pbcast.CoordGmsImpl handleMergeResponse SEVERE: this.merge_id ([172.16.195.131:7800|1152601002343]) is different from merge_id ([172.16.195.131:7800|1152600957961]) 2006-07-11 08:58:24 org.jgroups.protocols.pbcast.CoordGmsImpl$MergeTask run WARNING: merge responses from subgroup coordinators <= 1 ([]). Cancelling merge 2006-07-11 08:58:24 org.jgroups.protocols.pbcast.CoordGmsImpl sendMergeCancelledMessage SEVERE: coords or merge_id == null 2006-07-11 08:58:24 org.jgroups.protocols.pbcast.CoordGmsImpl sendMergeCancelledMessage SEVERE: coords or merge_id == null ... -- 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

18 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-259) Unidentified errors with TCP/TCPPING/MERGE2 protocol stack.

by Tomasz Skutnik (JIRA)

Unidentified errors with TCP/TCPPING/MERGE2 protocol stack. ----------------------------------------------------------- Key: JGRP-259 URL: http://jira.jboss.com/jira/browse/JGRP-259 Project: JGroups Issue Type: Bug Affects Versions: 2.2.9.2 Environment: Debian GNU/Linux 2.4.27, JDK 1.5.0_05 Reporter: Tomasz Skutnik Assigned To: Bela Ban Attachments: Test1.java I've encountered connect/disconnect problems during my experiments with TCP/TCPPING/MERGE2 protocol stack. I run client program (see attachment) on 2 different hosts (witnin two VMWare virtual hosts). One of the hosts (h1) plays role of well-known host from which initial membership will be retrieved, the other plays role of plain client. I use following command lines to run client programs: - on host h1: $ java -cp \ jgroups-all-2.2.9.2.jar:concurrent.jar:commons-logging-1.1.jar:\ classes test.Test1 "h1" "h1[7800]" - on host h2 $ java -cp \ jgroups-all-2.2.9.2.jar:concurrent.jar:commons-logging-1.1.jar:\ classes test.Test1 "h2" "h1[7800]" When I run client programs in h1, h2 order everyting works fine. But if I run them in h2, h1 order, or if I kill h1 and then rerun it something weird happens: merge of two disjoint groups happens (MergeView is transmitted), but then followin exception occurs: 2006-07-10 12:01:32 org.jgroups.Message readHeader SEVERE: magic number 306192 is not available in magic map 2006-07-10 12:01:32 org.jgroups.protocols.TP handleIncomingPacket SEVERE: failed unmarshalling message java.io.IOException: failed read header: java.lang.NullPointerException at org.jgroups.Message.readHeader(Message.java:697) at org.jgroups.Message.readFrom(Message.java:614) at org.jgroups.protocols.TP.bufferToMessage(TP.java:974) at org.jgroups.protocols.TP.handleIncomingPacket(TP.java:830) at org.jgroups.protocols.TP.receive(TP.java:781) at org.jgroups.protocols.TCP.receive(TCP.java:226) at org.jgroups.blocks.ConnectionTable.receive(ConnectionTable.java:471) at org.jgroups.blocks.ConnectionTable$Connection.run(ConnectionTable.java:813) at java.lang.Thread.run(Thread.java:595) Because there's no magic number in magic map (whatever that means) it causes NPE within org.jgroups.Message class (line 687). >From now on everything is going downhill - jgroups logs infinite stream of retransmition errors, e.g.: SEVERE: magic number 306192 is not available in magic map 2006-07-10 12:01:54 org.jgroups.protocols.pbcast.NAKACK handleXmitRsp SEVERE: message did not contain a list (LinkedList) of retransmitted messages: java.io.IOException: failed read header: java.lang.NullPointerException This flow of exceptions does not stop until all clients (h1 and h2) are killed - stopping h1 does not stop exceptions on h2 and vice versa. -- 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

18 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-100) Support Hypersonic

by Mark Little (JIRA)

Support Hypersonic ------------------ Key: JBESB-100 URL: http://jira.jboss.com/jira/browse/JBESB-100 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 -- 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

18 years, 1 month

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2006