Skip to main content

Cloud Computing

By tvik
Is it the ultimate innovation or is it the next buzzword managers and sales staff members must record into their notebooks?

After reading some material it doesn't mean more for me than a clustered client-server architecture where processing capacity and memory can be hired and clients are generally web browsers or other applications. It's not a big novelty form the developers' point of view so first of all we got a new phrase for the hot water.

Don't mix it with 'grid computing' where real math computations are running on a statically or dynamically built distributed network (SETI@home for an example) and clients are active participants of the process. Instead of this, with cloud computing, you connect to the service and use it. So I don't get again where is the magic. (Maybe the magic is in the ability of obtaining a large amount of personal data and money from the users.) I can imagine an architecture which discovers (sourceforge does this) or even deploys automatically service components geographically closer to the requester. So yes, there can be interesting aspects.

Anyway, we have to learn:
  • Internet, Server (deprecated, past)
  • Cloud Computing (trendy, future)

Comments

Post a Comment

Popular posts from this blog

Client's transaction aborted

By tvik
I've met the above error message using a Wicket 1.2 / EJB3 intranet application under Glassfish v2 . Here is the more particular head of the stack trace: javax.ejb.TransactionRolledbackLocalException: Client's transaction aborted at com.sun.ejb.containers.BaseContainer.useClientTx(BaseContainer.java:3394) at com.sun.ejb.containers.BaseContainer.preInvokeTx(BaseContainer.java:3274) at com.sun.ejb.containers.BaseContainer.preInvoke(BaseContainer.java:1244) at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:195) at com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate.invoke(EJBLocalObjectInvocationHandlerDelegate.java:127) This exception raised on the integration server sometimes, randomly, for simple page fetch operations. After pressing reload on the browser, the operation was usually successful. I couldn't reproduce the failure on the local machine where I regularly restart the app server and...
3 comments
Read more

jxl.log

By tvik
In an intranet production environment we have running a Glassfish v2 appserver with several J2EE applications which all use JexcelApi , a.k.a JXL, which is an open source library for accessing, generating or manipulating Microsoft Excel documents. We use version 2.6.3 of JXL because it's the recent one in the Maven repository which we use, however, at the official JXL site there are newer versions. Additionally we have log4j and Java Commons Logging (JCL), ignoring Glassfish's JSR-47 Java Util Logging (JUL) facility. Application #1 uses purely log4j and gets its log4j.xml config from a custom location. Application #2 runs Java Commons Logging with no explicite configuration file given, so JCL uses the default JUL facility of the appserver. Application #1 had been running for a long time without problems but when we installed #2 we realized that a jxl.log file had been created in the glassfish/domain/domain1/config directory and it's rapidly growing. As it happens, we ...
3 comments
Read more

Setting up EJB3 default interceptor

By tvik
It wasn't easy to find out how to configure a default interceptor in EJB3 environment. It's okay to make this snippet into the ejb-jar.xml: <assembly-descriptor> <interceptor-binding> <ejb-name>*</ejb-name> <interceptor-class>pkg.IC</interceptor-class> </interceptor-binding> </assembly-descriptor> Maybe everybody forget to mention maybe it's a Glassfish V2 trick that I get this error message during deployment: Interceptor binding contains an interceptor class name = pkg.IC that is not defined as an interceptor ...unless I register the interceptor class itself too with this: <interceptors> <interceptor> <interceptor-class>pkg.IC</interceptor-class> <around-invoke> <method-name>call</method-name> </around-invoke> </interceptor> </interceptors> <interceptors> and <as...
3 comments
Read more