| Author |
Message
|
| marcin.kasinski |
 Posted: Tue Dec 16, 2014 2:23 am Post subject: Broker Java classes trace com.ibm.broker.trace |
 |
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
Environment: WMB 8.0.0.3
I have problem with LDAPSecurityProvider.
I would like to trace LDAP communication to investigate source of my problem.
I know that LDAPSecurityProvider uses com.ibm.broker.trace.Trace class.
I tought that this is JAVA interface for standard broker service trace.
How I test it (turn service trace on):
| Code: |
mqsichangetrace MBBROKER -t -b -l normal
Here I test my flow
mqsichangetrace MBBROKER -t -b -l none
mqsireadlog MBBROKER -t -b agent -f -o flowtrace.xml
mqsiformatlog -i flowtrace.xml -o userflowtrace.txt
|
Problem is that using service trace I can not see LDAP communication information in my service trace.
Can you tell me how to enable this trace (com.ibm.broker.trace.Trace) to see my LDAP communication trace and where this trace file is placed ?
_________________
Marcin |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Dec 16, 2014 5:44 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
...
Are you using built-in LDAP Security Provider, or are you using java code you've written and you're trying to use the Trace class to add information to the service trace?
If you're doing the later, it's possible that your trace messages are getting written to the standard out, rather than the service trace. There's an eg specific stdout file (on windows it's a console.out file that contains both stdout and stderr). |
|
| Back to top |
|
|
| marcin.kasinski |
| Posted: Tue Dec 16, 2014 7:09 am Post subject: |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
| mqjeff wrote: |
...
Are you using built-in LDAP Security Provider, or are you using java code you've written and you're trying to use the Trace class to add information to the service trace?
If you're doing the later, it's possible that your trace messages are getting written to the standard out, rather than the service trace. There's an eg specific stdout file (on windows it's a console.out file that contains both stdout and stderr). |
I'm using built-in LDAP Security Provider.
I know that it uses com.ibm.broker.securityProviders.MbLDAPSecurityProvider class from built-in ldapSecurityProvider.jar
I know that this class uses Trace class.
My question is:
How can I set this trace and where can I read this trace info.
_________________
Marcin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Dec 16, 2014 7:25 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| You'll probably need to open a PMR. |
|
| Back to top |
|
|
| stoney |
| Posted: Tue Dec 16, 2014 11:34 am Post subject: Re: Broker Java classes trace com.ibm.broker.trace |
|
|
Centurion
Joined: 03 Apr 2013
Posts: 140
|
| marcin.kasinski wrote: |
Environment: WMB 8.0.0.3
| Code: |
mqsichangetrace MBBROKER -t -b -l normal
Here I test my flow
mqsichangetrace MBBROKER -t -b -l none
mqsireadlog MBBROKER -t -b agent -f -o flowtrace.xml
mqsiformatlog -i flowtrace.xml -o userflowtrace.txt
|
|
These commands are tracing the broker, rather than the execution group and any deployed message flows. Have you tried tracing the execution group? |
|
| Back to top |
|
|
|
|
