How to fix a maxQueueLength error in Tibco?
up vote
0
down vote
favorite
I get this error in TIBCO Administrator Log:
(BW-EXT-LOG-200000 njams: maxQueueLength(=20) is reached.)
My client returns:
Connexion to refused.
Everything returns to normal after restarting the instances, but it takes a few minutes and I get the same error.
tibco tibco-ems tibco-business-works tibco-topic tibco-designer
add a comment |
up vote
0
down vote
favorite
I get this error in TIBCO Administrator Log:
(BW-EXT-LOG-200000 njams: maxQueueLength(=20) is reached.)
My client returns:
Connexion to refused.
Everything returns to normal after restarting the instances, but it takes a few minutes and I get the same error.
tibco tibco-ems tibco-business-works tibco-topic tibco-designer
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I get this error in TIBCO Administrator Log:
(BW-EXT-LOG-200000 njams: maxQueueLength(=20) is reached.)
My client returns:
Connexion to refused.
Everything returns to normal after restarting the instances, but it takes a few minutes and I get the same error.
tibco tibco-ems tibco-business-works tibco-topic tibco-designer
I get this error in TIBCO Administrator Log:
(BW-EXT-LOG-200000 njams: maxQueueLength(=20) is reached.)
My client returns:
Connexion to refused.
Everything returns to normal after restarting the instances, but it takes a few minutes and I get the same error.
tibco tibco-ems tibco-business-works tibco-topic tibco-designer
tibco tibco-ems tibco-business-works tibco-topic tibco-designer
edited Nov 9 at 16:53
Graham
3,396123558
3,396123558
asked Nov 9 at 15:29
Hichem
1
1
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
Sounds like your maxMsgs property of that queue is set to 20 ? You can check this by connecting with tibemsadmin and show/changing queue properties. For Example:
tcp://localhost:7222> show queue Q1
Queue: Q1
Type: static
Properties: *prefetch=5,maxMsgs=1000,*store=$sys.nonfailsafe
JNDI Names: <none>
Bridges: <none>
Receivers: 0
Pending Msgs: 0, (0 persistent)
Delivered Msgs: 0
Pending Msgs Size: 0.0 Kb, (0.0 Kb persistent)
You can change it like this:
tcp://localhost:7222> setprop queue Q1 maxmsgs=1000
add a comment |
up vote
0
down vote
Issue Fixed
A process remained active so it allocated a space in the memory that it would not release.
This process contained a requestor for which the timeOut is not configured. it waited endlessly a response from the process containing the receiver which did not respond due to an access issue to an external database.
Best Regards.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Sounds like your maxMsgs property of that queue is set to 20 ? You can check this by connecting with tibemsadmin and show/changing queue properties. For Example:
tcp://localhost:7222> show queue Q1
Queue: Q1
Type: static
Properties: *prefetch=5,maxMsgs=1000,*store=$sys.nonfailsafe
JNDI Names: <none>
Bridges: <none>
Receivers: 0
Pending Msgs: 0, (0 persistent)
Delivered Msgs: 0
Pending Msgs Size: 0.0 Kb, (0.0 Kb persistent)
You can change it like this:
tcp://localhost:7222> setprop queue Q1 maxmsgs=1000
add a comment |
up vote
0
down vote
Sounds like your maxMsgs property of that queue is set to 20 ? You can check this by connecting with tibemsadmin and show/changing queue properties. For Example:
tcp://localhost:7222> show queue Q1
Queue: Q1
Type: static
Properties: *prefetch=5,maxMsgs=1000,*store=$sys.nonfailsafe
JNDI Names: <none>
Bridges: <none>
Receivers: 0
Pending Msgs: 0, (0 persistent)
Delivered Msgs: 0
Pending Msgs Size: 0.0 Kb, (0.0 Kb persistent)
You can change it like this:
tcp://localhost:7222> setprop queue Q1 maxmsgs=1000
add a comment |
up vote
0
down vote
up vote
0
down vote
Sounds like your maxMsgs property of that queue is set to 20 ? You can check this by connecting with tibemsadmin and show/changing queue properties. For Example:
tcp://localhost:7222> show queue Q1
Queue: Q1
Type: static
Properties: *prefetch=5,maxMsgs=1000,*store=$sys.nonfailsafe
JNDI Names: <none>
Bridges: <none>
Receivers: 0
Pending Msgs: 0, (0 persistent)
Delivered Msgs: 0
Pending Msgs Size: 0.0 Kb, (0.0 Kb persistent)
You can change it like this:
tcp://localhost:7222> setprop queue Q1 maxmsgs=1000
Sounds like your maxMsgs property of that queue is set to 20 ? You can check this by connecting with tibemsadmin and show/changing queue properties. For Example:
tcp://localhost:7222> show queue Q1
Queue: Q1
Type: static
Properties: *prefetch=5,maxMsgs=1000,*store=$sys.nonfailsafe
JNDI Names: <none>
Bridges: <none>
Receivers: 0
Pending Msgs: 0, (0 persistent)
Delivered Msgs: 0
Pending Msgs Size: 0.0 Kb, (0.0 Kb persistent)
You can change it like this:
tcp://localhost:7222> setprop queue Q1 maxmsgs=1000
answered Nov 9 at 17:02
Axel Podehl
1,5091415
1,5091415
add a comment |
add a comment |
up vote
0
down vote
Issue Fixed
A process remained active so it allocated a space in the memory that it would not release.
This process contained a requestor for which the timeOut is not configured. it waited endlessly a response from the process containing the receiver which did not respond due to an access issue to an external database.
Best Regards.
add a comment |
up vote
0
down vote
Issue Fixed
A process remained active so it allocated a space in the memory that it would not release.
This process contained a requestor for which the timeOut is not configured. it waited endlessly a response from the process containing the receiver which did not respond due to an access issue to an external database.
Best Regards.
add a comment |
up vote
0
down vote
up vote
0
down vote
Issue Fixed
A process remained active so it allocated a space in the memory that it would not release.
This process contained a requestor for which the timeOut is not configured. it waited endlessly a response from the process containing the receiver which did not respond due to an access issue to an external database.
Best Regards.
Issue Fixed
A process remained active so it allocated a space in the memory that it would not release.
This process contained a requestor for which the timeOut is not configured. it waited endlessly a response from the process containing the receiver which did not respond due to an access issue to an external database.
Best Regards.
answered Nov 14 at 15:59
Hichem
1
1
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53228669%2fhow-to-fix-a-maxqueuelength-error-in-tibco%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown