February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2483) Datasource model : dicrepancy between description and restart-required attribute

by Vimal Kansal (Created) (JIRA)

Datasource model : dicrepancy between description and restart-required attribute -------------------------------------------------------------------------------- Key: AS7-2483 URL: https://issues.jboss.org/browse/AS7-2483 Project: Application Server 7 Issue Type: Bug Reporter: Vimal Kansal Model returns : "background-validation-millis" => { "description" => "The background-validation-millis element specifies the amount of time, in milliseconds, that background validation will run. Changing this value require a server rest "type" => LONG, "required" => false, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }, The description says server restart required whereas "restart-required" says no. -- 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, 2 months

4
3
0 / 0

[JBoss JIRA] (AS7-1338) Remote JNDI support for AS7

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ] Miroslav Novak commented on AS7-1338: ------------------------------------- Hi all, I'm just adding some brief info from John about newly implemented remote jndi support and how to use it. As I understood everything what should be reachable in jndi from outside the server must be registered under "java:jboss/exported/" context. As an example I used it in standalone jms client to get connection factory and queue from jndi: {code} // jms client code // initialize context final Properties env = new Properties(); env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); env.put(Context.PROVIDER_URL, "remote://localhost:4447"); Context context = new InitialContext(env); // do lookups ConnectionFactory cf = (ConnectionFactory) context.lookup("jms/RemoteConnectionFactory"); Queue queue = (Queue) context.lookup("jms/queue/test"); // do whatever you want {code} How are jms objects registered to jndi in messaging subsystem in standalone-ha.xml: {code} <jms-connection-factories> ...  <connection-factory name="RemoteConnectionFactory"> <connectors> <connector-ref connector-name="netty"/> </connectors> <entries> <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/> <!- this is the important part --> </entries> </connection-factory> ... </jms-connection-factories> <jms-destinations> ... <jms-queue name="testQueue"> <entry name="java:jboss/exported/jms/queue/test"/> <!- this is the important part --> </jms-queue> ... </jms-destinations> {code} Used libraries (in my simple client): hornetq-core-2.2.11.Final.jar hornetq-jms-2.2.11.Final.jar jboss-as-naming-7.1.0.Final-SNAPSHOT.jar jboss-jms-api_1.1_spec-1.0.0.Final.jar jboss-logging-3.1.0.GA.jar jboss-marshalling-1.3.6.GA.jar jboss-marshalling-river-1.3.6.GA.jar jboss-modules.jar jboss-msc-1.0.2.GA.jar jboss-remote-naming-1.0.0.Beta4.jar jboss-remoting-3.2.0.CR9.jar jboss-sasl-1.0.0.Beta9.jar netty-3.2.6.Final.jar xnio-api-3.0.0.GA.jar xnio-nio-3.0.0.GA.jar Note: I had to add static block to my class so I could connect to server through remoting: {code} static { Security.addProvider(new JBossSaslProvider()); } {code} Hopefully I didn't forget anything and this info will help. Thanks for this cool feature, Mirek > Remote JNDI support for AS7 > --------------------------- > > Key: AS7-1338 > URL: https://issues.jboss.org/browse/AS7-1338 > Project: Application Server 7 > Issue Type: Task > Components: Naming > Reporter: Richard Opalka > Assignee: John Bailey > Priority: Critical > Labels: eap6_prd_req > Fix For: 7.1.0.Final > > > Add support for remote JNDI after all. It was agreed that: > * Remote JNDI would run over Remoting > * Remote JNDI for EJB is strictly a legacy access protocol, deprecated in favor of "ejb:" > * The Remote JNDI service would proxy to a specific Context of the server JNDI tree - maybe "java:jboss/shared", maybe something else > * Server-side services would opt-in to Remote JNDI; initially we'd only support: > ** Remote EJB interfaces > ** HornetQ connection factories > * In the future we may support: > ** User bindings, so long as they're serializable > * In the future we will never support: > ** Proxied DataSources > ** Proxied JMS invocations > Initial project tree is at https://github.com/dmlloyd/jboss-remote-jndi for now. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-3462) Server instances in domain aren't running with '-server' argument out-of-the-box

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created AS7-3462: -------------------------------------- Summary: Server instances in domain aren't running with '-server' argument out-of-the-box Key: AS7-3462 URL: https://issues.jboss.org/browse/AS7-3462 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Rostislav Svoboda Assignee: Brian Stansberry Fix For: 7.1.0.Final AS7-2491 fixed '-server' issue for PC and HC but server instances in domain aren't running with '-server' argument out-of-the-box. For standalone it's running out-of-the-box. Please develop functionality to add '-server' argument automatically (if JVM enables that) during server instances initialization. Currently user is forced to edit host.xml, section 'jvms': {code} <jvm name="default"> <heap size="64m" max-size="256m"/> <permgen size="256m" max-size="256m"/> <jvm-options> <option value="-server"/> </jvm-options> </jvm> {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

14 years, 2 months

3
2
0 / 0

[JBoss JIRA] (AS7-3616) DomainModelControllerService equals() is broken

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-3616: ------------------------------------- Summary: DomainModelControllerService equals() is broken Key: AS7-3616 URL: https://issues.jboss.org/browse/AS7-3616 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.CR1b Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.1.0.Final DomainModelControllerService has a very funky hashCode()/equals()/toString(). The equals() is definitely broken. I'm wondering if there is any reason for those to override the defaults from Object. -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] (AS7-3584) Better error reporting is needed when host attempts to register with a name already registered

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3584: ------------------------------------- Summary: Better error reporting is needed when host attempts to register with a name already registered Key: AS7-3584 URL: https://issues.jboss.org/browse/AS7-3584 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Brian Stansberry Fix For: 7.1.0.Final Register a master / slave set up and leave the setup so the slave has the name 'master' the master will attempt to connect, will exchange some messages and the master DC eventually reports: - "JBAS010832: There is already a registered host named 'master'" The slave however keeps on trying to connect again and again eventually giving up after opening without closing 100 connections to the master DC, at no point does the error get reported to an end user to actually correct the simple mistake. -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-1866) Update mod_cluster to 1.2.0.Final

by Radoslav Husar (JIRA)

Update mod_cluster to 1.2.0.Final --------------------------------- Key: AS7-1866 URL: https://issues.jboss.org/browse/AS7-1866 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Reporter: Radoslav Husar Assignee: Paul Ferraro -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
3
0 / 0

[JBoss JIRA] (AS7-3409) command to display details about a deployment

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-3409: -------------------------------------- Summary: command to display details about a deployment Key: AS7-3409 URL: https://issues.jboss.org/browse/AS7-3409 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.1.0.Final There is not way to see whether deployment (in domain mode) is enabled and in which server groups, i.e. using commands. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] (AS7-3540) jboss-cli --gui gives NPE

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created AS7-3540: ---------------------------------------- Summary: jboss-cli --gui gives NPE Key: AS7-3540 URL: https://issues.jboss.org/browse/AS7-3540 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.Final Reporter: Max Rydahl Andersen Assignee: Alexey Loubyansky Fix For: 7.1.0.Final {code} [max@greybeard ../jboss-as-7.1.0.Final-SNAPSHOT]$ bin/jboss-cli.sh --gui java.lang.NullPointerException at org.jboss.as.cli.gui.CommandExecutor.doCommand(CommandExecutor.java:52) at org.jboss.as.cli.gui.ManagementModelNode.explore(ManagementModelNode.java:66) at org.jboss.as.cli.gui.ManagementModel.makeTree(ManagementModel.java:57) at org.jboss.as.cli.gui.ManagementModel.<init>(ManagementModel.java:52) at org.jboss.as.cli.gui.GuiMain.makeTabbedPane(GuiMain.java:125) at org.jboss.as.cli.gui.GuiMain.initJFrame(GuiMain.java:112) at org.jboss.as.cli.gui.GuiMain.start(GuiMain.java:67) at org.jboss.as.cli.impl.CliLauncher.processGui(CliLauncher.java:222) at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:182) at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) 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.jboss.modules.Module.run(Module.java:260) at org.jboss.modules.Main.main(Main.java:288) {code} Any operations I do is showing "null" -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] (AS7-2155) Add -Djava.net.preferIPv4Stack=true into JAVA_OPTS for domain.conf.bat and standalone.conf.bat

by Rostislav Svoboda (Created) (JIRA)

Add -Djava.net.preferIPv4Stack=true into JAVA_OPTS for domain.conf.bat and standalone.conf.bat ---------------------------------------------------------------------------------------------- Key: AS7-2155 URL: https://issues.jboss.org/browse/AS7-2155 Project: Application Server 7 Issue Type: Bug Components: Scripts Affects Versions: 7.1.0.Alpha1 Reporter: Rostislav Svoboda Assignee: Brian Stansberry Fix For: 7.1.0.CR1 Parameter -Djava.net.preferIPv4Stack=true is used only when AS7 is started using .sh scripts and not using .bat scripts. Add -Djava.net.preferIPv4Stack=true into JAVA_OPTS for domain.conf.bat and standalone.conf.bat to support it on Windows too. -- 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, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-705) Red Hat look&feel

by Heiko Braun (JIRA)

Red Hat look&feel ----------------- Key: AS7-705 URL: https://issues.jboss.org/browse/AS7-705 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.CR1 We need a branded version of the web management interface -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

7
13
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 February 2012