March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4061) CLONE - String configuration parameters for HornetQ address cannot be set via CLI

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4061?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reassigned AS7-4061: ------------------------------------- Assignee: Emanuel Muckenhuber (was: Clebert Suconic) Problem is AddressSettingsWriteHandler: def.getValidator().validateParameter(ModelDescriptionConstants.VALUE, operation); It should be: def.getValidator().validateParameter(ModelDescriptionConstants.VALUE, operation.get(ModelDescriptionConstants.VALUE)); Any similar write handlers in this subsystem should be checked for the same bug. > CLONE - String configuration parameters for HornetQ address cannot be set via CLI > --------------------------------------------------------------------------------- > > Key: AS7-4061 > URL: https://issues.jboss.org/browse/AS7-4061 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, JMS > Affects Versions: 7.1.0.Final > Reporter: Pavel Slavicek > Assignee: Emanuel Muckenhuber > Labels: eap6_need_triage > Fix For: 7.1.2.Final > > > String configuration parameters for HornetQ address cannot be set via CLI because of the following issue "JBAS014688: Wrong type for value. Expected [STRING] but was OBJECT". > pwd: > /subsystem=messaging/hornetq-server=default/address-setting=# > [standalone@localhost:9999 address-setting=#:read-attribute(name=redistribution-delay) > { > "outcome" => "success", > "result" => -1L > } > [standalone@localhost:9999 address-setting=#] :write-attribute(name=redistribution-delay, value=1000L) > {"outcome" => "success"} > [standalone@localhost:9999 address-setting=#:read-attribute(name=redistribution-delay) > { > "outcome" => "success", > "result" => 1000L > } > [standalone@localhost:9999 address-setting=#] :write-attribute(name=address-full-policy, value=PAGE) > { > "outcome" => "failed", > "failure-description" => "JBAS014688: Wrong type for value. Expected [STRING] but was OBJECT", > "rolled-back" => true > } > [standalone@localhost:9999 address-setting=#] :write-attribute(name=address-full-policy, value="PAGE") > { > "outcome" => "failed", > "failure-description" => "JBAS014688: Wrong type for value. Expected [STRING] but was OBJECT", > "rolled-back" => true > } > [standalone@localhost:9999 address-setting=#] :write-attribute(name=expiry-address, value="jms.queue.DLQ") > { > "outcome" => "failed", > "failure-description" => "JBAS014688: Wrong type for value. Expected [STRING] but was OBJECT", > "rolled-back" => true > } > [standalone@localhost:9999 address-setting=#] ls -l > ATTRIBUTE VALUE TYPE > address-full-policy BLOCK STRING > dead-letter-address jms.queue.DLQ STRING > expiry-address jms.queue.ExpiryQueue STRING > last-value-queue false BOOLEAN > max-delivery-attempts 10 INT > max-size-bytes 10485760 INT > message-counter-history-day-limit 10 INT > page-max-cache-size 5 INT > page-size-bytes 10485760 LONG > redelivery-delay 0 INT > redistribution-delay -1 LONG > send-to-dla-on-no-route false BOOLEAN -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4061) CLONE - String configuration parameters for HornetQ address cannot be set via CLI

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4061?page=com.atlassian.jira.plugin.s... ] Brian Stansberry moved JBPAPP-8365 to AS7-4061: ----------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-4061 (was: JBPAPP-8365) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.0.Final (was: EAP 6.0.0 ER 1) Component/s: Domain Management JMS (was: HornetQ) Security: (was: Public) Fix Version/s: 7.1.2.Final (was: TBD EAP 6) Docs QE Status: (was: NEW) > CLONE - String configuration parameters for HornetQ address cannot be set via CLI > --------------------------------------------------------------------------------- > > Key: AS7-4061 > URL: https://issues.jboss.org/browse/AS7-4061 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, JMS > Affects Versions: 7.1.0.Final > Reporter: Pavel Slavicek > Assignee: Clebert Suconic > Labels: eap6_need_triage > Fix For: 7.1.2.Final > > > String configuration parameters for HornetQ address cannot be set via CLI because of the following issue "JBAS014688: Wrong type for value. Expected [STRING] but was OBJECT". > pwd: > /subsystem=messaging/hornetq-server=default/address-setting=# > [standalone@localhost:9999 address-setting=#:read-attribute(name=redistribution-delay) > { > "outcome" => "success", > "result" => -1L > } > [standalone@localhost:9999 address-setting=#] :write-attribute(name=redistribution-delay, value=1000L) > {"outcome" => "success"} > [standalone@localhost:9999 address-setting=#:read-attribute(name=redistribution-delay) > { > "outcome" => "success", > "result" => 1000L > } > [standalone@localhost:9999 address-setting=#] :write-attribute(name=address-full-policy, value=PAGE) > { > "outcome" => "failed", > "failure-description" => "JBAS014688: Wrong type for value. Expected [STRING] but was OBJECT", > "rolled-back" => true > } > [standalone@localhost:9999 address-setting=#] :write-attribute(name=address-full-policy, value="PAGE") > { > "outcome" => "failed", > "failure-description" => "JBAS014688: Wrong type for value. Expected [STRING] but was OBJECT", > "rolled-back" => true > } > [standalone@localhost:9999 address-setting=#] :write-attribute(name=expiry-address, value="jms.queue.DLQ") > { > "outcome" => "failed", > "failure-description" => "JBAS014688: Wrong type for value. Expected [STRING] but was OBJECT", > "rolled-back" => true > } > [standalone@localhost:9999 address-setting=#] ls -l > ATTRIBUTE VALUE TYPE > address-full-policy BLOCK STRING > dead-letter-address jms.queue.DLQ STRING > expiry-address jms.queue.ExpiryQueue STRING > last-value-queue false BOOLEAN > max-delivery-attempts 10 INT > max-size-bytes 10485760 INT > message-counter-history-day-limit 10 INT > page-max-cache-size 5 INT > page-size-bytes 10485760 LONG > redelivery-delay 0 INT > redistribution-delay -1 LONG > send-to-dla-on-no-route false BOOLEAN -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBEE-107) WebResourcePermission for negative permissions is doing incorrect implies

