August 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-640) Verify objects before casting

by Jesper Pedersen (JIRA)

Verify objects before casting ----------------------------- Key: JBJCA-640 URL: https://issues.jboss.org/browse/JBJCA-640 Project: IronJacamar Issue Type: Bug Components: Deployer Affects Versions: 1.0.1.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Critical Fix For: 1.0.2.Final, 1.1.0.Alpha1 Resource adapter objects, like ResourceAdapter, ManagedConnectionFactory and ActivationSpec should be verified before a type cast is performed -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1456) How to configure keystore-type and ciphers in jboss 7.0 standalone

by Gabriel Rabbaa (JIRA)

How to configure keystore-type and ciphers in jboss 7.0 standalone ------------------------------------------------------------------ Key: AS7-1456 URL: https://issues.jboss.org/browse/AS7-1456 Project: Application Server 7 Issue Type: Feature Request Reporter: Gabriel Rabbaa Fix For: 7.0.0.Final Hi, I'm trying to configure standalone.xml file in order to use my keystore certificate but I need to add some more attributes like keystoreType and ciphers. is it possible to do it? At the moment could just configure the file store location and its password {code} <connector name="https" scheme="https" protocol="HTTP/1.1" socket-binding="https" secure="true"> <ssl name="https" password="my_password" certificate-key-file="../standalone/configuration/server.keystore"/> </connector> {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1445) Pax-Logging deployment hangs server

by Thomas Diesler (JIRA)

Pax-Logging deployment hangs server ----------------------------------- Key: AS7-1445 URL: https://issues.jboss.org/browse/AS7-1445 Project: Application Server 7 Issue Type: Bug Reporter: Thomas Diesler Arnaud says, Trying to deploy an application using pax-logging (1.6.3), it seems to hang JBoss AS (7) By waiting some time I had the stackoverflow stack trace above, os I suspected something wrong with pax-logging service. If I remove pax-logging service from my application, it works fine. As JBoss 7 allow to deploy bundles direcly, I tried to deploy pax-logging-api and pax-logging-service directly and it seems to hand Jboss as well, the server stop to answer, but anything is log A simple way t reproduce, start a JBoss AS 7 server, go to the JBoss console (http://127.0.0.1:9990/console/App.html), the console page should be displayed Copy pax-logging-api and pax-logging-service in $JBOSS_HOME/standalone/deployments, wait for pax logging bundles to be deployed Then try to go to the jboss console again, it does not respond anymore. Is it a known issue ? is there any special configuration to have pax logging service to work with JBoss 7 ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (JBRULES-2949) Drools eclipse plugins build should not output stacktraces when trying to check the p2 repository (since upgrade to tycho 0.11.0)

by Geoffrey De Smet (JIRA)

Drools eclipse plugins build should not output stacktraces when trying to check the p2 repository (since upgrade to tycho 0.11.0) --------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2949 URL: https://issues.jboss.org/browse/JBRULES-2949 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Priority: Optional [INFO] Resolving target platform for project MavenProject: org.drools:org.drools.eclipse:5.2.0-SNAPSHOT @ /home/gdesmet/projects/jboss/droolsjbpm/droolsjbpm-tools/drools-eclipse/org.drools.eclipse/pom.xml java.io.FileNotFoundException: /home/gdesmet/.m2/repository/org/drools/org.drools.eclipse/5.2.0.M1/org.drools.eclipse-5.2.0.M1-p2artifacts.xml (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:106) at org.sonatype.tycho.p2.repository.LocalRepositoryReader.getContents(LocalRepositoryReader.java:28) at org.sonatype.tycho.p2.repository.LocalRepositoryReader.getContents(LocalRepositoryReader.java:22) at org.sonatype.tycho.p2.maven.repository.AbstractMavenArtifactRepository.loadMaven(AbstractMavenArtifactRepository.java:73) at org.sonatype.tycho.p2.maven.repository.AbstractMavenArtifactRepository.<init>(AbstractMavenArtifactRepository.java:61) at org.sonatype.tycho.p2.maven.repository.LocalArtifactRepository.<init>(LocalArtifactRepository.java:51) at org.sonatype.tycho.p2.impl.resolver.P2ResolverImpl.setLocalRepositoryLocation(P2ResolverImpl.java:661) at org.sonatype.tycho.p2.facade.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:196) at org.sonatype.tycho.p2.facade.P2TargetPlatformResolver.resolvePlatform(P2TargetPlatformResolver.java:151) at org.codehaus.tycho.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:86) at org.codehaus.tycho.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:94) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:273) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) java.io.FileNotFoundException: /home/gdesmet/.m2/repository/org/drools/org.drools.eclipse.feature/5.2.0.M1/org.drools.eclipse.feature-5.2.0.M1-p2artifacts.xml (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:106) at org.sonatype.tycho.p2.repository.LocalRepositoryReader.getContents(LocalRepositoryReader.java:28) at org.sonatype.tycho.p2.repository.LocalRepositoryReader.getContents(LocalRepositoryReader.java:22) at org.sonatype.tycho.p2.maven.repository.AbstractMavenArtifactRepository.loadMaven(AbstractMavenArtifactRepository.java:73) at org.sonatype.tycho.p2.maven.repository.AbstractMavenArtifactRepository.<init>(AbstractMavenArtifactRepository.java:61) at org.sonatype.tycho.p2.maven.repository.LocalArtifactRepository.<init>(LocalArtifactRepository.java:51) at org.sonatype.tycho.p2.impl.resolver.P2ResolverImpl.setLocalRepositoryLocation(P2ResolverImpl.java:661) at org.sonatype.tycho.p2.facade.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:196) at org.sonatype.tycho.p2.facade.P2TargetPlatformResolver.resolvePlatform(P2TargetPlatformResolver.java:151) at org.codehaus.tycho.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:86) at org.codehaus.tycho.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:94) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:273) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) ... [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
9
0 / 0

