I am trying to migrate an application that uses hibernate 2.1 from jboss4.0.2
to jboss4.0.3 SP1. Since we don't want to immediately migrate to hibernate 3.x,
I am trying to configure Jboss 4.0.3 SP1 with hibernate 2.1. I found the below
article on wiki that details switching from hibernate 3.x t
could you try deleting jboss-hibernate.deployer folder from the deploy
directory. I think jboss has removed the har deployer and built it's
functionality into one of the other deployers. Also place all the jar files
that are present in jboss-hibernate.deployer in the lib folder of the
appropria
Managed to solve this problem.
-->deleted hibernate3.jar, jboss-hibernate.jar from default/lib
-->placed jboss.hibernate.deployer (versaion 2.1) in deploy folder.
Application deploys fine.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912712#3912712
Reply t
refer to the below links for info on removal of har deployer and deploying har
files in ver 4.0.3.
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossHibernate3
http://jira.jboss.com/jira/browse/JBAS-2000#action_12321886
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=67027
View the original
I found another way to accurately calculate % CPU usage using J2SE 5.0
management MBean OperatingSystemMXBean, which has an attribute ProcessCpuTime.
Using this value provided accurate results for % cpu usage. The JConsole
monitoring application that comes with J2SE 5.0 also uses this MBean to r
I thought it'll be useful to post a small code snippet also:
MBeanServerConnection server = ManagementFactory.getPlatformMBeanServer();
|
| OperatingSystemMXBean sunOperatingSystemMXBean =
ManagementFactory.newPlatformMXBeanProxy(server,
| ManagementFactory.OPERATING_SYSTEM
I'm using ServerInfo listThreadCpuUtilization() (the "Total" value) to
calculate the %CPU utilization of the Jboss server. I'm also taking in to
account the no of CPUs while calculating this value. The problem is, I'm
getting absurd values for CPU usage like 170% etc.
The formula I'm using is:
Thanks for the reply.
Yeah, I count the elapsed time interval between the 2 calls and the total cpu
usage in this time interval. The no of CPUs is as reported by the jboss
web-console, home page (Hardware section)
The JVM i'm using is
java version "1.5.0_05"
Java(TM) 2 Runtime Environment, Sta
I'm getting the above exception while web application deployment in 4.0.4GA in
the default server configuration. It never occured in 4.0.3SP1. We don't need
any clustering enabled (hence running the default server config) and want to
get rid of this exception during deployment. The more detailed
I can get rid of the class not found exception by copying jboss-cache.jar from
all/lib into default/lib, but I still get an exception as follows
16:18:58,325 INFO [JBossCacheManager] init(): replicationGranularity_ is 0 and
invaldateSessionPolicy is 2
| 16:18:58,353 ERROR [JBossCacheService]
Actually I can see the error in 4.0.3SP1 also but the stack trace of this error
is suppressed in 4.0.3. I could locate the differences in the source code of
the two versions as follows.
4.0.3SP1, TomcatDeployer.java
catch (ClusteringNotSupportedException e)
| {
| lo
Hi All,
I have two instances of Jboss (v 4.0.1) running on fedora core 3, one with
clustering configured and the other with unclustered configuration running
webapps to use clustered session beans on the clustered instance.
The clustered instance is bound to IP address 204.246.8.199 where as th
Hi Bo,
I am facing the same issue. I have both the jars in the client folder and i
even tried just keeping jbossall-client.jar but I get the same exception.
Appreciate if you could help me here. Thanks.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884859#3
Hi All,
I even set up another cluster node and the communication between the cluster
nodes works file as follows
14:52:27,732 INFO [DefaultPartition] I am (204.246.8.199:1099) received
membershipChanged event:
14:52:27,732 INFO [DefaultPartition] Dead members: 0 ([])
14:52:27,733 INFO [Defau
Hi Trossmy,
Thanks for your reply. I also figured that out myself on the same day. But I
wonder why there is no mention about this anywhere in the JBOSS docs!
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885369#3885369
Reply to the post :
http://www.jbo
hi Hari,
In fact my problem was solved by placing jbossha.jar from server/all/lib to
server/default/lib. Wonder what was your problem. Clustering doc seems to have
missed out some small but important details.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=388
Hope JBOSS could add a note about this in the clustering documentation and save
people from going through hell with this issue..
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885525#3885525
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=po
Yup, I have added it there. Future JBoss versions could probably include that
jar file in the "default" configuration.
Thanks.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885725#3885725
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=pos
Hi,
To have multiple cluster nodes on the same machine, you would need a multihomed
machine and then you could bind each jboss instance to a different IP adress by
using
run.sh -b
Though having a cluster just on one machine doesn't truly serve the purpose of
clustering.
For load balancing a
1) After node B comes online again, subsequents requests will be loadbalanced
between A and B. I have tested this scenario and the loadbalancing works fine.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886679#3886679
Reply to the post :
http://www.jboss
Hi Menkun,
Thanks for your clarification. Actually your questions 1 and 4 contradict each
other if I am not mistaken. In question 1 you mention that "all processes in A
are transferred to B seamlessly" and as per your last clarification, these
processes are running processes i.e, still incomple
Hi,
Yeah JBoss has tomcat bundled with it and each jboss instance will have tomcat
running on it. Since all web requests are handled by tomcat, you need a
loadbalancer in front of your JBoss nodes to loadbalace web requests between
your JBoss instances. Apache web server is meant for that pur
Hi Nitin,
mod_jk currently supports only one method of load balancing i.e, weighted round
robin. As you may be aware now, the workers.properties configuration file
defines the configuration for each node as follows.
# Define list of workers that will be used
# for mapping reques
Hi Nitin,
>From the stack trace, it seems like an object that you are adding to the
>session is not Serializable. Ensure that all objects that need to be in the
>session are serializable.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3887302#3887302
Reply t
Hi,
You could deploy your applications in the "default" server configuration of
JBoss. The default server instance does not start clustering services and hence
the multicast communication between nodes would be automatically eliminated. If
you are already running the default configuration, you
Hi,
Assuming your main requirement is load balancing for multiple apps, you could
look into load balancing using Apache+mod_jk. I am sure that it supports
routing to multiple applications. You can refer to the below link for more
information.
http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingMod_j
Hi,
We have two clustered JBoss instances in cluster configuration containing
clustered SLSBs. Web applications deployed in a third JBoss instance access
these clustered SLSBs. I was testing failover by stopping the current active
clustered instance and each time testing the functionality of th
Thanks Ben and Darran,
Forgot to mention the JBoss version, it is 4.0.1.
1) I am not sure about whether they are cached or not as my role is more into
system implementation but I shall try to find out. However could you tell me
how does this caching affect the failover process. Also, what if th
Hi Bhatti,
Just out of curiosity, does HTTP loadbalancer provide the features you require
mainly Caching and security. I see that the documentation metions nothing about
caching nor security apart from load balancing. If you know better, could you
share this knowledge? Thanks in advance.
View
Hi,
Are you using Apache+mod_jk and EJB clustering? I am curious to know that If
the load is evenly distributed how can one particular node have excess load
than the others? Did you check how many sessions are on each node? I believe
there is no sort of co-ordinator at the EJB level, the client
Created an issue for this case in JIRA.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3888209#3888209
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3888209
---
SF.Ne
The status of the Jira issue can be tracked at the below URL
http://jira.jboss.com/jira/browse/JBAS-2074
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3888210#3888210
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=38882
Hi,
Is it solved by using the latest JBoss version? Please clarify. Would
appreactie if someone could give me pointers in the right direction towards
getting this resolved.
Thanks.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3888228#3888228
Reply to t
Appreciate your help here. All I requested was a little help that too in a
polite manner and did not expect sarcastic comments for responses. If the
attitude is not to help, then people should rather ignore instead of posting
such responses. Also the users cannot be expected to think at the sam
Yeah, How would you react if someone mocked you just because he was in a
superior technical position! Being superior doesn't give someone the authority
to be arrogant and mock polite strangers.
I shall continue to wait for an appropriate solution from the rest of the JBoss
community if not from
Hi Guys,
Thanks, really appreciate your inputs. Nick, I am facing the exact same problem
as you have described and I believe the failover should be transparent rather
than the client having to handle it. We are not caching the interfaces as well.
In fact I have just tested with the latest produ
Hey Guys,
I still encounter that error even with the latest release [4.0.2 (build:
CVSTag=JBoss_4_0_2 date=200505022023)]. I got to go now though I shall do
detailed testing tomorrow to confim my results and post my detailed analysis.
Thanks.
View the original post :
http://www.jboss.org/inde
Hi Nick,
Apparently as this seems to be a long exisitng bug in JBoss, I have to look
into handling the failover in the client as you have done for the time being. I
am not too sure of the patch posted in JIRA nor have time to test it.
Thanks.
View the original post :
http://www.jboss.org/inde
38 matches
Mail list logo
