I sent this off to inprise this morning....I'll let you know what response
I get.  (Oh man, I just noticed a type/think-o in there....s/thing/this/
towards the bottom.)

I figured the mentioning of recent events couldn't hurt.

Keith

-- 
  Keith T. Garner                                       [EMAIL PROTECTED]
  STR Consultant           http://www.str.com/             [EMAIL PROTECTED]
                      "Be silent, my JIT" -- Dru Henke


The name of the thread of e-mail that you have been forwarded was titled:
[[EMAIL PROTECTED]: Visibroker for Linux and JDK 1.1.6v2 problem]

Dear Inprise:

With the recent annoucements of Oracle, Informix, and Computer Associates
Linux is beginning to gain the respect and recognition it has long
deserved.  Linux is the only non-Microsoft OS to gain market share in
the past year and is a wonderful platform for development and for use
as a server of all sorts.

I've written you in the past asking you to consider porting the native
portions of Visibroker for Java to the Linux platform, most notably
the OSAgent.  The response in the past is that there has not been enough
interest in such a product.  While that may have been true in the past,
I think its becoming harder and harder to continue to give that answer
with the recent changes in the industry.

Attached to this mail is a recent thread that was on the java-linux
mailing list.  People are using the Visibroker package (minus the native
ports) and are sometimes going through hoops to do it.  People want to use
the product in the wonderful developement environment that Linux provides.
I argue that there is sufficient interest and people are awaiting this
move from Inprise.

(As a slight aside, I've been using Visibroker since I was hired at my
current job a year ago, and I've been developing solely on Linux that
whole time as well, and I can't tell you how much I would appriciate
and welcome a Linux port.  I also am fairly sure that a client of ours
in the near future will be wanting to use the product on Linux as well
as they make their move to the java world.)

I thank you for your time reading thing, and, again, I strongly encourage
Inprise to consider this request.

Keith

-- 
  Keith T. Garner                                       [EMAIL PROTECTED]
  STR Consultant           http://www.str.com/             [EMAIL PROTECTED]
                      "Be silent, my JIT" -- Dru Henke


Hi:

I get the following message occasionally from a client
trying to talk to a CORBA server. Both client and server
are built using Visibroker and running on Linux with
JDK 1.1.6v2 (glibc 2.0.7-13).

I added a message to the server which indicates that
the server's impl method is being called, and obviously
the error happens when the client tries to read back
the server's reply.

Anyone seen this or know what is going on?

Rich.

org.omg.CORBA.UNKNOWN[completed=MAYBE]
        at com.visigenic.vbroker.orb.SE.read(SE.java:28)
        at com.visigenic.vbroker.orb.GiopStubDelegate.invoke(GiopStubDelegate.java:552)
        at com.visigenic.vbroker.orb.GiopStubDelegate.invoke(GiopStubDelegate.java:460)
        at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:141)
        at 
com.orchestream.policy._st_PolicyManager.getStaticRuleset(_st_PolicyManager.java:69)
        at com.orchestream.policytest.Test1.main(Test1.java:68)

-- 
Richard Jones [EMAIL PROTECTED] Tel: +44 171 598 7557 Fax: 460 4461
Orchestream Ltd.  125 Old Brompton Rd. London SW7 3RP PGP: www.four11.com
"boredom ... one of the most overrated emotions ... the sky is made
of bubbles ..."   Original message content Copyright © 1998





Shane P. McCarron wrote:
> 
> Can I read this message to imply that Visibroker is available to run
> natively on Linux?

Yup. Of course, I'm not *really* running the mythical
`Visibroker for Linux'. Rather I'm running the commercial
Visibroker for Solaris, but I tarred up all the files and
copied them over to Linux and they work fine. Except for
osagent (which is a Solaris native program), but you
don't need osagent if you use URLNaming.

I wrote to Borland about this and they said that was
fine but (a) they wouldn't support it and (b) they wouldn't
port osagent to Linux because of `lack of interest'. Yeah ...
right ... Maybe you should write to them too and if enough
people do it, then they will change their mind.

Rich.

-- 
Richard Jones [EMAIL PROTECTED] Tel: +44 171 598 7557 Fax: 460 4461
Orchestream Ltd.  125 Old Brompton Rd. London SW7 3RP PGP: www.four11.com
"boredom ... one of the most overrated emotions ... the sky is made
of bubbles ..."   Original message content Copyright © 1998





On Thu, Jul 16, 1998 at 05:53:39, Richard Jones said:
> I wrote to Borland about this and they said that was
> fine but (a) they wouldn't support it and (b) they wouldn't
> port osagent to Linux because of `lack of interest'. Yeah ...
> right ... Maybe you should write to them too and if enough
> people do it, then they will change their mind.

I guess my mail to them twice over the past 9 months must be lack of
interest as well :)

Anyway, I've got the same setup as Richard going on, except we are using
OSAgent running on one of the NT boxes around here.  Might as well put
it to good use.

Keith

-- 
  Keith T. Garner                                       [EMAIL PROTECTED]
  STR Consultant           http://www.str.com/             [EMAIL PROTECTED]
 "You can tell a lot about a company from their hostnames." -- Brian Swetland





Richard,

I hope you don't mind me asking but ....

Where did you download it from, what was the URL ?
How much space does it need ?
Is it easy to install, what are the procedures you used ?

I'm sure loads of people will be interested in this..

Many thanks

Matt





Richard Jones wrote:
> org.omg.CORBA.UNKNOWN[completed=MAYBE]
>         at com.visigenic.vbroker.orb.SE.read(SE.java:28)

Sorry to answer my own question :-) This topic seemed
to cause more discussion about how I ever managed to
get VBJ working on Linux than on the original problem.
Anyway, I solved it, and for reference here is the
answer. It's nothing to do with the Linux JDK or JVM.

It's caused by the server implementation method throwing a
java.lang.* exception, in this case, it was a
ClassCastException. Bizarrely, the server prints
nothing. Instead, VBJ seems to pass the exception
back to the client. The client, instead of doing the
right thing, throws a wobbler -- it turns the undeclared
exception into a CORBA.UNKNOWN and throws that instead!

I caught this fairly easily in the end by wrapping my server
method with a try { ... } catch (Exception ex) { ... }.

There you go ...

Rich.

-- 
Richard Jones [EMAIL PROTECTED] Tel: +44 171 598 7557 Fax: 460 4461
Orchestream Ltd.  125 Old Brompton Rd. London SW7 3RP PGP: www.four11.com
"boredom ... one of the most overrated emotions ... the sky is made
of bubbles ..."   Original message content Copyright © 1998





Reply via email to