[JBoss JIRA] (WFLY-1548) Add fallback querry to jconsole plugin
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1548?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1548:
-----------------------------------------------
Shaun Appleton <sappleto(a)redhat.com> changed the Status of [bug 901311|https://bugzilla.redhat.com/show_bug.cgi?id=901311] from ASSIGNED to CLOSED
> Add fallback querry to jconsole plugin
> --------------------------------------
>
> Key: WFLY-1548
> URL: https://issues.jboss.org/browse/WFLY-1548
> Project: WildFly
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 8.0.0.Alpha1
> Reporter: Bartosz Baranowski
> Assignee: Darran Lofthouse
> Labels: JConsole, JMX, Plugin
> Fix For: 8.0.0.Beta1
>
>
> JConsolePlugin connecects to default port, despite chance to use proper info.
> Problem:
> Unless I miss somethingm JConsole has a bit tight isolation between components. There is no way for AS7 JConsolePlugin to access "connect dialog" info. Hence it has no idea what is the content of URL being passed as remote.
> AS7 JConsolePlugin checks if MBeanServerConnection is instance of RemotinConnection. If its not, it fallbacks to default: localhost:9990.
> However we can check for socket bindings and try to connect to proper socket.
--
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
11 years
[JBoss JIRA] (JGRP-1765) TP: enable loopback by default and discard own multicasts
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1765?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1765:
--------------------------------
Why ? I want to reduce the number of properties, and removing loopback is on my list as we'd loop back messages by default.
> TP: enable loopback by default and discard own multicasts
> ---------------------------------------------------------
>
> Key: JGRP-1765
> URL: https://issues.jboss.org/browse/JGRP-1765
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.5
>
>
> Enable {{TP.looback}} by default (deprecate and ignore prop): all messages sent by self are passed right to a thread pool to send them up again.
> When a multicast message sent by self is received, it is currently passed to a thread pool, de-serialized and only then discarded if loopback=true. This means that we create an unneeded buffer for de-serializationand perform de-serialization.
> SOLUTION: discard the multicast from self immediately when receiving it, in {{TP.receive()}}
--
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
11 years
[JBoss JIRA] (WFLY-490) Domain Management Role Based Access Control
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-490?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse commented on WFLY-490:
---------------------------------------
This feature is already included in EAP 6.2 - this issue is only still open to act as a container for any subsequent tasks identified that need to go into WildFly 8.
> Domain Management Role Based Access Control
> -------------------------------------------
>
> Key: WFLY-490
> URL: https://issues.jboss.org/browse/WFLY-490
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: Authorization
> Fix For: 8.0.0.Final
>
>
> Implement some coarse permissions for domain operations. Possibly allowing a break down for subsystem, profile, server, server-group - maybe read - write - execute.
> Also consider confidentiality in exchange e.g. Can read metrics over http but must use https to add new server.
--
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
11 years
[JBoss JIRA] (WFLY-2701) Deployed JMS resources are not manageable in the GUI console
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-2701:
---------------------------------
Summary: Deployed JMS resources are not manageable in the GUI console
Key: WFLY-2701
URL: https://issues.jboss.org/browse/WFLY-2701
Project: WildFly
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JMS
Affects Versions: 8.0.0.CR1
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
JMS resources that are part of a deployment are not manageable using the GUI console.
They are manageable using the CLI console though under
{noformat}
/deployment=*/subsystem=messaging/hornetq-server=*
{noformat}
--
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
11 years
[JBoss JIRA] (JBPORTAL-2497) CR1 jdk 1.8 (b106) fresh install standalone.bat hangs on "Starting"
by Jared Nagle (JIRA)
Jared Nagle created JBPORTAL-2497:
-------------------------------------
Summary: CR1 jdk 1.8 (b106) fresh install standalone.bat hangs on "Starting"
Key: JBPORTAL-2497
URL: https://issues.jboss.org/browse/JBPORTAL-2497
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Jared Nagle
When calling the standalone.bat from a fresh install of CR1 with JAVA_HOME set to jdk 1.8.0 (b106, 20th Sep 2013) the server hangs (seems to be in an infinite loop of some sort)..
WARNING: JBOSS_HOME may be pointing to a different installation - unpredictable results may occur.
JBOSS_HOME: "C:\JavaLibs\jboss-as-7.1.1.Final"
Calling "C:\JavaLibs\wildfly-8.0.0.CR1\bin\standalone.conf.bat"
Setting JAVA property to "C:\Program Files\Java\jdk1.8.0\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "C:\JavaLibs\jboss-as-7.1.1.Final"
JAVA: "C:\Program Files\Java\jdk1.8.0\bin\java"
JAVA_OPTS: "-XX:+UseCompressedOops -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman"
===============================================================================
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0
20:23:08,464 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
20:23:08,596 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
20:23:08,634 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
and then it hangs.
--
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
11 years
[JBoss JIRA] (JGRP-1765) TP: enable loopback by default and discard own multicasts
by Karim AMMOUS (JIRA)
[ https://issues.jboss.org/browse/JGRP-1765?page=com.atlassian.jira.plugin.... ]
Karim AMMOUS commented on JGRP-1765:
------------------------------------
Hi Bela,
Could you apply the enhancement without deprecating and ignoring this prop ?
TP.looback=false in our configuration.
> TP: enable loopback by default and discard own multicasts
> ---------------------------------------------------------
>
> Key: JGRP-1765
> URL: https://issues.jboss.org/browse/JGRP-1765
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.5
>
>
> Enable {{TP.looback}} by default (deprecate and ignore prop): all messages sent by self are passed right to a thread pool to send them up again.
> When a multicast message sent by self is received, it is currently passed to a thread pool, de-serialized and only then discarded if loopback=true. This means that we create an unneeded buffer for de-serializationand perform de-serialization.
> SOLUTION: discard the multicast from self immediately when receiving it, in {{TP.receive()}}
--
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
11 years
[JBoss JIRA] (WFLY-1950) Problems with connector 1.7
by Jeff Zhang (JIRA)
[ https://issues.jboss.org/browse/WFLY-1950?page=com.atlassian.jira.plugin.... ]
Jeff Zhang commented on WFLY-1950:
----------------------------------
Hi Frank, I had test on latest Wildfly8 CR and see the code logic, it seems fine and hadn't see the issue you reported. Could you try again on the Wildfly CR? Thanks!
> Problems with connector 1.7
> ---------------------------
>
> Key: WFLY-1950
> URL: https://issues.jboss.org/browse/WFLY-1950
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA
> Affects Versions: 8.0.0.Beta1
> Reporter: Frank Langelage
> Assignee: Jeff Zhang
> Attachments: filesystem-ra.xml.1.6.1.7, filesystem-ra.xml.1.7, filesystem-ra.xml.before, filesystem.rar
>
>
> Usually I see this when deploying my RA:
> 21:30:53,599 INFO [org.jboss.as.server.deployment#start] JBAS015876: Starting deployment of "filesystem.rar" (runtime-name: "filesystem.rar")
> 21:30:53,745 INFO [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/Filesystem
> 21:30:53,750 INFO [org.jboss.as.connector.deployers.RaXmlDeployer#createObjectsAndInjectValue] IJ020002: Deployed: file:/mbi/tools/jboss/8.0/standalone/tmp/vfs/temp8a8dd6af6d60d261/filesystem.rar-acf9504f544e0a1d/contents/
> 21:30:53,764 INFO [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/Filesystem]
> 21:30:53,822 INFO [org.jboss.as.server#handleResult] JBAS018559: Deployed "filesystem.rar" (runtime-name : "filesystem.rar")
> Because JCA 1.7 was introduced to head at github I changed header of ra.xml to 1.7 version.
> But then I no longer see the line
> 21:30:53,764 INFO [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/Filesystem]
> I did not specify the <outbound-resourceadapter> in ra.xml.
> Another adapter is working fine after version upgrade.
> So I added the <outbound-resourceadapter> also to the now failing one.
> But this gives this now:
> 21:35:57,797 INFO [org.jboss.as.server.deployment#start] JBAS015876: Starting deployment of "filesystem.rar" (runtime-name: "filesystem.rar")
> 21:35:57,941 ERROR [org.jboss.msc.service.fail#startFailed] MSC000001: Failed to start service jboss.ra.deployment."filesystem.rar_4": org.jboss.msc.service.StartException in service jboss.ra.deployment."filesystem.rar_4": org.jboss.msc.service.StartException in anonymous service: JBAS010446: Failed to start RA deployment [filesystem]
> at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:136)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
> Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS010446: Failed to start RA deployment [filesystem]
> at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:120)
> ... 5 more
> Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/mbi/tools/jboss/8.0/standalone/tmp/vfs/temp8a8dd6af6d60d261/filesystem.rar-c256d8da3c2df580/contents/
> at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2564)
> at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService$AS7RaXmlDeployer.doDeploy(ResourceAdapterXmlDeploymentService.java:197)
> at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:113)
> ... 5 more
> Caused by: java.lang.NullPointerException
> at org.jboss.jca.common.metadata.ra.common.OutboundResourceAdapterImpl.getReauthenticationSupport(OutboundResourceAdapterImpl.java:182)
> at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2073)
> ... 7 more
> 21:35:57,962 ERROR [org.jboss.as.controller.management-operation#executeStep] JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "filesystem.rar")]) - failure description: {"JBAS014671: Failed services" => {"jboss.ra.deployment.\"filesystem.rar_4\"" => "org.jboss.msc.service.StartException in service jboss.ra.deployment.\"filesystem.rar_4\": org.jboss.msc.service.StartException in anonymous service: JBAS010446: Failed to start RA deployment [filesystem]
> Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS010446: Failed to start RA deployment [filesystem]
> Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/mbi/tools/jboss/8.0/standalone/tmp/vfs/temp8a8dd6af6d60d261/filesystem.rar-c256d8da3c2df580/contents/
> Caused by: java.lang.NullPointerException"}}
> 21:35:57,982 ERROR [org.jboss.as.server#handleResult] JBAS015870: Deploy of deployment "filesystem.rar" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.ra.deployment.\"filesystem.rar_4\"" => "org.jboss.msc.service.StartException in service jboss.ra.deployment.\"filesystem.rar_4\": org.jboss.msc.service.StartException in anonymous service: JBAS010446: Failed to start RA deployment [filesystem]
> Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS010446: Failed to start RA deployment [filesystem]
> Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/mbi/tools/jboss/8.0/standalone/tmp/vfs/temp8a8dd6af6d60d261/filesystem.rar-c256d8da3c2df580/contents/
> Caused by: java.lang.NullPointerException"}}
> 21:35:58,011 INFO [org.jboss.as.server.deployment#stop] JBAS015877: Stopped deployment filesystem.rar (runtime-name: filesystem.rar) in 24ms
> Adding also <reauthentication-support>false</reauthentication-support> solves this NPE, the RA gets deployed and bound to JNDI again.
--
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
11 years