by Anil Saldhana (JIRA)

Anil Saldhana created JBEE-107: ---------------------------------- Summary: WebResourcePermission for negative permissions is doing incorrect implies Key: JBEE-107 URL: https://issues.jboss.org/browse/JBEE-107 Project: JBoss JavaEE Spec APIs Issue Type: Bug Components: jboss-jacc-api Reporter: Anil Saldhana Assignee: Anil Saldhana -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] (JASSIST-157) Add ExprEditor.edit(ParameterAccess)

by Ben Romberg (JIRA)

Ben Romberg created JASSIST-157: ----------------------------------- Summary: Add ExprEditor.edit(ParameterAccess) Key: JASSIST-157 URL: https://issues.jboss.org/browse/JASSIST-157 Project: Javassist Issue Type: Feature Request Affects Versions: 3.16.0-GA Reporter: Ben Romberg Assignee: Shigeru Chiba Provide the ability to detect read-/write-access on method parameters. Should be easy to do, as those are all a/i/...load/store <n> instructions, where n <= number of parameters. Alternatively, allow extension of ExprEditor without copying the whole class (as loopBody is 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBAS-2861) HttpSession sharing between WAR modules

by Himanshu Gupta (JIRA)

[ https://issues.jboss.org/browse/JBAS-2861?page=com.atlassian.jira.plugin.... ] Himanshu Gupta commented on JBAS-2861: -------------------------------------- Need to open this bug - this issue still persists in JBoss 7.1.0.Final. > HttpSession sharing between WAR modules > --------------------------------------- > > Key: JBAS-2861 > URL: https://issues.jboss.org/browse/JBAS-2861 > Project: Application Server 3 4 5 and 6 > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering, Web (Tomcat) service > Affects Versions: JBossAS-3.2.6 Final, JBossAS-3.2.7 Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: No Release > > > Creating a redacted version of JBAS-1909, which was opened as a non-public JIRA issue by a customer. > Our J2EE application is composed of several modules, each one addressing one facet of our business process, and currently this application has one web module (WAR) and several JAR modules (EJB). > We need to divide this web module into several smaller web modules. > In order to separate our unique WAR file into several WARs we must guarantee HttpSession sharing. This is due to the fact that we have a lot of session attributes that are used throughout the entire application and we cannot afford to refactor the application, in fact, that's impossible. > The security aspects for this requirement are completely addressed by the JBoss/Tomcat Single Sign-On mechanism but the session sharing requirements are not. > The ideal scenario is to keep the same HttpSession (same object in the heap, same session ID) when authenticating into one application (HttpSession created) and then forwarding to another application. > The current SSO mechanism allows the user to access the second application without reauthentication, as you know, but it creates a new HttpSession object. Also, if the two WARs have different session timeouts, if you access application A, migrates to application B, stays there until session in application A expires and then returns to application A from application B, a new HttpSession is also created in application A. > The ideal solution is to have one unique, monolithic session to all web applications configured to share a common session. IBM WebSphere and BEA WebLogic do have this configuration and feature. Please check the links below in case you want more information: > WebSphere Application Server V5: Sharing Session Context - http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/tips0215.ht... > BEA Weblogic - Enabling Web applications to share the same session - http://e-docs.bea.com/wls/docs90/webapp/sessions.html -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1722) dropped message WARNING on node leaving a group

by Radoslav Husar (JIRA)

dropped message WARNING on node leaving a group ----------------------------------------------- Key: AS7-1722 URL: https://issues.jboss.org/browse/AS7-1722 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.0.1.Final, 7.0.0.Final Reporter: Radoslav Husar Assignee: Paul Ferraro On node leaving the group there is a warning {code} 17:57:31,340 INFO [org.jboss.as.clustering.CoreGroupCommunicationService.lifecycle.web] (Incoming-13,web,rhusar-7808) New cluster view for partition web (id: 4, delta: -1, merge: false) : [rhusar-7808] 17:57:31,340 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-13,web,rhusar-7808) ISPN000094: Received new cluster view: [rhusar-7808|4] [rhusar-7808] 17:57:31,345 WARNING [org.jgroups.protocols.pbcast.NAKACK] (Incoming-15,web,rhusar-7808) rhusar-7808: dropped message from rhusar-41106 (not in table [rhusar-7808]), view=[rhusar-7808|4] [rhusar-7808] {code} because it removes the member before receiving the last message {code} 17:57:31,286 INFO [org.jboss.as.clustering.infinispan.subsystem] Stopped repl cache from web container 17:57:31,290 INFO [jacorb.orb] prepare ORB for shutdown... 17:57:31,290 INFO [jacorb.orb] ORB going down... 17:57:31,305 INFO [jacorb.orb.iiop] Listener exited 17:57:31,310 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] ISPN000080: Disconnecting and closing JGroups Channel 17:57:31,312 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [8ee2c584-d740-11e0-ad66-0022fabb0b50] stopped 17:57:31,310 INFO [jacorb.orb] ORB shutdown complete 17:57:31,313 INFO [jacorb.orb] ORB run, exit 17:57:31,349 INFO [org.jboss.as.server.deployment] Stopped deployment SessionTest-2.0-SNAPSHOT.war in 197ms 17:57:31,636 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] ISPN000082: Stopping the RpcDispatcher 17:57:31,637 INFO [com.arjuna.ats.jbossatx] ARJUNA32018: Destroying TransactionManagerService 17:57:31,638 INFO [com.arjuna.ats.jbossatx] ARJUNA32014: Stopping transaction recovery manager {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
3
0 / 0

[JBoss JIRA] (AS7-4040) Add AJP connector to default HA configuration

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-4040: --------------------------------- Summary: Add AJP connector to default HA configuration Key: AS7-4040 URL: https://issues.jboss.org/browse/AS7-4040 Project: Application Server 7 Issue Type: Feature Request Components: Web Affects Versions: 7.1.0.Final Reporter: Paul Ferraro Assignee: Jean-Frederic Clere Fix For: 7.1.1.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

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] (AS7-2407) Cannot connect to domain controller - more detail needed

