[JBoss JIRA] (DROOLS-733) Unify Drools and jBPM execution servers
by Edson Tirelli (JIRA)
Edson Tirelli created DROOLS-733:
------------------------------------
Summary: Unify Drools and jBPM execution servers
Key: DROOLS-733
URL: https://issues.jboss.org/browse/DROOLS-733
Project: Drools
Issue Type: Feature Request
Components: kie server
Affects Versions: 6.2.0.Final
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: 6.3.0.Final
This is a placeholder parent ticket for the merge of the code from Drools and jBPM execution servers into a single server.
The new server should be standalone, free of UI code, support remote interfaces, and comply to all requirements from both Drools and jBPM.
It should try to avoid the use of technologies that cause issues on different containers (like CDI), and be as lightweight as possible for cloud deployment.
Initial open questions include:
* support to databases and persistence: should this be a per-container configuration or per-kjar configuration?
* can a single deployment model be used for both drools and jbpm?
* how to apply the security model from jbpm?
* does the workbench need to continue to support remote REST calls for deployments or can it be moved completely out of it?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (WFLY-4324) While starting Jboss AS getting IllegalStateException.
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4324?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-4324:
-----------------------------------
see https://developer.jboss.org/message/919055#919055
> While starting Jboss AS getting IllegalStateException.
> ------------------------------------------------------
>
> Key: WFLY-4324
> URL: https://issues.jboss.org/browse/WFLY-4324
> Project: WildFly
> Issue Type: Bug
> Environment: Java with 1.8 v and JBOS 7
> Reporter: ANKUSH NIKHAR
>
> Hi,
> I am facing issue when I am trying to deploy web service on Jboss 7 and using jdk 1.8 version. Below are the sample log :
> This issue does not impact the processing of my code execution. Is this just warning or will it harm in future.
> I am migrating my project from jdk1.7 to 1.8.
> When I try to deploy WS with jdk1.7, I didn't get such error.
> 18:56:01,032 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015852: Could not index class sun/applet/AppletPanel.class at /D:/Test Eclipse/Migration Eclipse/Mig Workspace/CDLibrary/CDLibrary-test/content/InMemory.war/WEB-INF/lib/tools.jar: java.lang.IllegalStateException: Unknown tag! pos=1006 poolCount = 1018
> at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:606) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2]
> at org.jboss.jandex.Indexer.index(Indexer.java:640) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2]
> at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:100) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
> at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_31]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_31]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (WFCORE-510) Fix filtering in domain mode
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/WFCORE-510?page=com.atlassian.jira.plugin... ]
Heiko Braun commented on WFCORE-510:
------------------------------------
[~brian.stansberry] any update on this?
> Fix filtering in domain mode
> ----------------------------
>
> Key: WFCORE-510
> URL: https://issues.jboss.org/browse/WFCORE-510
> Project: WildFly Core
> Issue Type: Sub-task
> Components: Domain Management
> Reporter: Harald Pehl
> Assignee: Brian Stansberry
> Fix For: 1.0.0.Beta1
>
>
> The overall result for query operations in domain mode does not filter undefined results. Executing the following operation, will yield three results. However the last result needs to be filtered:
> {code}
> [domain@localhost:9990 /] /host=master/server-config=*:query(select=[name, status, auto-start], where={auto-start=>true})
> {
> "outcome" => "success",
> "result" => [
> {
> "address" => [
> ("host" => "master"),
> ("server-config" => "server-one")
> ],
> "outcome" => undefined,
> "result" => {
> "name" => "server-one",
> "status" => "STARTED",
> "auto-start" => true
> }
> },
> {
> "address" => [
> ("host" => "master"),
> ("server-config" => "server-two")
> ],
> "outcome" => undefined,
> "result" => {
> "name" => "server-two",
> "status" => "STARTED",
> "auto-start" => true
> }
> },
> {
> "address" => [
> ("host" => "master"),
> ("server-config" => "server-three")
> ],
> "outcome" => undefined,
> "result" => undefined
> }
> ],
> "server-groups" => undefined
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (WFLY-4396) mod_cluster subsystem find any http server on the network
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-4396?page=com.atlassian.jira.plugin.... ]
Paul Ferraro closed WFLY-4396.
------------------------------
Resolution: Rejected
This is by design. You can control which wildfly nodes can see which httpd servers by using distinct multicast address/port combinations.
> mod_cluster subsystem find any http server on the network
> ---------------------------------------------------------
>
> Key: WFLY-4396
> URL: https://issues.jboss.org/browse/WFLY-4396
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.2.0.Final
> Environment: Ubuntu 14.04, wildfly 8.2.0.final, apache http server 2.2.29
> Reporter: Jose Diaz
> Assignee: Paul Ferraro
> Priority: Critical
> Labels: jboss
> Original Estimate: 4 weeks
> Remaining Estimate: 4 weeks
>
> I configure a Load Balanced HA Standalone Cluster, in my machine however in the network there is other apache http server when I wake up the server I get the next error:
> MODCLUSTER000043: Failed to send INFO to 10.21.51.121/10.21.51.121:22001: java.net.NoRouteToHostException: No existe ninguna ruta hasta el «host»
> I configure the mod_cluster in standalone-full-ha with:
> <subsystem xmlns="urn:jboss:domain:modcluster:1.2">
> <mod-cluster-config advertise-socket="modcluster" proxy-list="127.0.0.1:80" balancer="jdcluster" connector="ajp">
> <dynamic-load-provider>
> <load-metric type="cpu"/>
> </dynamic-load-provider>
> </mod-cluster-config>
> </subsystem>
> Then get the same error.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (WFLY-4401) Deployment fails with missing/unavailable dependencies
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-4401?page=com.atlassian.jira.plugin.... ]
Thomas Diesler commented on WFLY-4401:
--------------------------------------
Yes, it is relate to the same race. The management endpoint becomes available while the services it relies on are still starting up. IMHO, there should be a notion on BOOTSTRAP_COMPLETE that is a prerequisite for client connectors to become available.
> Deployment fails with missing/unavailable dependencies
> ------------------------------------------------------
>
> Key: WFLY-4401
> URL: https://issues.jboss.org/browse/WFLY-4401
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 8.2.0.Final
> Reporter: Thomas Diesler
> Assignee: Brian Stansberry
>
> Our testsuite bootstraps the server and then waits for the native management interface to become available on 8181
> A subsequent deployment (intermittently) fails with
> {code}
> domain-master> [Host Controller] [0m[0m05:09:40,678 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /opt/jboss/wildfly/domain/data/content/ef/3743938a6b38a2ae473f12778fef7ad0ce464c/content[0m
> domain-slave> [Server:server-one] [0m[31m05:09:41,654 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 5) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "domain-endpoint.war")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"domain-endpoint.war\" is missing [jboss.deployment.chains]"]}[0m
> {code}
> There seems to be a missing guarantee that allows the management endpoint to answer deployment requests when the deployment chain services are not up.
> CrossLink: https://github.com/wildfly-extras/wildfly-camel/issues/175
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months
[JBoss JIRA] (WFCORE-478) log4j ConsoleAppender won't display messages with per-deployment logging
by Geert Coelmont (JIRA)
[ https://issues.jboss.org/browse/WFCORE-478?page=com.atlassian.jira.plugin... ]
Geert Coelmont commented on WFCORE-478:
---------------------------------------
Thanks James, very useful. I've opted for the second option and this is working nicely.
> log4j ConsoleAppender won't display messages with per-deployment logging
> ------------------------------------------------------------------------
>
> Key: WFCORE-478
> URL: https://issues.jboss.org/browse/WFCORE-478
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Minor
>
> Add the following log4j.properties file to a deployment and try to log.
> {code}
> # Root logger option
> log4j.rootLogger=INFO, stdout
> # Direct log messages to stdout
> log4j.appender.stdout=org.apache.log4j.ConsoleAppender
> log4j.appender.stdout.Target=System.out
> log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
> log4j.appender.stdout.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss} %-5p %c{1}:%L - %m%n
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 3 months