Unable to restart JBoss after installation of v18.1

pauls985 over 6 years ago

I've just installed 18.1 for the first time on my test server.

When I try to start JBOSS, I'm getting an exception with the following error message :

08:40:58,269 WARN [org.jboss.as.ee] (MSC service thread 1-2) JBAS011006: Not installing optional component com.appiancorp.ap2.ListingsServletFilter due to an exception (enable DEBUG log level to see the cause)
08:40:58,503 WARN [org.jboss.as.ee] (MSC service thread 1-2) JBAS011006: Not installing optional component com.appiancorp.common.BootstrapSpringContextLoaderListener due to an exception (enable DEBUG log level to see the cause)
08:40:58,597 INFO [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-1) IJ020002: Deployed: file:/d:/appian/ear/suite.ear/unattended-request-poller.rar/
08:40:58,597 INFO [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-3) IJ020002: Deployed: file:/d:/appian/ear/suite.ear/email-poller.rar/
08:40:58,894 INFO [org.jboss.web] (ServerService Thread Pool -- 209) JBAS018210: Register web context: /suite
08:40:59,003 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 209) JBWEB000285: Error configuring application listener of class com.appiancorp.common.BootstrapSpringContextLoaderListener: java.lang.ClassNotFoundException: com.appiancorp.common.BootstrapSpringContextLoaderListener from [Module "deployment.suite.ear.web.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.6.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.6.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.6.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.6.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.6.Final-redhat-1]
at org.jboss.as.web.deployment.WebInjectionContainer.newInstance(WebInjectionContainer.java:78) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3294) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3780) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:163) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:61) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_121]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)

I have increased logging to DEBUG in logging.properties, but no further details are output.

Discussion posts and replies are publicly visible

0 aswinb608
A Score Level 2
over 6 years ago

Can you pls upload the full log...the above entries doesn't contain the root cause of the issue
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 pauls985 over 6 years ago in reply to aswinb608

I'm not seeing anyway to upload the log file ?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Carlos Santander
A Score Level 2
over 6 years ago in reply to pauls985

Click 'Reply' and then 'Use rich formatting'. Drag and drop your file into the editor box.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 pauls985 over 6 years ago in reply to Carlos Santander

[deleted]
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 aswinb608
A Score Level 2
over 6 years ago in reply to pauls985

Seems like you are not connected to the network of your organization when you are starting jboss. Can you please verify if you are connected to the VPN or network of your company because your IP host address that you are providing for this install is in the domain of your organization.....if this is not the issue then I don't know...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 prakashb9987
Certified Senior Developer
over 6 years ago

Hi pauls985,

Please check the permissions on the folder. The user that is running Appian on the server should have full read, write, and execute permissions for <APPIAN_HOME> and all subfolders and files.

And you should also give same permissions to license as well (<APPIAN_HOME>/server/_bin/k/linux64). After you've checked that, with the application server stopped, please do the following:

This could be one of the reason for the issue as you are logging in for the first time , try to delete the below lines under the file "<Appian_HOME>/ear/suite.ear/web.war/WEB-INF/web.xml" and then try again with the same credentails
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<cookie-config>
<http-only>true</http-only>
<secure>true</secure>
</cookie-config>
<tracking-mode>COOKIE</tracking-mode>

1) In <APPIAN_HOME>/ear if the marker files reads "suite.ear.undeployed" or suite.ear.failed", please rename is to "suite.ear.dodeploy".

2) Manually clear the osgi cache by deleting the contents of D:\\Appy711Trng\\ear\\suite.ear\\web.war\\WEB-INF\\osgi-cache .
(community.appian.com/.../kb-1124-osgi-related-errors-cause-jboss-deployment-to-fail)

3) Start the application server

Let me know if you still encounter the issue after performing these steps. Thanks.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Benhail
A Score Level 1
over 6 years ago

I feel, you haven't configured your custom.properties file. But can you upload the completed log?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Will Teoh over 6 years ago in reply to prakashb9987

We are also encountering the same issue and following the steps above still throwing the same error. Any updates on how to fix this?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Benhail
A Score Level 1
over 6 years ago in reply to Will Teoh

Have you deployed using the configuration using Configuration.Bat after the upgrade?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Will Teoh over 6 years ago in reply to Benhail

Yes.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel