[Red Hat JIRA] (WFLY-14378) Generic JMS RA fails to authenticate
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-14378?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet updated WFLY-14378:
-------------------------------------
Affects Version/s: 22.0.0.Final
> Generic JMS RA fails to authenticate
> -------------------------------------
>
> Key: WFLY-14378
> URL: https://issues.redhat.com/browse/WFLY-14378
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 22.0.0.Final
> Reporter: Emmanuel Hugonnet
> Priority: Critical
>
> MDBs deployed in on WildFLy 22 using generic JMS resource adapter would fail to authenticate with external TIBCO broker due to missing password.
> {noformat}
> 2021-01-29 13:55:47,927 WARN [org.jboss.resource.adapter.jms.inflow.JmsActivation] (default-threads - 3) Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@25f70034(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)4b294f76 destination=jms/topic/inTopic destinationType=javax.jms.Topic acknowledgeMode=Auto-acknowledge subscriptionDurability=false reconnectInterval=10 reconnectAttempts=-1 user=quickuser maxMessages=1 minSession=1 maxSession=15 connectionFactory=jms/cf/XATopicConnectionFactory jndiParameters={java.naming.provider.url=tcp://aza:7222, java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory, java.naming.security.principal=quickuser, java.naming.security.credentials=<not shown>}): javax.jms.JMSSecurityException: authentication failed
> at com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:744)
> at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:1465)
> at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:4412)
> at com.tibco.tibjms.TibjmsXAConnection.<init>(TibjmsXAConnection.java:30)
> at com.tibco.tibjms.TibjmsXATopicConnection.<init>(TibjmsXATopicConnection.java:29)
> at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:147)
> at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:255)
> at com.tibco.tibjms.TibjmsXAConnectionFactory.createXAConnection(TibjmsXAConnectionFactory.java:61)
> at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupConnection(JmsActivation.java:442)
> at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupConnection(JmsActivation.java:417)
> at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupActivation(JmsActivation.java:316)
> at org.jboss.resource.adapter.jms.inflow.JmsActivation.access$100(JmsActivation.java:58)
> at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:546)
> at org.jboss.jca.core.workmanager.WorkWrapper.runWork(WorkWrapper.java:445)
> at org.jboss.as.connector.services.workmanager.WildflyWorkWrapper.runWork(WildflyWorkWrapper.java:69)
> at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:223)
> at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:29)
> at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:789)
> at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:44)
> at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:809)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {noformat}
> Authentication with TIBCO JNDI does works and JMS bridge would work only MDB are affected.
> This is due to missing getter() method on JMSActivationSpect class.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 3 months
[Red Hat JIRA] (WFLY-14378) Generic JMS RA fails to authenticate
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-14378?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet moved JBEAP-20928 to WFLY-14378:
--------------------------------------------------
Component/s: (was: Generic JMS RA)
Key: WFLY-14378 (was: JBEAP-20928)
QEStatus: ToDo
Affects Version/s: (was: 7.3.x)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Issue Type: Bug (was: Question)
Project: WildFly (was: JBoss Enterprise Application Platform)
> Generic JMS RA fails to authenticate
> -------------------------------------
>
> Key: WFLY-14378
> URL: https://issues.redhat.com/browse/WFLY-14378
> Project: WildFly
> Issue Type: Bug
> Reporter: Emmanuel Hugonnet
> Priority: Critical
>
> MDBs deployed in on WildFLy 22 using generic JMS resource adapter would fail to authenticate with external TIBCO broker due to missing password.
> {noformat}
> 2021-01-29 13:55:47,927 WARN [org.jboss.resource.adapter.jms.inflow.JmsActivation] (default-threads - 3) Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@25f70034(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)4b294f76 destination=jms/topic/inTopic destinationType=javax.jms.Topic acknowledgeMode=Auto-acknowledge subscriptionDurability=false reconnectInterval=10 reconnectAttempts=-1 user=quickuser maxMessages=1 minSession=1 maxSession=15 connectionFactory=jms/cf/XATopicConnectionFactory jndiParameters={java.naming.provider.url=tcp://aza:7222, java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory, java.naming.security.principal=quickuser, java.naming.security.credentials=<not shown>}): javax.jms.JMSSecurityException: authentication failed
> at com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:744)
> at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:1465)
> at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:4412)
> at com.tibco.tibjms.TibjmsXAConnection.<init>(TibjmsXAConnection.java:30)
> at com.tibco.tibjms.TibjmsXATopicConnection.<init>(TibjmsXATopicConnection.java:29)
> at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:147)
> at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:255)
> at com.tibco.tibjms.TibjmsXAConnectionFactory.createXAConnection(TibjmsXAConnectionFactory.java:61)
> at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupConnection(JmsActivation.java:442)
> at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupConnection(JmsActivation.java:417)
> at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupActivation(JmsActivation.java:316)
> at org.jboss.resource.adapter.jms.inflow.JmsActivation.access$100(JmsActivation.java:58)
> at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:546)
> at org.jboss.jca.core.workmanager.WorkWrapper.runWork(WorkWrapper.java:445)
> at org.jboss.as.connector.services.workmanager.WildflyWorkWrapper.runWork(WildflyWorkWrapper.java:69)
> at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:223)
> at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:29)
> at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:789)
> at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:44)
> at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:809)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {noformat}
> Authentication with TIBCO JNDI does works and JMS bridge would work only MDB are affected.
> This is due to missing getter() method on JMSActivationSpect class.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 3 months
[Red Hat JIRA] (WFLY-14344) helloworld-classfiletransformer throws javassist.NotFoundException
by Wolfgang Mayer (Jira)
[ https://issues.redhat.com/browse/WFLY-14344?page=com.atlassian.jira.plugi... ]
Wolfgang Mayer commented on WFLY-14344:
---------------------------------------
Yes, this looks to be the same issue
> helloworld-classfiletransformer throws javassist.NotFoundException
> ------------------------------------------------------------------
>
> Key: WFLY-14344
> URL: https://issues.redhat.com/browse/WFLY-14344
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Affects Versions: 22.0.0.Final
> Reporter: Wolfgang Mayer
> Assignee: Eduardo Martins
> Priority: Major
>
> Deployment of project helloworld-classfiletransformer throws Exception:
> javassist.NotFoundException: hello.server.ejb.HelloBean$$$view4
> mvn -v
> Apache Maven 3.6.3
> Maven home: /usr/share/maven
> Java version: 11.0.8, vendor: Oracle Corporation, runtime: /usr/local/java/jdk-11.0.8
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux", version: "5.8.0-40-generic", arch: "amd64", family: "unix"
> [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:2.0.2.Final:deploy (default-cli) on project helloworld-classfiletransformers: Failed to execute goal deploy: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"helloworld-classfiletransformers.war\".INSTALL" => "WFLYSRV0153: Failed to process phase INSTALL of deployment \"helloworld-classfiletransformers.war\"
> [ERROR] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0024: Could not configure component HelloBean
> [ERROR] Caused by: java.lang.ClassFormatError: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view4
> [ERROR] Caused by: java.lang.RuntimeException: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view4
> [ERROR] Caused by: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view4"},"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager","jboss.deployment.unit.\"helloworld-classfiletransformers.war\".WeldStartService"],"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"helloworld-classfiletransformers.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"helloworld-classfiletransformers.war\".WeldStartService, jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager]","jboss.deployment.unit.\"helloworld-classfiletransformers.war\".batch.artifact.factory is missing [jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager]"]}}}
> h1.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 3 months
[Red Hat JIRA] (WFCORE-5262) Add a timestamp at the beginning of image startup in EAP images
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-5262?page=com.atlassian.jira.plug... ]
Brian Stansberry updated WFCORE-5262:
-------------------------------------
Component/s: (was: CLI)
> Add a timestamp at the beginning of image startup in EAP images
> ---------------------------------------------------------------
>
> Key: WFCORE-5262
> URL: https://issues.redhat.com/browse/WFCORE-5262
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Scripts
> Reporter: Katarína Hermanová
> Assignee: Katarína Hermanová
> Priority: Optional
>
> I'm currently investigating some test failures, and I suspect the tests are failing because of a nonstandard manifestation of JBEAP-17984. To verify that, ideally without rerunning each test and measuring the EAP startup time, I'd like to have a timestamp at the very beginning of the image startup script:
> {noformat}
> <-- insert timestamp here
> ^[[0;33mWARN Configuration of an embedded messaging broker within the appserver is enabled but is not recommended. Support for such a configuration will be removed in a future release.^[[0m
> INFO If you are not configuring messaging destinations, to disable configuring an embedded messaging broker set the DISABLE_EMBEDDED_JMS_BROKER environment variable to true.
> ^[[0;33mWARN No password defined for JGroups cluster. AUTH protocol will be disabled. Please define JGROUPS_CLUSTER_PASSWORD.^[[0m
> ^[[0;33mWARN Environment variable OPENSHIFT_KUBE_PING_NAMESPACE undefined. Clustering will be unavailable. Please refer to the documentation for configuration.^[[0m
> INFO Configuring JGroups discovery protocol to openshift.KUBE_PING
> INFO Configuring JGroups cluster traffic encryption protocol to SYM_ENCRYPT.
> ^[[0;33mWARN Detected missing JGroups encryption configuration, the communication within the cluster WILL NOT be encrypted.^[[0m
> Using PicketBox SSL configuration.
> ^[[0;33mWARN Missing SSO_URL. Unable to properly configure SSO-enabled applications^[[0m
> INFO Access log is disabled, ignoring configuration.
> INFO Running jboss-eap-7/eap72-openj9-11-openshift-rhel8 image, version 7.2
> -XX:+UseParallelOldGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:MaxMetaspaceSize=100m -XX:+ExitOnOutOfMemoryError
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /opt/eap
> JAVA: /usr/lib/jvm/jre-11-openj9/bin/java
> JAVA_OPTS: -server -Xlog:gc*:file=/opt/eap/standalone/log/gc.log:time,uptimemillis:filecount=5,filesize=3M -Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.logmanager,jdk.nashorn.api,com.sun.crypto.provider -Djava.awt.headless=true -javaagent:/opt/jboss/container/jolokia/jolokia.jar=config=/opt/jboss/container/jolokia/etc/jolokia.properties -Xbootclasspath/a:/opt/eap/modules/system/layers/base/.overlays/layer-base-jboss-eap-7.2.4.CP/org/jboss/logmanager/main/jboss-logmanager-2.1.14.Final-redhat-00001.jar:/opt/eap/modules/system/layers/base/org/glassfish/javax/json/main/javax.json-1.1.2.redhat-1.jar:/opt/eap/modules/system/layers/base/javax/json/api/main/javax.json-api-1.1.2.redhat-1.jar:/opt/eap/modules/system/layers/base/.overlays/layer-base-jboss-eap-7.2.4.CP/org/wildfly/common/main/wildfly-common-1.5.1.Final-redhat-00001.jar -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dsun.util.logging.disableCallerCheck=true -XX:+UseParallelOldGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:+ExitOnOutOfMemoryError -Djava.security.egd=file:/dev/./urandom --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED --add-modules=java.se
> =========================================================================
> JVMJ9VM085W Malformed option: '-Xlog:gc*:file=/opt/eap/standalone/log/gc.log:time'
> Nov 11, 2019 9:40:13 PM java.lang.System$LoggerFinder lambda$getLoggerFinder$0
> WARNING: Failed to instantiate LoggerFinder provider; Using default.
> ...
> {noformat}
> There are other ways of finding out how long this took, e.g. events, but each has certain drawbacks. The events for example, get cleaned up after two hours, in default OpenShift configuration. I'd like the timestamp information to be persisted in the pod logs, and be present by default.
> Once the EAP startup commences, EAP prints timestamps, so that's fine. I just need to also measure the time before the EAP startup begins.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 3 months
[Red Hat JIRA] (WFCORE-5262) Add a timestamp at the beginning of image startup in EAP images
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-5262?page=com.atlassian.jira.plug... ]
Brian Stansberry commented on WFCORE-5262:
------------------------------------------
[~khermano] I believe this should go in the CLOUD JIRA project. The WildFly Core code base does not log at that point. [~luck3y] can help with any questions about the proper metadata for a CLOUD JIRA.
> Add a timestamp at the beginning of image startup in EAP images
> ---------------------------------------------------------------
>
> Key: WFCORE-5262
> URL: https://issues.redhat.com/browse/WFCORE-5262
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI, Scripts
> Reporter: Katarína Hermanová
> Assignee: Katarína Hermanová
> Priority: Optional
>
> I'm currently investigating some test failures, and I suspect the tests are failing because of a nonstandard manifestation of JBEAP-17984. To verify that, ideally without rerunning each test and measuring the EAP startup time, I'd like to have a timestamp at the very beginning of the image startup script:
> {noformat}
> <-- insert timestamp here
> ^[[0;33mWARN Configuration of an embedded messaging broker within the appserver is enabled but is not recommended. Support for such a configuration will be removed in a future release.^[[0m
> INFO If you are not configuring messaging destinations, to disable configuring an embedded messaging broker set the DISABLE_EMBEDDED_JMS_BROKER environment variable to true.
> ^[[0;33mWARN No password defined for JGroups cluster. AUTH protocol will be disabled. Please define JGROUPS_CLUSTER_PASSWORD.^[[0m
> ^[[0;33mWARN Environment variable OPENSHIFT_KUBE_PING_NAMESPACE undefined. Clustering will be unavailable. Please refer to the documentation for configuration.^[[0m
> INFO Configuring JGroups discovery protocol to openshift.KUBE_PING
> INFO Configuring JGroups cluster traffic encryption protocol to SYM_ENCRYPT.
> ^[[0;33mWARN Detected missing JGroups encryption configuration, the communication within the cluster WILL NOT be encrypted.^[[0m
> Using PicketBox SSL configuration.
> ^[[0;33mWARN Missing SSO_URL. Unable to properly configure SSO-enabled applications^[[0m
> INFO Access log is disabled, ignoring configuration.
> INFO Running jboss-eap-7/eap72-openj9-11-openshift-rhel8 image, version 7.2
> -XX:+UseParallelOldGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:MaxMetaspaceSize=100m -XX:+ExitOnOutOfMemoryError
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /opt/eap
> JAVA: /usr/lib/jvm/jre-11-openj9/bin/java
> JAVA_OPTS: -server -Xlog:gc*:file=/opt/eap/standalone/log/gc.log:time,uptimemillis:filecount=5,filesize=3M -Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.logmanager,jdk.nashorn.api,com.sun.crypto.provider -Djava.awt.headless=true -javaagent:/opt/jboss/container/jolokia/jolokia.jar=config=/opt/jboss/container/jolokia/etc/jolokia.properties -Xbootclasspath/a:/opt/eap/modules/system/layers/base/.overlays/layer-base-jboss-eap-7.2.4.CP/org/jboss/logmanager/main/jboss-logmanager-2.1.14.Final-redhat-00001.jar:/opt/eap/modules/system/layers/base/org/glassfish/javax/json/main/javax.json-1.1.2.redhat-1.jar:/opt/eap/modules/system/layers/base/javax/json/api/main/javax.json-api-1.1.2.redhat-1.jar:/opt/eap/modules/system/layers/base/.overlays/layer-base-jboss-eap-7.2.4.CP/org/wildfly/common/main/wildfly-common-1.5.1.Final-redhat-00001.jar -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dsun.util.logging.disableCallerCheck=true -XX:+UseParallelOldGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:+ExitOnOutOfMemoryError -Djava.security.egd=file:/dev/./urandom --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED --add-modules=java.se
> =========================================================================
> JVMJ9VM085W Malformed option: '-Xlog:gc*:file=/opt/eap/standalone/log/gc.log:time'
> Nov 11, 2019 9:40:13 PM java.lang.System$LoggerFinder lambda$getLoggerFinder$0
> WARNING: Failed to instantiate LoggerFinder provider; Using default.
> ...
> {noformat}
> There are other ways of finding out how long this took, e.g. events, but each has certain drawbacks. The events for example, get cleaned up after two hours, in default OpenShift configuration. I'd like the timestamp information to be persisted in the pod logs, and be present by default.
> Once the EAP startup commences, EAP prints timestamps, so that's fine. I just need to also measure the time before the EAP startup begins.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 3 months
[Red Hat JIRA] (WFLY-11794) Helloworld-classtransformer incompatibility
by Scott Marlow (Jira)
[ https://issues.redhat.com/browse/WFLY-11794?page=com.atlassian.jira.plugi... ]
Scott Marlow commented on WFLY-11794:
-------------------------------------
It looks like the latest Javassist version is 3.27.0-GA, perhaps try upgrading.
> Helloworld-classtransformer incompatibility
> -------------------------------------------
>
> Key: WFLY-11794
> URL: https://issues.redhat.com/browse/WFLY-11794
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Reporter: Eduardo Martins
> Assignee: Richard Opalka
> Priority: Major
>
> Changes done at server side, wrt JDK12 compatibility, introduced issues when deploying quickstart helloworld-classtransformer post WFLY 16 Beta:
> {code}
> 22:37:27,320 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /Users/emmartins/jboss/git/as/wildfly/dist-copy/target/wildfly-16.0.0.CR1-SNAPSHOT/standalone/data/content/23/641c0517f5106bee30dbc931cc7fe8784f52d7/content
> 22:37:27,350 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "helloworld-classfiletransformers.war" (runtime-name: "helloworld-classfiletransformers.war")
> 22:37:28,051 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.helloworld-classfiletransformers.war" is using a private module ("org.javassist") which may be changed or removed in future versions without notice.
> 22:37:28,108 INFO [hello.server.transformation.HelloByteCodeManipulator] (MSC service thread 1-8) Instrumenting hello.server.ejb.HelloBean
> 22:37:28,166 INFO [hello.server.transformation.HelloByteCodeManipulator] (MSC service thread 1-8) Successfully instrumented hello.server.ejb.HelloBean
> 22:37:28,206 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment helloworld-classfiletransformers.war
> 22:37:28,449 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 6.0.15.Final
> 22:37:28,699 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'HelloBean' in deployment unit 'deployment "helloworld-classfiletransformers.war"' are as follows:
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.invocation.proxy.AbstractProxyFactory$1 (jar:file:/Users/emmartins/jboss/git/as/wildfly/dist-copy/target/wildfly-16.0.0.CR1-SNAPSHOT/modules/system/layers/base/org/jboss/invocation/main/jboss-invocation-1.5.2.Final.jar!/) to method java.lang.Object.clone()
> WARNING: Please consider reporting this to the maintainers of org.jboss.invocation.proxy.AbstractProxyFactory$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> 22:37:29,062 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."helloworld-classfiletransformers.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."helloworld-classfiletransformers.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "helloworld-classfiletransformers.war"
> at org.jboss.as.server@8.0.0.CR1//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0024: Could not configure component HelloBean
> at org.jboss.as.ee@16.0.0.CR1-SNAPSHOT//org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:106)
> at org.jboss.as.server@8.0.0.CR1//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
> ... 8 more
> Caused by: java.lang.ClassFormatError: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> at org.jboss.modules.ModuleClassLoader.defineClassInternal(ModuleClassLoader.java:460)
> at org.jboss.modules.ModuleClassLoader.defineClassInternal(ModuleClassLoader.java:480)
> at org.jboss.modules.ClassDefiner.defineClass(ClassDefiner.java:144)
> at org.jboss.as.server@8.0.0.CR1//org.jboss.as.server.deployment.ModuleClassFactory.defineClass(ModuleClassFactory.java:56)
> at org.jboss.classfilewriter@1.2.4.Final//org.jboss.classfilewriter.ClassFile.defineInternal(ClassFile.java:299)
> at org.jboss.classfilewriter@1.2.4.Final//org.jboss.classfilewriter.ClassFile.define(ClassFile.java:286)
> at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.proxy.AbstractClassFactory.defineClass(AbstractClassFactory.java:202)
> at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.proxy.AbstractProxyFactory.getCachedMethods(AbstractProxyFactory.java:162)
> at org.jboss.as.ejb3@16.0.0.CR1-SNAPSHOT//org.jboss.as.ejb3.component.stateless.StatelessComponentDescription$3.configure(StatelessComponentDescription.java:147)
> at org.jboss.as.ee@16.0.0.CR1-SNAPSHOT//org.jboss.as.ee.component.DefaultComponentViewConfigurator.configure(DefaultComponentViewConfigurator.java:91)
> at org.jboss.as.ee@16.0.0.CR1-SNAPSHOT//org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:92)
> ... 9 more
> Caused by: java.lang.RuntimeException: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> at deployment.helloworld-classfiletransformers.war//hello.server.transformation.HelloByteCodeManipulator.getCtClass(HelloByteCodeManipulator.java:135)
> at deployment.helloworld-classfiletransformers.war//hello.server.transformation.HelloByteCodeManipulator.transform(HelloByteCodeManipulator.java:70)
> at deployment.helloworld-classfiletransformers.war//hello.server.transformation.HelloBeanClassFileTransformer.transform(HelloBeanClassFileTransformer.java:57)
> at org.jboss.as.server@8.0.0.CR1//org.jboss.as.server.deployment.module.DelegatingClassFileTransformer.transform(DelegatingClassFileTransformer.java:60)
> at org.jboss.modules.JLIClassTransformer.transform(JLIClassTransformer.java:55)
> at org.jboss.modules.ModuleClassLoader.defineClassInternal(ModuleClassLoader.java:458)
> ... 19 more
> Caused by: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> at org.javassist//javassist.ClassPool.get(ClassPool.java:422)
> at deployment.helloworld-classfiletransformers.war//hello.server.transformation.HelloByteCodeManipulator.getCtClass(HelloByteCodeManipulator.java:133)
> ... 24 more
> 22:37:29,154 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Infinity Minus ONE +2' 9.4.8.Final
> 22:37:29,620 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 74) WFLYCLINF0002: Started client-mappings cache from ejb container
> 22:37:29,695 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "helloworld-classfiletransformers.war")]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"helloworld-classfiletransformers.war\".INSTALL" => "WFLYSRV0153: Failed to process phase INSTALL of deployment \"helloworld-classfiletransformers.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0024: Could not configure component HelloBean
> Caused by: java.lang.ClassFormatError: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> Caused by: java.lang.RuntimeException: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> Caused by: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1"},
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager",
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".WeldStartService"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"helloworld-classfiletransformers.war\".WeldStartService, jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager]",
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".batch.artifact.factory is missing [jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager]"
> ]
> }
> 22:37:29,697 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "helloworld-classfiletransformers.war" was rolled back with the following failure message:
> {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"helloworld-classfiletransformers.war\".INSTALL" => "WFLYSRV0153: Failed to process phase INSTALL of deployment \"helloworld-classfiletransformers.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0024: Could not configure component HelloBean
> Caused by: java.lang.ClassFormatError: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> Caused by: java.lang.RuntimeException: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> Caused by: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1"},
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager",
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".WeldStartService"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"helloworld-classfiletransformers.war\".WeldStartService, jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager]",
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".batch.artifact.factory is missing [jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager]"
> ]
> }
> 22:37:29,727 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment helloworld-classfiletransformers.war (runtime-name: helloworld-classfiletransformers.war) in 29ms
> {code}
> It's not clear the actual QS design is something we want to keep promoting tho:
> * it teaches how to use a private module
> * we use byteman with users/customers, when intercepting code on the fly
> Assuming incompatibility we should drop the QS from WFLY releases, and we should rethink if we going to fix it, or replace it with a new QS.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 3 months
[Red Hat JIRA] (DROOLS-5977) [DMN Editor] A nested Structure with no fields breaks the Decision Table Editor
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5977?page=com.atlassian.jira.plug... ]
Matteo Mortari commented on DROOLS-5977:
----------------------------------------
The result produced by the Editor is a DMN model where the typeRef does not correspond to an existing/valid type.
> [DMN Editor] A nested Structure with no fields breaks the Decision Table Editor
> -------------------------------------------------------------------------------
>
> Key: DROOLS-5977
> URL: https://issues.redhat.com/browse/DROOLS-5977
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.49.0.Final
> Reporter: Edoardo Vacchi
> Assignee: Guilherme Gomes
> Priority: Major
> Attachments: nested-structure.webm
>
>
> When a field of type Structure is added with no sub-fields in the data type editor, and a Decision Table for that type is created, then the type that shows up in the Decision Table bears the name of the structure, which is incorrect (see video)
> The video also shows how this may happen by mistake.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 3 months