December 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2934) Move non-standard configs out of smoke ParseAndMarshalModelsTestCase to a copy in basic

by Kabir Khan (Created) (JIRA)

Move non-standard configs out of smoke ParseAndMarshalModelsTestCase to a copy in basic --------------------------------------------------------------------------------------- Key: AS7-2934 URL: https://issues.jboss.org/browse/AS7-2934 Project: Application Server 7 Issue Type: Feature Request Components: Test Suite Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 7.1.0.CR1 Brian: Yes, the tests of the example configs and the historical configs should move to basic. On 12/6/11 9:39 AM, Kabir Khan wrote: I've merged https://github.com/jbossas/jboss-as/pull/790 There are a few outstanding requests to add more files there which are on hold awaiting tests being added to ParseAndMarshalModelsTestCase. However, ParseAndMarshalModelsTestCase is already one of the slowest smoke tests, it starts a new controller internally per tested config so each config is more or less like starting up a new server. This is needed since a modular environment is needed for the parsing. Maybe it would make sense to move, if not the whole test, at least the non-standard parts of it into basic? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-2921) Scope resource adapter deployments to their .ear

by Jesper Pedersen (Created) (JIRA)

Scope resource adapter deployments to their .ear ------------------------------------------------ Key: AS7-2921 URL: https://issues.jboss.org/browse/AS7-2921 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.0.Beta1 Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Blocker Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] (AS7-2437) EE6 WAR and EAR Maven Archetypes

by Burr Sutter (Created) (JIRA)

EE6 WAR and EAR Maven Archetypes -------------------------------- Key: AS7-2437 URL: https://issues.jboss.org/browse/AS7-2437 Project: Application Server 7 Issue Type: Enhancement Reporter: Burr Sutter Assignee: Pete Muir Blank or empty archetypes At this time, the current EE6 WAR and EAR archetypes add several demo/example files to the resulting project - this is wonderful for the new user and the getting started experience but less desirable for the advanced Maven user who just wants the project layout and initial pom.xml. Provide an option for either a blank/empty archetype or easy removal of the demo/example code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

6
6
0 / 0

[JBoss JIRA] (AS7-2893) Regenerate kitchensink (war) quickstart

by Pete Muir (Created) (JIRA)

Regenerate kitchensink (war) quickstart --------------------------------------- Key: AS7-2893 URL: https://issues.jboss.org/browse/AS7-2893 Project: Application Server 7 Issue Type: Task Components: Documentation Affects Versions: 7.1.0.Beta1 Reporter: Pete Muir Assignee: Pete Muir Priority: Minor Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
1
0 / 0

[JBoss JIRA] (AS7-2894) Add release script for quickstarts

by Pete Muir (Created) (JIRA)

Add release script for quickstarts ---------------------------------- Key: AS7-2894 URL: https://issues.jboss.org/browse/AS7-2894 Project: Application Server 7 Issue Type: Task Components: Documentation Affects Versions: 7.1.0.Beta1 Reporter: Pete Muir Assignee: Pete Muir Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
1
0 / 0

[JBoss JIRA] (AS7-2900) Add Openshift profile to Maven archetypes

by Burr Sutter (Created) (JIRA)

Add Openshift profile to Maven archetypes ----------------------------------------- Key: AS7-2900 URL: https://issues.jboss.org/browse/AS7-2900 Project: Application Server 7 Issue Type: Feature Request Reporter: Burr Sutter Assignee: Pete Muir Priority: Critical Deployment to OpenShift requires a profile entry in the pom.xml - the maven archetypes should include this entry to allow for command-line users to easily/quickly push the newly generated project to OpenShift. In addition, this makes the end-user workflow vastly easier in the context of JBoss Tools/JBDS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] (JBVFS-181) VFS context lookups fail because of drive letter case sensitivity on Windows

by Michael Keefe (Created) (JIRA)

