May 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3445) DSL expander expands lines in /* */comment block

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3445: ------------------------------------ Summary: DSL expander expands lines in /* */comment block Key: JBRULES-3445 URL: https://issues.jboss.org/browse/JBRULES-3445 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When you comment some code in dslr file, the expander still tries to expand it. -- 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

11 years, 11 months

2
8
0 / 0

[JBoss JIRA] (AS7-4667) EJB invocations from a remote server don't commit or rollback remote transaction

by v a (JIRA)

v a created AS7-4667: ------------------------ Summary: EJB invocations from a remote server don't commit or rollback remote transaction Key: AS7-4667 URL: https://issues.jboss.org/browse/AS7-4667 Project: Application Server 7 Issue Type: Bug Components: EJB, Transactions Affects Versions: 7.1.1.Final Environment: JBoss 7.1.1.Final or a nightly build Reporter: v a Assignee: jaikiran pai Priority: Critical If I call a remote EJB as described here https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+... a transaction on a remote server does not commit or rollback. -- 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

11 years, 11 months

2
4
0 / 0

[JBoss JIRA] (EJBTHREE-2282) JBoss EJB3 Plugin is not installed in jboss-5.1.0.GA

by muthukrishnan.muthu (JIRA)

muthukrishnan.muthu created EJBTHREE-2282: --------------------------------------------- Summary: JBoss EJB3 Plugin is not installed in jboss-5.1.0.GA Key: EJBTHREE-2282 URL: https://issues.jboss.org/browse/EJBTHREE-2282 Project: EJB 3.0 Issue Type: Bug Environment: OS: Windows 7, Java 1.6, jboss-5.1.0.GA Reporter: muthukrishnan.muthu Not able to install the JBoss EJB3 Plugin in Jboss 5, it shows the below error message. i tried with below steps, java -jar jboss-osgi-installer-1.1.0.jar %JBOSS_HOME% java -jar jboss-osgi-installer-1.1.0.jar $JBOSS_HOME java -jar jboss-osgi-installer-1.1.0.jar F:/jboss-5.1.0.GA Error message: C:\Users\admin\Downloads>java -jar jboss-osgi-installer-1.1.0.jar $JBOSS_HOME - ERROR - java.io.FileNotFoundException: $JBOSS_HOME (The system cannot find the file specified) java.io.FileNotFoundException: $JBOSS_HOME (The system cannot find the file specified) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(Unknown Source) at com.izforge.izpack.installer.AutomatedInstaller.getXMLData(Unknown Source) at com.izforge.izpack.installer.AutomatedInstaller.<init>(Unknown Source) at com.izforge.izpack.installer.Installer.main(Unknown Source) or C:\Users\admin\Downloads>java -jar jboss-osgi-installer-1.1.0.jar %JBOSS_HOME% - ERROR - java.io.FileNotFoundException: F:\BancTec\eFPTest\jboss-5.1.0.GA (Access is denied) java.io.FileNotFoundException: F:\BancTec\eFPTest\jboss-5.1.0.GA (Access is denied) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(Unknown Source) at com.izforge.izpack.installer.AutomatedInstaller.getXMLData(Unknown Source) at com.izforge.izpack.installer.AutomatedInstaller.<init>(Unknown Source) at com.izforge.izpack.installer.Installer.main(Unknown Source) C:\Users\admin\Downloads> how to inmplement EJB3 plug-in in Jboss 5 -- 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

11 years, 11 months

2
1
0 / 0

[JBoss JIRA] (JBAS-9492) Type of JMS Connection Factory ALWAYS "JMS Factory" on JBoss EAP 5.1?

by Daniel BR (JIRA)

Daniel BR created JBAS-9492: ------------------------------- Summary: Type of JMS Connection Factory ALWAYS "JMS Factory" on JBoss EAP 5.1? Key: JBAS-9492 URL: https://issues.jboss.org/browse/JBAS-9492 Project: Application Server 3 4 5 and 6 Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS (HornetQ) Affects Versions: JBossAS-5.1.0.GA Environment: CentOS 5.5, JBoss EAP 5.1. Reporter: Daniel BR Assignee: Clebert Suconic Priority: Blocker >From Admin Console we can successfully create JMS Connection Factories, and select type of factory as "JMS XA Factory" (or other); but after creation, when checking properties on Configuration tab, it always returns to "JMS Factory". We need "JMS XA Factory". -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3376) ActivationCancelledEvent causes process to stay in current node

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3376: ------------------------------------ Summary: ActivationCancelledEvent causes process to stay in current node Key: JBRULES-3376 URL: https://issues.jboss.org/browse/JBRULES-3376 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Description of problem: If the activation is cancelled by AgendaFilter (getCause() == FILTER) the Ruleflow stops at current Rule Task node and the process never ends. Version-Release number of selected component (if applicable): BRMS-5.3.0.dev5 How reproducible: Every time Steps to Reproduce: 1. Insert events to create Activations 2. Start process with rule task and add event listeners (Process, Agenda) 3. call fireAllRules with AgendaFilter parameter Actual results: Process is never finished nor it moves to next node once no activations are left to fire. Expected results: Process continues once all rules are fired and eventually completes. Additional info: Included workaround shows this problem on StatefulKnowledgeSession although the same problem is on stateless. -- 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

11 years, 11 months

2
11
0 / 0

[JBoss JIRA] (AS7-4681) SSOKey.hashCode() not consistent per node

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-4681: --------------------------------- Summary: SSOKey.hashCode() not consistent per node Key: AS7-4681 URL: https://issues.jboss.org/browse/AS7-4681 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical Fix For: 7.1.2.Final-redhat1 Because Class.hashCode() is not uniform across cluster nodes, cache lookup of credentials will fail due to the fact that hashCodes are serialized along with key objects to support hash lookups without requiring objects to be deserialized. The short of it is, replace the use of Class.hashCode() with Class.getName().hashCode(). -- 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

