• State Not Answered
  • Replies 10 replies
  • Subscribers 8 subscribers
  • Views 3300 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Administration

I'm trying to do an upgrade from 7.8 to 7.9. I got a clean install of 7.9 ru

dsmithgxp
Certified Associate Developer
I'm trying to do an upgrade from 7.8 to 7.9. I got a clean install of 7.9 running using the Configure Script then I tried migrating the data from our 7.8 instance into the 7.9 install. I followed the migration guide (forum.appian.com/.../Migration_Guide.html. I got through starting up the engines and the search-sever but can't seem to successfully start the application server. Jboss seems to blow up after it installs the plugins and consistently breaking with the following error.

13:01:56,670 INFO [stdout] (ServerService Thread Pool -- 78) 2015-05-06 13:01:56,670 [ServerService Thread Pool -- 78] ERROR com.appiancorp.suiteapi.common.TypedValueReturnConverter - Error converting value of type 1780

13:01:56,683 INFO [stdout] (ServerService Thread Pool -- 78) 2015-05-06 13:01:56,674 [ServerService Thread Pool -- 78] ERROR com.appiancorp.kougar.mapper.returns.MapReturnConverter - MapR...

server.log

OriginalPostID-148090

OriginalPostID-148090

  Discussion posts and replies are publicly visible

Parents
  • 0
    Appian Employee
    If you search in your logs you'll see the new timeout setting is not being read:

    "Timeout after [300] seconds waiting for service container stability. "

    It is still using the 300 seconds limit which is the default.

    To address this issue:

    1. Stop JBoss
    2. Delete C:\\jboss-eap-6.3\\standalone\\log\\*.log
    3. MANUALLY deploy the attached SUPPORT_standalone.conf.bat under C:\\jboss-eap-6.3\\bin
    4. Rename C:\\jboss-eap-6.3\\bin\\SUPPORT_standalone.conf.bat to standalone.conf.bat
    5. Start JBoss
    6. After the start-up search for jboss.as.management.blocking.timeout in the server.log. You should see this:

    jboss.as.management.blocking.timeout=1500

    SUPPORT_standalone.conf.bat

Reply
  • 0
    Appian Employee
    If you search in your logs you'll see the new timeout setting is not being read:

    "Timeout after [300] seconds waiting for service container stability. "

    It is still using the 300 seconds limit which is the default.

    To address this issue:

    1. Stop JBoss
    2. Delete C:\\jboss-eap-6.3\\standalone\\log\\*.log
    3. MANUALLY deploy the attached SUPPORT_standalone.conf.bat under C:\\jboss-eap-6.3\\bin
    4. Rename C:\\jboss-eap-6.3\\bin\\SUPPORT_standalone.conf.bat to standalone.conf.bat
    5. Start JBoss
    6. After the start-up search for jboss.as.management.blocking.timeout in the server.log. You should see this:

    jboss.as.management.blocking.timeout=1500

    SUPPORT_standalone.conf.bat

Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.