5 Replies Latest reply: Apr 24, 2013 7:31 AM by TonieD

Cannot connect to apexlistener via SQL developer.

TonieD Apr 24, 2013 3:56 AM

1. Re: Cannot connect to apexlistener via SQL developer.

TonieD Apr 24, 2013 4:03 AM (in response to TonieD)

Further investigation;

In my custom conf_dir there is no file apex_al.xml but fblns01_al.xml instead.
how to correct this?
Like Show 0 Likes (0)

Actions
2. Re: Cannot connect to apexlistener via SQL developer.

TonieD Apr 24, 2013 5:26 AM (in response to TonieD)

Turned debug on in defaults.xml;

[#|2013-04-24T12:19:47.840+0200|SEVERE|glassfish3.1.2|null|_ThreadID=453;_ThreadName=Thread-2;|No pool found for: http://.......:8080/apex/oauth2/token|#]

[#|2013-04-24T12:19:47.840+0200|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=453;_ThreadName=Thread-2;|Could not find any database pool to use for this request|#]

[#|2013-04-24T12:19:47.841+0200|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=453;_ThreadName=Thread-2;|Applied database connection info|#]

[#|2013-04-24T12:19:47.841+0200|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=453;_ThreadName=Thread-2;|Attempting to process with PL/SQL Gateway|#]

[#|2013-04-24T12:19:47.842+0200|INFO|glassfish3.1.2|null|_ThreadID=453;_ThreadName=Thread-2;|No DB connection found for: /apex/oauth2/token|#]

[#|2013-04-24T12:19:47.844+0200|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=453;_ThreadName=Thread-2;|Not processed as PL/SQL Gateway request|#]

[#|2013-04-24T12:19:47.844+0200|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=453;_ThreadName=Thread-2;|Attempting to process as a RESTful Service|#]

[#|2013-04-24T12:19:47.863+0200|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=453;_ThreadName=Thread-2;|Default Database connection does not exist|#]

[#|2013-04-24T12:19:47.952+0200|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=453;_ThreadName=Thread-2;|Choosing: oracle.dbtools.rt.oauth.TokenHandler as current candidate with score: Score [handle=null, score=0, scope=SecurityConfig [constraint=secure, realm=OAUTH_CLIENT, logonConfig=LogonConfig [logonForm=null, logonFailed=null]], originsAllowed=[], corsEnabled=true]|#]

[#|2013-04-24T12:19:47.954+0200|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=453;_ThreadName=Thread-2;|Determining if request can be dispatched as a Tenanted RESTful Service|#]

[#|2013-04-24T12:19:47.954+0200|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=453;_ThreadName=Thread-2;|Request path has one path segment, continuing processing|#]

[#|2013-04-24T12:19:47.955+0200|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=453;_ThreadName=Thread-2;|No JDBC Principal established, cannot dispatch|#]

[#|2013-04-24T12:19:47.956+0200|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=453;_ThreadName=Thread-2;|Chose oracle.dbtools.rt.oauth.TokenHandler as the final candidate with score: Score [handle=null, score=0, scope=SecurityConfig [constraint=secure, realm=OAUTH_CLIENT, logonConfig=LogonConfig [logonForm=null, logonFailed=null]], originsAllowed=[], corsEnabled=true] for: POST oauth2/token|#]

[#|2013-04-24T12:19:47.960+0200|SEVERE|glassfish3.1.2|null|_ThreadID=453;_ThreadName=Thread-2;|The pool named: apex_al does not exist|#]

[#|2013-04-24T12:19:47.965+0200|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=453;_ThreadName=Thread-2;|oauth2/token authorized as: IsZv_-R511-vq79m880SQA..|#]

[#|2013-04-24T12:19:47.965+0200|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=453;_ThreadName=Thread-2;|must be accessed over https only|#]
Like Show 0 Likes (0)

Actions
3. Re: Cannot connect to apexlistener via SQL developer.

svms Apr 24, 2013 5:52 AM (in response to TonieD)

The pool named: apex_al does not exist
This is the exact same error that is happening here

{message:id=10965545}

apex_al.xml contains passwords for RESTful service's users.

It means it asks for RESTful services that are not configured during apex.war configuration.

Actually it's not a critical error. I was able to connect to administration even with this error. Thus it's also trying to apply a direct database connection.

It's according to my observations.
I think you need to pay attention on another error
No DB connection found for: /apex/oauth2/token
Try to check connection settings in defaults.xml

Regards,
Igor

Edited by: svms on 24.04.2013 16:34
Like Show 0 Likes (0)

Actions
4. Re: Cannot connect to apexlistener via SQL developer.

svms Apr 24, 2013 6:05 AM (in response to TonieD)

[#|2013-04-24T12:19:47.965+0200|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=453;_ThreadName=Thread-2;|must be accessed over https only|#]
Also if it's
http/1.1 403 Forbidden
try to add

<entry key="security.verifySSL">false</entry>
in defaults.xml.

Regards,
Igor
Like Show 0 Likes (0)

Actions
5. Re: Cannot connect to apexlistener via SQL developer.

TonieD Apr 24, 2013 7:31 AM (in response to TonieD)

Hi Igor,

this setting + stop and start of the glassfish domain did the trick!

<entry key="security.verifySSL">false</entry>

Thanks!

Regards,
Ton
Like Show 0 Likes (0)

Actions

Go to original post