January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2840) TS: How to use -Djpda with clustered tests

by Radoslav Husar (Created) (JIRA)

TS: How to use -Djpda with clustered tests ------------------------------------------ Key: AS7-2840 URL: https://issues.jboss.org/browse/AS7-2840 Project: Application Server 7 Issue Type: Bug Components: Clustering, Documentation, Test Suite Affects Versions: 7.1.0.Beta1 Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Minor The doc now says whats pasted below, but I am not sure if both servers are listening on 8787 because (that would fail the startup), if I have to connect to both or where do I configure that, etc. {code} Running JBoss AS instances with debugger Adding -Djpda (May be changed to -Ddebug in the future) will make JBoss AS run with JPDA JVM arguments for debugging. It will suspend and wait for the debugger to connect at port 8787. JBoss AS is started by Arquillian, when the first test which requires given instance is run. There's (currently) no challenge text in the console, it will look like the first test is stuck. This is being solved in http://jira.codehaus.org/browse/SUREFIRE-781. Depending on which test group(s) you run, multiple instances may be started. In that case, you need to attach the debugger multiple times. {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

12 years, 8 months

4
3
0 / 0

[JBoss JIRA] (AS7-333) Context is lost if a service fails to start for a 'random' reason

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/AS7-333?page=com.atlassian.jira.plugin.sy... ] Jason Greene updated AS7-333: ----------------------------- Fix Version/s: 7.2.0.Alpha1 (was: 7.1.0.Final) > Context is lost if a service fails to start for a 'random' reason > ----------------------------------------------------------------- > > Key: AS7-333 > URL: https://issues.jboss.org/browse/AS7-333 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Carlo de Wolf > Assignee: David Lloyd > Priority: Minor > Fix For: 7.2.0.Alpha1 > > > The error message only contains "Failed to start service" it would be nice if the optional causing message is also appended. > {noformat} > 13:58:53,058 INFO [org.jboss.as.server] (MSC service thread 1-9) Service status report > Services which failed to start: > service jboss.deployment.unit."welcome.war": org.jboss.msc.service.StartException in service jboss.deployment.unit."welcome.war": Failed to start service > {noformat} > https://github.com/jbossas/jboss-msc/blob/1.0.0.Beta8/src/main/java/org/j... -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-3358) CLONE - NullPointerException when HQ backup server is shutting down after clean shutdown

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/AS7-3358?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-3358: ------------------------------ Fix Version/s: 7.2.0.Alpha1 (was: 7.1.0.Final) > CLONE - NullPointerException when HQ backup server is shutting down after clean shutdown > ---------------------------------------------------------------------------------------- > > Key: AS7-3358 > URL: https://issues.jboss.org/browse/AS7-3358 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Affects Versions: 7.1.0.CR1 > Reporter: Pavel Slavicek > Assignee: Andy Taylor > Priority: Minor > Fix For: 7.2.0.Alpha1 > > > This issue is also in AS7. > Cloned from JBPAPP-6137: > Hi Clebert, > I hit NullPointerException when dedicated backup server was shutting down after clean shutdown command. Live server was stopped (clean shutdown too) several seconds before backup server. It seems that backup tried to take its role. NullPointerException is ugly and it should not occur. > I am putting it on minor priority. > Thank you. > 10:42:42,071 INFO [ClusterManagerImpl] announcing backup > 10:42:42,072 INFO [HornetQServerImpl] HornetQ Backup Server version 2.2.1.GA (Zmmmmmmmm, 121) [e9d8059a-5140-11e0-8830-005056c00008] started, waiting live to fail before it gets active > 10:42:49,387 INFO [ClusterManagerImpl] backup announced > ^C10:51:03,362 INFO [ServerImpl] Runtime shutdown hook called, forceHalt: true > 10:51:03,423 WARN [RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4] > 10:51:03,628 WARN [ClientSessionFactoryImpl] Failed to connect to server. > 10:51:03,634 SEVERE [HornetQServerImpl] Failure in initialisation > java.lang.NullPointerException > at org.hornetq.core.server.impl.HornetQServerImpl.initialisePart2(HornetQServerImpl.java:1436) > at org.hornetq.core.server.impl.HornetQServerImpl.access$100(HornetQServerImpl.java:130) > at org.hornetq.core.server.impl.HornetQServerImpl$SharedStoreBackupActivation.run(HornetQServerImpl.java:398) > at java.lang.Thread.run(Thread.java:636) > 10:51:04,634 INFO [HornetQServerImpl] HornetQ Server version 2.2.1.GA (Zmmmmmmmm, 121) [e9d8059a-5140-11e0-8830-005056c00008] stopped -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-2254) Point to explicit security doc in server.log

by Chuck Mosher (Created) (JIRA)

Point to explicit security doc in server.log -------------------------------------------- Key: AS7-2254 URL: https://issues.jboss.org/browse/AS7-2254 Project: Application Server 7 Issue Type: Enhancement Components: Server Affects Versions: 7.1.0.Alpha1 Environment: Thinkpad T510 w/ 4 cores, 8Gb, running CSB Reporter: Chuck Mosher Assignee: Jason Greene Priority: Minor Nice to warn me (in the server.log) that I have a security issue due to the cluster admin/user pwd using the defaults. Warning tells me to look at the docs; would it be possible to put it the hyperlink to the specific doc? -- 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

12 years, 8 months

4
4
0 / 0

[JBoss JIRA] (AS7-2314) Passing -Djboss.boot.server.log.level=DEBUG to standalone.sh script is ignored

by Rich Lucente (Created) (JIRA)

Passing -Djboss.boot.server.log.level=DEBUG to standalone.sh script is ignored ------------------------------------------------------------------------------ Key: AS7-2314 URL: https://issues.jboss.org/browse/AS7-2314 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.0.Alpha1 Environment: Fedora 14, java-1.6.0-openjdk, jboss-as-7.1.0.Alpha2-SNAPSHOT Reporter: Rich Lucente Assignee: Jason Greene Priority: Minor Fix For: Open To Community Attempting to change boot log level via a script argument to standalone.sh is ignored. I can edit standalone.conf (set value in JAVA_OPTS) or edit logging.properties directly. Other -D parameters are honored, so there seems to be some startup/timing issue with this specific setting. -- 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

12 years, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-9193) Tighten up the ServerEnvironment and HostControllerEnvironment contracts

by Brian Stansberry (JIRA)

Tighten up the ServerEnvironment and HostControllerEnvironment contracts ------------------------------------------------------------------------ Key: JBAS-9193 URL: https://issues.jboss.org/browse/JBAS-9193 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta4 Right now the contract/usage of these classes is a bit of a mishmash. The idea was to store state that's read from Main(). But if there's anything in these that can be overridden from standalone.xml, either we should restrict access to that data or make sure that it has the correct value if a change is made via the management API. For example, the server name can come from standalone.xml if the 'name' attribute is set and for sure will come from the HostController in domain mode. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
5
0 / 0

[JBoss JIRA] (AS7-2681) Make JAXR http endpoint configurable

by Thomas Diesler (Created) (JIRA)

Make JAXR http endpoint configurable ------------------------------------ Key: AS7-2681 URL: https://issues.jboss.org/browse/AS7-2681 Project: Application Server 7 Issue Type: Task Components: JAXR Reporter: Thomas Diesler Assignee: Kurt Stam Fix For: 7.1.0.CR1 Currently, the HTTP endpoint and database services are installed based on {code} if (config.getDataSourceBinding() != null) { newControllers.add(JAXRDatasourceService.addService(serviceTarget, config, verifyHandler)); newControllers.add(JAXRHttpEndpointService.addService(serviceTarget, config, verifyHandler)); } {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

12 years, 8 months

5
6
0 / 0

[JBoss JIRA] (AS7-3163) FS deployment scanner fails completely after single timeout failure

by Brent Douglas (Created) (JIRA)

FS deployment scanner fails completely after single timeout failure ------------------------------------------------------------------- Key: AS7-3163 URL: https://issues.jboss.org/browse/AS7-3163 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.0.CR1 Reporter: Brent Douglas Assignee: Jason Greene When deploying via the the FS deployment scanner a timeout causes all subsequent deployments to fail with further timeout failures. The problem appears to be that FileSystemDeploymentService submits the DeployTask for timed execution it acquires a lock it's copy of ContainerStateMonitor (via OperationContextImpl.acquireContainerMonitor()). When a timeout exception is throw by the first failure this lock is never cleaned up which results in all further deployment jobs to hang on ContainerStateMonitor.await (line 161). Restarting the server clears the monitor and allows the scanner to be reused as normal. -- 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

12 years, 8 months

5
5
0 / 0

[JBoss JIRA] Created: (AS7-1384) Strange state after :reload

by Heiko Rupp (JIRA)

Strange state after :reload --------------------------- Key: AS7-1384 URL: https://issues.jboss.org/browse/AS7-1384 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Rupp Assignee: Brian Stansberry 7.1 snapshot I did change a socket binding, so reload is needed. Did a /:read-resource Then :reload }, "response-headers" => {"process-state" => "reload-required"} } [standalone@localhost:9999 /] :reload { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } [standalone@localhost:9999 /] :reload { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } I think after the reload (which succeeded) the process-state should no longer be "reload needed". Also {"result" => } should be defined and not just null. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

5
5
0 / 0

[JBoss JIRA] (AS7-3315) Class loading problem in case of multiple .rar deployments

by Vladimir Rastseluev (JIRA)

Vladimir Rastseluev created AS7-3315: ---------------------------------------- Summary: Class loading problem in case of multiple .rar deployments Key: AS7-3315 URL: https://issues.jboss.org/browse/AS7-3315 Project: Application Server 7 Issue Type: Bug Environment: a694b08fd04d8b70729a019b5b72e68cf5b20a7b Reporter: Vladimir Rastseluev Assignee: Aslak Knutsen Priority: Critical Fix For: 7.1.0.Final I wrote a test, which deploys 2 .rar archives and tries to activate objects from both archives. Test doesn't pass. Seems, it can find objects by jndi names, if they were deployed in .rar together with test, but it can't find objects from another archive. Probably, there is a class loading problem. Test org.jboss.as.test.smoke.embedded.deployment.rar.examples.IronJacamarMultipleActivationTestCase.java is in my branch https://github.com/vratsel/jboss-as/commit/a694b08fd04d8b70729a019b5b72e6.... -- 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

12 years, 8 months

5
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012