11 years, 11 months

2
1
0 / 0

[JBoss JIRA] (AS7-4699) Use OperationBuilder.addFileAsAttachment in the ServerDeploymentManager and DomainDeploymentManager impls

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4699: ------------------------------------- Summary: Use OperationBuilder.addFileAsAttachment in the ServerDeploymentManager and DomainDeploymentManager impls Key: AS7-4699 URL: https://issues.jboss.org/browse/AS7-4699 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Fix For: 7.2.0.Alpha1 The ServerDeploymentManager and DomainDeploymentManager interfaces allow users to pass in a File. Currently we immediate convert that File to a FileInputStream and use that IS in the resulting operation. That will force an in-memory copy. Instead, use the OperationBuilder.addFileAsAttachment method introduced in the parent task. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-4597) Slave host error handling in a managed domain should not assume the context failure description node can be converted to ModelType.OBJECT

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4597: ------------------------------------- Summary: Slave host error handling in a managed domain should not assume the context failure description node can be converted to ModelType.OBJECT Key: AS7-4597 URL: https://issues.jboss.org/browse/AS7-4597 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.1.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.2.Final-redhat1 This failure was reported following a failed op: Host Controller] 12:11:33,014 ERROR [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 1) JBAS014612: Operation ("composite") failed - address: ([]): java.lang.IllegalArgumentException [Host Controller] at org.jboss.dmr.ModelValue.getChild(ModelValue.java:108) [jboss-dmr-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1] [Host Controller] at org.jboss.dmr.ModelNode.get(ModelNode.java:798) [jboss-dmr-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1] [Host Controller] at org.jboss.as.domain.controller.operations.coordination.DomainFinalResultHandler.collectHostFailures(DomainFinalResultHandler.java:158) [jboss-as-host-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.domain.controller.operations.coordination.DomainFinalResultHandler.execute(DomainFinalResultHandler.java:80) [jboss-as-host-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:387) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:274) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:202) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationCoordinatorStepHandler.executeTwoPhaseOperation(OperationCoordinatorStepHandler.java:225) [jboss-as-host-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationCoordinatorStepHandler.execute(OperationCoordinatorStepHandler.java:118) [jboss-as-host-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.execute(PrepareStepHandler.java:85) [jboss-as-host-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:387) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:274) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:202) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:309) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:299) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:294) [jboss-as-domain-http-interface-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:201) [jboss-as-domain-http-interface-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:208) [jboss-as-domain-http-interface-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.as.domain.http.server.security.SubjectAssociationHandler.handle(SubjectAssociationHandler.java:51) [jboss-as-domain-http-interface-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) [Host Controller] at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:69) [Host Controller] at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81) [Host Controller] at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:710) [Host Controller] at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) [Host Controller] at org.jboss.as.domain.http.server.RealmReadinessFilter.doFilter(RealmReadinessFilter.java:54) [jboss-as-domain-http-interface-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] [Host Controller] at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81) [Host Controller] at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682) [Host Controller] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0] [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0] [Host Controller] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0] [Host Controller] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA-redhat-1.jar:2.0.0.GA-redhat-1] The relevant logic at DomainFinalResultHandler.collectHostFailures(DomainFinalResultHandler.java:158) does this: context.getFailureDescription().get(HOST_FAILURE_DESCRIPTIONS).set(hostFailureResults); The IAE indicates the ModelNode returned by context.getFailureDescription() has already been initialized to some other ModelType (probably ModelType.STRING) and thus can't be used to store a failure description with a ModelType.OBJECT structure. We need to figure out why the failure description was already initialized in order to decide how best to deal with this. -- 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

11 years, 11 months

2
4
0 / 0

[JBoss JIRA] (AS7-3575) Socket-binding-group add operation does not work

by Dominik Pospisil (JIRA)

Dominik Pospisil created AS7-3575: ------------------------------------- Summary: Socket-binding-group add operation does not work Key: AS7-3575 URL: https://issues.jboss.org/browse/AS7-3575 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Final Reporter: Dominik Pospisil Assignee: Brian Stansberry The socket-binding-group add operation does not work. Add operation fails with the error: 11:25:35,087 ERROR [org.jboss.as.controller.management-operation] (management-handler-threads - 8) JBAS014612: Operation ("add") failed - address: ([("socket-binding-group" => "test-sockets")]): org.jboss.msc.service.DuplicateServiceException: Service jboss.socket-binding-manager is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] Steps to reproduce: 1) start standalone server 2) connect via CLI 3) [standalone@localhost:9999 /] /socket-binding-group=test-sockets:add(default-interface="public") { "outcome" => "failed", "failure-description" => "JBAS014749: Operation handler failed: Service jboss.socket-binding-manager is already registered", "rolled-back" => true } -- 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

11 years, 11 months

3
8
0 / 0

[JBoss JIRA] (AS7-3807) Transaction manager ads 600-800ms to boot of AS

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-3807: -------------------------------- Summary: Transaction manager ads 600-800ms to boot of AS Key: AS7-3807 URL: https://issues.jboss.org/browse/AS7-3807 Project: Application Server 7 Issue Type: Enhancement Components: Transactions Affects Versions: 7.1.0.Final, 7.1.0.CR1b Environment: Windows 7 64bit Reporter: Tomaz Cerar Assignee: Jason Greene Priority: Critical While starting transaction manager it loads properties from XML and this adds quite lots of time to boot of AS for more info JBTM-1054 -- 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

11 years, 11 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2012