AnsweredAssumed Answered

configuring Wildfly clustering

Question asked by neeraja mahajan on Aug 29, 2016
Latest reply on Oct 25, 2016 by Sanjay Kumar

Like • Show 0 Likes0
Comment • 10

Hello,

I am able to connect the Domain Controller and the host controller in wildfly cluster for Via L&G, the back-end says "service aveksa_cluster status
27291
RSA Via Lifecycle and Governance is running"

also

I am able to see the "Bridge Cluster.. is connected" message in both the server.log of DC and HC, but cant see the application when I hit Via L&G URL, getting 404- Not Found.

When restarting the aveksa_cluster service it says :

Kindly let me know how do i fix this. I am not able to make SON because of this issue.

Thanks,

Neeraja

No one else has this question

Outcomes

10 Replies

Daniel Cinnamon Aug 30, 2016 10:05 AM
Mark Correct
Correct Answer
It sounds to me like you have the wildfly cluster running, but have not yet deployed the aveksa.ear file onto the cluster.
If you look at page 15 of the wildfly install guide, there's really 2 steps there.
The first step is to configure/run the configureWildfly.sh script. This script will go into wildfly, and setup all the shared resources such as JMS queues/topics, and JDBC connections. Customers running weblogic/websphere have to do all this manually.
The second step there is to actually deploy the aveksa.ear onto the cluster:
/home/oracle/wildfly/bin/jboss-cli.sh -c --controller=<your domain controller ip address>:9999 --command="deploy /tmp/repackaged_ear_dir/aveksa.ear --server-groups=img-server-group"

Have you done both of these?
1 person found this helpful
Like • Show 1 Like1
Actions
- neeraja mahajan @ Daniel Cinnamon on Aug 31, 2016 8:39 AM
  Mark Correct
  Correct Answer
  Hi Daniel,
  
  I did follow the steps, I get this error:
  
  please advice.
  
  Thanks,
  Neeraja
  Like • Show 0 Likes0
  Actions
  - Daniel Cinnamon @ neeraja mahajan on Aug 31, 2016 9:36 AM
    Mark Correct
    Correct Answer
    Okay so that error is just saying that the aveksa.ear file has already been deployed, proving that you did deploy it as the install guide says. At this point I would advise taking this to support- we can't get any further without some analysis of the logs, and those really shouldn't be posted here in the community.
    Like • Show 0 Likes0
    Actions
  - Edwin Mullie @ neeraja mahajan on Aug 31, 2016 10:36 AM
    Mark Correct
    Correct Answer
    It looks like you already deployed the averse.ear on the domain controller, that is the error you are seeing.
    
    Do you see the "Tweek" starting and "Tweek" started in ...? in the stdout.log in /home/oracle/wildfly/domain/log?
    
    Edwin
    Like • Show 0 Likes0
    Actions
    - neeraja mahajan @ Edwin Mullie on Aug 31, 2016 11:13 AM
      Mark Correct
      Correct Answer
      Yes I saw "tweet started" ... but i also see this ERROR :
      "...ERROR [stderr] (MSC service thread 1-7) log4j:WARN No appenders could be found for logger (com.aveksa.server.ws.AccessRequestWebServiceProvider). [0m ....
      .
      .
      .
      JBAS015874: WildFly 8.2.0.Final "Tweek" started in 92487ms - Started 3202 of 3349 services (254 services are lazy, passive or on-demand) "
      
      Do I need to enable the log4j?
      
      Kindly advice!
      
      Thanks,
      Neeraja
      Like • Show 0 Likes0
      Actions
      - Edwin Mullie @ neeraja mahajan on Aug 31, 2016 11:28 AM
        Mark Correct
        Correct Answer
        No you can ignore the log4j
        
        do you have any errors in the /home/oracle/wildfly/domain/server/<servername>/log/aveksaServer.log or the /home/oracle/wildfly/domain/server/<servername>/log/server.log?
        
        Edwin
        Like • Show 0 Likes0
        Actions
      - Ted Barbour @ neeraja mahajan on Aug 31, 2016 11:29 AM
        Mark Correct
        Correct Answer
        Can you verify if port 8443 is listening on either machine: netstat -an |grep 8443
        
        Like • Show 0 Likes0
        Actions
        neeraja mahajan @ Ted Barbour on Sep 1, 2016 3:14 PM
        Mark Correct
        Correct Answer
        Hi Ted Barbour ,
        
        I could see it listened on both the machines....
        
        And Hi Edwin Mullie, at that point of time was having the error related to deployment:
        the Tweek started with errors.
        But... some how the DC's Admin GUI was up I could create the configurations in HC and made the next SON through Admin UI, on un-deploying the aveksa.ear and redeploying it made me fall in to issues again :
        
        Caused by: java.net.ConnectException: JBAS012174: Could not connect to remoting://<IP>:9999. The connection failed
        stdout.log say's:
        ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010932: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration [0m....
        
        Please advise me
        
        Thanks,
        Neeraja
        Like • Show 0 Likes0
        Actions
        Edwin Mullie @ neeraja mahajan on Sep 5, 2016 3:29 AM
        Mark Correct
        Correct Answer
        it says: Failed to parse configuration
        
        check your domain.xml, i've seen this before. Does the error give you anymore information than that?
        
        Edwin
        Like • Show 0 Likes0
        Actions
Sanjay Kumar Oct 25, 2016 9:40 AM
Mark Correct
Correct Answer
Please check Host.xml file.
Like • Show 0 Likes0
Actions

configuring Wildfly clustering

Outcomes

Related Content

Recommended Content