[JBoss JIRA] (AS7-4289) mbeanserverbuildermodule error: kitchensink fails to test is AS 7.1.0.Final
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/AS7-4289?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen moved ARQ-827 to AS7-4289:
----------------------------------------
Project: Application Server 7 (was: Arquillian)
Key: AS7-4289 (was: ARQ-827)
Affects Version/s: 7.1.0.Final
(was: 1.0.0.CR7)
Component/s: Documentation
Test Suite
(was: JBoss AS Containers)
Security: (was: Public)
> mbeanserverbuildermodule error: kitchensink fails to test is AS 7.1.0.Final
> ---------------------------------------------------------------------------
>
> Key: AS7-4289
> URL: https://issues.jboss.org/browse/AS7-4289
> Project: Application Server 7
> Issue Type: Bug
> Components: Documentation, Test Suite
> Affects Versions: 7.1.0.Final
> Environment: Windows 7 and linux fedora 16
> Reporter: Esteve Aviles
> Priority: Minor
> Labels: mbeanserverbuildermodule
>
> hi,
> This error appears when testing kitchensink application ( mvn test -Parq-jbossas-managed)
> I have just unzipped app server and quickstarts. No modification done.
> I am not using whitespaces.(C:\servers\jboss-as-quickstarts-7.1.0.Final\kitchensink\)
> log4j:WARN No appenders could be found for logger (org.jboss.logging).
> log4j:WARN Please initialize the log4j system properly.
> 26-mar-2012 10:43:29 org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal
> INFO: Starting container with: ["C:\Archivos de programa\Java\jdk1.6.0_16\bin\java", -Xmx512m, -XX:MaxPermSize=128m, -Djboss.home.dir=C:\servers\jboss-as-7.1.0.Final, -Dorg.jboss.boot.log.file=C:\servers\jbo
> ss-as-7.1.0.Final/standalone/log/boot.log, -Dlogging.configuration=file:C:\servers\jboss-as-7.1.0.Final/standalone/configuration/logging.properties, -Djboss.modules.dir=C:\servers\jboss-as-7.1.0.Final\module
> s, -jar, C:\servers\jboss-as-7.1.0.Final\jboss-modules.jar, -mp, C:\servers\jboss-as-7.1.0.Final\modules, -logmodule, org.jboss.logmanager, -jaxpmodule, javax.xml.jaxp-provider, -mbeanserverbuildermodule, or
> g.jboss.as.jmx, org.jboss.as.standalone, -server-config, standalone.xml]
> WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java.util.logging.LogManager' service loader.
> Invalid option '-mbeanserverbuildermodule'
> Usage: java [-jvmoptions...] -jar jboss-modules.jar [-options...] <module-spec> [args...]
> java [-jvmoptions...] -jar jboss-modules.jar [-options...] -jar <jar-name> [args...]
> java [-jvmoptions...] -jar jboss-modules.jar [-options...] -cp <class-path> <class-name> [args...]
> java [-jvmoptions...] -jar jboss-modules.jar [-options...] -class <class-name> [args...]
> where <module-spec> is a valid module specification string
> and options include:
> -help Display this message
> -modulepath <search path of directories>
> -mp <search path of directories>
> A list of directories, separated by ';', where modules may be located
> If not specified, the value of the "module.path" system property is used
> -class Specify that the final argument is a
> class to load from the class path; not compatible with -jar
> -cp,-classpath <search path of archives or directories>
> A search path for class files; implies -class
> -dep,-dependencies <module-spec>[,<module-spec>,...]
> A list of module dependencies to add to the class path;
> requires -class or -cp
> -jar Specify that the final argument is the name of a
> JAR file to run as a module; not compatible with -class
> -config <config-location>
> The location of the module configuration. Either -mp or -config
> may be specified, but not both
> -jaxpmodule <module-name>
> The default JAXP implementation to use of the JDK
> -version Print version and exit
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.303 sec <<< FAILURE!
> Results :
> Tests in error:
> org.jboss.as.quickstarts.kitchensink.test.MemberRegistrationTest: Could not start container
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 8.332s
> [INFO] Finished at: Mon Mar 26 10:43:32 CEST 2012
> [INFO] Final Memory: 9M/16M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.10:test (default-test) on project jboss-as-kitchensink: There are test failures.
> [ERROR]
> [ERROR] Please refer to C:\servers\jboss-as-quickstarts-7.1.0.Final\kitchensink\target\surefire-reports for the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
--
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
[JBoss JIRA] (AS7-4284) Unable to deploy seam booking example
by Bikramjit Kahlon (JIRA)
Bikramjit Kahlon created AS7-4284:
-------------------------------------
Summary: Unable to deploy seam booking example
Key: AS7-4284
URL: https://issues.jboss.org/browse/AS7-4284
Project: Application Server 7
Issue Type: Bug
Components: Build System
Affects Versions: 7.1.1.Final
Environment: Window Vista
Reporter: Bikramjit Kahlon
Assignee: Paul Gier
Priority: Minor
Fix For: 7.1.1.Final
Installed
Jdk1.6.0_31
Ant 1.8.3
jboss-seam version 2.2.2
jboss-as-7.1.1.Final
1. setup the JAVA_HOME and ANT_HOME ... tested ok
2. started jboss as ... tested ok
3.Edited build.properties in Seam directory C:\jboss-seam\build.properties and configure "jboss.home C:\\jboss-as-7.1.1.Final" property with JBoss AS installation
4.In the c:/jboss-seam/examples/booking directory, type ant deploy.
got below error
============================
C:\jboss-seam\examples\booking>ant deploy
Buildfile: C:\jboss-seam\examples\booking\build.xml
initcopy:
initpoms:
[echo] Setting up dependencies
[copy] Copying 1 file to C:\jboss-seam\classes\poms
BUILD FAILED
C:\jboss-seam\build\common.build.xml:96: The following error occurred while exec
uting this line:
C:\jboss-seam\build\utilities.build.xml:80: artifact:install doesn't support the
"settingsFile" attribute
Total time: 1 second
--
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
[JBoss JIRA] (AS7-4288) TCCL not set correctly when configuring components
by Stuart Douglas (JIRA)
Stuart Douglas created AS7-4288:
-----------------------------------
Summary: TCCL not set correctly when configuring components
Key: AS7-4288
URL: https://issues.jboss.org/browse/AS7-4288
Project: Application Server 7
Issue Type: Bug
Components: EE
Affects Versions: 7.1.1.Final
Reporter: Stuart Douglas
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
TCCL is not set when configuring components, so classes can be loaded with the wrong TCCL set:
23:18:55,573 INFO [com.test.Environment] (MSC service thread 1-4) Reading config file config/mes/mes.xml
23:18:55,578 INFO [stdout] (MSC service thread 1-4) ClassLoader is ModuleClassLoader for Module "org.jboss.as.server:main" from local module loader @84da23 (roots: C:\work\java\jboss-as-7.1.1.Final\modules)
23:18:55,585 ERROR [stderr] (MSC service thread 1-4) java.lang.NullPointerException
23:18:55,589 ERROR [stderr] (MSC service thread 1-4) at com.test.XMLToStringConverter.readFromResource(XMLToStringConverter.java:58)
23:18:55,593 ERROR [stderr] (MSC service thread 1-4) at com.test.Environment.getParameterList(Environment.java:325)
23:18:55,599 ERROR [stderr] (MSC service thread 1-4) at com.test.Environment.getValue(Environment.java:379)
23:18:55,604 ERROR [stderr] (MSC service thread 1-4) at com.test.DateTimeHandler.<clinit>(DateTimeHandler.java:48)
23:18:55,609 ERROR [stderr] (MSC service thread 1-4) at com.test.SystemEventManager.getServerStartEvtContent(SystemEventManager.java:498)
23:18:55,616 ERROR [stderr] (MSC service thread 1-4) at com.test.Environment.<clinit>(Environment.java:81)
23:18:55,621 ERROR [stderr] (MSC service thread 1-4) at com.test.B2MMLInterfaceBean.<clinit>(B2MMLInterfaceBean.java:36)
23:18:55,626 ERROR [stderr] (MSC service thread 1-4) at java.lang.Class.forName0(Native Method)
23:18:55,630 ERROR [stderr] (MSC service thread 1-4) at java.lang.Class.forName(Class.java:247)
23:18:55,633 ERROR [stderr] (MSC service thread 1-4) at org.jboss.invocation.proxy.AbstractProxyFactory.afterClassLoad(AbstractProxyFactory.java:94)
23:18:55,638 ERROR [stderr] (MSC service thread 1-4) at org.jboss.invocation.proxy.AbstractClassFactory.defineClass(AbstractClassFactory.java:166)
23:18:55,643 ERROR [stderr] (MSC service thread 1-4) at org.jboss.invocation.proxy.AbstractProxyFactory.getCachedMethods(AbstractProxyFactory.java:145)
23:18:55,648 ERROR [stderr] (MSC service thread 1-4) at org.jboss.as.ejb3.component.stateless.StatelessComponentDescription$3.configure(StatelessComponentDescription.java:138)
23:18:55,654 ERROR [stderr] (MSC service thread 1-4) at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:921)
23:18:55,659 ERROR [stderr] (MSC service thread 1-4) at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81)
23:18:55,666 ERROR [stderr] (MSC service thread 1-4) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113)
23:18:55,671 ERROR [stderr] (MSC service thread 1-4) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
23:18:55,676 ERROR [stderr] (MSC service thread 1-4) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
23:18:55,682 ERROR [stderr] (MSC service thread 1-4) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
23:18:55,687 ERROR [stderr] (MSC service thread 1-4) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
23:18:55,691 ERROR [stderr] (MSC service thread 1-4) at java.lang.Thread.run(Thread.java:662)
--
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
[JBoss JIRA] (AS7-4159) Double-checked locking in org.jboss.weld.util.BeansClosure#getClosure is a cause for NPE
by Anton Arhipov (JIRA)
Anton Arhipov created AS7-4159:
----------------------------------
Summary: Double-checked locking in org.jboss.weld.util.BeansClosure#getClosure is a cause for NPE
Key: AS7-4159
URL: https://issues.jboss.org/browse/AS7-4159
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.1.1.Final, 7.1.0.Final
Environment: N/A
Reporter: Anton Arhipov
Assignee: Stuart Douglas
Application deployment fails with a following exception:
05:33:26,201 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.deployment.unit."exp-cdi-injectApplication.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."exp-cdi-injectApplication.war".WeldService: java.lang.NullPointerException
at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_27]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_27]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_27]
Caused by: java.lang.NullPointerException
at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:194)
at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:336)
at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
... 5 more
Looking at the code that belongs to weld-core-1.1.5.AS71.Final, we can see the following at the lines 193-194 of BeanDeployment:
193: BeansClosure closure = BeansClosure.getClosure(this.beanManager);
194: closure.addEnvironment(this.beanDeployer.getEnvironment());
Which leads to a conclusion that closure is null (the lines prior to the mentioned ones show that beanDeployer itself couldn't be null).
Looking into BeansClosure#getClosure():
public static BeansClosure getClosure(BeanManagerImpl beanManager)
{
BeansClosure closure = (BeansClosure)closureMap.get(beanManager);
if (closure == null) {
synchronized (closureMap) {
if (!closureMap.containsKey(beanManager)) {
closure = new BeansClosure();
for (Iterable beanManagers : BeanManagers.getAccessibleClosure(beanManager)) {
for (BeanManagerImpl accessibleBeanManager : beanManagers) {
closureMap.put(accessibleBeanManager, closure);
}
}
}
}
}
return closure;
}
To prevent race conditions, maybe it makes sense to reside the full method body into synchronized block.
--
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
[JBoss JIRA] (AS7-4279) Application Server is not Responding
by GUNASEKHAR YALAMURI (JIRA)
GUNASEKHAR YALAMURI created AS7-4279:
----------------------------------------
Summary: Application Server is not Responding
Key: AS7-4279
URL: https://issues.jboss.org/browse/AS7-4279
Project: Application Server 7
Issue Type: Clarification
Environment: Linux Centos 64 bit
Production
Reporter: GUNASEKHAR YALAMURI
Priority: Blocker
We are facing the Problem in our production server. The application was running fine for a day or two and later getting "Requested resource is not available for the initial jsp". From logs we can see that there are no errors while forwarding to jsp in the servlet. The issue was fixed when we restarted the server. Imagine restarting servers in production environment.
Jboss Version :jboss-as-7.0.1.Final
Server : Centos 64 bit
Any solution will be appreciable.
--
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
[JBoss JIRA] (JGRP-1441) Add external_addr for NATs
by Bela Ban (JIRA)
Bela Ban created JGRP-1441:
------------------------------
Summary: Add external_addr for NATs
Key: JGRP-1441
URL: https://issues.jboss.org/browse/JGRP-1441
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 3.0.9, 3.1
When NATting between an internal and external network, we can use external_addr, e.g.
<TCP bind_addr="127.0.4.4" bind_port="5000" external_addr="10.2.3.4".../>
This means that the looopback address 127.0.4.4:5000 is going to be mapped to 10.2.3.4:5000.
However, if the internal port is different from the external port, we don't support that.
SOLUTION: add external_port, e.g.
<TCP bind_addr="127.0.4.4" bind_port="5000" external_addr="10.2.3.4" external_port="6000" .../>
Now we're mapping internal port 5000 to external port 6000.
This needs to be done in TP, FD_SOCK, STATE_SOCK (check if there are more places where we create server sockets)
--
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