November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6089) Can not disable autodiscovery if System.setProperty() is used

by Wolf-Dieter Fink (JIRA)

Can not disable autodiscovery if System.setProperty() is used ------------------------------------------------------------- Key: JBAS-6089 URL: https://jira.jboss.org/jira/browse/JBAS-6089 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Naming Affects Versions: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1, JBossAS-4.2.2.GA Reporter: Wolf-Dieter Fink Assignee: Scott M Stark If a InitialContext is created via new InitialContext() and the properties are set via System.setProperty(...) the autodiscovery can not be disabled. Here the JUnitTest method: public void checkSystemPropertiesConnection() throws NamingException { System.setProperty("java.naming.factory.initial", "org.jboss.naming.NamingContextFactory"); System.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces"); // System.setProperty("java.naming.provider.url", "jnp://localhost:1099"); System.setProperty("jnp.disableDiscovery", "true"); InitialContext ctx = new InitialContext(); LOGGER.debug("JNDI properties: "+ctx.getEnvironment()); } ------------------------------ The Log output 16:01:28,497 DEBUG [de.wfink.ejb21.ConnectionTest] JNDI properties: {jnp.parsedName=, java.naming.provider.url=padwfink1:1099, java.naming.factory.initial=org.jboss.naming.NamingContextFactory, jnp.disableDiscovery=false, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces} 16:01:29,481 DEBUG [org.jnp.interfaces.NamingContext] Failed to connect to padwfink1:1099 ---------------------------- If a lookup is started with this InitialContext autodiscovery is started. If all is set in a HashTable and InitialContext(hashTable) is call it works -- 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, 4 months

5
10
0 / 0

[JBoss JIRA] Created: (JBBUILD-483) jta.jar from the repo does not have a manifest.mf file

by Jay Balunas (JIRA)

jta.jar from the repo does not have a manifest.mf file ------------------------------------------------------ Key: JBBUILD-483 URL: https://jira.jboss.org/jira/browse/JBBUILD-483 Project: JBoss Build System Issue Type: Bug Components: JBossBuild, Maven Reporter: Jay Balunas Assignee: Pete Muir Priority: Critical jta.jar from the repository does not have a manifest.mf file -- 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, 4 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-5581) Setting jgroups.bind_address or bind.address in run.conf will be ignored if -b used

by Galder Zamarreno (JIRA)

Setting jgroups.bind_address or bind.address in run.conf will be ignored if -b used ----------------------------------------------------------------------------------- Key: JBAS-5581 URL: http://jira.jboss.com/jira/browse/JBAS-5581 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA Reporter: Galder Zamarreno Assigned To: Galder Zamarreno * Why it it useless specifying -Dbind.address=192.168.0.1 inside run.conf? Why does it work only specifying it on command line? For example: If you set -Dbind.address=127.0.0.1 in run.conf and starting AS with: ./bin/run.sh -b 10.33.144.245 The value assigned to -Dbind.address will be ignored. When you pass -Dbind.address in the command line, JBoss sets both this system property and -Djgroups.bind_address to that value, which means that if you pass -b after that, it won't override the given -Dbind.address. Bottom line, if -Dbind.address set in command line before -b, it's the winner. Example: ./bin/run.sh -Dbind.address=127.0.0.1 -b 1.2.3.4 -> JGroups will bind to 127.0.0.1 If you pass -b in the command line before -Dbind.address, -b will first set -Dbind.address and -Djgroups.bind_address, but then, when -Dbind.address is process, it will override the values of them two with what was passed in -Dbind.address ./bin/run.sh -b 1.2.3.4 -Dbind.address=127.0.0.1 -> JGroups will bind to 127.0.0.1 Now, This does not happen when the -Dbind.address is set in run.conf instead of command line. There's a bug here. When AS processes -b, it checks whether -Dbind.address has been set, which it has, so leaves it as it is. Now, when it checks -Djgroups.bind_address, it sees that it hasn't been set, but *does not do a double check in case -Dbind.address has been set*, so it ends up setting -Djgroups.bind_address to the value of -b, that way ignoring the value you passed to -Dbind.address. Example: run.conf with -Dbind.address=127.0.0.1 ./bin/run.sh -b 1.2.3.4 -> JGroups will bind to 1.2.3.4 What's the fix? Add the double check in -b processing so that if -Dbind.address was set by the user, AS does not take the value of -b and assign to -Djgroups.bind_addr -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-6003) jboss.entity.manager.jndi.name in persistence.xml doesn't work

