# Jboss process not working

{% hint style="info" %}
Note: If the Jboss instance / server is behind a Bastion server or similar use ssh tunnel to access the instance

```bash
ssh -i ~/.ssh/KEY_NAME -L 9990:IP_OF_REMOTE_SERVER:9990 -N USERNAME@IP_OF_BASTION_SERVER
```

* Once SSH tunnel is active access website via URL with localhost:

```
http://localhost:9990/console/App.html#server-instances
```

{% endhint %}

### Steps:

1\. Stop processes\
2\. Check processes on Linux\
3\. If still active use `kill` and wait\
4\. If still active use `kill -9`\
5\. Try to start the server manually with command:

```
manage-instance.sh -i instance_name start
```

\
6\. If failed, restart whole AWS instance via console or by using `shutdown -r now`\
7\. Check process

```bash
ps -ef | grep java | grep Server:INSTANCE_NAME # there should be a process
```

{% hint style="info" %}
Note: Needs refresh once you hit start/stop button on the web interface (old app) since it does not update status correctly unless you use refresh
{% endhint %}

To check the logs use:

```bash
tail -200f /opt/jboss/jboss-eap-6.0/domain/servers/INSTANCE_NAME/log/drm.log
```

{% hint style="info" %}
Note: Request times out but best way is to check logs to see if it starts properly. Check for the below:

```java
INFO  2022-05-03 09:26:47,284 [EDRMStartUp,MSC service thread 1-6]

******************************************************************

 Starting Axeda Enterprise Server 6.8.2.2 112217 (2015/01/26 13:11:58 EST) Release

 Protected by US Patent No. 6,757,714.

 Customizations:

******************************************************************
```

* Then refresh page to see if the tick is there
  {% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.arkannis.net/software/jboss/jboss-process-not-working.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.