Not quite sure I understand your problem. If a cache instance is shut down, then clients on the same VM as the stopped cache have no interface to the clustered cache as a whole.
The CCL is for cases where you want to disable state transfer (FetchStateOnStartup) perhaps because you have too much state and it takes too long to start up. CCL is just a way for this to happen lazily, on demand. But you still need both cache instances up and running.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204637#4204637
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204637
I have encoding set to ISO-8859-2 in index.html
| <html xmlns="http://www.w3.org/1999/xhtml">
| <head>
| <meta http-equiv="content-type" content="text/html; charset=ISO-8859-2">
| </head>
| </html>
|
but server ignores this setting and overwrites it with ISO-8859-1 as you can see in following code
| telnet localhost 80
| Trying localhost...
| Connected to localhost.
| Escape character is '^]'.
| GET / HTTP/1.0
|
| HTTP/1.1 200 OK
| Server: Apache-Coyote/1.1
| X-Powered-By: Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0
| Set-Cookie: JSESSIONID=A4A3B5DD4599B45E33761BD61FE00E50; Path=/
| ETag: W/"163-1232957301000"
| Last-Modified: Mon, 26 Jan 2009 08:08:21 GMT
| Content-Type: text/html;charset=ISO-8859-1
| Content-Length: 200
| Date: Mon, 26 Jan 2009 08:08:47 GMT
| Connection: close
|
| <html xmlns="http://www.w3.org/1999/xhtml">
| <head>
| <meta http-equiv="content-type" content="text/html; charset=ISO-8859-2">
| </head>
| </html>
| Connection closed by foreign host.
|
my question is how can I change the default Content-Type to ISO-8859-2 ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204625#4204625
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204625
Glad to clear this up.
JBossAS 5.0.0.GA shipped with a composite of the EJB3 components, which together had a release version of 1.0.0-Beta7. While this was sufficient for the release criteria of AS, the EJB3 Team had a different set of release criteria before we were comfortable branding as EJB3 1.0.0 (implicitly GA).
The newly-released EJB3 Plugin will update AS 5.0.0 to EJB3 1.0.0 level.
Additionally, we'll be releasing some form of the Plugin every 2 weeks, each one targeted to patch the most recent AS release.
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204615#4204615
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204615