December 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBUILD-443) Getting wrong version of a transitive dependency

by Carlo de Wolf (JIRA)

Getting wrong version of a transitive dependency ------------------------------------------------ Key: JBBUILD-443 URL: http://jira.jboss.com/jira/browse/JBBUILD-443 Project: JBoss Build System Issue Type: Bug Components: Maven Reporter: Carlo de Wolf jboss-ejb3-core depends on jboss-metadata 1.0.0.Beta4 jboss-metadata 1.0.0.Beta4 depends on jboss-container 2.0.0.Beta6 but jboss-container SNAPSHOT is used instead. -- 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

17 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-471) Release plugin screws up the pom header

by Carlo de Wolf (JIRA)

Release plugin screws up the pom header --------------------------------------- Key: JBBUILD-471 URL: http://jira.jboss.com/jira/browse/JBBUILD-471 Project: JBoss Build System Issue Type: Bug Components: Maven Reporter: Carlo de Wolf <?xml version="1.0" encoding="UTF-8"?>  <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> becomes: <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> -- 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

17 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-5872) Update org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase

by Dimitris Andreadis (JIRA)

Update org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase --------------------------------------------------------------------- Key: JBAS-5872 URL: https://jira.jboss.org/jira/browse/JBAS-5872 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assignee: Shelly McGowan Fix For: JBossAS-5.0.0.GA org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase needs updating. There should be a new test testJavaEE50Compatibility. I don't we need to keep testJ2EERI141Compatibility. And we should be testing against 4.2.x SerialVersionUIDs. -- 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

17 years, 7 months

2
10
0 / 0

[JBoss JIRA] Created: (JBAS-6273) Create release notes for AS 5.0.0.GA

by Dimitris Andreadis (JIRA)

Create release notes for AS 5.0.0.GA ------------------------------------ Key: JBAS-6273 URL: https://jira.jboss.org/jira/browse/JBAS-6273 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Priority: Critical Fix For: JBossAS-5.0.0.GA -- 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

17 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4735) Upon Shutdown connectors should be stopped before applications are undeployed

by Dominik Pospisil (JIRA)

Upon Shutdown connectors should be stopped before applications are undeployed ----------------------------------------------------------------------------- Key: JBAS-4735 URL: http://jira.jboss.com/jira/browse/JBAS-4735 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Affects Versions: JBossAS-4.2.1.GA Reporter: Dominik Pospisil Assigned To: Brian Stansberry In clustered environment the process of shutting down single AS instance should be transparent to clients. This is not the case since applications are udeployed at first while connectors are still servicing requests. This causes clients not to be redirected to another cluster nodes and to receive resource not avaiable exceptions. >From the client perspective, shutdown process should should work like follows: 1) stop connectors so they refuse servicing new requests 2) complete running requests 3) undeploy applications -- 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

17 years, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-6139) Create a hudson job that builds using a clean local maven repo.

by Paul Gier (JIRA)

Create a hudson job that builds using a clean local maven repo. --------------------------------------------------------------- Key: JBAS-6139 URL: https://jira.jboss.org/jira/browse/JBAS-6139 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Paul Gier Assignee: Paul Gier -- 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

17 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-5982) Configuration guide lists <ha-local-datasource> as experimental

by Chris Bredesen (JIRA)

Configuration guide lists <ha-local-datasource> as experimental --------------------------------------------------------------- Key: JBAS-5982 URL: https://jira.jboss.org/jira/browse/JBAS-5982 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Docs/Administration and Configuration Guide Affects Versions: JBossAS-5.0.0.CR2, JBossAS-4.2.3.GA Reporter: Chris Bredesen Assignee: Samson Kittoli Priority: Trivial <ha-local-datasource> is no longer experimental and the documentation needs to be updated to reflect this and any other information needed to use this feature. -- 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

17 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-5799) HAJNDI lookup clarification

by Galder Zamarreno (JIRA)

HAJNDI lookup clarification --------------------------- Key: JBAS-5799 URL: https://jira.jboss.org/jira/browse/JBAS-5799 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1 Reporter: Galder Zamarreno Assignee: Samson Kittoli In AS documentation, in the clustering section, it says: "For clients running inside the application server. If you want to access HA-JNDI from inside the application server, you must explicitly get an InitialContext by passing in JNDI properties. The following code shows how to create a naming Context bound to HA-JNDI: Properties p = new Properties(); p.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); p.put(Context.URL_PKG_PREFIXES, "jboss.naming:org.jnp.interfaces"); p.put(Context.PROVIDER_URL, "localhost:1100"); // HA-JNDI port. return new InitialContext(p); " As explained in http://wiki.jboss.org/auth/wiki/JBossHAJNDIUseCluster I think this section below should appended to the comment above. "However, this does not work in all cases, especially when running a multi-homed cluster (several JBoss instances on one machine bound to different IPs). A safer method is not to specify the Context.PROVIDER_URL (which does not work in all scenarios) but the partition name property: Properties p = new Properties(); p.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); p.put(Context.URL_PKG_PREFIXES, "jboss.naming:org.jnp.interfaces"); p.put("jnp.partitionName", "DefaultPartition"); // partition name. return new InitialContext(p); " -- 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

17 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-5203) Deprecate the track-connection-by-tx (enabled-by-default) with a <interleaving/> flag for XA Users

by Dimitris Andreadis (JIRA)

Deprecate the track-connection-by-tx (enabled-by-default) with a <interleaving/> flag for XA Users -------------------------------------------------------------------------------------------------- Key: JBAS-5203 URL: http://jira.jboss.com/jira/browse/JBAS-5203 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Reporter: Dimitris Andreadis Assigned To: Alexey Loubyansky Fix For: JBossAS-5.0.0.CR1 See JBAS-5171. Deprecate the track-connection-by-tx (enabled-by-default) with a <interleaving/> flag for XA Users. When track-connection-by-tx is set by the user, a warning should be printed. -- 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

17 years, 7 months

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-5698) Add RmiBindAddress to HANamingServiceMBean documentation

by Paul Ferraro (JIRA)

Add RmiBindAddress to HANamingServiceMBean documentation -------------------------------------------------------- Key: JBAS-5698 URL: http://jira.jboss.com/jira/browse/JBAS-5698 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: JBossAS-5.0.0.CR2 Reporter: Paul Ferraro Assigned To: Samson Kittoli Previously, HANamingServiceMBean.bindAddress served two functions: >From trunk/cluster/src/etc/hajndi-service.xml:  <attribute name="BindAddress">${jboss.bind.address}</attribute> The bootstrap and HA-JNDI RMI endpoints are now defined separately:  <attribute name="BindAddress">${jboss.bind.address}</attribute>  <attribute name="RmiBindAddress">${jboss.bind.address}</attribute> They each default to the same value. Users may want to override the RMI bind address if deployed on a multi-homed machine, and want to use an specific network interface for HA-JNDI RMI calls. This ability already exists in the standard NamingService. -- 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

17 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 2008