Java 1.5 FYI

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Java 1.5 FYI

Ruth Hoffman

I found a regression problem with Java 1.5 that I thought might be of
interest to some:

I took a version of OFBiz (I think it was 7759 - still pre Geronimo) and
moved it back from production to development for some work. When I tried
to start it up, I got the following error:

    Aug 12, 2006 7:00:35 AM
    com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl <init>
    WARNING: "IOP00410201: (COMM_FAILURE) Connection failure:
    socketType: IIOP_CLEAR_TEXT; hostname: localhost; port: 2000"
    org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  completed: No
            at
    com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2172)

After doing all the normal hair pulling locally, I searched the Sun site
for some possible clues. What I found (several bug reports) reminded me
that I had installed Java 1.5 on the machine I'm working on - and this
version had been built with 1.4.

So, I repointed my Java runtime to a 1.4 version, restarted and
everything worked fine.

Just an FYI - for those moving to 1.5 but need to concern themselves
with existing 1.4 builds.

Ruth

Reply | Threaded
Open this post in threaded view
|

Re: Java 1.5 FYI

David E Jones-2

Pre-geronimo OOTB did not work with 1.5.

-David


On Aug 12, 2006, at 6:37 AM, Ruth Hoffman wrote:

>
> I found a regression problem with Java 1.5 that I thought might be  
> of interest to some:
>
> I took a version of OFBiz (I think it was 7759 - still pre  
> Geronimo) and moved it back from production to development for some  
> work. When I tried to start it up, I got the following error:
>
>    Aug 12, 2006 7:00:35 AM
>    com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl  
> <init>
>    WARNING: "IOP00410201: (COMM_FAILURE) Connection failure:
>    socketType: IIOP_CLEAR_TEXT; hostname: localhost; port: 2000"
>    org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  
> completed: No
>            at
>    
> com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure
> (ORBUtilSystemException.java:2172)
>
> After doing all the normal hair pulling locally, I searched the Sun  
> site for some possible clues. What I found (several bug reports)  
> reminded me that I had installed Java 1.5 on the machine I'm  
> working on - and this version had been built with 1.4.
>
> So, I repointed my Java runtime to a 1.4 version, restarted and  
> everything worked fine.
>
> Just an FYI - for those moving to 1.5 but need to concern  
> themselves with existing 1.4 builds.
>
> Ruth
>

Reply | Threaded
Open this post in threaded view
|

Re: Java 1.5 FYI

Ruth Hoffman
David:

With all due respect, that wasn't the point of my post.

Regards,
Ruth

David E. Jones wrote:

>
> Pre-geronimo OOTB did not work with 1.5.
>
> -David
>
>
> On Aug 12, 2006, at 6:37 AM, Ruth Hoffman wrote:
>
>>
>> I found a regression problem with Java 1.5 that I thought might be  
>> of interest to some:
>>
>> I took a version of OFBiz (I think it was 7759 - still pre  Geronimo)
>> and moved it back from production to development for some  work. When
>> I tried to start it up, I got the following error:
>>
>>    Aug 12, 2006 7:00:35 AM
>>    com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl  <init>
>>    WARNING: "IOP00410201: (COMM_FAILURE) Connection failure:
>>    socketType: IIOP_CLEAR_TEXT; hostname: localhost; port: 2000"
>>    org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  
>> completed: No
>>            at
>>    
>> com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure
>> (ORBUtilSystemException.java:2172)
>>
>> After doing all the normal hair pulling locally, I searched the Sun  
>> site for some possible clues. What I found (several bug reports)  
>> reminded me that I had installed Java 1.5 on the machine I'm  working
>> on - and this version had been built with 1.4.
>>
>> So, I repointed my Java runtime to a 1.4 version, restarted and  
>> everything worked fine.
>>
>> Just an FYI - for those moving to 1.5 but need to concern  themselves
>> with existing 1.4 builds.
>>
>> Ruth
>>
>
>