February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3603) Release and upgrade org.jboss.remoting3.remoting-jmx to GA

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3603: ------------------------------------- Summary: Release and upgrade org.jboss.remoting3.remoting-jmx to GA Key: AS7-3603 URL: https://issues.jboss.org/browse/AS7-3603 Project: Application Server 7 Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 7.1.0.Final -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-3602) Release and upgrade org.jboss.com.sun.httpserver to GA

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3602: ------------------------------------- Summary: Release and upgrade org.jboss.com.sun.httpserver to GA Key: AS7-3602 URL: https://issues.jboss.org/browse/AS7-3602 Project: Application Server 7 Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 7.1.0.Final -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-3594) Windows path problems with resource builder

by Jason Greene (JIRA)

Jason Greene created AS7-3594: --------------------------------- Summary: Windows path problems with resource builder Key: AS7-3594 URL: https://issues.jboss.org/browse/AS7-3594 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Jason Greene Assignee: Thomas Diesler Fix For: 7.1.0.Final From: http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-windows... Caused by: java.lang.IllegalStateException: java.io.FileNotFoundException: C:\Users\jenkins\jenkins-work\workspace\as7-master-windows-build\build\target\jboss-as-7.1.0.Final-SNAPSHOT\modules\rg\jboss\netty\main\netty-3.2.6.Final.jar (The system cannot find the path specified) at org.jboss.osgi.resolver.v2.spi.URLBasedResource.getContent(URLBasedResource.java:96) [jbosgi-repository-api-1.0.4.jar:1.0.4] at org.jboss.osgi.resolver.v2.XResourceBuilder.create(XResourceBuilder.java:95) [jbosgi-repository-api-1.0.4.jar:1.0.4] at org.jboss.as.osgi.service.ModuleIdentityArtifactProvider.findProviders(ModuleIdentityArtifactProvider.java:133) [jboss-as-osgi-service-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] ... 16 more Caused by: java.io.FileNotFoundException: C:\Users\jenkins\jenkins-work\workspace\as7-master-windows-build\build\target\jboss-as-7.1.0.Final-SNAPSHOT\modules\rg\jboss\netty\main\netty-3.2.6.Final.jar (The system cannot find the path specified) at java.io.FileInputStream.open(Native Method) [rt.jar:1.6.0_30] at java.io.FileInputStream.<init>(FileInputStream.java:120) [rt.jar:1.6.0_30] at org.jboss.osgi.resolver.v2.spi.URLBasedResource.getContent(URLBasedResource.java:91) [jbosgi-repository-api-1.0.4.jar:1.0.4] ... 18 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

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] (AS7-3500) Add org/w3c/dom/views to the javax.api module

by Robert Reimann (JIRA)

Robert Reimann created AS7-3500: ----------------------------------- Summary: Add org/w3c/dom/views to the javax.api module Key: AS7-3500 URL: https://issues.jboss.org/browse/AS7-3500 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.1.0.CR1b Reporter: Robert Reimann Please add the org/w3c/dom/views path to the javax.api module. {code} <path name="org/w3c/dom/views"/> {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

13 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1291) UserTransaction not exposed in JDNI

by Juergen Zimmermann (JIRA)

UserTransaction not exposed in JDNI ----------------------------------- Key: AS7-1291 URL: https://issues.jboss.org/browse/AS7-1291 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.0.0.Final Environment: 7.1.0.Alpha1 Jenkins build 1402 Reporter: Juergen Zimmermann Assignee: John Bailey In JBoss 6 UserTransaction was exposed in JNDI named as java:comp/UserTransaction. Thus an Arquillian test method could be encapsulated in one single transaction: * lookup() the UserTransaction * begin() inside @Before * commit() inside @After Unfortunately, JBoss 7 doesn't have a JNDI entry for UserTransaction. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

8
11
0 / 0

[JBoss JIRA] (JBRULES-3372) kbase.addKnowledgePackages() infinite loop

by Esteban Aliverti (JIRA)

Esteban Aliverti created JBRULES-3372: ----------------------------------------- Summary: kbase.addKnowledgePackages() infinite loop Key: JBRULES-3372 URL: https://issues.jboss.org/browse/JBRULES-3372 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.4.0.Beta2 Reporter: Esteban Aliverti Assignee: Mark Proctor Attachments: testProject.zip I have attached a simple project containing just 1 rule and some model classes. The rule is compiled ok, but when I try to add the generated package to a kbase, an infinite-loop (or what it seems like an infinite-loop) occurs. If you remove some of the patterns in the rule, everything works fine. I have debugged up to RuleTerminalNode.networkUpdated(). The execution never returns from that method. -- 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

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] (AS7-3598) It's impossible to add and activate resource adapter after .rar deployment

by Vladimir Rastseluev (JIRA)

Vladimir Rastseluev created AS7-3598: ---------------------------------------- Summary: It's impossible to add and activate resource adapter after .rar deployment Key: AS7-3598 URL: https://issues.jboss.org/browse/AS7-3598 Project: Application Server 7 Issue Type: Bug Reporter: Vladimir Rastseluev Assignee: Stefano Maestri Fix For: 7.1.0.Final 1.Deploy .rar archive 2.Add resource-adapters subsytem configuration for this .rar by DMR API 3.Try to proceed "activate" operation. Get error: "rar is not deployed yet" -- 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

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] (AS7-3578) Errors in data source subsystem checking

