I think we should throw an error with anything less than 1.5. We don't  
test it and we want to use 1.5
features moving forward.

On Oct 30, 2007, at 2:18 PM, Tim Eck wrote:

> Is there some compelling reason to just not make the L2 as a whole  
> mandate
> a 1.5 runtime? It sounds like you were just suggesting that an L2 in
> network active/passive should have the runtime requirement.
>
> At the moment, one piece of data here is that the classes for the  
> dso-l2
> module are compiled for 1.4 targets in 2.4.x, but in 2.5.x they are  
> for
> 1.5.
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED] [mailto:tc-dev-
>> [EMAIL PROTECTED] On Behalf Of Saravanan Subbiah
>> Sent: Tuesday, October 30, 2007 2:14 PM
>> To: [email protected]
>> Subject: Re: [tc-dev] [JIRA] Created: (CDV-492) Active / Passive over
>> Network issue on 1.4
>>
>> Tribes doesnt run and hence we short circuit it in 1.4. We should
>> probably change it to fail on startup in anything less than 1.5
>>
>> Steven Harris wrote:
>>> It does. It runs but is unsupported on 1.4
>>>
>>> Cheers,
>>> Steve
>>>
>>> On Oct 30, 2007, at 10:38 AM, Alex Miller <[EMAIL PROTECTED] 
>>> >
>>> wrote:
>>>
>>>
>>>> I thought our server requires 1.5?
>>>>
>>>> ----- Original Message -----
>>>> From: "Terracotta JIRA (on behalf of Taylor Gautier)"
>> <[EMAIL PROTECTED]
>>>>
>>>> To: [email protected]
>>>> Sent: Tuesday, October 30, 2007 12:30:34 PM (GMT-0600)
> America/Chicago
>>>> Subject: [tc-dev] [JIRA] Created: (CDV-492) Active / Passive over
>>>> Network issue on 1.4
>>>>
>>>> Active / Passive over Network issue on 1.4
>>>> ------------------------------------------
>>>>
>>>>                Key: CDV-492
>>>>                URL: https://jira.terracotta.org/jira//browse/ 
>>>> CDV-492
>>>>            Project: Community Development
>>>>         Issue Type: Bug
>>>>           Reporter: Taylor Gautier
>>>>           Assignee: Issue Review Board
>>>>
>>>>
>>>>
>>>>> From the forums:
>>>>>
>>>> http://forums.terracotta.org/forums/posts/list/465.page
>>>>
>>>> I have got another problem.
>>>> I conficured a terracotta server custer running in active passive-
>>>> mode over network. My server machines are linux based.
>>>> When using Java 5 everyting works fine, in fact starting the first
>>>> node the message I get is the following:
>>>>
>>>> 2007-10-30 14:38:53,446 INFO - Configuration loaded from the file  
>>>> at
>>>> '/opt/tc-config.xml'.
>>>> 2007-10-30 14:38:53,496 INFO - Log file: '/var/log/terracotta/ 
>>>> server-
>>>> logs/terracotta-server.log'.
>>>> 2007-10-30 14:38:54,453 INFO - JMX Server started. Authentication
>>>> OFF - Available at URL[service:jmx:rmi:///jndi/rmi://localhost: 
>>>> 9520/
>>>> jmxrmi]
>>>> Oct 30, 2007 2:38:55 PM
>>>> org.apache.catalina.tribes.transport.ReceiverBase bind
>>>> INFO: Receiver Server Socket bound to:/172.42.1.151:9530
>>>> 2007-10-30 14:39:00,880 INFO - Becoming State[ ACTIVE-COORDINATOR ]
>>>> 2007-10-30 14:39:00,985 INFO - Terracotta Server has started up as
>>>> ACTIVE node on port 9510 successfully, and is now ready for work.
>>>>
>>>> On the other hand, using java 1.4. Both nodes come up as active.
>>>>
>>>> The message I get stating the first node is the following:
>>>>
>>>> 2007-10-30 14:43:48,153 INFO - Configuration loaded from the file  
>>>> at
>>>> '/opt/tc-config.xml'.
>>>> 2007-10-30 14:43:48,211 INFO - Log file: '/var/log/terracotta/ 
>>>> server-
>>>> logs/terracotta-server.log'.
>>>> 2007-10-30 14:43:49,836 INFO - JMX Server started. Authentication
>>>> OFF - Available at URL[service:jmx:rmi:///jndi/rmi://localhost: 
>>>> 9520/
>>>> jmxrmi]
>>>> 2007-10-30 14:43:56,996 INFO - Becoming State[ ACTIVE-COORDINATOR ]
>>>> 2007-10-30 14:43:57,151 INFO - Terracotta Server has started up as
>>>> ACTIVE node on port 9510 successfully, and is now ready for work.
>>>>
>>>> Note that the message:
>>>>
>>>> Oct 30, 2007 2:38:55 PM
>>>> org.apache.catalina.tribes.transport.ReceiverBase bind
>>>> INFO: Receiver Server Socket bound to:/172.42.1.151:9530
>>>>
>>>> is missing now and trying to execute the command:
>>>>
>>>> netstat -na
>>>>
>>>> no socket appears to be listenining on the port 9530, so the packet
>>>> sent by other node is rejected (I saw that sniffing packet on the
>>>> other node).
>>>> Of course no problem for me using java 1.5, but how come terracotta
>>>> server cluster doesn't work proberly with java 1.4?
>>>>
>>>> The distribution I've used is Red hat enterprise 3, but I've got  
>>>> the
>>>> same problem even using CentOS final 4.3.
>>>>
>>>> --
>>>> This message is automatically generated by JIRA.
>>>> -
>>>> If you think it was sent incorrectly contact one of the
>>>> administrators:
>> https://jira.terracotta.org/jira//secure/Administrators.jspa
>>>> -
>>>> For more information on JIRA, see:
>> http://www.atlassian.com/software/jira
>>>>
>>>>
>>>> _______________________________________________
>>>> tc-dev mailing list
>>>> [email protected]
>>>> http://lists.terracotta.org/mailman/listinfo/tc-dev
>>>>
>>>> _______________________________________________
>>>> tc-dev mailing list
>>>> [email protected]
>>>> http://lists.terracotta.org/mailman/listinfo/tc-dev
>>>>
>>> _______________________________________________
>>> tc-dev mailing list
>>> [email protected]
>>> http://lists.terracotta.org/mailman/listinfo/tc-dev
>>>
>>
>> _______________________________________________
>> tc-dev mailing list
>> [email protected]
>> http://lists.terracotta.org/mailman/listinfo/tc-dev
>
> _______________________________________________
> tc-dev mailing list
> [email protected]
> http://lists.terracotta.org/mailman/listinfo/tc-dev

_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev

Reply via email to