[Logo] Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)
  [Search] Search   [Recent Topics] Recent Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
[Expert]
Java 1.7 compatibility  XML
Forum Index -> Ehcache Go to Page: 1, 2 Next 
Author Message
zaraki

master

Joined: 11/05/2010 11:17:04
Messages: 62
Offline

Hi, Is the Terracotta 3.6.0 with ehcache 2.5.0 open source bundle compatible with Java 1.7?
rajoshi

seraphim

Joined: 07/04/2011 04:36:10
Messages: 1491
Offline

Hi,

As if now ehcache + Terracotta don't support java 7

Rakesh Joshi
Senior Consultant
Terracotta.
zaraki

master

Joined: 11/05/2010 11:17:04
Messages: 62
Offline

Are there any compatibility plans going with future releases this year?
steve

ophanim

Joined: 05/24/2006 14:22:53
Messages: 619
Offline

Yes, we are actively moving to Java 7. Our trunk nightly builds are jdk 7 compatible.


Want to post to this forum? Join the Terracotta Community
zaraki

master

Joined: 11/05/2010 11:17:04
Messages: 62
Offline

Hi Steve,
When is GA availability expected?
Thanks
cid

neo

Joined: 06/28/2012 06:48:29
Messages: 3
Offline

Any update on the Java 7 support?

I'm starting the tc server with Java 7 and I get the following error:
java.lang.OutOfMemoryError: Direct buffer memory. When using java 6 starts fine. Is there some configuration or JVM argument I could set?

Thanks.
cdennis

master

Joined: 01/19/2009 10:03:26
Messages: 89
Offline

Are you by chance trying to run the server on Java 1.7.0_04 on a Windows machine? There is a bug in this JVM version that prevents the TC server from starting: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7172708

Chris Dennis (Terracotta Engineer)
cid

neo

Joined: 06/28/2012 06:48:29
Messages: 3
Offline

It's Java 1.7.0_05. The server starts now (I changed the -XX:MaxDirectMemorySize parameter), but the client application application doesn't start. This is what I see in the server log:

