Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

task.logmsg returning null

34 views
Skip to first unread message

Andrija

unread,
Mar 27, 2012, 4:37:15 AM3/27/12
to eddieh...@gmail.com
Hello All,

My initial question was about
task.logmsg("Something") returning null instead of the message string:
"Something"?

After Eddie Hartman's answer to check the method signature, this one
is resolved:
logmsg

public void logmsg(Object msg)

This method sends the specified message (msg) to whatever Log
Appenders have been defined for this AssemblyLine.

Specified by:
logmsg in interface TaskInterface

Parameters:
msg - The message

But this is what my question should have been:

I am not being able to see any log messages in TDI console editor,
what setting should I check in order to solve this? However I see my
logs on the file system, how I've defined them in solution/logs/ folder

Eddie Hartman

unread,
Mar 27, 2012, 5:28:39 AM3/27/12
to
When you run your AL from the CE, a Log Appender is added that allows
the CE to capture output and display this onscreen. If this is not
happening then it could be that a jar is corrupt. Also, check the
various log properties files under your SolDir/etc folder.

To write to the commandline you can use the Console Log Appender, or
with Javascript: java.lang.System.out.println("my message")

-Eddie

Andrija

unread,
Mar 27, 2012, 8:10:14 AM3/27/12
to
On Mar 27, 11:28 am, Eddie Hartman <eddiehart...@gmail.com> wrote:
> On Mar 27, 10:37 am, Andrija <andrij...@gmail.com> wrote:
>
>
>
> > Hello All,
>
> > My initial question was about
> > task.logmsg("Something") returning null instead of the message string:
> > "Something"?
>
> > After Eddie Hartman's answer to check the method signature, this one
> > is resolved:
> > logmsg
>
> > public void logmsg(Object msg)
>
> >     This method sends the specified message (msg) to whatever Log
> > Appenders have been defined for this AssemblyLine.
>
> >     Specified by:
> >         logmsg in interface TaskInterface
>
> >     Parameters:
> >         msg - The message
>
> > But this is what my question should have been:
I have substitued the cli.jar file in TDI installation path:
...\IBM\TDI\V7.1\jars\common

Version which came with TDI installation is from 5/11/2010 and I have
replaced it with another version of cli.jar from 12/2/2011. This
solved my issue, I can now see logs regularly from TDI CE

Eddie Hartman

unread,
Mar 29, 2012, 3:57:25 AM3/29/12
to
It didn't help to just apply the latest fixpack, Andrija?

-Eddie

Andrija SM

unread,
Mar 29, 2012, 6:01:30 AM3/29/12
to
On another machine it worked without any fix pack so it did not cross my mind to apply a fixpack, but you are right it would probably also fix the issue, since I would get a newer cli.jar with it
0 new messages