[JBoss JIRA] (WFLY-11049) Quickstart jaxws-retail expected errors section needs to be extended
by Eduardo Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-11049?page=com.atlassian.jira.plugin... ]
Eduardo Martins commented on WFLY-11049:
----------------------------------------
[~jamontoya] Which Quickstarts version? Did you made any changes in the code?
> Quickstart jaxws-retail expected errors section needs to be extended
> --------------------------------------------------------------------
>
> Key: WFLY-11049
> URL: https://issues.jboss.org/browse/WFLY-11049
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Environment: Fedora 28; JDK11 build 11+28
> Reporter: Jan Blizňák
> Assignee: Sande Gilda
> Priority: Major
> Fix For: 17.0.0.Beta1
>
>
> When jaxws-retail quickstart is executed on JDK11, you may encounter these warnings:
> {code:java}
> [INFO] --- jaxws-tools-maven-plugin:1.2.2.Final:wsconsume (default) @ jaxws-retail-service ---
> [ERROR] /bin/sh: switchml: line 1: syntax error: unexpected end of file
> [ERROR] /bin/sh: error importing function definition for `switchml'
> [ERROR] /bin/sh: _moduleraw: line 1: syntax error: unexpected end of file
> [ERROR] /bin/sh: error importing function definition for `_moduleraw'
> {code}
> This is similar of what is already in expected errors section https://github.com/wildfly/quickstart/blob/master/jaxws-retail/README.adoc, so we might extend the section to be more generic, talking about {{BASH_FUNC_*}}.
> The interesting thing is I can see this happening only with JDK11.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-5785) EJB lookup fails with "No cluster context available" in failover tests
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/WFLY-5785?page=com.atlassian.jira.plugin.... ]
Paul Ferraro closed WFLY-5785.
------------------------------
Resolution: Out of Date
> EJB lookup fails with "No cluster context available" in failover tests
> ----------------------------------------------------------------------
>
> Key: WFLY-5785
> URL: https://issues.jboss.org/browse/WFLY-5785
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.CR5
> Reporter: Michal Vinkler
> Assignee: Richard Achmatowicz
> Priority: Major
>
> Seen in our failover tests for remote stateful EJBs - scenarios:
> ejb-ejbremote-shutdown-dist-async
> ejb-ejbremote-shutdown-dist-sync
> ejb-ejbremote-undeploy-dist-async
> After failing a node, occasionally EJB lookup starts failing - client starts logging these error messages:
> {code}
> 2015/12/03 04:46:47:078 EST [ERROR][Runner - 9] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb>
> java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb
> at org.jboss.ejb.client.EJBClientContext.requireClusterEJBReceiverContext(EJBClientContext.java:1063)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:84)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
> at com.sun.proxy.$Proxy2.getSerialAndIncrement(Unknown Source)
> at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:84)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> It stops logging these messages only after the failed node is restarted and joins the cluster again.
> Link (this job was configured to use only 100 sessions in order to keep the log size small)
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mvinkler_eap-7x-failo...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3854) DMN: Add a nested row to a new Structured data type by default
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3854?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-3854:
-------------------------------------------
[~karreiro] Well if we keep the Save action, per row, then once you click Save for the Structured data type the new child row could be added by default (in Edit mode.)
* Although are you proposing that we save rows dynamically without using Save and Edit buttons? If so, what action would the user take to save the selections made per row. And how would they get the row in edit mode? I'm assuming that we're still talking about per row, versus per field, actions?
> DMN: Add a nested row to a new Structured data type by default
> --------------------------------------------------------------
>
> Key: DROOLS-3854
> URL: https://issues.jboss.org/browse/DROOLS-3854
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam
> Attachments: Screen Shot 2019-04-03 at 4.15.11 PM.png
>
>
> Usability: Reduce the number of clicks / actions to add a nested element.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-5437) Occassional stale data with remote EJB invocations and sync cache
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/WFLY-5437?page=com.atlassian.jira.plugin.... ]
Paul Ferraro closed WFLY-5437.
------------------------------
Resolution: Out of Date
> Occassional stale data with remote EJB invocations and sync cache
> -----------------------------------------------------------------
>
> Key: WFLY-5437
> URL: https://issues.jboss.org/browse/WFLY-5437
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.CR1
> Reporter: Richard Janik
> Assignee: Paul Ferraro
> Priority: Major
>
> Hi,
> we're occasionally getting stale data on remote EJB invocations (number counter returns number 1 lower than expected, see example). -This is usually preceded (~6 seconds before that) by cluster wide rebalance after a node is brought back from dead.-
> - 2000 clients, stale data is uncommon
> - requests from a single client are separated by a 4 second window.
> An example of stale data:
> {code}
> 2015/08/28 13:01:35:442 EDT [WARN ][Runner - 640] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Response serial does not match. Expected: 86, received: 85, runner: 640.>
> {code}
> And a link to our jobs if you're interested:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-...
> This behavior has so far been observed with jvmkill and undeploy scenario, on REPL-SYNC and DIST-SYNC caches.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-5437) Occassional stale data with remote EJB invocations and sync cache
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-5437?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-5437:
--------------------------------------
Clean undeploy is not yet supported, see WFLY-11945.
> Occassional stale data with remote EJB invocations and sync cache
> -----------------------------------------------------------------
>
> Key: WFLY-5437
> URL: https://issues.jboss.org/browse/WFLY-5437
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.CR1
> Reporter: Richard Janik
> Assignee: Paul Ferraro
> Priority: Major
>
> Hi,
> we're occasionally getting stale data on remote EJB invocations (number counter returns number 1 lower than expected, see example). -This is usually preceded (~6 seconds before that) by cluster wide rebalance after a node is brought back from dead.-
> - 2000 clients, stale data is uncommon
> - requests from a single client are separated by a 4 second window.
> An example of stale data:
> {code}
> 2015/08/28 13:01:35:442 EDT [WARN ][Runner - 640] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Response serial does not match. Expected: 86, received: 85, runner: 640.>
> {code}
> And a link to our jobs if you're interested:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-...
> This behavior has so far been observed with jvmkill and undeploy scenario, on REPL-SYNC and DIST-SYNC caches.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-5304) NullPointerException during server graceful shutdown after EJBClient invocation arrived
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/WFLY-5304?page=com.atlassian.jira.plugin.... ]
Paul Ferraro closed WFLY-5304.
------------------------------
Resolution: Duplicate Issue
Clean undeploy is to covered by WFLY-11945.
> NullPointerException during server graceful shutdown after EJBClient invocation arrived
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-5304
> URL: https://issues.jboss.org/browse/WFLY-5304
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB, Remoting
> Affects Versions: 10.0.0.Beta1
> Reporter: Michal Vinkler
> Assignee: Richard Achmatowicz
> Priority: Minor
>
> EAP 7.0.0.DR9
> Scenario: ejb-ejbremote-shutdown-repl-async
> Perf21 logged NPE just before it gracefully shut down:
> {code}
> [JBossINF] [0m[31m09:02:25,058 ERROR [org.jboss.as.ejb3.remote] (default task-24) WFLYEJB0148: Exception on channel Channel ID 423b1c54 (inbound) of Remoting connection 41f997cb to /10.16.90.52:54492 from message org.jboss.remoting3.remote.InboundMessage$3@45c60b2c: java.lang.NullPointerException
> [JBossINF] at org.jboss.as.ejb3.deployment.DeploymentRepository.getStartedModules(DeploymentRepository.java:152)
> [JBossINF] at org.jboss.as.ejb3.remote.protocol.versionone.EJBIdentifierBasedMessageHandler.findEJB(EJBIdentifierBasedMessageHandler.java:46)
> [JBossINF] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.processMessage(MethodInvocationMessageHandler.java:124)
> [JBossINF] at org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver.processMessage(VersionOneProtocolChannelReceiver.java:213)
> [JBossINF] at org.jboss.as.ejb3.remote.protocol.versiontwo.VersionTwoProtocolChannelReceiver.processMessage(VersionTwoProtocolChannelReceiver.java:76)
> [JBossINF] at org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver.handleMessage(VersionOneProtocolChannelReceiver.java:157)
> [JBossINF] at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:463)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [JBossINF] at java.lang.Thread.run(Thread.java:745)
> [JBossINF]
> [JBossINF] [0m[0m09:02:25,104 INFO [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 81) ISPN000029: Passivating all entries to disk
> [JBossINF] [0m[0m09:02:25,108 INFO [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 81) ISPN000030: Passivated 3 entries in 3 milliseconds
> [JBossINF] [0m[0m09:02:25,131 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0008: Undertow HTTP listener default suspending
> [JBossINF] [0m[0m09:02:25,132 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 81) WFLYCLINF0003: Stopped repl cache from ejb container
> [JBossINF] [0m[0m09:02:25,148 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0008: Undertow AJP listener ajp suspending
> [JBossINF] [0m[0m09:02:25,151 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0007: Undertow HTTP listener default stopped, was bound to perf21/10.16.90.60:8080
> [JBossINF] [0m[0m09:02:25,156 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0208: Stopped subdeployment (runtime-name: clusterbench-ee7-ejb.jar) in 1024ms
> [JBossINF] [0m[0m09:02:25,156 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0208: Stopped subdeployment (runtime-name: clusterbench-ee7-web-passivating.war) in 1055ms
> [JBossINF] [0m[0m09:02:25,156 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0208: Stopped subdeployment (runtime-name: clusterbench-ee7-web-default.war) in 1041ms
> [JBossINF] [0m[0m09:02:25,167 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000080: Disconnecting JGroups channel ejb
> [JBossINF] [0m[0m09:02:25,169 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0007: Undertow AJP listener ajp stopped, was bound to perf21/10.16.90.60:8009
> [JBossINF] [0m[0m09:02:25,169 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment clusterbench-ee7.ear (runtime-name: clusterbench-ee7.ear) in 1054ms
> [JBossINF] [0m[0m09:02:25,170 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000082: Stopping the RpcDispatcher for channel ejb
> [JBossINF] [0m[0m09:02:25,171 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 1.3.0.Beta9 stopping
> [JBossINF] [0m[0m09:02:25,275 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: EAP 7.0.0.Alpha1 (WildFly Core 2.0.0.Beta4) stopped in 1125ms
> {code}
> Graceful shutdown timeout was set to 300 seconds.
> It does not seem to generate any kind of error on the client.
> The similar issue was already mentioned by Richard Achmatowicz here:
> https://issues.jboss.org/browse/WFLY-4697?focusedCommentId=13076866&page=...
> Server log:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-e...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-11945) Support clean/graceful undeploy
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-11945?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-11945:
----------------------------------
Description: Currently we only support clean/graceful server shutdown this placeholder issue is to support clean/graceful undeploy. (was: Currently we only support clean/graceful undeploy this placeholder issue is to support clean/graceful undeploy.)
> Support clean/graceful undeploy
> -------------------------------
>
> Key: WFLY-11945
> URL: https://issues.jboss.org/browse/WFLY-11945
> Project: WildFly
> Issue Type: Feature Request
> Components: Management
> Affects Versions: 16.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Jeff Mesnil
> Priority: Major
>
> Currently we only support clean/graceful server shutdown this placeholder issue is to support clean/graceful undeploy.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-5178) Intermittent failure: NullPointerException during undeployment
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-5178?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-5178:
--------------------------------------
Clean undeploy is not currently supported, see WFLY-11945.
> Intermittent failure: NullPointerException during undeployment
> --------------------------------------------------------------
>
> Key: WFLY-5178
> URL: https://issues.jboss.org/browse/WFLY-5178
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Affects Versions: 10.0.0.Beta1
> Reporter: Michal Vinkler
> Assignee: Richard Achmatowicz
> Priority: Major
> Labels: clean_undeploy
>
> Intermittent failure, so far seen in only one failover test for remote stateful EJBs:
> scenario ejb-ejbremote-undeploy-dist-async
> Setup: 4 node cluster, one node at time undeploys application (clusterbench-ee7.ear), while standalone clients keep calling the application.
> Just before server perf19 finished undeployment of the application, it logged this error 50 times:
> {code}
> [JBossINF] [0m[31m14:50:41,136 ERROR [org.jboss.as.ejb3.remote] (EJB default - 9) WFLYEJB0151: Exception while generating session id for component RemoteStatefulSBImpl with invocation id: -28551 on channel Channel ID 1ca843e6 (inbound) of Remoting connection 4b2907f9 to /10.16.90.52:58920: javax.ejb.EJBException: java.lang.NullPointerException
> [JBossINF] at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createSessionRemote(StatefulSessionComponent.java:263)
> [JBossINF] at org.jboss.as.ejb3.remote.protocol.versionone.SessionOpenRequestHandler$SessionIDGeneratorTask.run(SessionOpenRequestHandler.java:145)
> [JBossINF] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [JBossINF] at java.lang.Thread.run(Thread.java:745)
> [JBossINF] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> [JBossINF] Caused by: java.lang.NullPointerException
> [JBossINF] at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createSession(StatefulSessionComponent.java:238)
> [JBossINF] at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createSessionRemote(StatefulSessionComponent.java:258)
> [JBossINF] ... 7 more
> {code}
> The other nodes did not log this error.
> Server log:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-e...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-5178) Intermittent failure: NullPointerException during undeployment
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-5178?page=com.atlassian.jira.plugin.... ]
Radoslav Husar closed WFLY-5178.
--------------------------------
Resolution: Duplicate Issue
> Intermittent failure: NullPointerException during undeployment
> --------------------------------------------------------------
>
> Key: WFLY-5178
> URL: https://issues.jboss.org/browse/WFLY-5178
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Affects Versions: 10.0.0.Beta1
> Reporter: Michal Vinkler
> Assignee: Richard Achmatowicz
> Priority: Major
> Labels: clean_undeploy
>
> Intermittent failure, so far seen in only one failover test for remote stateful EJBs:
> scenario ejb-ejbremote-undeploy-dist-async
> Setup: 4 node cluster, one node at time undeploys application (clusterbench-ee7.ear), while standalone clients keep calling the application.
> Just before server perf19 finished undeployment of the application, it logged this error 50 times:
> {code}
> [JBossINF] [0m[31m14:50:41,136 ERROR [org.jboss.as.ejb3.remote] (EJB default - 9) WFLYEJB0151: Exception while generating session id for component RemoteStatefulSBImpl with invocation id: -28551 on channel Channel ID 1ca843e6 (inbound) of Remoting connection 4b2907f9 to /10.16.90.52:58920: javax.ejb.EJBException: java.lang.NullPointerException
> [JBossINF] at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createSessionRemote(StatefulSessionComponent.java:263)
> [JBossINF] at org.jboss.as.ejb3.remote.protocol.versionone.SessionOpenRequestHandler$SessionIDGeneratorTask.run(SessionOpenRequestHandler.java:145)
> [JBossINF] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [JBossINF] at java.lang.Thread.run(Thread.java:745)
> [JBossINF] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> [JBossINF] Caused by: java.lang.NullPointerException
> [JBossINF] at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createSession(StatefulSessionComponent.java:238)
> [JBossINF] at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createSessionRemote(StatefulSessionComponent.java:258)
> [JBossINF] ... 7 more
> {code}
> The other nodes did not log this error.
> Server log:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-e...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month