VFS context lookups fail because of drive letter case sensitivity on Windows ---------------------------------------------------------------------------- Key: JBVFS-181 URL: https://issues.jboss.org/browse/JBVFS-181 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.4.GA Environment: Windows, JBoss 5.1.0 GA patched with VFS 2.1.4 GA Reporter: Michael Keefe Assignee: John Bailey We currently run JBoss on both Windows and Linux platforms. On Windows we started to see the notorious explosion of nested resources in the vfs-nested.tmp folder. After stepping through the VFS code, I discovered code like the following in several places (this example from IterableVFSCache): String uriString = VFSUtils.stripProtocol(uri); Iterable<String> keys = getKeys(); readLock(); try { for (String key : keys) { if (uriString.startsWith(key)) return getContext(key); } } ... The simple "startsWith" check ignores the case of a drive letter in Windows which makes context lookups fail. For example, a uriString like "d:/myPath" will result in a failed context lookup if the associated key is "D:/myPath". A solution may be to simply "canonicalize" drive letters in Windows file URLs so that they are always upper cased when performing a context lookup. For now, we have converted all our drive letter references to upper case, but this is a fragile solution. VFS should be able to handle this correctly. It would be great if a patch could be made for this particular issue. Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1389) Per-sender flush

by Bela Ban (Created) (JIRA)

Per-sender flush ---------------- Key: JGRP-1389 URL: https://issues.jboss.org/browse/JGRP-1389 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.1 FLUSH ensures that every member has received all messages from *all* other members. This is quite costly, especially if we have a large cluster. However, sometimes, it is only necessary to ensure that a given message M sent by P has been received by everyone, for example, if P is the coordinator and installs view V, then it would be sufficient to ensure that everyone received V. A message M4 sent by P is sometimes delivered late because M is the last message sent by P, and if members Q and R don't receive M4 (e.g. because it was dropped), and P doesn't send another message M5, then Q and R have no means of detecting that M4 was sent by P and thus ask P for retransmission of M4. This is of course solved by STABLE which periodically broadcasts the highest seqnos sent, and then Q and R can ask P for retransmission of M4. However, if we don't want to wait that long, and don't want to risk Q and R to leave before they've received M4, we can implement a *sender-flush* of M4 sent by P. This works as follows: - P can add a RSVP flag to M4 - P adds M4 to a retransmit table and keeps retransmitting M4 until it has received ACKs from every non-faulty member in the target set, or P leaves - When a message is received that is tagged with RSVP, an ACK is sent back to the sender - When P has received ACKs from everyone, the message send returns. The caller is blocked until this is the case (maybe bound with a timeout ?) The reason why this works is that every receiver gets the latest message M4 from P, and adds it to its retransmit table. If there is a gap, it will ask P for retransmission of missing messages. This way, a receiver won't have to wait until STABLE sends a digest to find out it's missing messages from P. There could be an option for a receiver R to delay sending an ACK back to P until it has actually *received* P's missing messages. If this isn't the case, P could leave or crash *before* R got all of P's missing messages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

5
10
0 / 0

[JBoss JIRA] (JBJCA-711) ConnectionManager in violates Serializable contract

by Karel Piwko (Created) (JIRA)

ConnectionManager in violates Serializable contract --------------------------------------------------- Key: JBJCA-711 URL: https://issues.jboss.org/browse/JBJCA-711 Project: IronJacamar Issue Type: Bug Components: Core Affects Versions: 1.0.5.Final Reporter: Karel Piwko Assignee: Jesper Pedersen Priority: Critical AbstractConnectionManager does not implement Serializable interface according to the specification. See following code: {code} /** * Write the object to the stream -- THIS IS NOT SUPPORTED * @param out The stream * @exception IOException Thrown in case of an error */ private void writeObject(ObjectOutputStream out) throws IOException { throw new IOException(bundle.thisMethodNotSupported()); } /** * Read the object from the stream -- THIS IS NOT SUPPORTED * @param in The stream * @exception IOException Thrown in case of an error * @exception ClassNotFoundException Thrown if a class can't be resolved */ private void readObject(ObjectInputStream in) throws IOException, ClassNotFoundException { throw new IOException(bundle.thisMethodNotSupported()); } /** * Read the object -- THIS IS NOT SUPPORTED * @exception ObjectStreamException Thrown in case of an error */ private void readObjectNoData() throws ObjectStreamException { throw new NotSerializableException(bundle.thisMethodNotSupported()); } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
3
0 / 0

[JBoss JIRA] (AS7-2924) ConnectionManager in JCA violates Serializable contract

by Karel Piwko (Created) (JIRA)

ConnectionManager in JCA violates Serializable contract ------------------------------------------------------- Key: AS7-2924 URL: https://issues.jboss.org/browse/AS7-2924 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.0.Beta1 Reporter: Karel Piwko Assignee: Jesper Pedersen IronJacamar 1.0.5 distributed in JBoss AS does not implement the Serializable interface correctly. This causes errors when an application which requires serialization of the session, such as Spring WebFlow for snapshoting support. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
1
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 December 2011