[JBoss JIRA] (DROOLS-1728) There is always HTTP 404 Error Where I request the maven2 in workbench
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1728?page=com.atlassian.jira.plugi... ]
Mario Fusco reassigned DROOLS-1728:
-----------------------------------
Assignee: Michael Anstis (was: Mario Fusco)
> There is always HTTP 404 Error Where I request the maven2 in workbench
> ----------------------------------------------------------------------
>
> Key: DROOLS-1728
> URL: https://issues.jboss.org/browse/DROOLS-1728
> Project: Drools
> Issue Type: Bug
> Components: tools
> Affects Versions: 7.3.0.Final
> Environment: CentOS 6.8
> Virtual Box 5.x
> Tomcat 8.5.20
> kie-drools-wb-7.3.0.Final-tomcat8.war
> MySQL 5.6.x
> Reporter: HuiYu Zhou
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: reported-by-qe
>
> I want to try KieScanner for the remote maven repo. So I setup the workbench and create "Project1" as a sample, I also build and deploy it successfully. I can see the jar named "Project1-1.0.0.jar" with GAV "com.myteam:Project1:1.0.0" exist in “Admin” -> "Artifacts".
> So I add the repository into my development pom.xml and the jar as dependency, but the jar can't been downloaded by Maven Project.
> I also try to open the url: http://192.168.56.101:8080/kie-drools-wb/maven2, but there is always HTTP Status 404 – Not Found happened with description " The origin server did not find a current representation for the target resource or is not willing to disclose that one exists."
> The most funny thing is I can open the url: http://192.168.56.101:8080/kie-drools-wb/maven2/com/myteam/Project1/maven..., the content is shown in my webpage as following:
> This XML file does not appear to have any style information associated with it. The document tree is shown below.
> <metadata>
> <groupId>com.myteam</groupId>
> <artifactId>Project1</artifactId>
> <versioning>
> <release>1.0.0</release>
> <versions>
> <version>1.0.0</version>
> </versions>
> <lastUpdated>20170913142741</lastUpdated>
> </versioning>
> </metadata>
> As remote maven repo of workbench, why not like my private nexus maven that I can open the link even if it 's a folder?
>
> my pom.xml as following:
> <?xml version="1.0" encoding="UTF-8"?>
> <project xmlns="http://maven.apache.org/POM/4.0.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>drools</groupId>
> <artifactId>drools</artifactId>
> <version>1.0-SNAPSHOT</version>
> <properties>
> <drools.version>7.3.0.Final</drools.version>
> </properties>
> <repositories>
> <repository>
> <id>guvnor-m2-repo</id>
> <name>Guvnor M2 Repo</name>
> <url>http://192.168.56.101:8080/kie-drools-wb/maven2/</url>
> </repository>
> </repositories>
> <dependencies>
> <dependency>
> <groupId>com.myteam</groupId>
> <artifactId>Project1</artifactId>
> <version>1.0.0</version>
> </dependency>
> <!--drools dependencies -->
> </dependencies>
> </project>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (DROOLS-1709) KieServicesException: Error while deserializing data received from server!
by Maciej Swiderski (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1709?page=com.atlassian.jira.plugi... ]
Maciej Swiderski commented on DROOLS-1709:
------------------------------------------
could you please provide minimal reproducer for this? Like maven project with your business assets (kjar) that can be deployed to kie server to verify and fix.
> KieServicesException: Error while deserializing data received from server!
> --------------------------------------------------------------------------
>
> Key: DROOLS-1709
> URL: https://issues.jboss.org/browse/DROOLS-1709
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 7.1.0.Final
> Environment: - Wildfly 10.0.0.Final.
> - Kie-server and kie-workbench 7.1.0 FINAL.
> - Drools 7.1.0 FINAL.
> - Java 8.
> - joda-time 2.9.9.
> - Oracle Linux.
> Reporter: Nicolae Turcan
> Assignee: Maciej Swiderski
> Labels: DateTime, drools, joda-time, json, kie-server, serialization
>
> Hello,
> I'm trying to make working drools 7.1.0 FINAL but I'm getting *unmarshalling input error* when I'm sending an object with a *joda DateTime* attribute to kie-server. Seems like a bug while serializing/deserializing datetime object to json.
> Can someone help me please?
> org.kie.server.api.exception.KieServicesException: Error while deserializing data received from server!
> at org.kie.server.client.impl.AbstractKieServicesClientImpl.deserialize(AbstractKieServicesClientImpl.java:592)
> at org.kie.server.client.impl.AbstractKieServicesClientImpl.makeHttpPostRequestAndCreateServiceResponse(AbstractKieServicesClientImpl.java:286)
> at org.kie.server.client.impl.AbstractKieServicesClientImpl.makeHttpPostRequestAndCreateServiceResponse(AbstractKieServicesClientImpl.java:264)
> at org.kie.server.client.impl.RuleServicesClientImpl.executeCommandsWithResults(RuleServicesClientImpl.java:66)
> at kettle.resources.KieServerClient.fireKettleRules(KieServerClient.java:135)
> at kettle.application.NegocioBean.aplicarReglas(NegocioBean.java:102)
> at kettle.services.KettleService.recieveDataJson(KettleService.java:72)
> at KettleTester.main(KettleTester.java:37)
> Caused by: org.kie.server.api.marshalling.MarshallingException: Error unmarshalling input
> at org.kie.server.api.marshalling.json.JSONMarshaller.unmarshall(JSONMarshaller.java:279)
> at org.kie.server.client.impl.AbstractKieServicesClientImpl.deserialize(AbstractKieServicesClientImpl.java:590)
> ... 7 more
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: Can not construct instance of org.joda.time.Chronology, problem: abstract types either need to be mapped to concrete types, have custom deserializer, or be instantiated with additional type information
> at [Source: {
> "type" : "SUCCESS",
> "msg" : "Container DEV successfully called.",
> "result" : {
> "execution-results" : {
> "results" : [ {
> "value" : [{
> "kettle.model.MensajesError" : {
> "tipoError" : null
> }
> },{
> "tws.hibernate.mappings.TmOt" : {
> "id" : 150078,
> "finishedAt" : {
> "dayOfMonth" : 19,
> "year" : 2017,
> "era" : 1,
> "dayOfYear" : 231,
> "dayOfWeek" : 6,
> "millisOfDay" : 46800000,
> "monthOfYear" : 8,
> "hourOfDay" : 13,
> "minuteOfHour" : 0,
> "secondOfMinute" : 0,
> "millisOfSecond" : 0,
> "weekOfWeekyear" : 33,
> "weekyear" : 2017,
> "yearOfEra" : 2017,
> "yearOfCentury" : 17,
> "centuryOfEra" : 20,
> "secondOfDay" : 46800,
> "minuteOfDay" : 780,
> "millis" : 1503140400000,
> "zone" : {
> "fixed" : false,
> "uncachedZone" : {
> "fixed" : false,
> "cachable" : true,
> "id" : "Europe/Madrid"
> },
> "id" : "Europe/Madrid"
> },
> "chronology" : {
> "zone" : {
> "fixed" : false,
> "uncachedZone" : {
> "fixed" : false,
> "cachable" : true,
> "id" : "Europe/Madrid"
> },
> "id" : "Europe/Madrid"
> }
> },
> "afterNow" : false,
> "beforeNow" : true,
> "equalNow" : false
> },
> "startedAt" : {
> "dayOfMonth" : 19,
> "year" : 2017,
> "era" : 1,
> "dayOfYear" : 231,
> "dayOfWeek" : 6,
> "millisOfDay" : 34200000,
> "monthOfYear" : 8,
> "hourOfDay" : 9,
> "minuteOfHour" : 30,
> "secondOfMinute" : 0,
> "millisOfSecond" : 0,
> "weekOfWeekyear" : 33,
> "weekyear" : 2017,
> "yearOfEra" : 2017,
> "yearOfCentury" : 17,
> "centuryOfEra" : 20,
> "secondOfDay" : 34200,
> "minuteOfDay" : 570,
> "millis" : 1503127800000,
> "zone" : {
> "fixed" : false,
> "uncachedZone" : {
> "fixed" : false,
> "cachable" : true,
> "id" : "Europe/Madrid"
> },
> "id" : "Europe/Madrid"
> },
> "chronology" : {
> "zone" : {
> "fixed" : false,
> "uncachedZone" : {
> "fixed" : false,
> "cachable" : true,
> "id" : "Europe/Madrid"
> },
> "id" : "Europe/Madrid"
> }
> },
> "afterNow" : false,
> "beforeNow" : true,
> "equalNow" : false
> }
> }},
> "key" : "orden"
> }, {
> "value" : {"kettle.model.MensajesError" : {
> "tipoError" : null
> }},
> "key" : "mensaje"
> } ],
> "facts" : [ {
> "value" : {"org.drools.core.common.DefaultFactHandle":{
> "external-form" : "0:1:242655221:1872950214:1:DEFAULT:NON_TRAIT:java.util.LinkedHashMap"
> }},
> "key" : "orden"
> }, {
> "value" : {"org.drools.core.common.DefaultFactHandle":{
> "external-form" : "0:2:1104605608:-2037841024:2:DEFAULT:NON_TRAIT:java.util.LinkedHashMap"
> }},
> "key" : "mensaje"
> } ]
> }
> }
> }; line: 88, column: 8] (through reference chain: org.kie.server.api.model.ServiceResponse["result"]->org.drools.core.runtime.impl.ExecutionResultImpl["results"]->Object[][0]->org.drools.core.xml.jaxb.util.JaxbStringObjectPair["value"]->tws.hibernate.mappings.TmOt["finishedAt"]->org.joda.time.DateTime["chronology"])
> at com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:148)
> at com.fasterxml.jackson.databind.DeserializationContext.instantiationException(DeserializationContext.java:889)
> at com.fasterxml.jackson.databind.deser.AbstractDeserializer.deserialize(AbstractDeserializer.java:139)
> at com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:520)
> at com.fasterxml.jackson.databind.deser.impl.MethodProperty.deserializeAndSet(MethodProperty.java:95)
> at com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:256)
> at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:125)
> at com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:520)
> at com.fasterxml.jackson.databind.deser.impl.MethodProperty.deserializeAndSet(MethodProperty.java:95)
> at com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:256)
> at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:125)
> at com.fasterxml.jackson.databind.ObjectMapper._readValue(ObjectMapper.java:3703)
> at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2006)
> at org.kie.server.api.marshalling.json.JSONMarshaller$CustomObjectDeserializer.mapObject(JSONMarshaller.java:667)
> at com.fasterxml.jackson.databind.deser.std.UntypedObjectDeserializer.deserialize(UntypedObjectDeserializer.java:222)
> at com.fasterxml.jackson.databind.deser.std.UntypedObjectDeserializer.mapArray(UntypedObjectDeserializer.java:356)
> at com.fasterxml.jackson.databind.deser.std.UntypedObjectDeserializer.deserialize(UntypedObjectDeserializer.java:230)
> at com.fasterxml.jackson.databind.deser.std.StdDelegatingDeserializer.deserialize(StdDelegatingDeserializer.java:160)
> at com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:520)
> at com.fasterxml.jackson.databind.deser.impl.FieldProperty.deserializeAndSet(FieldProperty.java:101)
> at com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:256)
> at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:125)
> at com.fasterxml.jackson.databind.deser.std.ObjectArrayDeserializer.deserialize(ObjectArrayDeserializer.java:156)
> at com.fasterxml.jackson.databind.deser.std.ObjectArrayDeserializer.deserialize(ObjectArrayDeserializer.java:17)
> at com.fasterxml.jackson.databind.deser.std.StdDelegatingDeserializer.deserialize(StdDelegatingDeserializer.java:160)
> at com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:520)
> at com.fasterxml.jackson.databind.deser.impl.FieldProperty.deserializeAndSet(FieldProperty.java:101)
> at com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:256)
> at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:125)
> at com.fasterxml.jackson.databind.jsontype.impl.AsWrapperTypeDeserializer._deserialize(AsWrapperTypeDeserializer.java:114)
> at com.fasterxml.jackson.databind.jsontype.impl.AsWrapperTypeDeserializer.deserializeTypedFromAny(AsWrapperTypeDeserializer.java:64)
> at com.fasterxml.jackson.databind.deser.std.UntypedObjectDeserializer.deserializeWithType(UntypedObjectDeserializer.java:289)
> at com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:518)
> at com.fasterxml.jackson.databind.deser.impl.FieldProperty.deserializeAndSet(FieldProperty.java:101)
> at com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:256)
> at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:125)
> at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3731)
> at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2724)
> at org.kie.server.api.marshalling.json.JSONMarshaller.unmarshall(JSONMarshaller.java:277)
> ... 8 more
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (DROOLS-1728) There is always HTTP 404 Error Where I request the maven2 in workbench
by HuiYu Zhou (JIRA)
HuiYu Zhou created DROOLS-1728:
----------------------------------
Summary: There is always HTTP 404 Error Where I request the maven2 in workbench
Key: DROOLS-1728
URL: https://issues.jboss.org/browse/DROOLS-1728
Project: Drools
Issue Type: Bug
Components: tools
Affects Versions: 7.3.0.Final
Environment: CentOS 6.8
Virtual Box 5.x
Tomcat 8.5.20
kie-drools-wb-7.3.0.Final-tomcat8.war
MySQL 5.6.x
Reporter: HuiYu Zhou
Assignee: Mario Fusco
Priority: Blocker
I want to try KieScanner for the remote maven repo. So I setup the workbench and create "Project1" as a sample, I also build and deploy it successfully. I can see the jar named "Project1-1.0.0.jar" with GAV "com.myteam:Project1:1.0.0" exist in “Admin” -> "Artifacts".
So I add the repository into my development pom.xml and the jar as dependency, but the jar can't been downloaded by Maven Project.
I also try to open the url: http://192.168.56.101:8080/kie-drools-wb/maven2, but there is always HTTP Status 404 – Not Found happened with description " The origin server did not find a current representation for the target resource or is not willing to disclose that one exists."
The most funny thing is I can open the url: http://192.168.56.101:8080/kie-drools-wb/maven2/com/myteam/Project1/maven..., the content is shown in my webpage as following:
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<metadata>
<groupId>com.myteam</groupId>
<artifactId>Project1</artifactId>
<versioning>
<release>1.0.0</release>
<versions>
<version>1.0.0</version>
</versions>
<lastUpdated>20170913142741</lastUpdated>
</versioning>
</metadata>
As remote maven repo of workbench, why not like my private nexus maven that I can open the link even if it 's a folder?
my pom.xml as following:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>drools</groupId>
<artifactId>drools</artifactId>
<version>1.0-SNAPSHOT</version>
<properties>
<drools.version>7.3.0.Final</drools.version>
</properties>
<repositories>
<repository>
<id>guvnor-m2-repo</id>
<name>Guvnor M2 Repo</name>
<url>http://192.168.56.101:8080/kie-drools-wb/maven2/</url>
</repository>
</repositories>
<dependencies>
<dependency>
<groupId>com.myteam</groupId>
<artifactId>Project1</artifactId>
<version>1.0.0</version>
</dependency>
<!--drools dependencies -->
</dependencies>
</project>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9343) Modcluster fails to start with negative port offset used
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9343?page=com.atlassian.jira.plugin.... ]
Radoslav Husar moved JBEAP-13159 to WFLY-9343:
----------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9343 (was: JBEAP-13159)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: mod_cluster
(was: mod_cluster)
Affects Version/s: 11.0.0.CR1
(was: 7.1.0.CR1)
> Modcluster fails to start with negative port offset used
> --------------------------------------------------------
>
> Key: WFLY-9343
> URL: https://issues.jboss.org/browse/WFLY-9343
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 11.0.0.CR1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
>
> When using a negative port-offset in HA profiles, mod-cluster fails to start.
> This problem doesn't occur in non-HA profiles (e.g. default), because the modcluster subsystem is not present in them.
> Server log contains:
> {noformat}
> 19:59:41,337 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service org.wildfly.mod_cluster.config: org.jboss.msc.service.StartException in service org.wildfly.mod_cluster.config: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: port out of range:-100
> at java.net.InetSocketAddress.checkPort(InetSocketAddress.java:143)
> at java.net.InetSocketAddress.<init>(InetSocketAddress.java:188)
> at org.jboss.as.network.SocketBinding.getSocketAddress(SocketBinding.java:129)
> at org.wildfly.extension.mod_cluster.ModClusterConfigurationServiceBuilder.getValue(ModClusterConfigurationServiceBuilder.java:272)
> at org.wildfly.extension.mod_cluster.ModClusterConfigurationServiceBuilder.getValue(ModClusterConfigurationServiceBuilder.java:104)
> at org.jboss.msc.service.ValueService.start(ValueService.java:49)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> ... 3 more
> 19:59:41,492 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
> 19:59:41,493 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
> 19:59:41,657 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0014: Creating file handler for path '/home/kwart/test/710CR1/jboss-eap-7.1/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
> 19:59:41,663 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0012: Started server default-server.
> 19:59:41,666 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
> 19:59:41,729 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0493: EJB subsystem suspension complete
> 19:59:41,747 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow AJP listener ajp listening on 127.0.0.1:7909
> 19:59:41,749 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:7980
> 19:59:41,881 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
> 19:59:41,989 INFO [org.jboss.as.patching] (MSC service thread 1-3) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none
> 19:59:42,006 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore /home/kwart/test/710CR1/jboss-eap-7.1/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
> 19:59:42,043 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) WFLYDS0013: Started FileSystemDeploymentService for directory /home/kwart/test/710CR1/jboss-eap-7.1/standalone/deployments
> 19:59:42,151 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8343
> 19:59:42,252 INFO [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBossWS 5.1.9.Final-redhat-1 (Apache CXF 3.1.12.redhat-1)
> 19:59:42,259 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "modcluster")]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.mod_cluster.config" => "Failed to start service
> Caused by: java.lang.IllegalArgumentException: port out of range:-100"}}
> 19:59:42,282 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service org.wildfly.mod_cluster.config: Failed to start service
> 19:59:42,367 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
> 19:59:42,369 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9890/management
> 19:59:42,370 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9890
> 19:59:42,370 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.1.0.GA (WildFly Core 3.0.1.Final-redhat-1) started (with errors) in 4175ms - Started 309 of 642 services (3 services failed or missing dependencies, 421 services are lazy, passive or on-demand)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3290) Incorrect WARN in DC log for remoting endpoint resource transformation to EAP 6
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-3290:
----------------------------------------
Summary: Incorrect WARN in DC log for remoting endpoint resource transformation to EAP 6
Key: WFCORE-3290
URL: https://issues.jboss.org/browse/WFCORE-3290
Project: WildFly Core
Issue Type: Bug
Components: Domain Management, Remoting
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Critical
When a slave running EAP 6 connects to a current DC, the following appears in the DC log even though the endpoint resource should be discarded:
{code}2017-08-07 14:35:09,000 WARN [org.jboss.as.controller.transformer.slave] (Host Controller Service Threads - 55) WFLYCTL0032: There were problems during the transformation process for target host: 'slave'
Problems found:
[ WFLYCTL0303: Resource [
("profile" => "full-ha"),
("subsystem" => "remoting"),
("configuration" => "endpoint")
] is rejected on the target host, and will need to be ignored on the host
]
{code}
This is because the remoting endpoint transformation was overly simplified in https://github.com/wildfly/wildfly-core/pull/2577
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3291) Incorrect WARN in DC log for remoting endpoint resource transformation to EAP 6
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-3291:
----------------------------------------
Summary: Incorrect WARN in DC log for remoting endpoint resource transformation to EAP 6
Key: WFCORE-3291
URL: https://issues.jboss.org/browse/WFCORE-3291
Project: WildFly Core
Issue Type: Bug
Components: Domain Management, Remoting
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Critical
When a slave running EAP 6 connects to a current DC, the following appears in the DC log even though the endpoint resource should be discarded:
{code}2017-08-07 14:35:09,000 WARN [org.jboss.as.controller.transformer.slave] (Host Controller Service Threads - 55) WFLYCTL0032: There were problems during the transformation process for target host: 'slave'
Problems found:
[ WFLYCTL0303: Resource [
("profile" => "full-ha"),
("subsystem" => "remoting"),
("configuration" => "endpoint")
] is rejected on the target host, and will need to be ignored on the host
]
{code}
This is because the remoting endpoint transformation was overly simplified in https://github.com/wildfly/wildfly-core/pull/2577
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9227) XA-Datasources not shown in admin console when using expressions (${some.thing}) in xml config
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-9227?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-9227:
--------------------------------------
Assignee: Harald Pehl (was: Brian Stansberry)
> XA-Datasources not shown in admin console when using expressions (${some.thing}) in xml config
> ----------------------------------------------------------------------------------------------
>
> Key: WFLY-9227
> URL: https://issues.jboss.org/browse/WFLY-9227
> Project: WildFly
> Issue Type: Bug
> Components: JCA, Web Console
> Affects Versions: 10.1.0.Final
> Reporter: Marius Schmidt
> Assignee: Harald Pehl
> Priority: Minor
>
> I expected the this to work, but I does not seem to:
> {noformat}
> GIVEN a Wildfly 10.1.0.Final subsystem datasources configuration as
> <subsystem xmlns="urn:jboss:domain:datasources:4.0">
> <datasources>
> <xa-datasource jndi-name="java:/datasources/SOURCE" pool-name="SOURCE" enabled="${source.db.enabled:false}">
> <xa-datasource-property name="URL">
> ${source.db.url:undefined}
> </xa-datasource-property>
> <driver>OracleJDBCDriver</driver>
> <xa-pool>
> <min-pool-size>0</min-pool-size>
> <max-pool-size>10</max-pool-size>
> <is-same-rm-override>false</is-same-rm-override>
> <no-tx-separate-pools>true</no-tx-separate-pools>
> </xa-pool>
> <security>
> <user-name>${source.db.user:user}</user-name>
> <password>${source.db.password:password}</password>
> </security>
> <recovery no-recovery="true"/>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker"/>
> <stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker"/>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"/>
> </validation>
> </xa-datasource>
> </datasources>
> <drivers>
> <driver name="h2" module="com.h2database.h2">
> <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
> </driver>
> <driver name="OracleJDBCDriver" module="com.oracle.ojdbc7">
> <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
> </driver>
> </drivers>
> </subsystem>
> AND a /full/path/to/file.properties file fitting a database connection, containing
> source.db.enabled=true
> source.db.url=jdbc:oracle:thin:@sample.de:1521:MY_SID
> source.db.user=USER
> source.db.password=PASSWORD
> WHEN the server is started with --properties=/full/path/to/file.properties
> THEN the webadmin console shows the xa-datasource SOURCE within the datasources subsytem
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9342) managed-executor-service does not create more than core-threads
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-9342?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-9342.
----------------------------------
Resolution: Rejected
Unfortunately this is the way that Java executors work. Threads will only be raised to max-threads if the queue is full. So in your case you would need to submit over 1000 tasks before it might start creating new threads.
Even though this is not very intuitive or useful it is how the JDK behaves.
> managed-executor-service does not create more than core-threads
> ---------------------------------------------------------------
>
> Key: WFLY-9342
> URL: https://issues.jboss.org/browse/WFLY-9342
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 11.0.0.CR1
> Environment: Fedora 25
> Reporter: Ravi Shankar Nori
>
> <managed-executor-service
> name="commandCoordinator"
> jndi-name="java:jboss/ee/concurrency/executor/commandCoordinator"
> core-threads="1"
> max-threads="10"
> queue-length="1000"
> />
> Creates only one executable thread, does not create additional threads when new tasks are submitted.
> Expected result: When new tasks are submitted more threads should be created capped by max-threads.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months