[JBoss JIRA] (WFLY-10745) Broken JSF module installer
by Dmitrii Tikhomirov (JIRA)
[ https://issues.jboss.org/browse/WFLY-10745?page=com.atlassian.jira.plugin... ]
Dmitrii Tikhomirov updated WFLY-10745:
--------------------------------------
Steps to Reproduce:
{code}
git clone https://github.com/wildfly/wildfly
cd wildfly
mvn clean install -DskipTests
cd jsf/multi-jsf-installer
mvn -Djsf-version=2.3.5.SP1 -Pmojarra-2.x clean assembly:single
cp target/install-mojarra2.3.5.SP1.zip target/install-mojarra-2.3.5.SP1.cli
deploy ~/workspace/wildfly/jsf/multi-jsf-installer/target/install-mojarra-2.3.5.SP1.cli
/subsystem=jsf/:write-attribute(name=default-jsf-impl-slot,value=mojarra-2.3.5.SP1)
deploy hello-jsf.war
{code}
was:
{code}
git clone https://github.com/wildfly/wildfly
cd wildfly
mvn clean install -DskipTests
cd jsf/multi-jsf-installer
mvn -Djsf-version=2.2.17 -Pmojarra-2.x clean assembly:single
cp target/install-mojarra-2.2.17.zip target/install-mojarra-2.2.17.cli
deploy ~/workspace/wildfly/jsf/multi-jsf-installer/target/install-mojarra-2.2.17.cli
/subsystem=jsf/:write-attribute(name=default-jsf-impl-slot,value=mojarra-2.2.17)
deploy hello-jsf-version-0.0.1-SNAPSHOT.war
{code}
> Broken JSF module installer
> ---------------------------
>
> Key: WFLY-10745
> URL: https://issues.jboss.org/browse/WFLY-10745
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 14.0.0.Beta2
> Reporter: Jan Kašík
> Assignee: Dmitrii Tikhomirov
> Fix For: 14.0.0.CR1
>
> Attachments: hello_jsf.war
>
>
> It is currently not possible to deploy *.cli built by multi-jsf-installer shipped with WildFly. When attempting to deploy, this message will appear:
> {code}
> org.jboss.as.cli.CommandFormatException: org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to locate /tmp/vfs/cli-1528866094723/cli-1528866094723450313ef1dc90cff/install-mojarra-2.2.17.cli-212b6d42ba0c47e1/jsf-api-2.2.17.jar, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10745) Broken JSF module installer
by Dmitrii Tikhomirov (JIRA)
[ https://issues.jboss.org/browse/WFLY-10745?page=com.atlassian.jira.plugin... ]
Dmitrii Tikhomirov updated WFLY-10745:
--------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/11537 (was: https://github.com/wildfly/wildfly/pull/11346)
> Broken JSF module installer
> ---------------------------
>
> Key: WFLY-10745
> URL: https://issues.jboss.org/browse/WFLY-10745
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 14.0.0.Beta2
> Reporter: Jan Kašík
> Assignee: Dmitrii Tikhomirov
> Fix For: 14.0.0.CR1
>
> Attachments: hello_jsf.war
>
>
> It is currently not possible to deploy *.cli built by multi-jsf-installer shipped with WildFly. When attempting to deploy, this message will appear:
> {code}
> org.jboss.as.cli.CommandFormatException: org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to locate /tmp/vfs/cli-1528866094723/cli-1528866094723450313ef1dc90cff/install-mojarra-2.2.17.cli-212b6d42ba0c47e1/jsf-api-2.2.17.jar, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10875) Connection factory with discovery-group doesn't work
by ehsavoie Hugonnet (JIRA)
ehsavoie Hugonnet created WFLY-10875:
----------------------------------------
Summary: Connection factory with discovery-group doesn't work
Key: WFLY-10875
URL: https://issues.jboss.org/browse/WFLY-10875
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 13.0.0.Final
Reporter: ehsavoie Hugonnet
Assignee: ehsavoie Hugonnet
Priority: Critical
Jms client can not use remote connection factory defined as follows
{noformat}
<discovery-group name="dg-group1" jgroups-cluster="activemq-cluster"/>
<connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory" discovery-group="dg-group1" ha="true" block-on-acknowledge="true" reconnect-attempts="-1"/>
{noformat}
Following exception is thrown on client
{noformat}
Exception in thread "main" java.lang.RuntimeException: javax.naming.CommunicationException: WFNAM00020: Remote naming operation failed [Root exception is java.io.EOFException: Read past end of file]
at client.ProducerJms11.sendMessages(ProducerJms11.java:67)
at client.Producer.run(Producer.java:34)
at client.Producer.sendAllSync(Producer.java:25)
at client.ProducerJms11.main(ProducerJms11.java:14)
Caused by: javax.naming.CommunicationException: WFNAM00020: Remote naming operation failed [Root exception is java.io.EOFException: Read past end of file]
at org.wildfly.naming.client.remote.RemoteClientTransport.lookup(RemoteClientTransport.java:261)
at org.wildfly.naming.client.remote.RemoteContext.lambda$lookupNative$0(RemoteContext.java:190)
at org.wildfly.naming.client.NamingProvider.performExceptionAction(NamingProvider.java:222)
at org.wildfly.naming.client.remote.RemoteContext.performWithRetry(RemoteContext.java:100)
at org.wildfly.naming.client.remote.RemoteContext.lookupNative(RemoteContext.java:188)
at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
at org.wildfly.naming.client.store.RelativeFederatingContext.lookupNative(RelativeFederatingContext.java:58)
at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:74)
at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:60)
at org.wildfly.naming.client.AbstractFederatingContext.lookup(AbstractFederatingContext.java:66)
at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at client.ProducerJms11.sendMessages(ProducerJms11.java:43)
... 3 more
Caused by: java.io.EOFException: Read past end of file
at org.jboss.marshalling.SimpleDataInput.eofOnRead(SimpleDataInput.java:151)
at org.jboss.marshalling.SimpleDataInput.readUnsignedByteDirect(SimpleDataInput.java:294)
at org.jboss.marshalling.SimpleDataInput.readUnsignedByte(SimpleDataInput.java:249)
at org.jboss.marshalling.river.BlockUnmarshaller.readUnsignedByte(BlockUnmarshaller.java:258)
at org.jboss.marshalling.river.BlockUnmarshaller.readInt(BlockUnmarshaller.java:296)
at org.jboss.marshalling.river.BlockUnmarshaller.readUTF(BlockUnmarshaller.java:326)
at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.readExternal(ActiveMQConnectionFactory.java:186)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1414)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272)
at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:205)
at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41)
at org.wildfly.naming.client.remote.RemoteClientTransport.lookup(RemoteClientTransport.java:243)
... 15 more
Caused by: an exception which occurred:
in object of type org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory
{noformat}
It fails on attempt to look up RemoteCF
{noformat}
ConnectionFactory connectionFactory = (ConnectionFactory) namingContext.lookup(ClientDefaults.CONNECTION_FACTORY);
{noformat}
Same scenario with connector works well.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10745) Broken JSF module installer
by Dmitrii Tikhomirov (JIRA)
[ https://issues.jboss.org/browse/WFLY-10745?page=com.atlassian.jira.plugin... ]
Dmitrii Tikhomirov updated WFLY-10745:
--------------------------------------
Attachment: hello_jsf.war
> Broken JSF module installer
> ---------------------------
>
> Key: WFLY-10745
> URL: https://issues.jboss.org/browse/WFLY-10745
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 14.0.0.Beta2
> Reporter: Jan Kašík
> Assignee: Dmitrii Tikhomirov
> Fix For: 14.0.0.CR1
>
> Attachments: hello_jsf.war
>
>
> It is currently not possible to deploy *.cli built by multi-jsf-installer shipped with WildFly. When attempting to deploy, this message will appear:
> {code}
> org.jboss.as.cli.CommandFormatException: org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to locate /tmp/vfs/cli-1528866094723/cli-1528866094723450313ef1dc90cff/install-mojarra-2.2.17.cli-212b6d42ba0c47e1/jsf-api-2.2.17.jar, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10745) Broken JSF module installer
by Dmitrii Tikhomirov (JIRA)
[ https://issues.jboss.org/browse/WFLY-10745?page=com.atlassian.jira.plugin... ]
Dmitrii Tikhomirov updated WFLY-10745:
--------------------------------------
Attachment: (was: hello-jsf-version-0.0.1-SNAPSHOT.war)
> Broken JSF module installer
> ---------------------------
>
> Key: WFLY-10745
> URL: https://issues.jboss.org/browse/WFLY-10745
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 14.0.0.Beta2
> Reporter: Jan Kašík
> Assignee: Dmitrii Tikhomirov
> Fix For: 14.0.0.CR1
>
> Attachments: hello_jsf.war
>
>
> It is currently not possible to deploy *.cli built by multi-jsf-installer shipped with WildFly. When attempting to deploy, this message will appear:
> {code}
> org.jboss.as.cli.CommandFormatException: org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to locate /tmp/vfs/cli-1528866094723/cli-1528866094723450313ef1dc90cff/install-mojarra-2.2.17.cli-212b6d42ba0c47e1/jsf-api-2.2.17.jar, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1624) BC FIPS with CLI: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1624?page=com.atlassian.jira.plugin.s... ]
Martin Choma commented on ELY-1624:
-----------------------------------
I have prechecked and it works.
> BC FIPS with CLI: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
> ----------------------------------------------------------------------------------------------
>
> Key: ELY-1624
> URL: https://issues.jboss.org/browse/ELY-1624
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Reporter: Martin Choma
> Assignee: Farah Juma
> Priority: Blocker
> Attachments: eap_server.log, jboss-cli.log, keystore.bcfks, standalone.xml
>
>
> I am trying to connect from jboss-cli.sh to EAP server. Server and client run with BC FIPS.
> {code:java|title=jboss-cli.log}
> 11:48:08,992 TRACE [org.jboss.remoting.remote] Attempting to connect to "remote+https://127.0.0.1:9993" with options {org.xnio.Options.SSL_STARTTLS=>false,org.xnio.Options.SSL_ENABLED=>true}
> 11:48:14,005 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:330)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:304)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at 127.0.0.1:9993
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1447)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1226)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328)
> ... 5 more
> Caused by: java.io.IOException: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1394)
> ... 9 more
> Caused by: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+https://127.0.0.1:9993. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:130)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:167)
> at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:192)
> at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:126)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> {code}
> It works when I use
> - non-FIPS java for CLI and FIPS java for server when connecting to secured 9993 port
> - FIPS java for CLI and non-FIPS java for server when connecting to unsecured port 9990
> Here I get getting over ELY-1621 and ELY-1622
> I would appreciate any hint for way of investigation.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10847) Multiple service modules in single EAR use same tracer instance
by Juraci Paixão Kröhling (JIRA)
[ https://issues.jboss.org/browse/WFLY-10847?page=com.atlassian.jira.plugin... ]
Juraci Paixão Kröhling commented on WFLY-10847:
-----------------------------------------------
I was just talking with [~mkouba] on IRC about this one, and he made me realize that we might actually indeed want only one tracer instance per EAR, if we deem the EAR as being the "service". Previously, I had in mind that each WAR would be a service on its own, given that people are explicitly packaging WARs into a single EAR is a hint that they see that as a single service.
[~objectiser], [~pilhuhn], what do you think? What makes more sense, one service per EAR, or one service per WAR (potentially having multiple services per EAR)?
> Multiple service modules in single EAR use same tracer instance
> ---------------------------------------------------------------
>
> Key: WFLY-10847
> URL: https://issues.jboss.org/browse/WFLY-10847
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing
> Reporter: Michal Jurc
> Assignee: Juraci Paixão Kröhling
> Priority: Blocker
> Fix For: 14.0.0.CR1
>
>
> When deploying an EAR with two stand-alone JAX-RS services in stand-alone WAR modules, both of the services use the same {{Tracer}} instance.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2888) Data Type UX - dialog enhancements: Add and Reorder
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2888?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-2888:
---------------------------------------
Attachment: previous.gif
> Data Type UX - dialog enhancements: Add and Reorder
> ----------------------------------------------------
>
> Key: DROOLS-2888
> URL: https://issues.jboss.org/browse/DROOLS-2888
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: previous.gif
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * Add fields first to last, not last to first, in an ordered list to support the "reading" order of the fields so that I can simplify my workflow.
> * Reorder the list of Custom data types so that I can arrange data types in a logical order.
> * Add list items in such a way that added Fields will be presented at the bottom of a structured list by default.
> Functional considerations/ pre conditions:
> * Fields will be presented at the bottom of a structured list by default.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> * Drag-n-drop be evaluated with regard to accessibility.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months