Skip to Main Content

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

bea.jolt.ServiceException: Service is not available:Test

Hrushi AgrawalMar 7 2019 — edited Mar 7 2019

Hi all,

I have created a new service Test at the Tuxedo server. when I boot the server the service is boot successfully.

boot log:

pastedImage_0.png

===================================================

Ubbconfig File:

GROUPS

GROUP1 LMID=emple GRPNO=1

OPENINFO=NONE

*SERVERS

DEFAULT:

JREPSVR SRVGRP=GROUP1 SRVID=2 GRACE=0 CLOPT="-A -- -W -P /home/administrator/TuxSvc/jrepository"

JSL SRVGRP=GROUP1 SRVID=3 CLOPT="-A -- -n //192.168.81.156:7777 -m3 -M10 -x15 -d /dev/tcp"

evGtAddPrm00 SRVGRP=GROUP1 SRVID=10

Test SRVGRP=GROUP1 SRVID=11

*SERVICES

evGtAddPrm00 SVCTIMEOUT=0 TRANTIME=0

Test SVCTIMEOUT=0 TRANTIME=0

=================================================

Entry to make.sh:

buildserver -o Test -f Test.c -s Test

tmloadcf -y ubbrpc

tmboot -y

=======================================

Jrepository Entry:

add PKG/BULKPKG:EmpInfo:AllDataTypes:SeqElem:EmpInformation:evGtAddPrm00:Test:

add SVC/Test:bt=FML32:ex=0:BT=FML32:vs=4:bp:pf=33554433:po=1:pa=rw:pn=GENERATION:pt=integer:ep:bp:pf=33554434:po=1:pa=rw:\

pn=DIRECTIVE:pt=integer:ep:

===============================================

tmadmin psc command output:

Service Name Routine Name Prog Name Grp Name ID Machine # Done Status

------------ ------------ --------- -------- -- ------- ------ ------

AllDataTypes AllDataTypes AllDataTy+ GROUP1 4 emple 0 AVAIL

EmpInfo EmpInfo EmpInfo GROUP1 5 emple 0 AVAIL

SeqElem SeqElem SeqElem GROUP1 6 emple 0 AVAIL

NullElems NullElems NullElems GROUP1 7 emple 0 AVAIL

ReceiveChar+ ReceiveChar+ ReceiveCh+ GROUP1 8 emple 0 AVAIL

EmpInformat+ EmpInformat+ EmpInform+ GROUP1 9 emple 0 AVAIL

evGtAddPrm00 evGtAddPrm00 evGtAddPr+ GROUP1 10 emple 0 AVAIL

Test Test Test GROUP1 11 emple 0 AVAIL

========================================================================

But when i try to call my service by jolt client, but the server gave me the error,

Error occurred when invoking service Test, due to bea.jolt.ServiceException: Service is not available:Test

Can anyone help me with this?

I'm attaching all the necessary file you need.

Thanks

Som

Comments

vikram thakur

Hi,

Just curious, can you try without the double-quotes for region?

From:

region=us-"ashburn-1"

To:

region=us-ashburn-1

Thanks,

Vikram

3622227

Thanks Vikram for pointing out. Still the same without any quotes.

I was desperate and trying different options and tried with quotes. Initial config file created has no quotes and i reverted back what it was.

Tried with different region too but no luck.

$cat config

[DEFAULT]

user=ocid1.user.oc1..aaaaxxxxxxxxxrhbpmiv3vmx3fanyfotrjnfa

fingerprint=5e:e3:43:c6:b3:64:73:df:a4:e2:a6:a3:35:e6:39:e3

key_file=/home/.oci/oci_api_key.pem

tenancy=ocid1.tenancy.oc1..aaaaaxjjaryrxflyysgaganbmybm

region=us-ashburn-1

I am out of ideas and any help in this regard is greatly appreciated.

vikram thakur
Answer

Understood. I also noticed the file timestamp for oci_api_key_public.pem, oci_api_key.pem and config are all the same. So I did not think the config file was manually updated.

Was yours an auto install or manual? From documentation, it almost looks like some of your information may be incorrect in the config. Clock, I remember, you mentioned is in sync.

---- from doc (Ref: https://docs.us-phoenix-1.oraclecloud.com/Content/API/References/apierrors.htm#ErrorDetailsandTroubleshooting )

html status code: 401

  • Missing or incorrect authentication information. Verify that all the required information (tenant OCID, user OCID, fingerprint, and private key) is provided and accurate. Verify that the public key corresponding to the fingerprint has been uploaded for the user. For more information, see Required Keys and OCIDs.
  • Clock skew. This status code is returned if the client's clock is skewed more than 5 minutes from the server's clock. For more information, see Maximum Allowed Client Clock Skew.
  • API request signature error. This status code is returned if a required header is missing from a signing string. For more information, see Request Signatures.

Thanks,

Vikram

Marked as Answer by 3622227 · Mar 17 2018
3622227

I did a fresh install on a OCI compute instance just to see if it has anything to do with my install scripts.

Anyway I tried with a new user instead of a service administrator and it worked ...YAYYYYYYYYYYYYYYYYYYYY

Vikram thanks a lot man for your kind support and help.... Really appreciated.

[opc@shaikprod .oci]$ oci os ns get

{

  "data": "shaikscloud33"

}

User_ID7D0

I'm having same problem

User_YCV6N

Hi,
I was also facing similar issue as above followed the below steps ,but while trying initialKubeSetup its throwing 401,Can anyone
once in the BOAT, follow the below instructions -
Click on the user icon in the top right
Click on "User Settings"
Click on "API Keys"
Click on "Add API Key"
Either generate a keypair, or use your own
Copy the private key to the host machine
Copy the configuration file, and update your ~/.oci/config with the required information
image.png

I was having a similar problem when trying to create a PHP script to download an object from Object Storage via the API.

It turned out that the date format was the cause of the problem. Using date("r") from PHP will generate a date string like this:

Sat, 26 Oct 2024 15:52:49 +0000

However, I had to use a named timezone like GMT instead:

Sat, 26 Oct 2024 15:52:49 GMT

As soon as I made this change, it accepted the signature.

nausherwan adil

When you authenticate an OCI session, a new key pair and fingerprint are generated. However, the OCI console does not automatically update with the newly generated key pair and fingerprint.

There are two solutions to resolve this:

Create a new session using oci session authenticate. This will generate a new OCI config along with a new key pair. Then, upload the new public key to the OCI console under the API Key section.

Manually generate an API key, download the key pair, and upload the public key to the OCI console. Then, copy the newly generated key pair to your OCI config folder on your machine. Additionally, when a new API key is generated in the OCI console, update your OCI config file accordingly on your machine.

Following either of these approaches will resolve the issue.

1 - 8

Post Details

Added on Mar 7 2019
1 comment
318 views