[PolyORB-users] error in test in testsuite/corba/cos/event ?

[Olga Dolbilina]

Hello!

I try to run test testsuit/corba/cos/event/typedtest_event with 
supplier.cmd and  get this result (see attachment).

Is this correct result?

I have similar result in testsuit/corba/cos/event/typedtest_event with 
consumer.cmd.


And more question:
I am runing typedtest_event, it  is ask "enter naming IOR [otherwise 
create one]", and after press enter, generate IOR.
When I am running typedtest_event on other console and take to it  this IOR.
I thing, second copy typedtest_event will work similar first it, but it 
is hangup :-(. The first running typedtest_event is working in this time.

Is I can use owen IOR, generate by test only?  What another IOR I can put?


Olga.


-------------- next part --------------
enter naming IOR [otherwise create one]: IOR:016e61672800000049444c3a6f6d672e6f72672f436f734e616d696e672f4e616d696e67436f6e746578743a312e3000020000000000000058000000010102000e0000003139322e3136382e31372e3138002580130000002f3030303030303031315430646561646330640001000000010000001c0000000100000001000100000000000001010002000000010101000201010004ffff7f34000000010100000e0000003139322e3136382e31372e3138000d80130000002f3030303030303031315430646561646330640000000000
HELP			print this message
QUIT			quit this shell
RUN			run <file of commands from this language>
SLEEP			sleep <seconds>
GET_TYPED_OBJECT			get_typed_object on <entity> from <channel>
CONNECT			connect <entity> to <channel>
CREATE			create <kind> <entity>
	<kind> in CHANNEL PULLCONSUMER PULLSUPPLIER PUSHCONSUMER PUSHSUPPLIER

> > create channel c
look for "AAAA	c	K_CHANNEL;"
register "AAAA	c	K_CHANNEL;" in naming context
append "AAAA	c	K_CHANNEL;" to naming context
AAAA ... c	K_CHANNEL	NOBJECT
> create pushsupplier pss
look for "AAAA	pss	K_PUSHSUPPLIER;"
AAAA ... c	K_CHANNEL	NOBJECT
register "AAAA	pss	K_PUSHSUPPLIER;" in naming context
AAAA ... c	K_CHANNEL	NOBJECT
append "AAAA	pss	K_PUSHSUPPLIER;" to naming context
AAAA ... c	K_CHANNEL	NOBJECT
AAAA ... pss	K_PUSHSUPPLIER	NOBJECT
> create pullsupplier pls
look for "AAAA	pls	K_PULLSUPPLIER;"
AAAA ... c	K_CHANNEL	NOBJECT
AAAA ... pss	K_PUSHSUPPLIER	NOBJECT
register "AAAA	pls	K_PULLSUPPLIER;" in naming context
AAAA ... c	K_CHANNEL	NOBJECT
AAAA ... pss	K_PUSHSUPPLIER	NOBJECT
append "AAAA	pls	K_PULLSUPPLIER;" to naming context
AAAA ... c	K_CHANNEL	NOBJECT
AAAA ... pss	K_PUSHSUPPLIER	NOBJECT
AAAA ... pls	K_PULLSUPPLIER	NOBJECT
> connect pss to c
look for "AAAA	c	K_CHANNEL;"
AAAA ... c	K_CHANNEL	NOBJECT
AAAA ... pss	K_PUSHSUPPLIER	NOBJECT
AAAA ... pls	K_PULLSUPPLIER	NOBJECT
look for "AAAA	pss	K_PUSHSUPPLIER;"
AAAA ... c	K_CHANNEL	NOBJECT
AAAA ... pss	K_PUSHSUPPLIER	NOBJECT
AAAA ... pls	K_PULLSUPPLIER	NOBJECT
syntax error
> connect pls to c
look for "AAAA	c	K_CHANNEL;"
AAAA ... c	K_CHANNEL	NOBJECT
AAAA ... pss	K_PUSHSUPPLIER	NOBJECT
AAAA ... pls	K_PULLSUPPLIER	NOBJECT
look for "AAAA	pls	K_PULLSUPPLIER;"
AAAA ... c	K_CHANNEL	NOBJECT
AAAA ... pss	K_PUSHSUPPLIER	NOBJECT
AAAA ... pls	K_PULLSUPPLIER	NOBJECT
> sleep 6
> produce "running test 1" in pss
raise CONSTRAINT_ERROR
s-valenu.adb:75 explicit raise
Exception name: CONSTRAINT_ERROR
Message: s-valenu.adb:75 explicit raise

> sleep 6
> produce "running test 2" in pss
raise CONSTRAINT_ERROR
s-valenu.adb:75 explicit raise
Exception name: CONSTRAINT_ERROR
Message: s-valenu.adb:75 explicit raise

> sleep 6
> produce "running test 3" in pls
raise CONSTRAINT_ERROR
s-valenu.adb:75 explicit raise
Exception name: CONSTRAINT_ERROR
Message: s-valenu.adb:75 explicit raise

> sleep 6
> produce "running test 4" in pls
raise CONSTRAINT_ERROR
s-valenu.adb:75 explicit raise
Exception name: CONSTRAINT_ERROR
Message: s-valenu.adb:75 explicit raise

> quit