[JBoss JIRA] (WFCORE-3355) logging subsystem should skip if directories can't be listed
by Janine Eichler (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3355?page=com.atlassian.jira.plugi... ]
Janine Eichler updated WFCORE-3355:
-----------------------------------
Affects Version/s: 2.1.0.Final
> logging subsystem should skip if directories can't be listed
> ------------------------------------------------------------
>
> Key: WFCORE-3355
> URL: https://issues.jboss.org/browse/WFCORE-3355
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Logging
> Affects Versions: 2.1.0.Final, 3.0.5.Final
> Reporter: Janine Eichler
> Assignee: James Perkins
>
> Following condition:
> - a mounted volume within the jboss.log.dir
> - the mounted volume is an ext filesystem
> as a consequence a lost+found directory is automatically created, owned by root.root, permissions are 700.
> Now when you spin up a jboss instance, the logging directory is recursively scanned, due to the lost+found folder the logging subsystem throws the error https://github.com/wildfly/wildfly-core/blob/802d4dfcf58e24030d6c43ed2b01...
> using the cli or mgmt console to read the log is then not possible.
> it might be good to skip reading those files/directories and continue rather than throwing an error.
> i tested it using the EAP7 (so wildfly-logging-2.1.2-final-redhat.jar), but also built the 3.0.6-SNAPSHOT and used this jar in the logging subsystem to check whether it may have been already fixed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (JGRP-2223) Make DNS_PING more user-friendly
by Sebastian Łaskawiec (JIRA)
Sebastian Łaskawiec created JGRP-2223:
-----------------------------------------
Summary: Make DNS_PING more user-friendly
Key: JGRP-2223
URL: https://issues.jboss.org/browse/JGRP-2223
Project: JGroups
Issue Type: Enhancement
Affects Versions: 4.0.7
Reporter: Sebastian Łaskawiec
Assignee: Bela Ban
Priority: Minor
Currently the {{DNS_PING}} protocol is pretty hard to use. User needs to specify both DNS Server Address (which could be automatically discovered) and needs to specify {{svc.cluster.local}} suffix (which could be automatically added - if missing).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (JGRP-2223) Make DNS_PING more user-friendly
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/JGRP-2223?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec reassigned JGRP-2223:
-----------------------------------------
Assignee: Sebastian Łaskawiec (was: Bela Ban)
> Make DNS_PING more user-friendly
> --------------------------------
>
> Key: JGRP-2223
> URL: https://issues.jboss.org/browse/JGRP-2223
> Project: JGroups
> Issue Type: Enhancement
> Affects Versions: 4.0.7
> Reporter: Sebastian Łaskawiec
> Assignee: Sebastian Łaskawiec
> Priority: Minor
>
> Currently the {{DNS_PING}} protocol is pretty hard to use. User needs to specify both DNS Server Address (which could be automatically discovered) and needs to specify {{svc.cluster.local}} suffix (which could be automatically added - if missing).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (DROOLS-1760) Enhance test coverage of FEEL built-in functions part 2
by Tibor Zimányi (JIRA)
Tibor Zimányi created DROOLS-1760:
-------------------------------------
Summary: Enhance test coverage of FEEL built-in functions part 2
Key: DROOLS-1760
URL: https://issues.jboss.org/browse/DROOLS-1760
Project: Drools
Issue Type: Enhancement
Components: dmn engine
Affects Versions: 7.4.0.Final
Reporter: Tibor Zimányi
Assignee: Tibor Zimányi
Fix For: 7.5.0.Final
Add unit test coverage for function classes:
- SortFunction
- SubstringFunction
- SumFunction
- TimeFunction
- TodayFunction
- UnionFunction
- YearsAndMonthFunction
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-9427) JDBC_PING gets a NameNotFoundException when using jndi resource
by Alessandro Moscatelli (JIRA)
[ https://issues.jboss.org/browse/WFLY-9427?page=com.atlassian.jira.plugin.... ]
Alessandro Moscatelli closed WFLY-9427.
---------------------------------------
Resolution: Rejected
You were right, this is the right syntax :
<stack name="jdbc">
<transport type="TCP" socket-binding="jgroups-tcp">
<property name="external_addr">${env.EC2HOSTNAME}</property>
</transport>
{color:#d04437}<jdbc-protocol type="JDBC_PING" data-source="db_optoplus"/>{color}
<protocol type="MERGE3"/>
<protocol type="FD_SOCK">
<property name="external_addr">${env.EC2HOSTNAME}</property>
<property name="external_port">57600</property>
<property name="start_port">57600</property>
<property name="port_range">1</property>
</protocol>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
</stack>
When I tried it something went wrong, probably because I had a modified jgroups module to use the JDBC driver, I relaly don't know.
I removed the extra jgroups module, I retried the above configuration and it worked.
Thank you
> JDBC_PING gets a NameNotFoundException when using jndi resource
> ---------------------------------------------------------------
>
> Key: WFLY-9427
> URL: https://issues.jboss.org/browse/WFLY-9427
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.CR1
> Reporter: Alessandro Moscatelli
> Assignee: Radoslav Husar
> Fix For: 11.0.0.Final
>
>
> JDBC_PING if configured with jndi resources will cause :
> IllegalArgumentException: Could not lookup datasource
> NameNotFoundException
> IllegalStateException
> The same jndi resource is correctly found and used by a deployed application.
> It seems the jndi resouce is not ready, yet, when JGROUPS needs it.
> {quote}2017-10-09 17:32:48,695 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Final
> 2017-10-09 17:32:49,479 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1
> 2017-10-09 17:32:49,724 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: {color:#14892c}WildFly Full 11.0.0.CR1{color} (WildFly Core 3.0.1.Final) starting
> 2017-10-09 17:32:54,695 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-i
> nterface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 2017-10-09 17:32:54,758 INFO [org.wildfly.security] (ServerService Thread Pool -- 10) ELY00001: WildFly Elytron version 1.1.1.Final
> 2017-10-09 17:32:54,824 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 33) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=d
> efault-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecat
> ion.
> 2017-10-09 17:32:54,891 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 8) WFLYCTL0028: Attribute 'socket-binding' in the resource at address '/subsystem=jgroups/stack=jdbc
> /protocol=FD_SOCK' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 2017-10-09 17:32:55,665 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 27) WFLYDR0001: Content added at location /opt/wildfly/standalone/data/content/93/8e4c4a161a44fd84a305161a786cc43453d82b/c
> ontent
> 2017-10-09 17:32:55,727 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
> 2017-10-09 17:32:55,803 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.5.1.Final
> 2017-10-09 17:32:55,829 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.5.1.Final
> 2017-10-09 17:32:55,952 INFO [org.jboss.as.security] (ServerService Thread Pool -- 68) WFLYSEC0002: Activating Security Subsystem
> 2017-10-09 17:32:55,985 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 61) WFLYNAM0001: Activating Naming Subsystem
> 2017-10-09 17:32:56,008 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 49) WFLYIIOP0001: Activating IIOP Subsystem
> 2017-10-09 17:32:56,011 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 53) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 3.6.13
> 2017-10-09 17:32:56,017 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 72) WFLYWS0002: Activating WebServices Extension
> 2017-10-09 17:32:55,948 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 70) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for en
> vironments running multiple servers. Please make sure the attribute value is unique.
> 2017-10-09 17:32:55,965 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 56) WFLYJSF0007: Activated the following JSF Implementations: [main]
> 2017-10-09 17:32:56,029 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) WFLYCLINF0001: Activating Infinispan subsystem.
> 2017-10-09 17:32:55,980 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 50) WFLYRS0016: RESTEasy version 3.0.24.Final
> 2017-10-09 17:32:56,063 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 47) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available proc
> essors
> 2017-10-09 17:32:56,350 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.0.Final
> 2017-10-09 17:32:56,456 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.4.18.Final starting
> 2017-10-09 17:32:56,489 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=5.0.2.Final
> 2017-10-09 17:32:56,552 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.6.Final)
> 2017-10-09 17:32:56,806 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0004: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 12.1)
> 2017-10-09 17:32:56,794 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
> 2017-10-09 17:32:56,844 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
> 2017-10-09 17:32:56,935 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 6.0)
> 2017-10-09 17:32:56,962 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
> 2017-10-09 17:32:57,452 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs
> on this host.
> 2017-10-09 17:32:57,467 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker poo
> l sizing.
> 2017-10-09 17:32:57,556 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 71) WFLYUT0014: Creating file handler for path '/opt/wildfly/welcome-content' with options [directory-listing: 'fal
> se', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
> 2017-10-09 17:32:57,732 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = oracle
> 2017-10-09 17:32:58,002 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = mysql
> 2017-10-09 17:32:58,020 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
> 2017-10-09 17:32:59,265 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
> 2017-10-09 17:32:59,495 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
> 2017-10-09 17:32:59,609 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8180
> 2017-10-09 17:32:59,623 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow AJP listener ajp listening on 0.0.0.0:8109
> 2017-10-09 17:32:59,682 INFO [org.jboss.as.patching] (MSC service thread 1-2) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
> 2017-10-09 17:32:59,703 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started
> 2017-10-09 17:32:59,716 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 74) MODCLUSTER000001: Initializing mod_cluster version 1.3.7.Final
> 2017-10-09 17:32:59,738 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 74) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
> 2017-10-09 17:32:59,749 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore /opt/wildfly/standalone/configuration/application.keystore not found, it will be auto gene
> rated on first use with a self signed certificate for host localhost
> 2017-10-09 17:32:59,775 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/wildfly/standalone/deployments
> 2017-10-09 17:32:59,801 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "OptoPlusServices-ear-1.0.0.ear" (runtime-name: "OptoPlusServices-ear-1.0.0.ear")
> 2017-10-09 17:32:59,825 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0493: EJB subsystem suspension complete
> 2017-10-09 17:33:00,546 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8543
> 2017-10-09 17:33:01,121 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 74) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException
> in service org.wildfly.clustering.jgroups.channel.ee: java.lang.IllegalArgumentException: Could not lookup datasource java:/jdbc/db_optoplus
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:104)
> at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99)
> 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)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.lang.IllegalArgumentException: Could not lookup datasource java:/jdbc/db_optoplus
> at org.jgroups.protocols.JDBC_PING.getDataSourceFromJNDI(JDBC_PING.java:436)
> at org.jgroups.protocols.JDBC_PING.init(JDBC_PING.java:129)
> at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861)
> at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:831)
> at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:108)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:102)
> ... 5 more
> Caused by: {color:#d04437}javax.naming.NameNotFoundException: jdbc/db_optoplus [Root exception is java.lang.IllegalStateException]
> {color} at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:153)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at org.jgroups.protocols.JDBC_PING.getDataSourceFromJNDI(JDBC_PING.java:423)
> ... 10 more
> Caused by: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:142)
> at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:46)
> at org.jboss.msc.service.ServiceControllerImpl.getValue(ServiceControllerImpl.java:1158)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:131)
> ... 18 more
> 2017-10-09 17:33:01,294 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
> 2017-10-09 17:33:01,303 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
> 2017-10-09 17:33:01,304 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: {color:#d04437}Bound data source [java:/jdbc/db_optoplus{color}]
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-9336) Extend security context propagation test coverage
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-9336?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas updated WFLY-9336:
-------------------------------
Description:
Extend security context propagation test coverage:
* add servlet-to-ejb credential propagation scenarios (BASIC, FORM, BEARER)
* add tests for manual credentials retrieving (use in *-to-servlet scenarios)
* credential-less propagation
* clustered scenarios for authorization forwarding
* sequence of more authentication/authorization forwarding mode calls
* exception propagation to previous server
* negative scenario for credentials not being accessible on forwarded server after authorization forwarding
* identity switching on one remote connection for
** authentication and authorization switching
** authorization and different authorization switching
was:
Extend security context propagation test coverage:
* add servlet-to-ejb credential propagation scenarios (BASIC, FORM, BEARER)
* add tests for manual credentials retrieving (use in *-to-servlet scenarios)
* credential-less propagation
> Extend security context propagation test coverage
> -------------------------------------------------
>
> Key: WFLY-9336
> URL: https://issues.jboss.org/browse/WFLY-9336
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Josef Cacek
> Assignee: Josef Cacek
> Priority: Critical
>
> Extend security context propagation test coverage:
> * add servlet-to-ejb credential propagation scenarios (BASIC, FORM, BEARER)
> * add tests for manual credentials retrieving (use in *-to-servlet scenarios)
> * credential-less propagation
> * clustered scenarios for authorization forwarding
> * sequence of more authentication/authorization forwarding mode calls
> * exception propagation to previous server
> * negative scenario for credentials not being accessible on forwarded server after authorization forwarding
> * identity switching on one remote connection for
> ** authentication and authorization switching
> ** authorization and different authorization switching
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months