Bug 1220300 - Met 500 error when access "Administration Console" of jboss-wildfly-9 kitchensink quickstart
Summary: Met 500 error when access "Administration Console" of jboss-wildfly-9 kitchen...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Templates
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Farah Juma
QA Contact: XiuJuan Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-11 09:18 UTC by XiuJuan Wang
Modified: 2015-09-08 20:14 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-08 20:14:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-4624 0 Blocker Resolved JGroups protocol properties are not applied 2015-12-23 15:12:28 UTC

Description XiuJuan Wang 2015-05-11 09:18:01 UTC
Description of problem:
Met "500 - Internal Server Error" when access "Administration Console" of jboss-wildfly-9 kitchensink quickstart 

Version-Release number of selected component (if applicable):
devenv_5514
jboss-wildfly-9

How reproducible:
always

Steps to Reproduce:
1.Create a jboss-wildfly-9 kitchensink quickstart 
rhc app create kitchensink jboss-wildfly-9 
cd kitchensink
git remote add upstream -m master git://github.com/openshift/kitchensink-example.git
git pull -s recursive -X theirs upstream master
2.Access the app's url
3.Click "Administration Console"

Actual results:
Step 3:
Will meet "500 - Internal Server Error"

Expected results:
Should acess Administration Console

Additional info:
Find logs in wildfly/logs/server.log
--------------------------------------------------------------
 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.jgroups.channel.ee: org.jboss.msc.service.StartException in service jboss.jgroups.channel.ee: java.security.PrivilegedActionException: java.lang.Exception: Property assignment of initial_hosts in TCPPING with original property value null and converted to null could not be assigned
        at org.wildfly.clustering.jgroups.spi.service.ChannelBuilder.start(ChannelBuilder.java:79)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.security.PrivilegedActionException: java.lang.Exception: Property assignment of initial_hosts in TCPPING with original property value null and converted to null could not be assigned
        at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:638)
        at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:99)
        at org.wildfly.clustering.jgroups.spi.service.ChannelBuilder.start(ChannelBuilder.java:77)
        ... 5 more
Caused by: java.lang.Exception: Property assignment of initial_hosts in TCPPING with original property value null and converted to null could not be assigned
        at org.jgroups.stack.Configurator.resolveAndAssignField(Configurator.java:1153)
        at org.jgroups.stack.Configurator.createLayer(Configurator.java:444)
        at org.jgroups.stack.Configurator.createProtocols(Configurator.java:398)
        at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:90)
        at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:57)
        at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:477)
        at org.jgroups.JChannel.init(JChannel.java:854)
        at org.jgroups.JChannel.<init>(JChannel.java:159)
        at org.jboss.as.clustering.jgroups.JChannelFactory$1.run(JChannelFactory.java:96)
        at org.jboss.as.clustering.jgroups.JChannelFactory$1.run(JChannelFactory.java:93)
        at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:634)
        ... 7 more

Comment 1 Farah Juma 2015-05-11 19:31:07 UTC
It looks like the kitchensink app isn't getting deployed successfully due to a JGroups issue in WildFly 9 CR1. I've created the following WFLY issue to track this:

https://issues.jboss.org/browse/WFLY-4624

Since the kitchensink app isn't getting deployed successfully, the default WildFly welcome page is displayed instead when the app's URL is accessed. Clicking on the "Administration Console" link on this page should result in a "500 - Internal Server Error" since the Administration Console is only accessible via port forwarding.

Comment 2 JBoss JIRA Server 2015-05-15 11:56:57 UTC
Radoslav Husar <rhusar> updated the status of jira WFLY-4624 to Coding In Progress

Comment 3 Farah Juma 2015-05-20 19:42:54 UTC
WFLY-4624 has now been resolved. Once WildFly 9.0.0.CR2 is released and the WildFly cartridge is updated accordingly, the kitchensink quickstart should work fine.

Comment 4 Ben Parees 2015-06-18 04:48:47 UTC
Farah is the WF9 cart on CR2 yet?

Comment 5 Farah Juma 2015-06-18 13:16:53 UTC
The WF 9 cart has been updated to 9.0.0.CR2 but it turns out that we still need one more JGroups fix to get the kitchensink quickstart working again:

https://issues.jboss.org/browse/WFLY-4674

The above issue is currently scheduled for the 9.0.0.Final release.

Comment 6 Fabiano Franz 2015-07-02 21:51:42 UTC
QE please test.

Comment 7 Farah Juma 2015-07-02 21:59:32 UTC
WildFly 9.0.0.Final was just released and I'm working on updating the cartridge accordingly. I'll add a comment here when that's ready (should be some time tomorrow). Please hold off on testing until then. Thanks!

Comment 8 Farah Juma 2015-07-03 18:19:48 UTC
The WF 9 cart has now been updated to 9.0.0.Final. QE please test.
Thanks!

Comment 9 XiuJuan Wang 2015-07-06 05:55:06 UTC
The bug has been fixed.
Thanks!


Note You need to log in before you can comment on or make changes to this bug.