by Vladimir Rastseluev (JIRA)

Vladimir Rastseluev created AS7-3578: ---------------------------------------- Summary: Errors in data source subsystem checking Key: AS7-3578 URL: https://issues.jboss.org/browse/AS7-3578 Project: Application Server 7 Issue Type: Bug Components: JCA Reporter: Vladimir Rastseluev Assignee: Stefano Maestri Fix For: 7.1.0.Final 1) it's possible to add <flush-strategy> element with any value (not only listed in xsd schema) 2) it's possible to add <xa-data-source> element without any <xa-datasource-property>(in xsd schema minOccurs=1) 3) it's possible to add 2 or more <security-domain> elements without error(in xsd schema maxOccurs=1) -- 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

13 years, 10 months

1
2
0 / 0

[JBoss JIRA] (AS7-3380) Changing MDB configuration in jboss-ejb3.xml causes ClassCastException

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created AS7-3380: ------------------------------------- Summary: Changing MDB configuration in jboss-ejb3.xml causes ClassCastException Key: AS7-3380 URL: https://issues.jboss.org/browse/AS7-3380 Project: Application Server 7 Issue Type: Bug Reporter: Ondřej Chaloupka Assignee: jaikiran pai I did change of destination of mdb queue in jboss-ejb3.xml file in following way: https://github.com/ochaloup/jboss-as/commit/5a0501387821994b6a94ddb508f6f... But during deployment I get exception: java.lang.ClassCastException: org.jboss.metadata.ejb.spec.MessageDrivenBean31MetaData cannot be cast to org.jboss.metadata.ejb.jboss.ejb3.JBossGenericBeanMetaData {code} ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."mdb.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."mdb.jar".PARSE: Failed to process phase PARSE of deployment "mdb.jar" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [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$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] Caused by: java.lang.ClassCastException: org.jboss.metadata.ejb.spec.MessageDrivenBean31MetaData cannot be cast to org.jboss.metadata.ejb.jboss.ejb3.JBossGenericBeanMetaData at org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.merge(MessageDrivenBeanMetaData.java:353) at org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:85) at org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:36) at org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.merge(EnterpriseBeansMetaData.java:73) at org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.createMerged(EnterpriseBeansMetaData.java:52) at org.jboss.metadata.ejb.spec.EjbJarMetaData.merge(EjbJarMetaData.java:175) at org.jboss.metadata.ejb.spec.EjbJarMetaData.createMerged(EjbJarMetaData.java:668) at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.deploy(EjbJarParsingDeploymentUnitProcessor.java:125) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] ... 5 more {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

13 years, 10 months

3
5
0 / 0

[JBoss JIRA] (AS7-3599) Inconsistent Jacorb configuration

by Heiko Braun (JIRA)

Heiko Braun created AS7-3599: -------------------------------- Summary: Inconsistent Jacorb configuration Key: AS7-3599 URL: https://issues.jboss.org/browse/AS7-3599 Project: Application Server 7 Issue Type: Bug Components: IIOP Reporter: Heiko Braun Assignee: Stefan Guilhen {noformat} this config: <subsystem xmlns="urn:jboss:domain:jacorb:1.1"> <orb> <initializers security="on"/> </orb> <poa> <request-processors pool-size="2"/> </poa> <naming export-corbaloc="off"/> </subsystem> <subsystem xmlns="urn:jboss:domain:jaxrs:1.0"/> <subsystem xmlns="urn:jboss:domain:jca:1.1"> <archive-validation enabled="true"/> <bean-validation enabled="true"/> <default-workmanager> <short-running-threads> <core-threads count="50"/> <queue-length count="50"/> <max-threads count="50"/> <keepalive-time time="10" unit="seconds"/> </short-running-threads> <long-running-threads> <core-threads count="50"/> <queue-length count="50"/> <max-threads count="50"/> <keepalive-time time="10" unit="seconds"/> </long-running-threads> </default-workmanager> </subsystem> leads to : [Host Controller] Message: JBAS014724: Missing required attribute(s): POA_REQUEST_PROC_MAX_THREADS [Host Controller] at org.jboss.as.controller.parsing.ParseUtils.missingRequired(ParseUtils.java:134) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at org.jboss.as.jacorb.JacORBSubsystemParser.parseAttributes(JacORBSubsystemParser.java:683) [Host Controller] at org.jboss.as.jacorb.JacORBSubsystemParser.parsePOAConfig(JacORBSubsystemParser.java:399) [Host Controller] at org.jboss.as.jacorb.JacORBSubsystemParser.readElement_1_1(JacORBSubsystemParser.java:185) [Host Controller] at org.jboss.as.jacorb.JacORBSubsystemParser.readElement(JacORBSubsystemParser.java:91) [Host Controller] at org.jboss.as.jacorb.JacORBSubsystemParser.readElement(JacORBSubsystemParser.java:62) [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100) [staxmapper-1.0.0.Final.jar:1.0.0.Final] {noformat} -- 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

13 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2012