by Kevin Barfield (Created) (JIRA)

Cannot connect to domain controller - more detail needed -------------------------------------------------------- Key: AS7-2407 URL: https://issues.jboss.org/browse/AS7-2407 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Kevin Barfield Assignee: Brian Stansberry There needs to be more detail when a host controller can't connect to a domain controller. Several times we saw the "cannot connect to the domain controller" message when we knew the two servers could see each other. The host tried 5-6 times to connect then shut down. There were no other messages on the host or domain controller with more detail (even at DEBUG logging level). We could stop the domain controller while the host was trying to connect and we would see an immediate error message on the host. -- 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, 1 month

4
4
0 / 0

[JBoss JIRA] (AS7-3966) In domain mode, stop-server command on server-group fails

by Bernard Tison (JIRA)

Bernard Tison created AS7-3966: ---------------------------------- Summary: In domain mode, stop-server command on server-group fails Key: AS7-3966 URL: https://issues.jboss.org/browse/AS7-3966 Project: Application Server 7 Issue Type: Bug Reporter: Bernard Tison My setup: domain controller + host controller server group main-server-group, with one server server is running when from the CLI I issue the command: /server-group=main-server-group:stop-servers the command fails with error message: { "outcome" => "failed", "failure-description" => {"domain-failure-description" => "JBAS014749: Operation handler failed: null"}, "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

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] (AS7-4058) Investigate use of OperationContext.completeStep() from within

by Kabir Khan (JIRA)

Kabir Khan created AS7-4058: ------------------------------- Summary: Investigate use of OperationContext.completeStep() from within Key: AS7-4058 URL: https://issues.jboss.org/browse/AS7-4058 Project: Application Server 7 Issue Type: Feature Request Reporter: Kabir Khan The lines are highlighted in https://github.com/jbossas/jboss-as/pull/1709/files HandlerDisable and HandlerEnable do things like public void execute(OperationContext context, ModelNode operation) { if (context.isNormalServer()) { context.addStep(new OperationStepHandler() { if (controller != null) { controller.addListener(new AbstractServiceListener<Object>() { public void listenerAdded(ServiceController<?> serviceController) { serviceController.setMode(ServiceController.Mode.NEVER); } @Override public void transition(ServiceController<?> serviceController, ServiceController.Transition transition) { if (transition == ServiceController.Transition.STOPPING_to_DOWN) { context.completeStep(); <<<< } } }); } else { context.completeStep(); } } }, OperationContext.Stage.RUNTIME); } context.completeStep(); } -- 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, 1 month

1
2
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 March 2012