Bamboo server ouath giving 500 error

sagar rudrawar

Hi, 

I'm getting internal server error while connecting to bamboo server (version 6.4.1). Can someone help?

error log:

 

Internal server error
Go to...
Site homepage
A system error has occurred - our apologies!

Please create a problem report on our support system at https://support.atlassian.com with the following information:

a description of your problem and what you were doing at the time it occurred
cut & paste the error and system information found below
attach the atlassian-bamboo.log log file found in your application home.
We will respond as promptly as possible.
Thank you!

 

Version: 6.4.1
Build: 60405
Build Date: 19 Mar 2018

Request information:
Request URL: http://xxx:8085/500.action
Scheme: http
Server: xxx
Port: 8085
URI: /500.action
Context path:
Servlet path: /500.action
Path info:
Query string:
Stack Trace:

 

java.lang.reflect.UndeclaredThrowableException at com.sun.proxy.$Proxy1413.getSchema(Unknown Source) at com.atlassian.bamboo.utils.db.AbstractDbmsBean.getSchemaUncached(AbstractDbmsBean.java:419) at com.atlassian.bamboo.utils.db.AbstractDbmsBean.getSchema(AbstractDbmsBean.java:411) at sun.reflect.GeneratedMethodAccessor2776.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) at com.sun.proxy.$Proxy94.getSchema(Unknown Source) at com.atlassian.bamboo.spring.AbstractTransactionalExecutor.lambda$null$0(AbstractTransactionalExecutor.java:56) at com.atlassian.bamboo.utils.BambooCallables.callUnchecked(BambooCallables.java:32) at com.atlassian.bamboo.spring.AbstractTransactionalExecutor.lambda$getSchemaName$1(AbstractTransactionalExecutor.java:56) at com.atlassian.bamboo.spring.PluginSpringHibernateTransactionalExecutor.lambda$null$0(PluginSpringHibernateTransactionalExecutor.java:56) at org.hibernate.jdbc.WorkExecutor.executeWork(WorkExecutor.java:37) at org.hibernate.internal.SessionImpl$1.accept(SessionImpl.java:2321) at org.hibernate.internal.SessionImpl$1.accept(SessionImpl.java:2318) at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.coordinateWork(JdbcCoordinatorImpl.java:314) at org.hibernate.internal.SessionImpl.doWork(SessionImpl.java:2340) at org.hibernate.internal.SessionImpl.doWork(SessionImpl.java:2325) at com.atlassian.bamboo.spring.PluginSpringHibernateTransactionalExecutor.lambda$toSpringCallback$1(PluginSpringHibernateTransactionalExecutor.java:54) at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:133) at 

 

Gerhard Forster

Hello Sagar,

unfortunately Internal Server error 500 can mean a lot of things as it is a general HTTP status code claiming that something went wrong on server side which could not be specified more precisely.

However, you mentioned this in the context of Oauth and that makes me believe that the issue ocurres when setting up or using Application links in Bamboo. Not sure what Atlassian application(s) you link to, e.g. Bitbucket Server or Jira, but you might navigate to Overview >> Application links and check the status there.

In a healthy situation it should show CONNECTED in green.

Note that you need to be admin on both sides to setup an Application link. Also an Application link is always 2-way, so reciprocal which means that it needs to work on the other side too. Hence you should check the same on your linked application.

Finally find attached this KB for your reference https://confluence.atlassian.com/bamboo/linking-to-another-application-360677713.html that also contains a great Application link troubleshooting link at its end.

On a side-note: The error snippet you added to your post points to Proxy. Possibly you have a reverse Procy in front of Bamboo and this causes your problem. Then, try to bypass your Proxy and see if the error goes away. If so, next go ahead and troubleshoot your Proxy configuration.

Hope this helps.

Cheers, Gerhard