August 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1972) CLI command should not allow same runtime-name to be used at another deploy

by Emmanuel Hugonnet (JIRA)

Emmanuel Hugonnet created WFLY-1972: --------------------------------------- Summary: CLI command should not allow same runtime-name to be used at another deploy Key: WFLY-1972 URL: https://issues.jboss.org/browse/WFLY-1972 Project: WildFly Issue Type: Feature Request Components: Domain Management Reporter: Emmanuel Hugonnet Assignee: Brian Stansberry -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1972) CLI command should not allow same runtime-name to be used at another deploy

by Emmanuel Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-1972?page=com.atlassian.jira.plugin.... ] Emmanuel Hugonnet updated WFLY-1972: ------------------------------------ Description: Having two deployments with the same runtime-name in the domain content repository, so they can be deployed to different instances, is ok. Having two deployments with the same runtime name actually deployed to an instance is not (that's the issue here). Same for standalone. > CLI command should not allow same runtime-name to be used at another deploy > --------------------------------------------------------------------------- > > Key: WFLY-1972 > URL: https://issues.jboss.org/browse/WFLY-1972 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Emmanuel Hugonnet > Assignee: Brian Stansberry > > Having two deployments with the same runtime-name in the domain content repository, so they can be deployed to different instances, is ok. > Having two deployments with the same runtime name actually deployed to an instance is not (that's the issue here). > Same for standalone. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-244) Sliding windows working incorrectly

by Vytautas Gimbutas (JIRA)

[ https://issues.jboss.org/browse/DROOLS-244?page=com.atlassian.jira.plugin... ] Vytautas Gimbutas updated DROOLS-244: ------------------------------------- Attachment: Event.java file.drl Transaction.java TransactionCompletedEvent.java TransactionCreatedEvent.java TransactionEvent.java > Sliding windows working incorrectly > ----------------------------------- > > Key: DROOLS-244 > URL: https://issues.jboss.org/browse/DROOLS-244 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Vytautas Gimbutas > Assignee: Mark Proctor > Attachments: Event.java, file.drl, Transaction.java, TransactionCompletedEvent.java, TransactionCreatedEvent.java, TransactionEvent.java > > > I'm having an issue with sliding windows. For some reason even though event is in the past it still gets into the window. > I'm attaching drl file, the event/fact classes. > I expect it to print 1 0, but instead it prints: 1 1 > The code that reproduces the issue: > KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder(); > kbuilder.add(ResourceFactory.newClassPathResource("file.drl") , ResourceType.DRL); > if (kbuilder.hasErrors() ) { > System.out.println( kbuilder.getErrors() ); > } > KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase(); > kbase.addKnowledgePackages(kbuilder.getKnowledgePackages()); > StatefulKnowledgeSession ksession = kbase.newStatefulKnowledgeSession(); > Transaction transaction = new Transaction(); > TransactionCompletedEvent event = new TransactionCompletedEvent(); > event.setTransaction(transaction); > ksession.insert(transaction); > Date today = new Date(); > Calendar cal = new GregorianCalendar(); > cal.setTime(today); > cal.add(Calendar.DAY_OF_MONTH, -30); > event.setCreated(cal.getTime()); > WorkingMemoryEntryPoint wmep = ksession.getWorkingMemoryEntryPoint("TransactionCompletedEventStream"); > wmep.insert(event); > ksession.fireAllRules(); > TransactionCreatedEvent event2 = new TransactionCreatedEvent(); > event2.setTransaction(transaction); > ksession.insert(transaction); > ksession.getWorkingMemoryEntryPoint("TransactionCreatedEventStream").insert(event2); > ksession.fireAllRules(); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1907) The whoami operation is not usable with the JMX integration.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-1907?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-1907: ----------------------------------- Description: The whoami operation is not usable with the JMX integration as the return type is Void. Need to review the operation description for the correct return type. {code} [standalone@localhost:9990 /] :whoami(verbose=true) { "outcome" => "success", "result" => { "identity" => { "username" => "darranl", "realm" => "ManagementRealm" }, "groups" => [ "One", "Two", "Three" ], "roles" => [ "One", "Two", "Three" ] } } {code} was: The whoami operation is not usable with the JMX integration as the return type is Void. Need to review the operation description for the correct return type. > The whoami operation is not usable with the JMX integration. > ------------------------------------------------------------ > > Key: WFLY-1907 > URL: https://issues.jboss.org/browse/WFLY-1907 > Project: WildFly > Issue Type: Bug > Components: Domain Management, JMX > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Beta1 > > > The whoami operation is not usable with the JMX integration as the return type is Void. > Need to review the operation description for the correct return type. > {code} > [standalone@localhost:9990 /] :whoami(verbose=true) > { > "outcome" => "success", > "result" => { > "identity" => { > "username" => "darranl", > "realm" => "ManagementRealm" > }, > "groups" => [ > "One", > "Two", > "Three" > ], > "roles" => [ > "One", > "Two", > "Three" > ] > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1971) Add rotate-on-boot attribute to size-rotating-file-handler

by James Perkins (JIRA)

James Perkins created WFLY-1971: ----------------------------------- Summary: Add rotate-on-boot attribute to size-rotating-file-handler Key: WFLY-1971 URL: https://issues.jboss.org/browse/WFLY-1971 Project: WildFly Issue Type: Feature Request Components: Logging Reporter: James Perkins Assignee: James Perkins Add {{rotate-on-boot}} attribute to the {{size-rotating-file-handler}}. Property available in JBoss LogManger 1.5+. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-244) Sliding windows working incorrectly

by Vytautas Gimbutas (JIRA)

Vytautas Gimbutas created DROOLS-244: ---------------------------------------- Summary: Sliding windows working incorrectly Key: DROOLS-244 URL: https://issues.jboss.org/browse/DROOLS-244 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Vytautas Gimbutas Assignee: Mark Proctor I'm having an issue with sliding windows. For some reason even though event is in the past it still gets into the window. I'm attaching drl file, the event/fact classes. I expect it to print 1 0, but instead it prints: 1 1 The code that reproduces the issue: KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder(); kbuilder.add(ResourceFactory.newClassPathResource("file.drl") , ResourceType.DRL); if (kbuilder.hasErrors() ) { System.out.println( kbuilder.getErrors() ); } KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase(); kbase.addKnowledgePackages(kbuilder.getKnowledgePackages()); StatefulKnowledgeSession ksession = kbase.newStatefulKnowledgeSession(); Transaction transaction = new Transaction(); TransactionCompletedEvent event = new TransactionCompletedEvent(); event.setTransaction(transaction); ksession.insert(transaction); Date today = new Date(); Calendar cal = new GregorianCalendar(); cal.setTime(today); cal.add(Calendar.DAY_OF_MONTH, -30); event.setCreated(cal.getTime()); WorkingMemoryEntryPoint wmep = ksession.getWorkingMemoryEntryPoint("TransactionCompletedEventStream"); wmep.insert(event); ksession.fireAllRules(); TransactionCreatedEvent event2 = new TransactionCreatedEvent(); event2.setTransaction(transaction); ksession.insert(transaction); ksession.getWorkingMemoryEntryPoint("TransactionCreatedEventStream").insert(event2); ksession.fireAllRules(); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1909) Upgrade Remoting JMX to 2.0.0.CR1

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-1909?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-1909: ----------------------------------- Summary: Upgrade Remoting JMX to 2.0.0.CR1 (was: Upgrade Remoting JMX to 2.0.0 (Beta 3)) > Upgrade Remoting JMX to 2.0.0.CR1 > --------------------------------- > > Key: WFLY-1909 > URL: https://issues.jboss.org/browse/WFLY-1909 > Project: WildFly > Issue Type: Task > Components: JMX, Remoting > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Beta1 > > > This will bring in the changes that allow for local authentication to be disabled where username/password authentication is possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1970) Make mod_cluster status configurable

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-1970: ------------------------------------ Summary: Make mod_cluster status configurable Key: WFLY-1970 URL: https://issues.jboss.org/browse/WFLY-1970 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 8.0.0.Alpha4 Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 8.0.0.Beta1 There is a TODO in UndertowEventHandlerAdapter.start(StartContext) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1853) Pass the callers Subject from master domain controller to slaves and from host controllers to app servers.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-1853?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reopened WFLY-1853: ------------------------------------ > Pass the callers Subject from master domain controller to slaves and from host controllers to app servers. > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-1853 > URL: https://issues.jboss.org/browse/WFLY-1853 > Project: WildFly > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1853) Pass the callers Subject from master domain controller to slaves and from host controllers to app servers.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-1853?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-1853. ------------------------------------ Resolution: Done > Pass the callers Subject from master domain controller to slaves and from host controllers to app servers. > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-1853 > URL: https://issues.jboss.org/browse/WFLY-1853 > Project: WildFly > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2013