OpenBankProject / OpenBankProject/OBP-API

Error runing OBP-API using IntelliJ IDEA

Open
#2,365 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
1.7k
Forks
482
Avg merge
1d 12h
Merged PRs (30d)
15

Description

I have been facing issues while running the OBP-API using the steps mentioned in this link: Run via IntelliJ IDEA.

image

Note: It is important to note that the build was successful. There were only 80+ warnings present.

Following are the exception logs:

13:27:00.688 [qtp180353207-16] DEBUG org.eclipse.jetty.server.HttpChannel - handle //localhost:8080/ HttpChannelOverHttp@34c58f5f{s=HttpChannelState@2d951605{s=IDLE rs=BLOCKING os=OPEN is=IDLE awp=false se=false i=true al=0},r=1,c=false/false,a=IDLE,uri=//localhost:8080/,age=0} 
13:27:00.688 [qtp180353207-16] DEBUG org.eclipse.jetty.server.HttpChannelState - handling HttpChannelState@2d951605{s=IDLE rs=BLOCKING os=OPEN is=IDLE awp=false se=false i=true al=0}
13:27:00.688 [qtp180353207-16] DEBUG org.eclipse.jetty.server.HttpChannel - action DISPATCH HttpChannelOverHttp@34c58f5f{s=HttpChannelState@2d951605{s=HANDLING rs=BLOCKING os=OPEN is=IDLE awp=false se=false i=true al=0},r=1,c=false/false,a=HANDLING,uri=//localhost:8080/,age=0}
13:27:00.688 [qtp180353207-16] DEBUG org.eclipse.jetty.server.Server - REQUEST GET / on HttpChannelOverHttp@34c58f5f{s=HttpChannelState@2d951605{s=HANDLING rs=BLOCKING os=OPEN is=IDLE awp=false se=false i=true al=0},r=1,c=false/false,a=HANDLING,uri=//localhost:8080/,age=0}
13:27:00.688 [qtp180353207-16] DEBUG org.eclipse.jetty.server.handler.ContextHandler - scope null||/ @ o.e.j.w.WebAppContext@2e807c54{/,file:///C:/Users/My-COMPUTER/Desktop/OpenBank/OBP-API/obp-api/src/main/webapp/,UNAVAILABLE}{file:/C:/Users/My-COMPUTER/Desktop/OpenBank/OBP-API/obp-api/src/main/webapp}
13:27:00.688 [qtp180353207-16] DEBUG org.eclipse.jetty.server.HttpChannelState - sendError HttpChannelState@2d951605{s=HANDLING rs=BLOCKING os=OPEN is=IDLE awp=false se=false i=true al=0}
13:27:00.688 [qtp180353207-16] DEBUG org.eclipse.jetty.server.Server - handled=true async=false committed=true on HttpChannelOverHttp@34c58f5f{s=HttpChannelState@2d951605{s=HANDLING rs=BLOCKING os=OPEN is=IDLE awp=false se=true i=true al=0},r=1,c=false/false,a=HANDLING,uri=//localhost:8080/,age=0}
13:27:00.688 [qtp180353207-16] DEBUG org.eclipse.jetty.server.HttpChannelState - unhandle HttpChannelState@2d951605{s=HANDLING rs=BLOCKING os=OPEN is=IDLE awp=false se=true i=true al=0}
13:27:00.688 [qtp180353207-16] DEBUG org.eclipse.jetty.server.HttpChannelState - nextAction(false) SEND_ERROR HttpChannelState@2d951605{s=HANDLING rs=BLOCKING os=OPEN is=IDLE awp=false se=false i=false al=0}
13:27:00.688 [qtp180353207-16] DEBUG org.eclipse.jetty.server.HttpChannel - action SEND_ERROR HttpChannelOverHttp@34c58f5f{s=HttpChannelState@2d951605{s=HANDLING rs=BLOCKING os=OPEN is=IDLE awp=false se=false i=false al=0},r=1,c=false/false,a=HANDLING,uri=//localhost:8080/,age=0}
13:27:00.689 [qtp180353207-16] DEBUG org.eclipse.jetty.io.ChannelEndPoint - filled 0 HeapByteBuffer@2e3be707[p=0,l=0,c=8192,r=0]={<<<>>>GET / HTT...\x00\x00\x00\x00\x00\x00\x00}

I have been using the following:

  • JDK 1.8
  • IntelliJ IDEA 2023.3.4

, and configuration of the props file,

  • default.props

image

  • test.default.props

image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with obp-api/src/main/docs/glossary/Run_via_IntelliJ_IDEA.md, then compare the reported IntelliJ configuration, default.props, test.default.props, and Jetty logs. Reproduce the run with JDK 1.8 and IntelliJ IDEA 2023.3.4. Done means the startup issue is reproducible and the documentation or configuration guidance clearly records the confirmed resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, scala
Domain
api, backend, developer-experience
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.