[Red Hat JIRA] (WFLY-14348) Unhelpful failure message 'WFLYJCA0032: Unable to start the ds because it generated more than one cf'
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-14348:
---------------------------------------
Summary: Unhelpful failure message 'WFLYJCA0032: Unable to start the ds because it generated more than one cf'
Key: WFLY-14348
URL: https://issues.redhat.com/browse/WFLY-14348
Project: WildFly
Issue Type: Bug
Components: JCA
Reporter: Brian Stansberry
Assignee: Tomasz Adamski
Playing with driver and DS installation I ended up with this in the server log:
{code}
10:54:11,424 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "Postgres")
]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.data-source.Postgres" => "WFLYJCA0033: Error during the deployment of Postgres
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"}}
{code}
That was quite cryptic.
1) The 'ds' and 'cf' abbreviations should be replaced with full words. To me this is the minimum resolution of this issue.
2) If it is possible to make a reasonably likely guess at what would lead to this situation and provide that info in the message, that would be nice.
Context:
I tried deploying a JDBC driver and then adding a datasource using a CLI command:
{code}
data-source add --name=Postgres --driver-name=postgresql-42.2.18.jar --jndi-name=java:jboss/datasources/Postgres
{code}
The 3 params are the required ones. I wasn't surprised that wasn't sufficient and I understand that what's required beyond that can vary from driver to driver. But those are the required ones, so users experimenting with WildFly are liable to do what I did. (If any other params *should be* required, someone please file a separate issue.)
Adding a connection-url param allowed the command to work. If that param shouldn't be required, but not providing it is a likely cause of this problem, perhaps the WFLYJCA0032 message should note that as a hint?
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (WFCORE-5252) Log WARN if wildfly.config.url is set on the server.
by Ilia Vassilev (Jira)
[ https://issues.redhat.com/browse/WFCORE-5252?page=com.atlassian.jira.plug... ]
Ilia Vassilev updated WFCORE-5252:
----------------------------------
Security: (was: Red Hat Internal)
> Log WARN if wildfly.config.url is set on the server.
> ----------------------------------------------------
>
> Key: WFCORE-5252
> URL: https://issues.redhat.com/browse/WFCORE-5252
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 14.0.0.Final
> Reporter: Ilia Vassilev
> Assignee: Ilia Vassilev
> Priority: Major
> Labels: downstream_dependency
>
> -Dwildfly.config.url=wildfly-config.xml can be set to specify configuration to be used , this should typically only be used for a standalone JVM application, not when running EAP. If this system property is set when starting EAP, it will overrule the configuration in the JBoss Profile xml. Logging a WARN when this is set inside of EAP would warn the user that their JBoss Profile xml configuration is not being used.
> Steps to test:
> * Create wildfly-config.xml in JBOSS_HOME
> * Start the server: ./standalone.sh -Dwildfly.config.url=wildfly-config.xml
> * Verify that the following warning is in server.log
> {code}
> 2021-01-23 09:41:04,669 WARN [org.jboss.as.config] (MSC service thread 1-2) WFLYSRV0281: System property wildfly.config.url = wildfly-config.xml is set. This should only be used for standalone clients. Setting this on the server will override your profile configuration.
> {code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (WFLY-14345) Ensure ByteBufferMarshalledValue marshaller generates a valid protobuf message
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-14345:
-----------------------------------
Summary: Ensure ByteBufferMarshalledValue marshaller generates a valid protobuf message
Key: WFLY-14345
URL: https://issues.redhat.com/browse/WFLY-14345
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 22.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Protobuf messages generated by the ByteBufferMarshalledValueExternalizer from the org.wildfly.clustering.marshalling.spi module is not a valid protobuf message.
This requires a native ProtoStream marshaller, that can additionally optimize for null values.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (WFLY-14344) helloworld-classfiletransformer throws javassist.NotFoundException
by Wolfgang Mayer (Jira)
Wolfgang Mayer created WFLY-14344:
-------------------------------------
Summary: 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
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)
3 years, 5 months