Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error runing OBP-API using IntelliJ IDEA #2365

Open
madeline000 opened this issue Feb 16, 2024 · 4 comments
Open

Error runing OBP-API using IntelliJ IDEA #2365

madeline000 opened this issue Feb 16, 2024 · 4 comments

Comments

@madeline000
Copy link

madeline000 commented Feb 16, 2024

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

@ardatov
Copy link

ardatov commented Feb 26, 2024

Hello,
I had the same error. It’s so strange that the developers did not foresee this, but the error disappeared when I launched the redis in docker:

version: '3.8'
services:
  cache:
    image: redis
    restart: always
    ports:
      - '6379:6379'
    command: redis-server --save 20 1 --loglevel warning
    volumes:
      - cache:/data
volumes:
  cache:
    driver: local

@madeline000
Copy link
Author

Hi @ardatov,

So you mean to say, the steps I have mentioned above are good to go, and I just need to run Redis in a Docker?

Thank you

@ardatov
Copy link

ardatov commented Mar 5, 2024

Hi @ardatov,

So you mean to say, the steps I have mentioned above are good to go, and I just need to run Redis in a Docker?

Thank you

Hi @madeline000

Yes that should help

@madeline000
Copy link
Author

No that did not work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants