[JBoss Tools (users)] - Re: JBossTools and Eclipse 3.3.0 , does it work at all ?
by davidbalazic
OK, I installed Eclipse freshly (unzipped eclipse-SDK-3.3-win32.zip , md5sum c7f5df655e5bd22190f31168b4f37c64), went straight to the update/install , added http://download.jboss.org/jbosstools/updates/development as new remote site, checked it and also the two other sites ("Europa Discovery Site" and "The Eclipse Project Updates") and clicked Finish.
The in the search results dialog I checked "JBossTools 2.0.0.beta3".
Immediatelly the error message "JBossTools (2.0.0.beta3) requires feature "org.eclipse.emf". popped up. I clicked on the "Select Required" button, but nothing happened. I selected the "JBossTools 2.0.0.beta3" item and clicked "Select Required" again, but nothing happened either.
Shouldn't this automatically select all dependencies for install ?
I manually checked some EMF related items, but the error was still there. As some of the items I checked also had unresolved dependencies, I clicked "Select Required" again, and not it resolved all problems. I Unchecked all except "JBossTools 2.0.0.beta3" and tried to figure out the minimum set of features required. To make it short, after I while it happened, that I had ONLY had "JBossTools 2.0.0.beta3" selected, clicked "Select Required" and now it worked and selected only 6 other features.
But not datatools.
I install them.
No errors, but I have no Deployment or Debug item.
I then install "JBossIDE JBossAS Adapter Feature". OK now I have additional items in the Preferences. JBoss Tools / JBoss Servers / View. Which causes an exception.
I then installed all datatools features, but it is the same. The error is same as described in the third post (posted at Wed Aug 22, 2007 08:40 AM)
Summary :
- problems with dependency resolving. Eclipse or JBossTools packaging bug ?
- features description URL should be changed to something meaningful from http://www.jboss.com/products/jbosside which just says "site moved"
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077228#4077228
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077228
18Â years, 8Â months
Jboss 4.0.3SP1 and jgroups >= 2.5 | problems
by Hartung, Christopher
Hello everybody,
we've a problems using jgroups 2.5 with jboss 4.0.3SP1 in cluster mode.
The two jboss will startup with the parameter
"-Djgroups.marshalling.compatible" to get compatibility with jgroups
>=2.5 .Starting up the first jboss (10.100.255.26) works fine. If we
startup the second jboss app-server (10.100.255.20), it will received
error-messages like this:
2007-08-23 09:34:09,443 ERROR [STDERR] 23.08.2007 09:34:09
org.jgroups.protocols.pbcast.NAKACK handleMessage
WARNUNG: 10.100.255.20:32785] discarded message from non-member
10.100.255.26:32779, my view is [10.100.255.20:32785|0]
[10.100.255.20:32785]
We're using the standard-jgroups-config off jboss:
<Config>
<UDP mcast_addr="${jboss.partition.udpGroup:228.4.5.6}"
mcast_port="45566"
ip_ttl="10" ip_mcast="true"
mcast_send_buf_size="800000" mcast_recv_buf_size="150000"
ucast_send_buf_size="800000" ucast_recv_buf_size="150000"
loopback="false"/>
<PING timeout="2000" num_initial_members="3"
up_thread="true" down_thread="true"/>
<MERGE2 min_interval="10000" max_interval="20000"/>
<FD shun="true" up_thread="true" down_thread="true"
timeout="2500" max_tries="5"/>
<VERIFY_SUSPECT timeout="3000" num_msgs="3"
up_thread="true" down_thread="true"/>
<pbcast.NAKACK gc_lag="50"
retransmit_timeout="300,600,1200,2400,4800"
max_xmit_size="8192"
up_thread="true" down_thread="true"/>
<UNICAST timeout="300,600,1200,2400,4800" window_size="100"
min_threshold="10"
down_thread="true"/>
<pbcast.STABLE desired_avg_gossip="20000"
up_thread="true" down_thread="true"/>
<FRAG frag_size="8192"
down_thread="true" up_thread="true"/>
<pbcast.GMS join_timeout="5000" join_retry_timeout="2000"
shun="true" print_local_addr="true"/>
<pbcast.STATE_TRANSFER up_thread="true" down_thread="true"/>
</Config>
Did anyone use jboss 4.0.3SP1 with jgroups 2.5 succesfully ?
Thx for you answers
So long
chris
18Â years, 8Â months