[JBoss JIRA] Created: (AS7-949) JBoss Negotiation Toolkit shoud not be required to depend on org.jboss.logmanager

by Darran Lofthouse (JIRA)

JBoss Negotiation Toolkit shoud not be required to depend on org.jboss.logmanager --------------------------------------------------------------------------------- Key: AS7-949 URL: https://issues.jboss.org/browse/AS7-949 Project: Application Server 7 Issue Type: Bug Components: Modules Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (SECURITY-608) Switch to PicketBox Base64

by Darran Lofthouse (JIRA)

Switch to PicketBox Base64 -------------------------- Key: SECURITY-608 URL: https://issues.jboss.org/browse/SECURITY-608 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Reporter: Darran Lofthouse Assignee: Darran Lofthouse The PicketBox Base64 impl is now available in AS7 so we can switch to it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files

by Emmanuel Bernard (JIRA)

Should we add a relax flag for people using out of order content inside elements of their XML files --------------------------------------------------------------------------------------------------- Key: JBAS-8268 URL: https://jira.jboss.org/browse/JBAS-8268 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployers Affects Versions: 6.0.0.M4 Reporter: Emmanuel Bernard Assignee: Ales Justin Fix For: 6.0.0.Final It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the content in elements https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_... Would it make sense to have a flag to relax this rule? I am thinking of people with existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of use and less pain in support down the road). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

6
15
0 / 0

[JBoss JIRA] Created: (JGRP-1349) JChannel InputStream constructor

by Jesper Pedersen (JIRA)

JChannel InputStream constructor -------------------------------- Key: JGRP-1349 URL: https://issues.jboss.org/browse/JGRP-1349 Project: JGroups Issue Type: Feature Request Affects Versions: 3.0 Reporter: Jesper Pedersen Assignee: Bela Ban It would be nice to have a JChannel(java.io.InputStream) constructor for environments where the XML configuration is loaded through a classloader. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1402) domain-preview.xml bootstrap errors

by Heiko Braun (JIRA)

domain-preview.xml bootstrap errors ----------------------------------- Key: AS7-1402 URL: https://issues.jboss.org/browse/AS7-1402 Project: Application Server 7 Issue Type: Bug Components: JMS Reporter: Heiko Braun Assignee: Clebert Suconic The serves throws these errors when booting the preview.xml: {noformat} [Server:server-one] 14:37:20,714 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.messaging.jms.connection-factory.RemoteConnectionFactory: org.jboss.msc.service.StartException in service jboss.messaging.jms.connection-factory.RemoteConnectionFactory: failed to create connection-factory [Server:server-one] at org.jboss.as.messaging.jms.ConnectionFactoryService.start(ConnectionFactoryService.java:83) [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] [Server:server-one] at java.lang.Thread.run(Thread.java:680) [:1.6.0_26] [Server:server-one] Caused by: HornetQException[errorCode=104 message=Connector 'netty' not found on the main configuration file] [Server:server-one] at org.hornetq.jms.server.impl.JMSServerManagerImpl.internalCreateCFPOJO(JMSServerManagerImpl.java:1174) {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (AS7-1281) Cannot deploy different EARs with same WARs inside.

by Juri Timošin (JIRA)

Cannot deploy different EARs with same WARs inside. --------------------------------------------------- Key: AS7-1281 URL: https://issues.jboss.org/browse/AS7-1281 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.0.0.Final Environment: $uname -a Linux 2.6.38-10-generic-pae #46-Ubuntu SMP Tue Jun 28 16:54:49 UTC 2011 i686 i686 i386 GNU/Linux Reporter: Juri Timošin Assignee: Carlo de Wolf Hello, I have a problem of deploying several EARs on jboss-as-7.0.0-Final. I have 2 EARs, both have test.war inside them. I cannot deploy both EARs at the same time 10:09:31,237 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.subunit."myTest.ear"."test.war".INSTALL: org.jboss.msc. service.StartException in service jboss.deployment.subunit."myTest.ear"."test.war".INSTALL: Failed to process phase INSTALL of subdeployment "test.war" of deployment "myTest.ear" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to add JBoss web deployment service at org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:234) at org.jboss.as.web.deployment.WarDeploymentProcessor.deploy(WarDeploymentProcessor.java:105) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) ... 5 more Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.web.realm."test.war" is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:226) at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2194) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2194) at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) at org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:209) ... 7 more If I deploy them 1 by 1 then only the first one deploys. If i deploy them both at the same time, then both deployments are rolled back. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

5
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2011