WSIT/ACMS Important and Urgent problem.

[Jesús Paulino]

It's very URGENT. I'm making a prototype with WSIT on OpenVMS 7.3.2, ACMS.

Now I'm probing this environment with a J2EE object. This object call to generated WSIT objects. In execution obtain this message:

com.hp.wsi.WsiServerException: %NONAME-W-NOMSG, Message number 00000000

But, in JSP execution it's Ok, application runs fine, and return correct data.

Someone could help me???

Thanks,

[Steven Schweda]

No bets, but perhaps you're just seeing a
normal UNIX exit status of zero, which DCL
will interpret as a warning, but which some
other UNIX-like program will interpret as
success. There is a _POSIX_EXIT macro which
affects (at compile time) what exit() will
do (at run time), and some or all of this
stuff may have been built to accomodate the
normal UNIX behavior.

[Jesús Paulino]

But, I've just run java other time and hasn't connect with ACMS. I know this, looking for time in ACMSATR:

com.hp.wsi.WsiServerException: %NONAME-W-NOMSG, Message number 00000000
at com.hp.wsi.WsiJNIShell.n_invoke(Native Method)
at com.hp.wsi.WsiJNIShell.invoke(Unknown Source)
at TWE_A_PORTAL_CLIENTE.TWE_A_PORTAL_CLIENTEImpl.TWE_T_CONSULTA_CLIENTE_NIF(TWE_A_PORTAL_CLIENTEImpl.java)
at pruebas.ConsultaClienteNIF.callTWE_T_CONSULTA_CLIENTE_NIF(ConsultaClienteNIF.java)
at pruebas.ConsultaClienteNIF.main(ConsultaClienteNIF.java)
com.hp.wsi.WsiServerException: %NONAME-W-NOMSG, Message number 00000000
at com.hp.wsi.WsiJNIShell.n_invoke(Native Method)
at com.hp.wsi.WsiJNIShell.invoke(Unknown Source)
at TWE_A_PORTAL_CLIENTE.TWE_A_PORTAL_CLIENTEImpl.TWE_T_CONSULTA_CLIENTE_NIF(TWE_A_PORTAL_CLIENTEImpl.java)
at pruebas.ConsultaClienteNIF.callTWE_T_CONSULTA_CLIENTE_NIF(ConsultaClienteNIF.java)
at pruebas.ConsultaClienteNIF.main(ConsultaClienteNIF.java)
HISMAQ_$mc acmsatr

ATR> list /SINCE=10:!5
ACMS Log Report 26-JUN-2007 10:23:04.76
Type : ALL
Since : 26-JUN-2007 10:00:00.00
Before : *
Appl : *
Task : *
ID : *
User : *
Sub : *
Term : *
File : SYS$SYSROOT:[SYSERR]AUDIT.LOG;
************************************************************
End Report 26-JUN-2007 10:23:04.76

Thanks,

[Phil Hudson · Accepted solution]

Unfortunately the error message doesn't give us a clue on what may be going on. However, the fact that the generated JSP client does work means that the problem is most likely in the way that your client is calling into the generated Javabean.

Do you know if your client is correctly calling the ACMS SignIn() method call before attempting to call any of the task methods?

[Jesús Paulino]

Perfect, it was, AcmsSign and user definition.
Pojo run in out-of-proces fine.

A lot of thanks,

[Phil Hudson]

I am glad that I was able to help. Of course, it would have been easier to track down if the error message was accurate. I will put it on the WSIT team's list of problems to look at.

[Jesús Paulino]

I put AcmsSingIn(String user), and AcmsSignOut in my java code and its run fine.

Execution mode is out-of-process.