Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WFLY-2912 Generic JMS adapter does not deploy correctly in domain mode. #5903

Merged
merged 2 commits into from Apr 1, 2014

Conversation

maeste
Copy link
Contributor

@maeste maeste commented Feb 12, 2014

No description provided.

@wildfly-ci
Copy link

Build 2661 is now running using a merge of a83399a

@wildfly-ci
Copy link

Build 2661 outcome was SUCCESS using a merge of a83399a
Summary: Tests passed: 5570, ignored: 74 Build time: 1:26:54

final ServiceVerificationHandler svh = new ServiceVerificationHandler();


ServiceName restartedServiceName = RaOperationUtil.restartIfPresent(context, archiveOrModuleName, name, svh);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really understand what is going on here. It looks like the logic is 'if the server is booting restart the service' however I don't really see why this should be necessary, because if the server is booting then there should be no service there yet to restart?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well the code is not very self explaining. I'll rework it a bit to make it more readable asap, but le me explain what it's aiming to do: RaOperationUtil.installRaServicesAndDeployFromModule create services for rar deployed as module. This service require an explicit activation (:activate command from CLI) when a configuration is added. In case of boot time both operation need to be executed, and this "restart" service is exactly activating configuration on previous installed service.
As said I'll rework a bit the code to make it more readable (at least w/ some comments).
Thanks to point it out.

@wildfly-ci
Copy link

Build 2917 is now running using a merge of fa29697

@wildfly-ci
Copy link

Build 2917 outcome was SUCCESS using a merge of fa29697
Summary: Tests passed: 5600, ignored: 79 Build time: 1:30:11

@jmesnil
Copy link
Member

jmesnil commented Mar 20, 2014

I've checked that the generic JMS RA is correctly deployed in domain mode with that fix.

final ServiceVerificationHandler svh = new ServiceVerificationHandler();

//Next lines activate configuration on module deployed rar
//in case there is 2 different resource-adapter config using same module deployed rar
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This commit fixes the issue of deploying the generic JMS RA in domain mode but I don't understand what is the relation with this comment.
I have only 1 resource-adapter defined (org.jboss.genericjms) in each of my profile. Each server should have only one deployed RA, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could have multiple config (at least theoretically) for same module RA

@jesperpedersen
Copy link
Contributor

Bump :)

n1hility added a commit that referenced this pull request Apr 1, 2014
WFLY-2912 Generic JMS adapter does not deploy correctly in domain mode.
@n1hility n1hility merged commit 9806509 into wildfly:master Apr 1, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
6 participants