January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3267) JSF redirect from https connector ends up on port 80

by Nicklas Karlsson (Created) (JIRA)

JSF redirect from https connector ends up on port 80 ---------------------------------------------------- Key: AS7-3267 URL: https://issues.jboss.org/browse/AS7-3267 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.0.CR1b Reporter: Nicklas Karlsson Assignee: Remy Maucherat Given a JSF page with a link {code} <h:commandLink action="test2?faces-redirect=true">link</h:commandLink> {code} and the app running on https://localhost/Test/faces/test.xhtml, attempts to load https://localhost:80/Test/faces/test2.xhtml are made (failing, of course). The port is 80 even if the http connector is 8080 (it's 80 even if the http connector is removed altogether) -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] (AS7-3128) Arquillian doesn't wait for the process to really end, causes problems like "port in use".

by Ondrej Zizka (Updated) (JIRA)

[ https://issues.jboss.org/browse/AS7-3128?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka updated AS7-3128: ------------------------------ Priority: Blocker (was: Critical) > Arquillian doesn't wait for the process to really end, causes problems like "port in use". > ------------------------------------------------------------------------------------------ > > Key: AS7-3128 > URL: https://issues.jboss.org/browse/AS7-3128 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.1.0.CR1 > Reporter: Ondrej Zizka > Assignee: Aslak Knutsen > Priority: Blocker > > (05:54:09) dmlloyd: when running with JDWP enabled on the client or server, I occasionally get bind exceptions due to address in use > (05:54:25) dmlloyd: which means that tests are running into each other without waiting for termination of the previous one > (05:54:35) dmlloyd: which may also be causing other issues > (05:56:04) ozizka: dmlloyd: Yes, lbarrerio observed similar problem too, > (05:56:47) ozizka: And that's arq's issue too - there's no way to get around this currently AFAIK. Or is there? > (05:57:05) ozizka: Perhaps "manually" wait in @AfterClass or such > (05:57:07) dmlloyd: yeah, it can wait for the child process to terminate > (05:57:07) ozizka: which is ugly > (05:57:14) dmlloyd: I mean arq should > (05:59:17) ozizka: dmlloyd: Do you have it somewhere on hudson? > (05:59:24) ozizka: dmlloyd: It never happened to me actually > (05:59:49) ozizka: Send me a log if you have one handy > (06:01:35) dmlloyd: ozizka: no, try running with this command though: > {code} > mvn -DallTests install -Djpda -Dsurefire.jpda.args=-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n \ > -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005" > {code} > (06:13:56) ozizka: dmlloyd: That's on linux? > (06:14:03) dmlloyd: yes -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-3128) Arquillian doesn't wait for the process to really end, causes problems like "port in use".

by Ondrej Zizka (Assigned) (JIRA)

[ https://issues.jboss.org/browse/AS7-3128?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka reassigned AS7-3128: --------------------------------- Assignee: Aslak Knutsen > Arquillian doesn't wait for the process to really end, causes problems like "port in use". > ------------------------------------------------------------------------------------------ > > Key: AS7-3128 > URL: https://issues.jboss.org/browse/AS7-3128 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.1.0.CR1 > Reporter: Ondrej Zizka > Assignee: Aslak Knutsen > Priority: Critical > > (05:54:09) dmlloyd: when running with JDWP enabled on the client or server, I occasionally get bind exceptions due to address in use > (05:54:25) dmlloyd: which means that tests are running into each other without waiting for termination of the previous one > (05:54:35) dmlloyd: which may also be causing other issues > (05:56:04) ozizka: dmlloyd: Yes, lbarrerio observed similar problem too, > (05:56:47) ozizka: And that's arq's issue too - there's no way to get around this currently AFAIK. Or is there? > (05:57:05) ozizka: Perhaps "manually" wait in @AfterClass or such > (05:57:07) dmlloyd: yeah, it can wait for the child process to terminate > (05:57:07) ozizka: which is ugly > (05:57:14) dmlloyd: I mean arq should > (05:59:17) ozizka: dmlloyd: Do you have it somewhere on hudson? > (05:59:24) ozizka: dmlloyd: It never happened to me actually > (05:59:49) ozizka: Send me a log if you have one handy > (06:01:35) dmlloyd: ozizka: no, try running with this command though: > {code} > mvn -DallTests install -Djpda -Dsurefire.jpda.args=-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n \ > -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005" > {code} > (06:13:56) ozizka: dmlloyd: That's on linux? > (06:14:03) dmlloyd: yes -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-3225) ModuleGroupSingletonProvider throws NullPoinerException instead of clear exception message because of Hashtable usage

by Geoffrey De Smet (Created) (JIRA)

ModuleGroupSingletonProvider throws NullPoinerException instead of clear exception message because of Hashtable usage --------------------------------------------------------------------------------------------------------------------- Key: AS7-3225 URL: https://issues.jboss.org/browse/AS7-3225 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Reporter: Geoffrey De Smet Assignee: Stuart Douglas Priority: Minor Here's a stacktrace we get: {code} 14:45:47,087 INFO [stdout] (http--127.0.0.1-8080-2) java.lang.NullPointerException 14:45:47,087 INFO [stdout] (http--127.0.0.1-8080-2) at java.util.Hashtable.get(Hashtable.java:334) 14:45:47,087 INFO [stdout] (http--127.0.0.1-8080-2) at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:71) 14:45:47,088 INFO [stdout] (http--127.0.0.1-8080-2) at org.jboss.weld.Container.instance(Container.java:58) 14:45:47,088 INFO [stdout] (http--127.0.0.1-8080-2) at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:72) 14:45:47,088 INFO [stdout] (http--127.0.0.1-8080-2) at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:124) 14:45:47,088 INFO [stdout] (http--127.0.0.1-8080-2) at org.drools.guvnor.server.RepositoryAssetOperations$Proxy$_$$_WeldClientProxy.findAssetPage(RepositoryAssetOperations$Proxy$_$$_WeldClientProxy.java) {code} The code uses a java.util.Hashtable, which isn't null-safe (while a HashMap is) Replacing this code in ModuleGroupSingletonProvider.java: {code} private final Map<ClassLoader, T> store = new Hashtable<ClassLoader, T>(); {code} by this, will probably fix it {code} private final Map<ClassLoader, T> store = Collections.synchronizedMap(new HashMap<ClassLoader, T>()); {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, 3 months

2
1
0 / 0

[JBoss JIRA] (AS7-672) HostController status

by Brian Stansberry (Commented) (JIRA)

[ https://issues.jboss.org/browse/AS7-672?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry commented on AS7-672: -------------------------------------- Yes, it's analogous to the server-state attribute on a server's root resource. It doesn't just check whether the HC is out of sync with the master. It's also possible to put the HC itself into reload-required state via some operation that affects the HC config. For example, changing something in the management security configuration, etc. > HostController status > --------------------- > > Key: AS7-672 > URL: https://issues.jboss.org/browse/AS7-672 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Kabir Khan > Fix For: 7.1.0.Final > > > Analogous to a server's status, but for a HostController. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-3260) Deplyoment distribution fails when DC is Windows and HC is linux

by Tomaz Cerar (Created) (JIRA)

Deplyoment distribution fails when DC is Windows and HC is linux ---------------------------------------------------------------- Key: AS7-3260 URL: https://issues.jboss.org/browse/AS7-3260 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.CR1b Environment: HC on linux DC on windows 7 Reporter: Tomaz Cerar Assignee: Brian Stansberry Priority: Critical Fix For: 7.1.0.Final There is problem with the distribution of the content (deployments) between the DC running on Windows 7 and the slaves running on CentOS/RHEL 6.2. The content is distributed to the slaves, but the filename "content" in content sub directories is prefixed with "\", as "\content". If I rename the file to "content", the host picks up the correct deployment after restart. -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] (AS7-2895) Errors in standard.conf.bat and domain.conf.bat variable expansions

by Nicklas Karlsson (Created) (JIRA)

Errors in standard.conf.bat and domain.conf.bat variable expansions ------------------------------------------------------------------- Key: AS7-2895 URL: https://issues.jboss.org/browse/AS7-2895 Project: Application Server 7 Issue Type: Bug Components: Scripts Affects Versions: 7.1.0.Beta1 Reporter: Nicklas Karlsson Assignee: Brian Stansberry Priority: Minor in some places in the windows conf files, there are incorrect appending and expansion used (see forum reference for details). domain.conf.bat also has unix-style expansions used in the examples -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] (AS7-3242) Convert pojo subsystem to i18n logging and exceptions messages as per ANDIAMO-2

by Brian Stansberry (Created) (JIRA)

Convert pojo subsystem to i18n logging and exceptions messages as per ANDIAMO-2 ------------------------------------------------------------------------------- Key: AS7-3242 URL: https://issues.jboss.org/browse/AS7-3242 Project: Application Server 7 Issue Type: Task Components: POJO Reporter: Brian Stansberry Assignee: Ales Justin Fix For: 7.1.0.Final The PojoLogger and PojoMessages classes are currently empty shells. The INFO and above logging and any exception messages in the subsystem needs to be converted to use these classes. See EJB subsystem for an example. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] (AS7-3231) Property jboss.entity.manager.factory.jndi.name not working

by Zbyněk Roubalík (Created) (JIRA)

Property jboss.entity.manager.factory.jndi.name not working ----------------------------------------------------------- Key: AS7-3231 URL: https://issues.jboss.org/browse/AS7-3231 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.1.0.CR1 Reporter: Zbyněk Roubalík Assignee: Scott Marlow Fix For: 7.1.0.Final If there is specified property jboss.entity.manager.factory.jndi.name in persistence.xml file, it isn't possible to deploy application using this file. I've create test for this issue: https://github.com/zroubalik/jboss-as/blob/emfBind/testsuite/integration/... Error on output from this tests: 21:15:38,732 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."jpa_emfactory.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jpa_emfactory.jar".INSTALL: Failed to process phase INSTALL of deployment "jpa_emfactory.jar" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_20] at java.lang.Thread.run(Thread.java:636) [:1.6.0_20] Caused by: java.lang.NullPointerException at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.addPuService(PersistenceUnitDeploymentProcessor.java:329) at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.handleJarDeployment(PersistenceUnitDeploymentProcessor.java:139) at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.deploy(PersistenceUnitDeploymentProcessor.java:120) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] ... 5 more -- 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, 3 months

3
3
0 / 0

[JBoss JIRA] (AS7-2409) host.xml host name should default to something unique

by Rich Sharples (Created) (JIRA)

host.xml host name should default to something unique ----------------------------------------------------- Key: AS7-2409 URL: https://issues.jboss.org/browse/AS7-2409 Project: Application Server 7 Issue Type: Enhancement Components: Clustering Affects Versions: 7.1.0.Alpha1 Environment: all Reporter: Rich Sharples Assignee: Paul Ferraro Fix For: 7.1.0.Beta1 in a distribibuted domain environment (ie. typical production env.) host name in host.xml must be unique : <host xmlns="urn:jboss:domain:1.1" name="RichS"> otherwise we get a startup error. To avoid having to modify this config for all machines (could be 10^3), we need a way to default this to a unique id. One idea would be to have a UUID property generated from the host-ip + process-id. That would provide unique IDs across the domain and also allow multiple instances per machine. In domain mode this really should be the default (ie. we shold always use the property in domain/configuration/host.xml). Note : if we do use host-ip+process-id then the ID is going to be different every time the process start - that may be a problem in itself. -- 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, 3 months

4
3
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 January 2012