Bug 1201776 - NullPointerException in Business Central output after installation
Summary: NullPointerException in Business Central output after installation
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Installer
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: DR1
: 6.2.0
Assignee: manstis
QA Contact: Dominik Hanak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-13 13:26 UTC by Tomas Livora
Modified: 2020-03-27 19:02 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:02:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
BRMS Business Central console output (102.48 KB, text/plain)
2015-03-13 13:26 UTC, Tomas Livora
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1199215 0 medium CLOSED NullPointerException during fresh Business Central startup 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1202285 0 unspecified CLOSED javax.ejb.EJBException: java.lang.NullPointerException 2021-02-22 00:41:40 UTC

Internal Links: 1199215 1202285

Description Tomas Livora 2015-03-13 13:26:39 UTC
Created attachment 1001374 [details]
BRMS Business Central console output

Description of problem:
There is NullPointerException in server output when you run Business Central after installation. It is not present there if you use application distributed in deployable ZIP file so it is probably caused by some wrong settings in installer distribution.

Version-Release number of selected component (if applicable):
6.1.0 ER6

Steps to Reproduce:
1. Run the installer.
2. Finish the installation following the default scenario.
3. Run the server with Business Central.
4. See console output.

Actual results:
javax.ejb.EJBException: java.lang.NullPointerException

Expected results:
No exceptions in the console output.

Additional info:
This bug can be found in both BPM Suite and BRMS. So far, I have not found any functionality loss. However, I think it should be fixed since it can cause some problems in the future.

Comment 1 Thomas Hauser 2015-03-13 21:11:37 UTC
Hi Tomas,

I seem to be able to reproduce this issue on the deployable zip.

Comment 2 manstis 2015-03-16 15:02:08 UTC

*** This bug has been marked as a duplicate of bug 1199215 ***

Comment 5 Dominik Hanak 2015-09-30 05:51:12 UTC
Hi,

I am unable to reproduce this with DR1 build on both BRMS and BPMS.
Same goes for deployable zips.

Marking as Verified.


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