December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5253) [Migration operation] [Web to Undertow] Protocol attribute in ssl configuration of https connector is not properly migrated

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5253?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5253. ---------------------------- > [Migration operation] [Web to Undertow] Protocol attribute in ssl configuration of https connector is not properly migrated > --------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5253 > URL: https://issues.jboss.org/browse/WFLY-5253 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Beta2 > Reporter: Radim Hatlapatka > Assignee: Stuart Douglas > Priority: Critical > Fix For: 10.0.0.CR1 > > > In Web {{protocol}} attribute of https ssl configuration is used for defining ssl protocols such as TLSv1.2. This attribute isn't properly migrated. Migrate operation defines {{enabled-protocols}} in {{https-listener}} based on Web's {{ssl-protocol}} which is incorrect as {{ssl-protocol}} in Web stands for name of custom ssl protocol provider. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4873) Update the servlet feature pack templates to use version 4.0 of the schema,

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4873?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4873. ---------------------------- > Update the servlet feature pack templates to use version 4.0 of the schema, > --------------------------------------------------------------------------- > > Key: WFLY-4873 > URL: https://issues.jboss.org/browse/WFLY-4873 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: affects_elytron > Fix For: 10.0.0.Alpha5 > > > It appears many of the templates are still stuck on version 2.1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4796) IIOPTransactionPropagationTestCase fails with -Dnode0 property set

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4796?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4796. ---------------------------- > IIOPTransactionPropagationTestCase fails with -Dnode0 property set > ------------------------------------------------------------------ > > Key: WFLY-4796 > URL: https://issues.jboss.org/browse/WFLY-4796 > Project: WildFly > Issue Type: Bug > Components: IIOP, Test Suite > Reporter: Petr Kremensky > Assignee: Petr Kremensky > Fix For: 10.0.0.Alpha4 > > > org.jboss.as.test.iiop.client.IIOPTransactionPropagationTestCase fails once -Dnode0 and -Dnode1 properties are used. > {noformat} > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 19,243.526 sec <<< FAILURE! - in org.jboss.as.test.iiop.client.IIOPTransactionPropagationTestCase > org.jboss.as.test.iiop.client.IIOPTransactionPropagationTestCase Time elapsed: 19,241.627 sec <<< ERROR! > javax.naming.CommunicationException: Cannot connect to ORB > at sun.nio.ch.Net.connect0(Native Method) > at sun.nio.ch.Net.connect(Net.java:458) > at sun.nio.ch.Net.connect(Net.java:450) > at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648) > at java.nio.channels.SocketChannel.open(SocketChannel.java:189) > at com.sun.corba.se.impl.transport.DefaultSocketFactoryImpl.createSocket(DefaultSocketFactoryImpl.java:95) > at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:207) > at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:236) > at com.sun.corba.se.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:119) > at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:187) > at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:137) > at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:229) > at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:130) > at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69) > at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:381) > at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:247) > at com.sun.jndi.cosnaming.CNCtx.<init>(CNCtx.java:105) > at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.java:49) > at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313) > at javax.naming.InitialContext.init(InitialContext.java:244) > at javax.naming.InitialContext.<init>(InitialContext.java:216) > at org.jboss.as.test.iiop.client.Util.getContext(Util.java:130) > at org.jboss.as.test.iiop.client.IIOPTransactionPropagationTestCase.beforeClass(IIOPTransactionPropagationTestCase.java:102) > {noformat} > Fix > {noformat} > --- a/testsuite/integration/iiop/src/test/java/org/jboss/as/test/iiop/client/Util.java > +++ b/testsuite/integration/iiop/src/test/java/org/jboss/as/test/iiop/client/Util.java > @@ -56,7 +56,7 @@ import com.arjuna.orbportability.ORB; > import com.sun.corba.se.impl.orbutil.ORBConstants; > > public class Util { > - public static final String HOST = NetworkUtils.formatPossibleIpv6Address(System.getProperty("node0", "localhost")); > + public static final String HOST = NetworkUtils.formatPossibleIpv6Address(System.getProperty("node1", "localhost")); > private static ORB orb = null; > > // Recovery manager is needed till the end of orb usage > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5277) Upgrade HAL to 2.8.7

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5277?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5277. ---------------------------- > Upgrade HAL to 2.8.7 > -------------------- > > Key: WFLY-5277 > URL: https://issues.jboss.org/browse/WFLY-5277 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 10.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5091) User supplied externalizers are ignored by web/ejb clustering code

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5091?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5091. ---------------------------- > User supplied externalizers are ignored by web/ejb clustering code > ------------------------------------------------------------------ > > Key: WFLY-5091 > URL: https://issues.jboss.org/browse/WFLY-5091 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 10.0.0.CR1 > > > Several users were surprised to find that their custom Infinispan externalizers are not used when marshalling of objects placed in the web session or used as fields in their SFSB. Without this functionality, users cannot use non-serializable objects in their web session or SFSB. > There are a few reasons why this does not currently work: > # The cache in which user objects is placed does not scan the application classloader for externalizers. > # In both the web and ejb case, user objects are stored within a MarshalledValue - the serialization of which is done by JBoss Marshalling directly, not via Infinispan's marshaller. > # Neither the org.infinispan.commons (containing org.infinispan.commons.marshall.AdvancedExternalizer) nor org.jboss.marshalling (containing org.jboss.marshalling.Externalizer) modules are exported to the application classpath. > Clearly, we need a common, public mechanism that bridges these two APIs so that users can register custom externalizers without needing to know the specific marshalling framework to which to adhere. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4686) Operation list-delivering-messages is missing in CLI

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4686?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4686. ---------------------------- > Operation list-delivering-messages is missing in CLI > ---------------------------------------------------- > > Key: WFLY-4686 > URL: https://issues.jboss.org/browse/WFLY-4686 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Alpha1 > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha4 > > > There is missing operation list-delivering-messages on runtime-queue: > {code} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/runtime-queue=jms.queue.testQueue:list- > list-add list-get list-message-counter-history-as-html list-messages-as-json list-scheduled-messages-as-json > list-clear list-message-counter-as-html list-message-counter-history-as-json list-remove > list-consumers-as-json list-message-counter-as-json list-messages list-scheduled-messages > {code} > This was hit on Wildfly 9 with ActiveMQ (built from Jeff's branch) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5085) [Migration operation] If connector has set factory-class org.hornetq.core.remoting.impl.netty.NettyConnectorFactory then migration operation does not translate it to Artemis equivalent

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5085?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5085. ---------------------------- > [Migration operation] If connector has set factory-class org.hornetq.core.remoting.impl.netty.NettyConnectorFactory then migration operation does not translate it to Artemis equivalent > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5085 > URL: https://issues.jboss.org/browse/WFLY-5085 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Alpha6 > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Fix For: 10.0.0.Beta2 > > > We should migrate configuration like: > {code} > <connector name="myconnector"> > ... > <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class> > </connector> > {code} > to: > {code} > <connector name="myconnector" factory-class="org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector"> > ... > {code} > and not to: > {code} > <connector name="myconnector" factory-class="org.hornetq.core.remoting.impl.netty.NettyConnectorFactory"> > ... > {code} > The same holds for InVMConnector. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4705) Enable interface declaration in subsystem template

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4705?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4705. ---------------------------- > Enable interface declaration in subsystem template > -------------------------------------------------- > > Key: WFLY-4705 > URL: https://issues.jboss.org/browse/WFLY-4705 > Project: WildFly > Issue Type: Feature Request > Components: Build System, IIOP > Affects Versions: 10.0.0.Alpha1 > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Optional > Fix For: 10.0.0.Alpha4 > > > Currently interfaces cannot be defined in subsystem templates. As a result of "unsecure" interface, which is used only by iiop subsystem, is defined in main template file and it's included in all subsystems configurations. Implement extension to feature pack plugin which enables specifying interfaces in subsystem configuration files and move "unsecure" interface configuration from main template to jacorb. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5201) Do not use newly disallowed characters in jgroups runtime metric attributes names

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5201?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5201. ---------------------------- > Do not use newly disallowed characters in jgroups runtime metric attributes names > --------------------------------------------------------------------------------- > > Key: WFLY-5201 > URL: https://issues.jboss.org/browse/WFLY-5201 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Domain Management > Affects Versions: 10.0.0.Beta2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Blocker > Fix For: 10.0.0.CR1 > > > When doing a :read-resource(include-runtime=true,recursive=true) this blows up. Debugging shows that to be because e.g. the resource /subsystem=jgroups/channel=ee/protocol=UDP contains metrics called things like > {code} > "timer.keep_alive_time" => { > "type" => LONG, > "description" => "Timeout in ms to remove idle threads from the timer pool", > "expressions-allowed" => false, > "nillable" => false, > "access-type" => "metric", > "storage" => "runtime" > }, > "timer.max_threads" => { > "type" => INT, > "description" => "Max thread pool size for the timer thread pool", > "expressions-allowed" => false, > "nillable" => false, > "access-type" => "metric", > "storage" => "runtime" > }, > "timer.min_threads" => { > "type" => INT, > "description" => "Minimum thread pool size for the timer thread pool", > "expressions-allowed" => false, > "nillable" => false, > "access-type" => "metric", > "storage" => "runtime" > }, > {code} > i.e. they have a dot in their name. So when the r-r handler wants to read the attributes it in effect tries to do the following demonstrated by CLI commands: > {code} > [standalone@localhost:9990 /] /subsystem=jgroups/channel=ee/protocol=UDP:read-attribute(name=timer > timer.keep_alive_time timer.min_threads timer.rejection_policy timer.wheel_size timer_queue_size timer_threads > timer.max_threads timer.queue_max_size timer.tick_time timer_class timer_tasks timer_type > [standalone@localhost:9990 /] /subsystem=jgroups/channel=ee/protocol=UDP:read-attribute(name=timer.max_threads) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0201: Unknown attribute 'timer'", > "rolled-back" => true > } > {code} > I see ReadResourceHandler has some stuff to extract the attribute name if 'extended syntax' is used. So we have two options: > 1) Ban dots in metric/attribute names > 2) Add a workaround to fall back. In other words if ReadAttributeHandler thinks extended syntax is being used, and cannot find the extracted 'timer' attribute, then try the full non-extracted name, e.g. timer.max_threads, and only then error. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5025) Suspending server has no effect for root context

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5025?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5025. ---------------------------- > Suspending server has no effect for root context > ------------------------------------------------ > > Key: WFLY-5025 > URL: https://issues.jboss.org/browse/WFLY-5025 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Radim Hatlapatka > Assignee: Stuart Douglas > Fix For: 10.0.0.Beta2 > > > Suspending the server works only on deployed deployments but it doesn't work for root context. > => after executing {{:suspend}} operation, requests to deployment are rejected as expected, still requests to {{http://localhost:8080}} are permitted and processed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017