[JBoss JIRA] (SWSQE-963) OCP 4.2 provisioning fails with Error creating OpenStack container object
by Filip Brychta (Jira)
[ https://issues.jboss.org/browse/SWSQE-963?page=com.atlassian.jira.plugin.... ]
Filip Brychta commented on SWSQE-963:
-------------------------------------
Created https://redhat.service-now.com/surl.do?n=PNT0672701
> OCP 4.2 provisioning fails with Error creating OpenStack container object
> -------------------------------------------------------------------------
>
> Key: SWSQE-963
> URL: https://issues.jboss.org/browse/SWSQE-963
> Project: Kiali QE
> Issue Type: Bug
> Reporter: Filip Brychta
> Assignee: Filip Brychta
> Priority: Blocker
> Labels: infrastructure
>
> Full exception:
> level=debug msg="module.masters.openstack_compute_instance_v2.master_conf[0]: Still creating... [1m0s elapsed]"
> level=debug msg="module.masters.openstack_compute_instance_v2.master_conf[0]: Creation complete after 1m7s [id=440a6c32-ef73-4bbf-9ea9-1cdade8314d0]"
> level=error
> level=error msg="Error: Error creating OpenStack container object: Expected HTTP response code [] when accessing [PUT https://rhos-d.infra.prod.upshift.rdu2.redhat.com:13808/v1/AUTH_0d9514d7d...], but got 413 instead"
> level=error msg="Upload exceeds quota."
> level=error
> level=error msg=" on ../../../../../../../tmp/openshift-install-535787086/bootstrap/main.tf line 49, in resource \"openstack_objectstorage_object_v1\" \"ignition\":"
> level=error msg=" 49: resource \"openstack_objectstorage_object_v1\" \"ignition\" {"
> level=error
> level=error
> level=fatal msg="failed to fetch Cluster: failed to generate asset \"Cluster\": failed to create cluster: failed to apply using Terraform"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 7 months
[JBoss JIRA] (SWSQE-963) OCP 4.2 provisioning fails with Error creating OpenStack container object
by Filip Brychta (Jira)
Filip Brychta created SWSQE-963:
-----------------------------------
Summary: OCP 4.2 provisioning fails with Error creating OpenStack container object
Key: SWSQE-963
URL: https://issues.jboss.org/browse/SWSQE-963
Project: Kiali QE
Issue Type: Bug
Reporter: Filip Brychta
Assignee: Filip Brychta
Full exception:
level=debug msg="module.masters.openstack_compute_instance_v2.master_conf[0]: Still creating... [1m0s elapsed]"
level=debug msg="module.masters.openstack_compute_instance_v2.master_conf[0]: Creation complete after 1m7s [id=440a6c32-ef73-4bbf-9ea9-1cdade8314d0]"
level=error
level=error msg="Error: Error creating OpenStack container object: Expected HTTP response code [] when accessing [PUT https://rhos-d.infra.prod.upshift.rdu2.redhat.com:13808/v1/AUTH_0d9514d7d...], but got 413 instead"
level=error msg="Upload exceeds quota."
level=error
level=error msg=" on ../../../../../../../tmp/openshift-install-535787086/bootstrap/main.tf line 49, in resource \"openstack_objectstorage_object_v1\" \"ignition\":"
level=error msg=" 49: resource \"openstack_objectstorage_object_v1\" \"ignition\" {"
level=error
level=error
level=fatal msg="failed to fetch Cluster: failed to generate asset \"Cluster\": failed to create cluster: failed to apply using Terraform"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 7 months
[JBoss JIRA] (DROOLS-4604) Query code generation neglects query parameter(s)
by IVAN ZILOTTI (Jira)
[ https://issues.jboss.org/browse/DROOLS-4604?page=com.atlassian.jira.plugi... ]
IVAN ZILOTTI updated DROOLS-4604:
---------------------------------
Priority: Blocker (was: Major)
> Query code generation neglects query parameter(s)
> -------------------------------------------------
>
> Key: DROOLS-4604
> URL: https://issues.jboss.org/browse/DROOLS-4604
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.27.0.Final
> Reporter: IVAN ZILOTTI
> Assignee: Mario Fusco
> Priority: Blocker
>
> The Drools _query_ code generated by the test method below is not including the query parameter ({{String eventId}}) specified via {{PackageDescrBuilder}}.
> Note that parameters to Drools _functions_ constructed through the same process are correctly included. See _org.drools.compiler.lang.api.DescrBuilderTest#testFunctions_.
>
> h3. Generated code
> {code:java}
> package org.test.rules
> import org.test.event.TemporalEvent
> query "getTemporalEventById"
> TemporalEvent( id == eventId ) from entry-point "TemporalEventStream"
> end
> {code}
> h3. Test
> {code:java}
> @Test
> public void testFluentQuery() {
> PackageDescrBuilder packBuilder =
> DescrFactory.newPackage()
> .name("org.test.rules")
> .newImport()
> .target("org.test.event.TemporalEvent")
> .end()
> .newQuery()
> .name("getTemporalEventById")
> .parameter("String", "eventId")
> .lhs()
> .pattern( "TemporalEvent")
> .constraint("id == eventId")
> .from()
> .entryPoint("EventStream")
> .end()
> .end()
> .end()
> .end();
> String query = new DrlDumper().dump(packBuilder.getDescr());
> System.out.println(query);
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 7 months
[JBoss JIRA] (WFLY-12535) Container does not pass the beanManager when creating eclipselink EntityManagerFactory
by Scott Marlow (Jira)
[ https://issues.jboss.org/browse/WFLY-12535?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-12535:
-------------------------------------
I added a println to the WildFly JPA container createContainerEntityManagerFactory() call and confirmed your correct, output from a unit test run with EclipseLink:
{quote}
calling createContainerEntityManagerFactory for pu=toplink_module_test.ear#hibernate3_pc with:
integration properties={
eclipselink.logging.logger=org.jipijapa.eclipselink.JBossLogger,
eclipselink.archive.factory=org.jipijapa.eclipselink.JBossArchiveFactoryImpl,
eclipselink.target-server=org.jipijapa.eclipselink.WildFlyServerPlatform
}
{quote}
> Container does not pass the beanManager when creating eclipselink EntityManagerFactory
> --------------------------------------------------------------------------------------
>
> Key: WFLY-12535
> URL: https://issues.jboss.org/browse/WFLY-12535
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 16.0.0.Final
> Reporter: charles ghislain
> Assignee: Scott Marlow
> Priority: Major
>
> When creating the entity manager factory for eclipseliknk using `javax.persistence.spi.PersistenceProvider#createContainerEntityManagerFactory`, wildfly does not pass the properties required by the jee8 spec, as specified in the javadoc of this method:
> {code}
> If a Bean Validation provider is present in the classpath, the container must pass the ValidatorFactory instance in the map with the key "javax.persistence.validation.factory". If the containing archive is a bean archive, the container must pass the BeanManager instance in the map with the key "javax.persistence.bean.manager"
> {code}
> Debugging the eclipselink implementation of this method, `org.eclipse.persistence.jpa.PersistenceProvider#createContainerEntityManagerFactory`, the properties set by the container contains the following 3 entries:
> {code:java}
> eclipselink.logging.logger -> org.jipijapa.eclipselink.JBossLogger
> eclipselink.archive.factory -> org.jipijapa.eclipselink.JBossArchiveFactoryImpl
> eclipselink.target-server -> org.jipijapa.eclipselink.WildFlyServerPlatform
> {code}
> I think this prevents CDI injection in custom ConstraintValidators, as mentionned on an old eclipselink thread: https://www.eclipse.org/lists/eclipselink-users/msg08503.html.
> I have a `ConstraintValidator` with an `@Inject`ed EJB, but when validation is triggered on the call to `javax.persistence.EntityManager#merge`, the injected field is null.
> The wildfly installation has been updated to include eclipselink as per documentation:
> the org.eclipse.persistence module has been updated to include the eclipselink jar with the following descriptor:
> {code:java}
> <module xmlns="urn:jboss:module:1.1" name="org.eclipse.persistence">
> <resources>
> <!-- jipijapa line is kept from the original module -->
> <resource-root path="eclipselink.jar">
> <filter>
> <exclude path="javax/**" />
> </filter>
> </resource-root>
> </resources>
> <dependencies>
> <module name="asm.asm"/>
> <module name="javax.api"/>
> <module name="javax.annotation.api"/>
> <module name="javax.enterprise.api"/>
> <module name="javax.persistence.api"/>
> <module name="javax.transaction.api"/>
> <module name="javax.validation.api"/>
> <module name="javax.xml.bind.api"/>
> <module name="javax.ws.rs.api"/>
> <module name="org.antlr"/>
> <module name="org.apache.commons.collections"/>
> <module name="org.dom4j"/>
> <module name="org.jboss.as.jpa.spi"/>
> <module name="org.jboss.logging"/>
> <module name="org.jboss.vfs"/>
> </dependencies>
> </module>
> {code}
> The persistence unit provider has been set to `org.eclipse.persistence.jpa.PersistenceProvider` in the persistence.xml file.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 7 months
[JBoss JIRA] (WFLY-12535) Container does not pass the beanManager when creating eclipselink EntityManagerFactory
by Scott Marlow (Jira)
[ https://issues.jboss.org/browse/WFLY-12535?page=com.atlassian.jira.plugin... ]
Scott Marlow edited comment on WFLY-12535 at 10/4/19 2:02 PM:
--------------------------------------------------------------
I added a println to the WildFly JPA container createContainerEntityManagerFactory() call and confirmed your correct, output from a unit test run with EclipseLink:
{code}
calling createContainerEntityManagerFactory for pu=toplink_module_test.ear#hibernate3_pc with:
integration properties={
eclipselink.logging.logger=org.jipijapa.eclipselink.JBossLogger,
eclipselink.archive.factory=org.jipijapa.eclipselink.JBossArchiveFactoryImpl,
eclipselink.target-server=org.jipijapa.eclipselink.WildFlyServerPlatform
}
{code}
was (Author: smarlow):
I added a println to the WildFly JPA container createContainerEntityManagerFactory() call and confirmed your correct, output from a unit test run with EclipseLink:
{quote}
calling createContainerEntityManagerFactory for pu=toplink_module_test.ear#hibernate3_pc with:
integration properties={
eclipselink.logging.logger=org.jipijapa.eclipselink.JBossLogger,
eclipselink.archive.factory=org.jipijapa.eclipselink.JBossArchiveFactoryImpl,
eclipselink.target-server=org.jipijapa.eclipselink.WildFlyServerPlatform
}
{quote}
> Container does not pass the beanManager when creating eclipselink EntityManagerFactory
> --------------------------------------------------------------------------------------
>
> Key: WFLY-12535
> URL: https://issues.jboss.org/browse/WFLY-12535
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 16.0.0.Final
> Reporter: charles ghislain
> Assignee: Scott Marlow
> Priority: Major
>
> When creating the entity manager factory for eclipseliknk using `javax.persistence.spi.PersistenceProvider#createContainerEntityManagerFactory`, wildfly does not pass the properties required by the jee8 spec, as specified in the javadoc of this method:
> {code}
> If a Bean Validation provider is present in the classpath, the container must pass the ValidatorFactory instance in the map with the key "javax.persistence.validation.factory". If the containing archive is a bean archive, the container must pass the BeanManager instance in the map with the key "javax.persistence.bean.manager"
> {code}
> Debugging the eclipselink implementation of this method, `org.eclipse.persistence.jpa.PersistenceProvider#createContainerEntityManagerFactory`, the properties set by the container contains the following 3 entries:
> {code:java}
> eclipselink.logging.logger -> org.jipijapa.eclipselink.JBossLogger
> eclipselink.archive.factory -> org.jipijapa.eclipselink.JBossArchiveFactoryImpl
> eclipselink.target-server -> org.jipijapa.eclipselink.WildFlyServerPlatform
> {code}
> I think this prevents CDI injection in custom ConstraintValidators, as mentionned on an old eclipselink thread: https://www.eclipse.org/lists/eclipselink-users/msg08503.html.
> I have a `ConstraintValidator` with an `@Inject`ed EJB, but when validation is triggered on the call to `javax.persistence.EntityManager#merge`, the injected field is null.
> The wildfly installation has been updated to include eclipselink as per documentation:
> the org.eclipse.persistence module has been updated to include the eclipselink jar with the following descriptor:
> {code:java}
> <module xmlns="urn:jboss:module:1.1" name="org.eclipse.persistence">
> <resources>
> <!-- jipijapa line is kept from the original module -->
> <resource-root path="eclipselink.jar">
> <filter>
> <exclude path="javax/**" />
> </filter>
> </resource-root>
> </resources>
> <dependencies>
> <module name="asm.asm"/>
> <module name="javax.api"/>
> <module name="javax.annotation.api"/>
> <module name="javax.enterprise.api"/>
> <module name="javax.persistence.api"/>
> <module name="javax.transaction.api"/>
> <module name="javax.validation.api"/>
> <module name="javax.xml.bind.api"/>
> <module name="javax.ws.rs.api"/>
> <module name="org.antlr"/>
> <module name="org.apache.commons.collections"/>
> <module name="org.dom4j"/>
> <module name="org.jboss.as.jpa.spi"/>
> <module name="org.jboss.logging"/>
> <module name="org.jboss.vfs"/>
> </dependencies>
> </module>
> {code}
> The persistence unit provider has been set to `org.eclipse.persistence.jpa.PersistenceProvider` in the persistence.xml file.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 7 months
[JBoss JIRA] (WFCORE-4703) Add log4j2 support for WildFly
by James Perkins (Jira)
James Perkins created WFCORE-4703:
-------------------------------------
Summary: Add log4j2 support for WildFly
Key: WFCORE-4703
URL: https://issues.jboss.org/browse/WFCORE-4703
Project: WildFly Core
Issue Type: Task
Components: Logging
Environment: Spring 3, Hibernate, Wicket, JBoss AS7
Reporter: Amarkanth Ranganamayna
Assignee: James Perkins
I am trying to use Flume Appender which comes with Log4j2 (log4j 1.x doesn't support flume appender) (AND) inorder to acheive this, I am looking at how to configure JBoss AS7 to use log4j2.
Looks like Jboss AS7 by default use log4j 1.x
Are you guys already working on using log4j2 ?
If NOT, can you please suggest how to configure Jboss AS7 such that it picks up "log4j2.xml" file and doesn't use its own logging.
Thanks,
Amar
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 7 months
[JBoss JIRA] (WFWIP-229) Configuring JGroups encryption protocols produces deprecated configuration
by Yeray Borges (Jira)
[ https://issues.jboss.org/browse/WFWIP-229?page=com.atlassian.jira.plugin.... ]
Yeray Borges commented on WFWIP-229:
------------------------------------
Hi [~mjurc], in my opinion, this issue should be resolved as rejected because there is a non-deprecated version of ASYM_ENCRYPT protocol when the cluster security is not managed by Elytron. I tested the Elytron variant, and I successfully see the non-deprecated version added to the stack.
Using docker you could try with the following configuration:
{noformat}
-e JGROUPS_ENCRYPT_PROTOCOL="SYM_ENCRYPT" \
-e JGROUPS_ENCRYPT_SECRET="encrypt_secret" \
-e JGROUPS_ENCRYPT_NAME="encrypt_name" \
-e JGROUPS_ENCRYPT_PASSWORD="encrypt_password" \
-e JGROUPS_ENCRYPT_KEYSTORE="encrypt_keystore" \
-e JGROUPS_ENCRYPT_KEYSTORE_DIR="jboss.server.base.dir" \
-e JGROUPS_CLUSTER_PASSWORD="cluster_password" \
{noformat}
In Openshift, you can use the eap-cd-https-s2i, I tested with:
{noformat}
oc new-app --template=eap-cd-https-s2i \
-p IMAGE_STREAM_NAMESPACE=eap-demo \
-p SOURCE_REPOSITORY_URL=https://github.com/jboss-developer/jboss-eap-quicks... \
-p SOURCE_REPOSITORY_REF=openshift \
-p CONTEXT_DIR=kitchensink \
-e HTTPS_PASSWORD=mykeystorepass \
-e HTTPS_KEYSTORE=keystore.jks \
-e HTTPS_NAME=jboss \
-e HTTPS_KEYSTORE_TYPE=jks \
-e JGROUPS_ENCRYPT_NAME="secret-key" \
-e JGROUPS_ENCRYPT_PASSWORD="password" \
-e CONFIGURE_ELYTRON_SSL=true
{noformat}
> Configuring JGroups encryption protocols produces deprecated configuration
> --------------------------------------------------------------------------
>
> Key: WFWIP-229
> URL: https://issues.jboss.org/browse/WFWIP-229
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Environment: The example has been produced with the following S2I environment variables:
> {code}
> OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service
> JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT
> JGROUPS_CLUSTER_PASSWORD=foobar123
> OPENSHIFT_DNS_PING_SERVICE_PORT=8888
> JGROUPS_PING_PROTOCOL=dns.DNS_PING
> SCRIPT_DEBUG=true
> {code}
> Reporter: Michal Jurc
> Assignee: Yeray Borges
> Priority: Critical
>
> Any S2I configuration of ping protocols utilising encryption for protocols will result in deprecated configuration. S2I should not configure runtime to deprecated configuration by default, unless the user chooses to.
> {code:title=Example JGroups ASYM_ENCRYPT configuration}
> [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=org.jgroups.protocols.ASYM_ENCRYPT:read-resource-description
> {
> "outcome" => "success",
> "result" => {
> "description" => "The configuration of a protocol within a protocol stac
> k.",
> "capabilities" => [{
> "name" => "org.wildfly.clustering.jgroups.protocol",
> "dynamic" => true,
> "dynamic-elements" => [
> "stack",
> "protocol"
> ]
> }],
> "deprecated" => {
> "since" => "5.0.0",
> "reason" => "Deprecated. Use protocol=ASYM_ENCRYPT instead."
> },
> "attributes" => {
> "module" => {
> "type" => STRING,
> "description" => "The module with which to resolve the protocol
> type.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "default" => "org.jgroups",
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> "properties" => {
> "type" => OBJECT,
> "description" => "The properties of this protocol.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> "socket-binding" => {
> "type" => STRING,
> "description" => "Defines the bind address/port used of the serv
> er socket used to receive messages from other cluster members.",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "deprecated" => {
> "since" => "5.0.0",
> "reason" => "Deprecated. Supports EAP 7.0 slaves."
> },
> "access-type" => "read-only",
> "storage" => "configuration"
> },
> "statistics-enabled" => {
> "type" => BOOLEAN,
> "description" => "Indicates whether or not this protocol will co
> llect statistics overriding stack configuration.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> }
> },
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {"property" => {
> "description" => "A JGroups protocol property.",
> "model-description" => undefined
> }}
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 7 months