[JBoss JIRA] (DROOLS-3715) Zipkiemodule nullpointerexception
by Tibor Zimányi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3715?page=com.atlassian.jira.plugi... ]
Tibor Zimányi updated DROOLS-3715:
----------------------------------
Sprint: 2019 Week 11-13 (was: 2019 Week 08-10)
> Zipkiemodule nullpointerexception
> ---------------------------------
>
> Key: DROOLS-3715
> URL: https://issues.jboss.org/browse/DROOLS-3715
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.16.0.Final, 7.17.0.Final
> Reporter: Łukasz Szmolke
> Assignee: Tibor Zimányi
> Priority: Major
>
> o During ZipKieModule loading in “org.drools.compiler.kie.builder.impl.ZipKieModule:142” nullpointerexception is thrown:
>
> urlPath = urlPath.substring( urlPath.lastIndexOf( '!' ) + 1 );
> ArrayList<ZipEntry> entries = new ArrayList<>();
> // read jar file from uber-jar
> InputStream in = this.getClass().getResourceAsStream(urlPath); // nullpointerexception
>
> For example full UrlPath on windows to internal .jar is:
> C:\Users\xbbnv0c\IdeaProjects\ais-data-exchange\data-exchange-app\target\data-exchange-app-1.0.1-SNAPSHOT.jar!\BOOT-INF\lib\data-exchange-brms-1.0.1-SNAPSHOT.jar
> So the result of this first line will be:
> \BOOT-INF\lib\data-exchange-brms-1.0.1-SNAPSHOT.jar
> It will be perfect, but during accessing internal resource file separator should be “/” not “\”. So InputStream in = null.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11827) Broken validation for pooled-connection-factory's transaction attribute.
by Petr Kremensky (Jira)
[ https://issues.jboss.org/browse/WFLY-11827?page=com.atlassian.jira.plugin... ]
Petr Kremensky commented on WFLY-11827:
---------------------------------------
_equals()_ should be used instead of _==_ here. This should solve the 1)
https://github.com/wildfly/wildfly/blob/master/messaging-activemq/src/mai...
> Broken validation for pooled-connection-factory's transaction attribute.
> -------------------------------------------------------------------------
>
> Key: WFLY-11827
> URL: https://issues.jboss.org/browse/WFLY-11827
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 16.0.0.Final
> Reporter: Petr Kremensky
> Assignee: Chao Wang
> Priority: Major
>
> The issue was introduced by https://issues.jboss.org/browse/WFLY-11617 Validation not working for pooled-connection-factory's transaction attribute.
> *1) Starting Wildfly with _full_ profile gives now a WARN log, although the value for the transaction attribute is valid.*
> *2) Writing the invalid value to the attribute should fail the management operation.*
> Starting vanilla server:
> {noformat}
> 09:19:00,578 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 18) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
> {noformat}
> Write operation:
> {noformat}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=xa)
> 09:31:21,542 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 2) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=invalid)
> 09:33:52,278 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value invalid for transaction, legal values are [local, none, xa], default value is applied.
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-attribute(name=transaction)
> {
> "outcome" => "success",
> "result" => "xa"
> }
> {noformat}
> Start (not reload, reload gives a single warning) server with invalid value logs two warnings:
> {noformat}
> ...
> 09:35:37,737 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) starting
> 09:35:38,481 INFO [org.wildfly.security] (ServerService Thread Pool -- 15) ELY00001: WildFly Elytron version 1.8.0.Final
> 09:35:38,688 WARN [org.wildfly.extension.messaging-activemq] (Controller Boot Thread) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are ["local", "none", "xa"], default value is applied.
> 09:35:38,945 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 09:35:38,979 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 7) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are [local, none, xa], default value is applied.
> 09:35:38,980 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 38) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> ...
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (DROOLS-3205) [DMN Designer][IE11] Missing Structure option
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3205?page=com.atlassian.jira.plugi... ]
Jozef Marko closed DROOLS-3205.
-------------------------------
Fix Version/s: 7.19.0.Final
Resolution: Done
Not reproducible after RHDM-869 fix.
> [DMN Designer][IE11] Missing Structure option
> ---------------------------------------------
>
> Key: DROOLS-3205
> URL: https://issues.jboss.org/browse/DROOLS-3205
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Minor
> Labels: drools-tools
> Fix For: 7.19.0.Final
>
> Attachments: Screenshot from 2018-10-30 09-09-52.png
>
>
> The *manage custom data type* dialog misses the *Structure* option for the IE11, see the attached screenshot. Other browsers works fine.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11827) Broken validation for pooled-connection-factory's transaction attribute.
by Petr Kremensky (Jira)
[ https://issues.jboss.org/browse/WFLY-11827?page=com.atlassian.jira.plugin... ]
Petr Kremensky updated WFLY-11827:
----------------------------------
Description:
The issue was introduced by https://issues.jboss.org/browse/WFLY-11617 Validation not working for pooled-connection-factory's transaction attribute.
*1) Starting Wildfly with _full_ profile gives now a WARN log, although the value for the transaction attribute is valid.*
*2) Writing the invalid value to the attribute should fail the management operation.*
Starting vanilla server:
{noformat}
09:19:00,578 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 18) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
{noformat}
Write operation:
{noformat}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=xa)
09:31:21,542 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 2) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=invalid)
09:33:52,278 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value invalid for transaction, legal values are [local, none, xa], default value is applied.
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-attribute(name=transaction)
{
"outcome" => "success",
"result" => "xa"
}
{noformat}
Start (not reload, reload gives a single warning) server with invalid value logs two warnings:
{noformat}
...
09:35:37,737 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) starting
09:35:38,481 INFO [org.wildfly.security] (ServerService Thread Pool -- 15) ELY00001: WildFly Elytron version 1.8.0.Final
09:35:38,688 WARN [org.wildfly.extension.messaging-activemq] (Controller Boot Thread) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are ["local", "none", "xa"], default value is applied.
09:35:38,945 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
09:35:38,979 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 7) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are [local, none, xa], default value is applied.
09:35:38,980 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 38) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
...
{noformat}
was:
The issue was introduced by https://issues.jboss.org/browse/WFLY-11617 Validation not working for pooled-connection-factory's transaction attribute.
1) Starting Wildfly with *full* profile gives now a WARN log, although the value for the transaction attribute is valid.
2) Writing the invalid value to the attribute should fail the management operation.
Starting vanilla server:
{noformat}
09:19:00,578 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 18) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
{noformat}
Write operation:
{noformat}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=xa)
09:31:21,542 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 2) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=invalid)
09:33:52,278 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value invalid for transaction, legal values are [local, none, xa], default value is applied.
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-attribute(name=transaction)
{
"outcome" => "success",
"result" => "xa"
}
{noformat}
Start (not reload, reload gives a single warning) server with invalid value logs two warnings:
{noformat}
...
09:35:37,737 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) starting
09:35:38,481 INFO [org.wildfly.security] (ServerService Thread Pool -- 15) ELY00001: WildFly Elytron version 1.8.0.Final
09:35:38,688 WARN [org.wildfly.extension.messaging-activemq] (Controller Boot Thread) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are ["local", "none", "xa"], default value is applied.
09:35:38,945 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
09:35:38,979 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 7) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are [local, none, xa], default value is applied.
09:35:38,980 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 38) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
...
{noformat}
> Broken validation for pooled-connection-factory's transaction attribute.
> -------------------------------------------------------------------------
>
> Key: WFLY-11827
> URL: https://issues.jboss.org/browse/WFLY-11827
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 16.0.0.Final
> Reporter: Petr Kremensky
> Assignee: Chao Wang
> Priority: Major
>
> The issue was introduced by https://issues.jboss.org/browse/WFLY-11617 Validation not working for pooled-connection-factory's transaction attribute.
> *1) Starting Wildfly with _full_ profile gives now a WARN log, although the value for the transaction attribute is valid.*
> *2) Writing the invalid value to the attribute should fail the management operation.*
> Starting vanilla server:
> {noformat}
> 09:19:00,578 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 18) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
> {noformat}
> Write operation:
> {noformat}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=xa)
> 09:31:21,542 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 2) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=invalid)
> 09:33:52,278 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value invalid for transaction, legal values are [local, none, xa], default value is applied.
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-attribute(name=transaction)
> {
> "outcome" => "success",
> "result" => "xa"
> }
> {noformat}
> Start (not reload, reload gives a single warning) server with invalid value logs two warnings:
> {noformat}
> ...
> 09:35:37,737 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) starting
> 09:35:38,481 INFO [org.wildfly.security] (ServerService Thread Pool -- 15) ELY00001: WildFly Elytron version 1.8.0.Final
> 09:35:38,688 WARN [org.wildfly.extension.messaging-activemq] (Controller Boot Thread) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are ["local", "none", "xa"], default value is applied.
> 09:35:38,945 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 09:35:38,979 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 7) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are [local, none, xa], default value is applied.
> 09:35:38,980 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 38) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> ...
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11827) Broken validation for pooled-connection-factory's transaction attribute.
by Petr Kremensky (Jira)
Petr Kremensky created WFLY-11827:
-------------------------------------
Summary: Broken validation for pooled-connection-factory's transaction attribute.
Key: WFLY-11827
URL: https://issues.jboss.org/browse/WFLY-11827
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 16.0.0.Final
Reporter: Petr Kremensky
Assignee: Chao Wang
The issue was introduced by https://issues.jboss.org/browse/WFLY-11617 Validation not working for pooled-connection-factory's transaction attribute.
1) Starting Wildfly with *full* profile gives now a WARN log, although the value for the transaction attribute is valid.
2) Writing the invalid value to the attribute should fail the management operation.
Starting vanilla server:
{noformat}
09:19:00,578 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 18) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
{noformat}
Write operation:
{noformat}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=xa)
09:31:21,542 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 2) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=invalid)
09:33:52,278 WARN [org.wildfly.extension.messaging-activemq] (management-handler-thread - 1) WFLYMSGAMQ0101: Invalid value invalid for transaction, legal values are [local, none, xa], default value is applied.
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:read-attribute(name=transaction)
{
"outcome" => "success",
"result" => "xa"
}
{noformat}
Start (not reload, reload gives a single warning) server with invalid value logs two warnings:
{noformat}
...
09:35:37,737 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) starting
09:35:38,481 INFO [org.wildfly.security] (ServerService Thread Pool -- 15) ELY00001: WildFly Elytron version 1.8.0.Final
09:35:38,688 WARN [org.wildfly.extension.messaging-activemq] (Controller Boot Thread) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are ["local", "none", "xa"], default value is applied.
09:35:38,945 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
09:35:38,979 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 7) WFLYMSGAMQ0101: Invalid value foo for transaction, legal values are [local, none, xa], default value is applied.
09:35:38,980 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 38) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
...
{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (JGRP-2316) DNS_PING is not using correct ports with SRV based service discovery
by Sebastian Łaskawiec (Jira)
[ https://issues.jboss.org/browse/JGRP-2316?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec commented on JGRP-2316:
-------------------------------------------
[~ethompson] Could you please provide us some details on your deployment? At least we would need to know the {{dig}} command result and have some debug logs from {{org.jgroups}} category.
> DNS_PING is not using correct ports with SRV based service discovery
> --------------------------------------------------------------------
>
> Key: JGRP-2316
> URL: https://issues.jboss.org/browse/JGRP-2316
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.15
> Reporter: dmcnair
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.0.16
>
>
> This is a follow-up to JGRP-2296 - which changed `DefaultDNSResolver.java` to preserve the port for SRV records. While that change is working as desired, `DNS_PING.java` is not using the port when doing member discovery.
> Here are the log entries using *4.0.15*
> {noformat}
> 2018-11-29 21:37:41,561 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-4,null,null) Entries collected from DNS (in 5 ms): [172.29.11.50:27106, 172.29.11.50:27105]
> 2018-11-29 21:37:41,562 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-4,null,null) 982d38761cba: sending discovery requests to hosts [172.29.11.50:27106, 172.29.11.50:27105] on ports [7600 .. 7600]
> {noformat}
> Since the port was found via the SRV record, it should be used instead of the *transportPort* port.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-10584) Timer repeats uncontrolled
by Tomasz Adamski (Jira)
[ https://issues.jboss.org/browse/WFLY-10584?page=com.atlassian.jira.plugin... ]
Tomasz Adamski reassigned WFLY-10584:
-------------------------------------
Assignee: Tomasz Adamski (was: Jörg Bäsner)
> Timer repeats uncontrolled
> --------------------------
>
> Key: WFLY-10584
> URL: https://issues.jboss.org/browse/WFLY-10584
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 13.0.0.Final
> Reporter: Jörg Bäsner
> Assignee: Tomasz Adamski
> Priority: Major
> Attachments: playground-jar.jar
>
>
> Given an hourly timer like this:
> {code}
> @Schedule(hour = "*", persistent = false)
> public void hourlyTimer(Timer timer) {
> long methodEntryTime = System.currentTimeMillis();
> ZonedDateTime nextTimeout = ZonedDateTime.ofInstant(timer.getNextTimeout().toInstant(),
> ZoneId.systemDefault());
> logger.info("Call to hourly maintenance function completed in {} seconds, next timeout at {}",
> millis2secondsString(System.currentTimeMillis() - methodEntryTime), nextTimeout);
> }
> {code}
> Results in the Timezone [Europe/Helsinki] on the 24th or March 2018 at 23:00:00 LocalTime in a next trigger of the same, see:
> {noformat}
> 23:00:01,997 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 1) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:01,998 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 6) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:02,000 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> 23:00:02,001 INFO [org.jboss.playground.PlaygroundAutoTimerBean] (EJB default - 7) Call to hourly maintenance function completed in 0 seconds, next timeout at 2018-03-24T23:00+02:00[Europe/Helsinki]
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-9881) UnsatisfiedLinkError - Open CV
by Tomasz Adamski (Jira)
[ https://issues.jboss.org/browse/WFLY-9881?page=com.atlassian.jira.plugin.... ]
Tomasz Adamski reassigned WFLY-9881:
------------------------------------
Assignee: Tomasz Adamski (was: Jason Greene)
> UnsatisfiedLinkError - Open CV
> --------------------------------
>
> Key: WFLY-9881
> URL: https://issues.jboss.org/browse/WFLY-9881
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 11.0.0.Final
> Environment: Windows Server 2012 R2 \ Windows 8.1 Professional, 64 bit JRE\JDK 8 update 112
> OpenCV 3.3.0 (https://github.com/opencv/opencv/releases/tag/3.3.0)
> Reporter: Richard Cannock
> Assignee: Tomasz Adamski
> Priority: Major
>
> Deploying a simple Stateless session bean with a single get method that has a dependency on OpenCV release 3.3.0 (opencv-330.jar) and it's corresponding 64 bit native library (opencv_java330.dll) from https://github.com/opencv/opencv/releases/tag/3.3.0
> results in a UnsatisfiedLinkError:
> Caused by: java.lang.UnsatisfiedLinkError: org.opencv.core.Mat.n_eye(III)J
> at org.opencv.core.Mat.n_eye(Native Method)
> at org.opencv.core.Mat.eye(Mat.java:492)
> at test.SimpleJMSRestfulWebService.putMessage(SimpleJMSRestfulWebService.java:57)
> The sample get method is shown below:
> package test;
> import javax.ejb.Stateless;
> import javax.ws.rs.GET;
> import javax.ws.rs.Path;
> import org.opencv.core.Core;
> import org.opencv.core.CvType;
> import org.opencv.core.Mat;
> /**
> *
> */
> @Stateless
> @Path("/jms")
> public class SimpleJMSRestfulWebService
> {
> /**
> * Our RESTful webservice
> */
> @GET
> public String putMessage()
> {
> System.loadLibrary(Core.NATIVE_LIBRARY_NAME);
> Mat mat = Mat.eye(3, 3, CvType.CV_8UC1);
> System.out.println("mat = " + mat.dump());
> return "works";
> }
> }
> The native library is placed in C:\Windows, which is in the java.library.path system variable.
> Same code runs without exception in GlassFish Server 4.1 and also within netbeans 8.2 (albeit in a differnet test harness)
> Using -Djava.library.path VM argumnents using a different path for the native library also causes the same error.in wildfly.
> Removing the library from C:\Windows causes a different stack trace, which suggests that wildfly is at least partially loading the library:
> Caused by: java.lang.UnsatisfiedLinkError: no opencv_java330 in java.library.path
> at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1867)
> at java.lang.Runtime.loadLibrary0(Runtime.java:870)
> at java.lang.System.loadLibrary(System.java:1122)
> Using depends.exe or dependency walker on opencv_java330.dll reports no unsatisfied dependencies for this dll.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months