by Xavier Jodoin (JIRA)

jboss.entity.manager.jndi.name in persistence.xml doesn't work -------------------------------------------------------------- Key: JBAS-6003 URL: https://jira.jboss.org/jira/browse/JBAS-6003 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR2 Environment: Ubuntu 8.04 java 1.6 Reporter: Xavier Jodoin Works under jboss 5 CR1 and not under CR2 the jndi name is not bound: <property name="jboss.entity.manager.jndi.name" value="securityEntityManager"/> new InitialContext().lookup("securityEntityManager"); <?xml version="1.0" encoding="UTF-8"?> <persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation = "http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" version="1.0"> <persistence-unit name="NAIDsecurity" transaction-type="JTA"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <jta-data-source>java:/SECURITYDS</jta-data-source> <properties> <property name="hibernate.dialect" value="org.hibernate.dialect.SQLServerDialect"/> <property name="hibernate.show_sql" value="false"/> <property name="jboss.entity.manager.jndi.name" value="securityEntityManager"/> <property name="hibernate.hbm2ddl.auto" value="update"/> </properties> </persistence-unit> </persistence> -- 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, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-5993) Need to add ProfileService failed deployment tests

by Scott M Stark (JIRA)

Need to add ProfileService failed deployment tests -------------------------------------------------- Key: JBAS-5993 URL: https://jira.jboss.org/jira/browse/JBAS-5993 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ProfileService Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-5.0.0.GA We need to add ProfileService failed deployment tests to validate that the reason for the failure is being propagated back to the ProfileService.DeploymentManager client -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBREM-1039) Release 2.2.2.SP11

by Ron Sigal (JIRA)

Release 2.2.2.SP11 ------------------ Key: JBREM-1039 URL: https://jira.jboss.org/jira/browse/JBREM-1039 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP11 -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5529) Add for JBAS, JBossWeb, JBossWeb connector components

by Charles Crouch (JIRA)

Add for JBAS, JBossWeb, JBossWeb connector components ----------------------------------------------------- Key: JBAS-5529 URL: http://jira.jboss.com/jira/browse/JBAS-5529 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Charles Crouch -- 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, 4 months

4
19
0 / 0

[JBoss JIRA] Created: (JBAOP-666) Reimplement classpools for AS

by Kabir Khan (JIRA)

Reimplement classpools for AS ----------------------------- Key: JBAOP-666 URL: https://jira.jboss.org/jira/browse/JBAOP-666 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 2.1.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, 4 months

1
6
0 / 0

[JBoss JIRA] Created: (JBAOP-283) Better documentation for metadata and CallLoggingInterceptor

by Kabir Khan (JIRA)

Better documentation for metadata and CallLoggingInterceptor ------------------------------------------------------------ Key: JBAOP-283 URL: http://jira.jboss.com/jira/browse/JBAOP-283 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Fix For: 2.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

17 years, 4 months

2
15
0 / 0

[JBoss JIRA] Created: (JBAOP-309) Investigate pointcut matching on annotation attributes

by Kabir Khan (JIRA)

Investigate pointcut matching on annotation attributes ------------------------------------------------------ Key: JBAOP-309 URL: http://jira.jboss.com/jira/browse/JBAOP-309 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha3 -- 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, 4 months

2
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 November 2008