ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexWebSphere Message Broker SupportDev Broker stops responding

Post new topicReply to topic
Dev Broker stops responding View previous topic :: View next topic
Author Message
mpong
PostPosted: Tue Feb 06, 2018 11:37 am Post subject: Dev Broker stops responding Reply with quote

Centurion

Joined: 22 Jan 2010
Posts: 119

I noticed one of dev environment node is not responding to any of mqsi commands and writing below errors on logs every almost every 5 seconds.

stderr:

2018-02-06 13:20:56.699175 Execution group started. UUID is: '0fc91593-5401-0000-0080-e8c9e0b10a17'. Broker is: DRIIB9NODE
JVMJ9VM007E Command-line option unrecognised: Djavax.net.debug=true
main checker destroyed before initialisation completed, latest stage was JVM Startup, pid 17976, tid 17976, attempted stage was 11 and 10 stages completed

stdout:

Failed to open file /var/mqsi/registry/DRIIB9NODE/CurrentVersion/DSN/DSN/UserId with error No such file or directory
Failed to open file /var/mqsi/registry/DRIIB9NODE/CurrentVersion/DSN/DRIIB9NODE/UserId with error No such file or directory

I am trying to figure out what was changed by the developers. Meanwhile thought of sharing here to see if anyone can suggest
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Feb 06, 2018 11:59 am Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 24763
Location: Ohio, USA

someone's tried to switch on a Java debug option by adding an option to the java start command (badly). I would theorize there's a "-" missing.

They should try this instead.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
mpong
PostPosted: Tue Feb 06, 2018 1:29 pm Post subject: Reply with quote

Centurion

Joined: 22 Jan 2010
Posts: 119

yes, They tried to fetch JSSE logs. Below command is being used.

mqsichangeproperties DRIIB9NODE -e DRIIBINT -o ComIbmJVMManager -n jvmSystemProperty -v "Djavax.net.debug=true"
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Feb 06, 2018 1:40 pm Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 24763
Location: Ohio, USA

mpong wrote:
yes, They tried to fetch JSSE logs. Below command is being used.

mqsichangeproperties DRIIB9NODE -e DRIIBINT -o ComIbmJVMManager -n jvmSystemProperty -v "Djavax.net.debug=true"


Like I said, there's a "-" missing. See here, there's an example for jvmSystemProperty
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
mpong
PostPosted: Tue Feb 06, 2018 6:51 pm Post subject: Reply with quote

Centurion

Joined: 22 Jan 2010
Posts: 119

yes, the issue is resolved after resetting the value
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker SupportDev Broker stops responding
Jump to:



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.