[JBoss JIRA] (WFLY-3051) JMX connection to remote server-instances is not happening in wildfly 8.0.0.Final in domain mode
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-3051?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-3051:
-----------------------------------
Affects Version/s: 8.0.0.Final
> JMX connection to remote server-instances is not happening in wildfly 8.0.0.Final in domain mode
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-3051
> URL: https://issues.jboss.org/browse/WFLY-3051
> Project: WildFly
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JMX, Remoting
> Affects Versions: 8.0.0.Final
> Reporter: Rituraj Sinha
> Assignee: Darran Lofthouse
>
> i have gone through the below link for JMX subsystem for wildfly 8 as
> https://docs.jboss.org/author/display/WFLY8/JMX+subsystem+configuration
>
> but unable to connect to server-instances running remotely ...i have posted my question there as well and pasting it here now ...
> can someone please give us the steps to configure JMX through jconsole...?
> changes done on the domain.xml are the same as stated above
> <subsystem xmlns="urn:jboss:domain:jmx:1.3">
> <expose-resolved-model/>
> <expose-expression-model/>
> <remoting-connector use-management-endpoint="false"/>
> </subsystem>
> <subsystem xmlns="urn:jboss:domain:jmx:1.3">
> <expose-resolved-model/>
> <expose-expression-model/>
> <remoting-connector use-management-endpoint="false"/>
> </subsystem>
> as per the jboss-as-jmx_1_3.xsd its like
> <xs:attribute name="use-management-endpoint" type="xs:boolean" default="true" use="optional" >
> <xs:annotation>
> <xs:documentation>
> If true then this connector will use the management endpoint, otherwise it will use the
> remoting subsystem endpoint.
> </xs:documentation>
> </xs:annotation>
> </xs:attribute>
> now if we are making it false then it should be using the remoting endpoint ...now remoting subsystem by default uses ApplicatoinRealm
> i have created application-user and password for the same but when i am trying to connect to remote server-instances its not connecting it....
> below is what i am able to connect to
> service:jmx:http-remoting-jmx://remote_hostA:9990 --
> Unknown macro: {host A is where my domain_controller is running}
> how can i access the server-instances running on domain_controller
> Unknown macro: {there are three server_instanaces running on HostA with a port offset of 100 each}
> i am trying to connect with the below url as
> service:jmx:http-remoting-jmx://lremote_hostA:8180
> let me know if something is missing from my side...
> Thanks
--
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, 2 months
[JBoss JIRA] (WFLY-3051) JMX connection to remote server-instances is not happening in wildfly 8.0.0.Final in domain mode
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-3051?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-3051:
-----------------------------------
Fix Version/s: 8.0.1.Final
> JMX connection to remote server-instances is not happening in wildfly 8.0.0.Final in domain mode
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-3051
> URL: https://issues.jboss.org/browse/WFLY-3051
> Project: WildFly
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JMX, Remoting
> Affects Versions: 8.0.0.Final
> Reporter: Rituraj Sinha
> Assignee: Darran Lofthouse
> Fix For: 8.0.1.Final
>
>
> i have gone through the below link for JMX subsystem for wildfly 8 as
> https://docs.jboss.org/author/display/WFLY8/JMX+subsystem+configuration
>
> but unable to connect to server-instances running remotely ...i have posted my question there as well and pasting it here now ...
> can someone please give us the steps to configure JMX through jconsole...?
> changes done on the domain.xml are the same as stated above
> <subsystem xmlns="urn:jboss:domain:jmx:1.3">
> <expose-resolved-model/>
> <expose-expression-model/>
> <remoting-connector use-management-endpoint="false"/>
> </subsystem>
> <subsystem xmlns="urn:jboss:domain:jmx:1.3">
> <expose-resolved-model/>
> <expose-expression-model/>
> <remoting-connector use-management-endpoint="false"/>
> </subsystem>
> as per the jboss-as-jmx_1_3.xsd its like
> <xs:attribute name="use-management-endpoint" type="xs:boolean" default="true" use="optional" >
> <xs:annotation>
> <xs:documentation>
> If true then this connector will use the management endpoint, otherwise it will use the
> remoting subsystem endpoint.
> </xs:documentation>
> </xs:annotation>
> </xs:attribute>
> now if we are making it false then it should be using the remoting endpoint ...now remoting subsystem by default uses ApplicatoinRealm
> i have created application-user and password for the same but when i am trying to connect to remote server-instances its not connecting it....
> below is what i am able to connect to
> service:jmx:http-remoting-jmx://remote_hostA:9990 --
> Unknown macro: {host A is where my domain_controller is running}
> how can i access the server-instances running on domain_controller
> Unknown macro: {there are three server_instanaces running on HostA with a port offset of 100 each}
> i am trying to connect with the below url as
> service:jmx:http-remoting-jmx://lremote_hostA:8180
> let me know if something is missing from my side...
> Thanks
--
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, 2 months
[JBoss JIRA] (WFLY-3051) JMX connection to remote server-instances is not happening in wildfly 8.0.0.Final in domain mode
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-3051?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse reassigned WFLY-3051:
--------------------------------------
Assignee: Darran Lofthouse (was: Kabir Khan)
> JMX connection to remote server-instances is not happening in wildfly 8.0.0.Final in domain mode
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-3051
> URL: https://issues.jboss.org/browse/WFLY-3051
> Project: WildFly
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JMX, Remoting
> Reporter: Rituraj Sinha
> Assignee: Darran Lofthouse
> Priority: Critical
>
> i have gone through the below link for JMX subsystem for wildfly 8 as
> https://docs.jboss.org/author/display/WFLY8/JMX+subsystem+configuration
>
> but unable to connect to server-instances running remotely ...i have posted my question there as well and pasting it here now ...
> can someone please give us the steps to configure JMX through jconsole...?
> changes done on the domain.xml are the same as stated above
> <subsystem xmlns="urn:jboss:domain:jmx:1.3">
> <expose-resolved-model/>
> <expose-expression-model/>
> <remoting-connector use-management-endpoint="false"/>
> </subsystem>
> <subsystem xmlns="urn:jboss:domain:jmx:1.3">
> <expose-resolved-model/>
> <expose-expression-model/>
> <remoting-connector use-management-endpoint="false"/>
> </subsystem>
> as per the jboss-as-jmx_1_3.xsd its like
> <xs:attribute name="use-management-endpoint" type="xs:boolean" default="true" use="optional" >
> <xs:annotation>
> <xs:documentation>
> If true then this connector will use the management endpoint, otherwise it will use the
> remoting subsystem endpoint.
> </xs:documentation>
> </xs:annotation>
> </xs:attribute>
> now if we are making it false then it should be using the remoting endpoint ...now remoting subsystem by default uses ApplicatoinRealm
> i have created application-user and password for the same but when i am trying to connect to remote server-instances its not connecting it....
> below is what i am able to connect to
> service:jmx:http-remoting-jmx://remote_hostA:9990 --
> Unknown macro: {host A is where my domain_controller is running}
> how can i access the server-instances running on domain_controller
> Unknown macro: {there are three server_instanaces running on HostA with a port offset of 100 each}
> i am trying to connect with the below url as
> service:jmx:http-remoting-jmx://lremote_hostA:8180
> let me know if something is missing from my side...
> Thanks
--
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, 2 months
[JBoss JIRA] (WFLY-3048) "Local" authentication fails when LDAP is used for ManagementRealm
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-3048?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-3048:
-----------------------------------
Fix Version/s: 8.0.1.Final
> "Local" authentication fails when LDAP is used for ManagementRealm
> ------------------------------------------------------------------
>
> Key: WFLY-3048
> URL: https://issues.jboss.org/browse/WFLY-3048
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Security
> Affects Versions: 8.0.0.Final
> Environment: Ubuntu 13.04, Xeon-based VPS
> Reporter: Matt Jensen
> Assignee: Darran Lofthouse
> Fix For: 8.0.1.Final
>
>
> When LDAP is used for authentication in ManagementRealm, "local" authentication, which is enabled in configuration for the realm, appears to stop working.
> I have configured my ManagementRealm to use LDAP for authentication of remote clients. However, I also need to allow local authentication without a username and password, for when jboss-cli is invoked from the command line on the server. This is needed in order for the wildfly-init-debian.sh script to shut down the server. I have configured the ManagementRealm as follows:
> <security-realm name="ManagementRealm">
> <authentication>
> <local default-user="$local" />
> <ldap connection="..." base-dn="ou=accounts,dc=..." recursive="false">
> ...
> </ldap>
> </authentication>
> <authorization map-groups-to-roles="false">
> <ldap connection="...">
> ...
> </ldap>
> </authorization>
> </security-realm>
> I left out most of the LDAP configuration because I don't think it is important for this issue. LDAP authentication works fine for remote clients. In fact, it works fine for local clients as well--when I invoke jboss-cli with LDAP authentication enabled, it prompts for a username and password; if I enter a valid combination from the LDAP directory, jboss-cli connects successfully and executes its command.
> The problem is that I need it to NOT prompt for a username and password when jboss-cli is invoked locally. Which, I believe, is how things are supposed to work when "local" authentication is also enabled; it just doesn't work that way when LDAP is enabled for the same realm.
> If I comment out the <ldap .../> element in <authentication> for the realm, local authentication starts working again. I can invoke jboss-cli locally and the command is carried out without a username and password prompt. Re-enable LDAP, with no other configuration changes, and again it flips back to requiring a username and password.
> I have tried replacing "$local" in the @default-user element of the <local> element with a valid name from the LDAP directory, both as a simple username and as a full DN, and jboss-cli still prompts for a username and password.
> The modification date on the [tmp/auth] directory changes when I run jboss-cli with LDAP in place and get the username/password prompt, so it appears that the client is putting a token in there to try to use local authentication. The server just never picks it up.
> The documentation specifically mentions that <local/> should work along with <ldap/> here:
> https://docs.jboss.org/author/display/WFLY8/Security+Realms
--
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, 2 months
[JBoss JIRA] (AS7-1899) HornetQ deletes all JMS messages after shutdown
by Peter Hinds (JIRA)
[ https://issues.jboss.org/browse/AS7-1899?page=com.atlassian.jira.plugin.s... ]
Peter Hinds commented on AS7-1899:
----------------------------------
I thought I would just add the following as a comment in case it helps anybody else who has searched this problem.
I found that my messages were disappearing after a shutdown even though I was using JBoss AS 7.3.0. I couldn't understand why I was still seeing the described problem when the version I was using should have included the fix.
In the end I was able to work out that my problem was that I was placing messages on the JMS queue using Hermes (www.hermesjms.com) and it uses non-persistent by default. To switch Hermes to persistent mode, click the icon in the tool bar that shows a tooltip of 'Toggle persistent message send'.
> HornetQ deletes all JMS messages after shutdown
> -----------------------------------------------
>
> Key: AS7-1899
> URL: https://issues.jboss.org/browse/AS7-1899
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Affects Versions: 7.0.1.Final
> Reporter: Fabrizio Benedetti
> Assignee: Andy Taylor
> Fix For: 7.1.0.Beta1
>
>
> After sending a persistent JMS message to a queue, and the message is not consumed, after reboot the message is deleted. Also, after the reboot, jboss reset persistence-enabled to false in standalone.xml, or sometimes the entire element is deleted.
> Following messaging subsystem configuration:
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:messaging:1.0">
> <journal-file-size>102400</journal-file-size>
> <journal-min-files>2</journal-min-files>
> <journal-type>NIO</journal-type>
> <persistence-enabled>true</persistence-enabled>
> <acceptors>
> <netty-acceptor name="netty" socket-binding="messaging"/>
> <netty-acceptor name="netty-throughput" socket-binding="messaging-throughput">
> <param key="batch-delay" value="50"/>
> <param key="direct-deliver" value="false"/>
> </netty-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> </acceptors>
> <address-settings>
> <address-setting match="#">
> <dead-letter-address>
> jms.queue.DLQ
> </dead-letter-address>
> <expiry-address>
> jms.queue.ExpiryQueue
> </expiry-address>
> <redelivery-delay>
> 0
> </redelivery-delay>
> <max-size-bytes>
> 10485760
> </max-size-bytes>
> <message-counter-history-day-limit>
> 10
> </message-counter-history-day-limit>
> <address-full-policy>
> BLOCK
> </address-full-policy>
> </address-setting>
> </address-settings>
> <connectors>
> <netty-connector name="netty" socket-binding="messaging"/>
> <netty-connector name="netty-throughput" socket-binding="messaging-throughput">
> <param key="batch-delay" value="50"/>
> </netty-connector>
> <in-vm-connector name="in-vm" server-id="0"/>
> </connectors>
> <security-settings>
> <security-setting match="#">
> <permission type="send" roles="guest"/>
> <permission type="consume" roles="guest"/>
> <permission type="createNonDurableQueue" roles="guest"/>
> <permission type="deleteNonDurableQueue" roles="guest"/>
> </security-setting>
> </security-settings>
> <jms-connection-factories>
> <connection-factory name="InVmConnectionFactory">
> <connectors>
> <connector-ref connector-name="in-vm"/>
> </connectors>
> <entries>
> <entry name="java:/ConnectionFactory"/>
> </entries>
> </connection-factory>
> <connection-factory name="RemoteConnectionFactory">
> <connectors>
> <connector-ref connector-name="netty"/>
> </connectors>
> <entries>
> <entry name="RemoteConnectionFactory"/>
> </entries>
> </connection-factory>
> <pooled-connection-factory name="hornetq-ra">
> <connectors>
> <connector-ref connector-name="in-vm"/>
> </connectors>
> <entries>
> <entry name="java:/JmsXA"/>
> </entries>
> <transaction mode="xa"/>
> </pooled-connection-factory>
> </jms-connection-factories>
> <jms-destinations>
> <jms-queue name="MyQueue">
> <entry name="queue/MyQueue"/>
> </jms-queue>
> </jms-destinations>
> </subsystem>
> {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, 2 months
[JBoss JIRA] (DROOLS-364) ClasspathKieProject fails vfs: path for jar deployments and exploded ear
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-364?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-364:
------------------------------------------------
Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1058254|https://bugzilla.redhat.com/show_bug.cgi?id=1058254] from MODIFIED to ON_QA
> ClasspathKieProject fails vfs: path for jar deployments and exploded ear
> ------------------------------------------------------------------------
>
> Key: DROOLS-364
> URL: https://issues.jboss.org/browse/DROOLS-364
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 6.0.0.Final
> Environment: JBoss AS 7.1.1
> Reporter: Nicolas-Xavier Vanderlinden
> Assignee: Mario Fusco
> Fix For: 6.1.0.Beta1
>
> Attachments: jbossas-deploy-reproducer.zip, windows-jboss-as-deploy-server.log
>
>
> Drools is not able to load kmodule.xml from an exploded ear.
> 17:24:45,116 WARN Unable to load pom.properties tried recursing down from\Project\Geline\jboss-as-7.1.1.Final\standalone\deployments\geline.ear\service-impl-1.4.0-SNAPcontent
> null
> 17:24:45,116 ERROR Unable to build index of kmodule.xml url=vfs:/E:/Project/Geline/jboss-as-7.1.1.Final/standalone/deployments/geline.ear/service-impl-1.4.0-SNAPSHOT.jar/META-INF/kmodule.xml
> null
--
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, 2 months