October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1332) Integrate the compressed message support that was introduced in EJB client library

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1332?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1332: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1149020|https://bugzilla.redhat.com/show_bug.cgi?id=1149020] from POST to MODIFIED > Integrate the compressed message support that was introduced in EJB client library > ---------------------------------------------------------------------------------- > > Key: WFLY-1332 > URL: https://issues.jboss.org/browse/WFLY-1332 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: jaikiran pai > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha2 > > > https://issues.jboss.org/browse/EJBCLIENT-76 introduced a feature where the message stream that contains the EJB protocol message can be compressed. This involves a new message header which the server needs to support for the compression to be functional. This JIRA tracks the server side additions to support this feature. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3932) Enable security manager via JBoss Modules

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-3932?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-3932: -------------------------------- Description: In WildFly Core the security manager can be enabled via the {{-secmgr}} argument or setting the {{SECMGR=true}} environment variable. In order for this change to work correctly the {{WildFlySecurityManager.install()}} needs to be disabled. Also -all- standalone, process-controller and host-controller modules that declare a dependency on {{org.wildfly.security.manager}} need to export the services. Tests need to be updated to use the {{-secmgr}} argument rather than {{-Djava.security.manager}}. was: In WildFly Core the security manager can be enabled via the {{-secmgr}} argument or setting the {{SECMGR=true}} environment variable. In order for this change to work correctly the {{WildFlySecurityManager.install()}} needs to be disabled. Also all modules that declare a dependency on {{org.wildfly.security.manager}} need to export the services. Tests need to be updated to use the {{-secmgr}} argument rather than {{-Djava.security.manager}}. > Enable security manager via JBoss Modules > ----------------------------------------- > > Key: WFLY-3932 > URL: https://issues.jboss.org/browse/WFLY-3932 > Project: WildFly > Issue Type: Feature Request > Components: Security Manager > Reporter: James Perkins > Assignee: James Perkins > > In WildFly Core the security manager can be enabled via the {{-secmgr}} argument or setting the {{SECMGR=true}} environment variable. In order for this change to work correctly the {{WildFlySecurityManager.install()}} needs to be disabled. > Also -all- standalone, process-controller and host-controller modules that declare a dependency on {{org.wildfly.security.manager}} need to export the services. > Tests need to be updated to use the {{-secmgr}} argument rather than {{-Djava.security.manager}}. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-270) Use logger instead of [stdout] for JGroups GMS logger

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-270?page=com.atlassian.jira.plugin.s... ] Radoslav Husar reassigned WFLY-270: ----------------------------------- Assignee: Paul Ferraro (was: Radoslav Husar) Paul is fixing this by <pbcast.GMS print_local_addr="false"/>. > Use logger instead of [stdout] for JGroups GMS logger > ----------------------------------------------------- > > Key: WFLY-270 > URL: https://issues.jboss.org/browse/WFLY-270 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 8.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Priority: Trivial > > ...and possibly remove the unnecessary dash lines on the way. > {noformat} > [JBossINF] 12:11:12,677 INFO [org.jboss.as.osgi] (MSC service thread 1-15) JBAS011907: Register module: Module "deployment.clusterbench-ee6.ear.clusterbench-ee6-ejb.jar:main" from Service Module Loader > [JBossINF] 12:11:13,142 INFO [stdout] (ChannelService lifecycle - 1) > [JBossINF] 12:11:13,142 INFO [stdout] (ChannelService lifecycle - 1) ------------------------------------------------------------------- > [JBossINF] 12:11:13,142 INFO [stdout] (ChannelService lifecycle - 1) GMS: address=perf18/web, cluster=web, physical address=10.16.90.54:55200 > [JBossINF] 12:11:13,143 INFO [stdout] (ChannelService lifecycle - 1) ------------------------------------------------------------------- > [JBossINF] 12:11:13,209 INFO [stdout] (ChannelService lifecycle - 1) > [JBossINF] 12:11:13,209 INFO [stdout] (ChannelService lifecycle - 1) ------------------------------------------------------------------- > [JBossINF] 12:11:13,209 INFO [stdout] (ChannelService lifecycle - 1) GMS: address=perf18/ejb, cluster=ejb, physical address=10.16.90.54:55200 > [JBossINF] 12:11:13,210 INFO [stdout] (ChannelService lifecycle - 1) ------------------------------------------------------------------- > [JBossINF] 12:11:13,441 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated. > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1840) Provide docker image for JGroups

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1840?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1840: -------------------------------- Instructions on how to get the image (or build it via Dockerfile) are at [1]. The image is on DockerHub [2]. [1] https://github.com/belaban/jgroups-docker [2] https://registry.hub.docker.com/u/belaban/jgroups/ > Provide docker image for JGroups > -------------------------------- > > Key: JGRP-1840 > URL: https://issues.jboss.org/browse/JGRP-1840 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Optional > Fix For: 3.6 > > > Provide a docker image for one or more JGroups demos. People could run multiple instances and see a cluster. Candidates for demos: > * Draw (can we set DISPLAY to be the user's desktop?) > * Topology > * Some replicated map (ReplCache) > * Chat > [1] https://gist.github.com/goldmann/d38589ad919343ba30dd -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-87) Authentication client configuration API

by David Lloyd (JIRA)

David Lloyd created ELY-87: ------------------------------ Summary: Authentication client configuration API Key: ELY-87 URL: https://issues.jboss.org/browse/ELY-87 Project: WildFly Elytron Issue Type: Enhancement Components: API / SPI Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.0.0.Beta1 The base implementation of the Elytron authentication client programmatic API. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-65) Verify client dependencies are minimal

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-65?page=com.atlassian.jira.plugin.sys... ] David Lloyd updated ELY-65: --------------------------- Summary: Verify client dependencies are minimal (was: Verify client decencies are minimal) > Verify client dependencies are minimal > -------------------------------------- > > Key: ELY-65 > URL: https://issues.jboss.org/browse/ELY-65 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > i.e. don't bring in all of Elytron -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-258) drools-camel-server and guvnor-webapp: Do not use the dependency cxf-bundle-jaxrs because it's an uber jar that disrupts our dependency graph

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-258?page=com.atlassian.jira.plugin... ] Geoffrey De Smet commented on DROOLS-258: ----------------------------------------- New requirements: - remove cxf-bundle-* jars from our dep tree, they are evil. - Submit PR to ip-bom to ban them with this enforcer rule: http://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html > drools-camel-server and guvnor-webapp: Do not use the dependency cxf-bundle-jaxrs because it's an uber jar that disrupts our dependency graph > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-258 > URL: https://issues.jboss.org/browse/DROOLS-258 > Project: Drools > Issue Type: Bug > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Priority: Critical > > cxf-bundle-jaxrs isn't mentioned in here: > http://cxf.apache.org/docs/using-cxf-with-maven.html > it pulls in a lot we don't need and we try to exclude what we don't need (but fail at it). > Furher proof that cxf-bundle-jaxrs is evil: > http://svn.apache.org/repos/asf/cxf/trunk/distribution/bundle/jaxrs/pom.xml > It uses the maven-shade-plugin, which is a blocker for the Red Hat re-packers team (see fosdem 2011 presentation) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1887) Remove the synchronization on JChannel.class in JChannel.init

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1887?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1887: --------------------------- Fix Version/s: 3.6 > Remove the synchronization on JChannel.class in JChannel.init > ------------------------------------------------------------- > > Key: JGRP-1887 > URL: https://issues.jboss.org/browse/JGRP-1887 > Project: JGroups > Issue Type: Task > Affects Versions: 3.5.1 > Reporter: Dan Berindei > Assignee: Bela Ban > Fix For: 3.5.2, 3.6 > > > {{JChannel.init(ProtocolCtackConfigurator)}} has a {{synchronized(Channel.class)}} block that doesn't seem necessary, as JChannel instances do not normally share resources. > This can cause serious delays in the Infinispan test suite, because we run many tests in parallel, each creating its own cluster. In some tests we also have a timeout for the test to create the JChannel (among other things), and these delays can lead to random failures (e.g. ISPN-4802). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1887) Remove the synchronization on JChannel.class in JChannel.init

by Dan Berindei (JIRA)

Dan Berindei created JGRP-1887: ---------------------------------- Summary: Remove the synchronization on JChannel.class in JChannel.init Key: JGRP-1887 URL: https://issues.jboss.org/browse/JGRP-1887 Project: JGroups Issue Type: Task Affects Versions: 3.5.1 Reporter: Dan Berindei Assignee: Bela Ban Fix For: 3.5.2 {{JChannel.init(ProtocolCtackConfigurator)}} has a {{synchronized(Channel.class)}} block that doesn't seem necessary, as JChannel instances do not normally share resources. This can cause serious delays in the Infinispan test suite, because we run many tests in parallel, each creating its own cluster. In some tests we also have a timeout for the test to create the JChannel (among other things), and these delays can lead to random failures (e.g. ISPN-4802). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3933) Controller is not available using https-remoting protocol

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3933?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-3933. ------------------------------------ Fix Version/s: 9.0.0.Beta1 Resolution: Rejected Please use the forums not Jira for requests for assistance. In general I recommend starting at http://wildfly.org/ to find the appropriate location to ask someone for help. > Controller is not available using https-remoting protocol > --------------------------------------------------------- > > Key: WFLY-3933 > URL: https://issues.jboss.org/browse/WFLY-3933 > Project: WildFly > Issue Type: Feature Request > Components: CLI > Environment: I am trying to deploy my war archive on 8.0.0 final jboss redhat RPM. Everything was working fine until I tried to enable my security options. I have added both <ssl> tag and <trustore> tag under SecurityRealm. In addition I added an <https-listener> and enabled the https-management console. > I've added a controller to jboss-cli.xml as follows: > <controllers> > <controller name="MyHttpsController"> > <protocol>https-remoting</protocol> > <host>myHost</host> > <port>myPort</port> > </controller> > </controllers> > I'm executing the jboss server process by runnning the standalone.sh script and then I'm trying to deploy my war by using the following line: > ./jboss-cli.sh --connect=MyHttpsController command="deploy [myWarPath]" > I get the following error: > The controller is not available at myIp:myPort: java.net.ConnectException: .....The connection timed out > I can open the https-management console via the browser and I checked that my server is actually listening to this port. Please help my if you can, this is very important. > I appreciate all help you can give me. > Thanks all, Michael > Reporter: Michael Sherman > Assignee: Darran Lofthouse > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2014