Code:
 2012-06-29 08:17:22,775 [WorkerThread(jmxremote_tunnel_stage, 0)] INFO com.tc.management.remote.protocol.terracotta.ClientTunnelingEventHandler - L1[ChannelID=[0]] notified us that their JMX server is now available
 2012-06-29 08:17:23,133 [L2_L1:TCWorkerComm # 0_R] INFO com.tc.net.core.TCConnection - error reading from channel java.nio.channels.SocketChannel[connected local=/16.53.237.105:9510 remote=/16.53.237.105:51702]: An existing connection was forcibly closed by the remote host
 2012-06-29 08:17:23,137 [L2_L1:TCWorkerComm # 0_R] INFO com.tc.net.core.TCConnectionManager - error event on connection com.tc.net.core.TCConnectionImpl@1350727368: connected: true, closed: false local=16.53.237.105:9510 remote=16.53.237.105:51702 connect=[Fri Jun 29 08:17:22 EEST 2012] idle=328ms [739 read, 789 write]: An existing connection was forcibly closed by the remote host
 2012-06-29 08:17:23,138 [L2_L1:TCWorkerComm # 0_R] WARN com.tc.net.protocol.transport.ServerMessageTransport - ConnectionID(0.8f7571cd96a646c48e37d58959050769.b890d596-9e4c-4250-b19d-671babf91a31-13836abfe7f): CLOSE EVENT : com.tc.net.core.TCConnectionImpl@1350727368: connected: false, closed: true local=16.53.237.105:9510 remote=16.53.237.105:51702 connect=[Fri Jun 29 08:17:22 EEST 2012] idle=329ms [739 read, 789 write]. STATUS : ESTABLISHED
 2012-06-29 08:17:23,138 [L2_L1:TCWorkerComm # 0_R] INFO com.tc.net.protocol.transport.ConnectionPolicyImpl - Removed connection [0] from jvm b890d596-9e4c-4250-b19d-671babf91a31-13836abfe7f
 2012-06-29 08:17:23,139 [L2_L1:TCWorkerComm # 0_R] INFO com.tc.net.protocol.transport.ConnectionPolicyImpl - De-allocated connection license for jvm b890d596-9e4c-4250-b19d-671babf91a31-13836abfe7f; ConnectionPolicy[maxConnections=2147483647, connectedJvmCount=0]
 2012-06-29 08:17:23,139 [L2_L1:TCWorkerComm # 0_R] INFO com.tc.net.protocol.transport.ConnectionHealthCheckerImpl: DSO Server - Connection to [cduma.emea.cpqcorp.net:51702] DISCONNECTED. Health Monitoring for this node is now disabled.
 2012-06-29 08:17:28,145 [OOO Connection Restore Timer] WARN tc.operator.event - NODE : 16.53.237.105:9510  Subsystem: CLUSTER_TOPOLOGY Message: Node ClientID[0] left the cluster
 2012-06-29 08:17:28,145 [WorkerThread(channel_life_cycle_stage, 0)] INFO com.tc.objectserver.handler.ChannelLifeCycleHandler - : Received transport disconnect.  Shutting down client ClientID[0]
 2012-06-29 08:17:28,149 [WorkerThread(channel_life_cycle_stage, 0)] INFO com.tc.objectserver.persistence.db.TransactionStoreImpl - shutdownClient() : Removing txns from DB : 0
 2012-06-29 08:17:28,814 [WorkerThread(jmxremote_connect_stage, 0)] ERROR com.tc.management.remote.connect.ClientConnectEventHandler - Unable to create tunneled JMX connection to the DSO client on host[16.53.237.105:51702], this DSO client will not show up in monitoring tools!!
 java.io.IOException: connection closed
 	at com.tc.management.remote.protocol.terracotta.TunnelingMessageConnection.readMessage(TunnelingMessageConnection.java:67)
 	at com.sun.jmx.remote.opt.security.AdminClient.connectionOpen(AdminClient.java:97)
 	at com.sun.jmx.remote.generic.ClientSynchroMessageConnectionImpl.connect(ClientSynchroMessageConnectionImpl.java:112)
 	at javax.management.remote.generic.GenericConnector.connect(GenericConnector.java:217)
 	at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:267)
 	at com.tc.management.remote.connect.ClientConnectEventHandler.addJmxConnection(ClientConnectEventHandler.java:133)
 	at com.tc.management.remote.connect.ClientConnectEventHandler.handleEvent(ClientConnectEventHandler.java:77)
 	at com.tc.async.impl.StageImpl$WorkerThread.run(StageImpl.java:145)
 
 


It looks like the client doesn't like something and shuts down. Is there some config I should look to?

Thanks.
teck

seraphim
[Avatar]
Joined: 05/24/2006 15:03:25
Messages: 1128
Offline

What do you see from the client side? That logging on the server looks like a client connected but then pretty quickly shutdown for some reason but I don't see that the server had any real errors (the IOException I think can be ignored)

Tim Eck (terracotta engineer)
cid

neo

Joined: 06/28/2012 06:48:29
Messages: 3
Offline

I don't see any errors on the client side.

2012-07-02 11:12:14,567 [WorkerThread(client_coordination_stage, 0)] INFO com.tc.object.handshakemanager.ClientHandshakeManagerImpl - ClientID[5]: Connected: Unpausing from State[ PAUSED ] RemoteNode : GroupID[0]. Disconnect count : 1
2012-07-02 11:12:14,577 [WorkerThread(client_coordination_stage, 0)] INFO com.tc.object.handshakemanager.ClientHandshakeManagerImpl - ClientID[5]: Received Handshake ack for this node :GroupID[0]
2012-07-02 11:12:14,577 [main] INFO com.terracottatech.console - Connection successfully established to server at 16.53.237.105:9510
2012-07-02 11:12:14,577 [main] INFO com.terracottatech.dso - Connection successfully established to server at 16.53.237.105:9510
2012-07-02 11:12:14,577 [WorkerThread(client_coordination_stage, 0)] INFO com.tc.management.remote.protocol.terracotta.TunnelingEventHandler - Client JMX server ready; sending notification to L2 server

How do I set the log level to DEBUG for the client and and the tc server? I tried to set it from log4j config of my app, but doesn't work.

Thanks.
teck

seraphim
[Avatar]
Joined: 05/24/2006 15:03:25
Messages: 1128
Offline

Any chance you could share your complete terracotta-server.log and terracotta-client.log?

I'm a little ashamed to admit it but we don't have a "good" mechanism for enabling debug logging. I don't suspect we need to enable anything like that though to get through this. That said, you can create a file named ".tc.custom.log4j.properties" either in your home directory ("user.home") or the working dir of your java process ("user.dir"). In there you can do the usual log4j configuration.


Tim Eck (terracotta engineer)
robmoore

neo

Joined: 04/13/2009 15:15:14
Messages: 6
Offline

Just curious if there's any word on when JDK 7 will be supported.
WaiPang

neo

Joined: 03/12/2012 05:38:00
Messages: 1
Offline

In the latest terracotta 3.7. I found that the examples in
terracotta-3.7.0\platform\samples\pojo\
Are not compatible in java 1.7.

The server process starts up without issue but when i start the client i get (this is independent on the client code)

Error occurred during initialization of VM

java.lang.NoSuchFieldError?: offset

at java.lang.String.getCharsFast(String.java) at java.lang.AbstractStringBuilder?.append(AbstractStringBuilder?.java:416) at java.lang.StringBuilder?.append(StringBuilder?.java:132) at sun.nio.cs.FastCharsetProvider?.lookup(FastCharsetProvider?.java:119) at sun.nio.cs.FastCharsetProvider?.charsetForName(FastCharsetProvider?.java:136) at java.nio.charset.Charset.lookup2(Charset.java:487) at java.nio.charset.Charset.lookup(Charset.java:475) at java.nio.charset.Charset.defaultCharset(Charset.java:618) at sun.nio.cs.StreamEncoder?.forOutputStreamWriter(StreamEncoder?.java:56) at java.io.OutputStreamWriter?.<init>(OutputStreamWriter?.java:111) at java.io.PrintStream?.<init>(PrintStream?.java:104) at java.io.PrintStream?.<init>(PrintStream?.java:151) at java.lang.System.initializeSystemClass(System.java:1141)






Please advice when JAVA 1.7 is fully supported.

jimkski

neo

Joined: 01/22/2013 12:29:02
Messages: 1
Offline

Hi Terracotta folks-

JDK6 is EOL next month. I can't find any evidence that there is a Terracotta/EHCache release imminent that will support JDK7. Can someone update this thread and let us know what that status is?

Thanks.
steve

ophanim

Joined: 05/24/2006 14:22:53
Messages: 619
Offline

http://terracotta.org/confluence/display/release/Terracotta+3.7%2C+Ehcache+2.6%2C+Quartz+2.1+Platform+Support

Want to post to this forum? Join the Terracotta Community
 
Forum Index -> Ehcache Go to Page: 1, 2 Next 
Go to:   
Powered by JForum 2.1.7 © JForum Team