Hi Ben,
it shows up on both nodes, but I do have RoundRobin in use for the SFSB. It
does not show up absoluteley simultaniously, one node starts shortly before the
other.
I am not sure, but I thought I rather mention it, just in case it is related.
(If not just ignore it). I still have a
Thanks, it worked (after multiple: 1. clean, 2.build 3.goto 1 again; eclipse
and ant after some attempts finally did what they should and it worked).
Unfourtunately there still is an error that shows up:
| ... //Server Start
| 13:35:47,062 INFO [STDOUT] I have been created by
Thank you Ben !
Sincerly
Marc
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3955385#3955385
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3955385
Using Tomcat but need to do more? Need to support web services, security?
Sorry to bother again, but I do have one more question.
Is there any workaround that I can implement into the 4.0.4.GA source, so that
when I build a version it will work with 1.4 ?
I had a look at the JBossCache sources (TreeCache, EvictionPolicy,
RegionManager, Region, Eviction,...) and at the
Yes, I have a modified \deploy\ejb3.deployer\META-INF\jboss-service.xml so that
we can use the http-invoker-servlet.
This is the changed line:
...
| attribute
name=InvokerLocatorservlet://mc0430-116:8080/servlet-invoker/ServerInvokerServlet/attribute
| ...
|
Also we have modified the
Strange, I just tried it with an 4.0.4CR2 Out-of-the-Box's all and the
1.4.0Cr1 and a HelloWorld SFSB and up the error came.
I for this I did use a 4.0.4CR2 that has been out for a while, files are dated
first of April 06... not that I am missing something here. The sources that I
use to
The SFSB should be on its way to you !
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3953759#3953759
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3953759
Using Tomcat but need to do more? Need to support web services,
(I hope I am not hijacking...)
I have the problem, that when I try to use the cache, it results in a:
16:51:44,625 WARN [ServiceController] Problem starting service jboss.j2ee:ear=t
| estEJB.ear,jar=testEJB.jar,name=NatPersLstSFBean,service=EJB3
| java.lang.RuntimeException:
Sure, (sorry for being unclear)
The error does not occure when just deploying the 1.3.0 or 1.4.0CR1
jboss-cache.jar into the /lib Folder
but as soon as I also deploy my ejb3 application (one SLSB, one SFSB and one
POJO used via *.hbm.xml as an entity).
It does not matter if I use a hibernate
I have tryed this with 1.3.0 and 1.4.0.CR1 and I allways get the above error as
soon as I deploy the ejb3 application. Just as the error message shows, It
doesnt matter If I define a cache service or use a Hibernate 2nd lvl.
If I dont define one and dont tell Hibernate to use one I still get
Hi,
I have a problem using the persistence.xml to configure my persistence for a
simple ejb3 test app.
I am using 4.0.4.GA, EJB3(RC7) and hibernate (3.2.0CR2).
It works fine when I use the config with the hibernate-service.xml and the
hibernate.cfg.xml (for the programmatic approach) but
Yes, it is the 1.2.4SP2 package (sorry for the late reply).
I got it to work (more or less) with 1.2.4sp2 with this config:
| server
| ...
| !-- Pesimistic is extremley slow, OPTIMISTIC only 1.3.0 --
| attribute name=NodeLockingSchemePESSIMISTIC/attribute
|
Hi,
I would also be interested in the solution, since I also have this problem (or
better very similar).
Thanks !
(I posted about it in the ejb3 forum since I thought the specific problem would
be related to ejb3 details,
http://www.jboss.com/index.html?module=bbop=viewtopict=84930 )
View
I am still having the problem... I can configure it as an MBean
(hibernate-service.xml) and it works fine, use a utility class for a static
factory and the hibernate.cfg.xml and it works.
But with the persistence.xml, it seems I am missing something. I read over the
documentation again and
Hi,
the Problem is that when I use the jar with persistence.xml it says:
| ObjectName: jboss.jca:name=jdbc/MYDB,service=ManagedConnectionFactory
| State: NOTYETINSTALLED
| Depends On Me:
| persistence.units:jar=EJBTest2EJB.jar,unitName=entwDS
|
I used to use the
Just saw that I have a typo in the post, both ds have the same name
java:/jdbc/OLGAENTW and are not different.
By misstake I copied the first code snipit with java:/jdbc/MYDB.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3950844#3950844
Reply to the post :
Thanks !
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3950387#3950387
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3950387
___
JBoss-user mailing list
Sure ! Somethings might be pointless, as it is a class just for testing purpose.
| @RemoteBinding(jndiBinding=EJBTEST/NatPerLstSFBean/remote)
| /* This is set as a System.property
| clientBindUrl=servlet://mc0430-116.somewhere.de:8080/invoker/JNDIFactory
| */
|
I have gone through all of the logs files. I thing it seems to be the problem
that
Node A registers org.hibernate.impl.SessionFactoryImpl with uid x1
An invokation on A does fine, when turning to Node B
SessionFactoryObjectFactory trys to look up the uid x1, which it cant find
since node B only
I have just stumbled over a solution.I thought about would could cause the
SessionFactory Problem (for the x't time) and had a stupid idea...
Clear the Farm folder on both nodes before start up (so all is up before
deploying the App). Start the nodes up. Then drop the ear to deploy in the farm
I guess I was to euphoric... so forget my last post :(.
Its still there. I tested invoking initialy on node 2 and deploying first on
node 1. That worked, no idea why. I tried it three time and all was good. Then
I invoked first on node 1 and the problem is there again and also in other
We are using a modified 4.0.4GA. StatfullRemoteProxyFactory,
StatefullClusterProxyFactory, StatlessRemoteProxyFactory,
StatelessClusterProxyFactory,RemoteProxyFactory and InvokerLocator have been
changed. They now fetch the bindURL from a System.property, since we needed to
use the host name.
Hi
Sorry for the information overflow...
I guess this sums it up:
| [org.jboss.cache.eviction.RegionManager] getRegions(): size of region 2
| [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover
notifying pools, interval: 45
|
I also have some issues on this, but maybe I can help a bit.
Do you want to configure the 2nd level Cache? If you have a hibernate.cfg.xml
in your project, you can set it up in there.
Alternatively the shiped full install comes with the
ejb3-clustered-sfsbcache-service.xml and
Hi I have a some questions about seting up the hibernate 2nd level Chach. I
read some docu on this and mainly followed the
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernate
I am using 4.0.4.GA all.
When I use the hibernate-recommended-config.xml from the cache package (renamed
to
Have a look at
http://www.jboss.com/index.html?module=bbop=viewtopict=82345
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3944835#3944835
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3944835
Thanks !, I'llkeep my eyes open for news !
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3944586#3944586
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3944586
---
Using
Hi, thanks for your answers!
I don?t know, but I would guess that the deployment descriptor override
function will act like useing the corresponding annotation at the moment.(?)
When I use the annotation ?clientBindURL?, I can set the port and the host
name. I then still have the problem that
Hi Tom,
I did some further testing, when I set up a cluster on a single machine, the
Bindingmanager assigns port 3873 and 4073 for the Connector defined in
/EJB3Deployer/META-INF/jboss-service.xml. When I kill the first node, 3873 is
of course gone and the app fails. Just running node 2 shows,
Are your versions compatible ? I had the same error when I tried using mod_jk
with Apache 2.2, switched to 2.0 and all was fine.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3942819#3942819
Reply to the post :
One way you can tell your bean how it should be placed into the JNDI Tree is
with annotations
| //Bind the remote interface under EJBTEST/NatPerLstBean/remote into the
//JNDI Tree
| @RemoteBinding( jndiBinding=EJBTEST/ThisIsYourtBean/remote)
| @LocalBinding(
Thanks a lot !
I'll keep my eyes open on the forum, and just in case I figure something out,
I'll post it. Thanks !
Sincerely Marc
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3941788#3941788
Reply to the post :
The scenario, a (cluster of) JBoss 4.0.4RC2 running behind a Firewall/NAT, a
client communicating via http with the Server and visa versa. So, all over http
and just using a single port (e.g. 8080) and using EJB 3.0. (Something like
client = Firewall = I-Net = Firewall=Apache=JBossCluster )
We
I should have noticed it, the problem is that the jndi.properties got into the
jar and ear package, so ofcourse causing trouble. Corrected the ant script and
I could continue on to the next problems ;)
View the original post :
Thanks for the reply !
In this context, I havent looked into those configs very much until now.
We also try to get our App/JBoss to just use one port. Have you done any
approach into configuring jboss to do this ?
We started with the \ejb3.deployer\META-INF\jbosss-service.xml and configured
|
Have you made any advance in this ?
I also would like to just use http and port 80.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3941323#3941323
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3941323
You are right. It has the same effect if I manually do the deploy in each
deploy folder. It seems to be my ear (and what is within) that causes the
trouble. We have a real project we ported to 4.0.4rc2 and it worked, no matter
if farmed or not (at least in the short time we tested it).
The
... as always, just after posting, one problem or cause is solved. The culster
invocation error was due to a typo (I read over it about 20times yesterday and
did'nt see it, sorry) in the hibernate.cfg.xml at
| !-- Define cached entities and collections --
| class-cache
There it is again...
| java.lang.RuntimeException: cluster invocation failed, last exception was:
| at
org.jboss.aspects.remoting.ClusterChooserInterceptor.invoke(ClusterChooserInterceptor.java:115)
| at
Hi,
no I did not, that is what is confusing me also.
The deploy dir contains nothing but the elements that come with the default
deploy dir (no personal stuff at all, I cleared all out and used a clean
install made out of the all and ejb 3.0 cluster folders, to make sure there is
nothing I
It seems to be a problem of my Test ear file. We deployed a larger application
made out of jar, har, ejb3 and ear files and they were distributed fine (none
are market @clustered though).
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3940147#3940147
Reply to
This one works for my config (at least the farming works ;-) )
| ?xml version=1.0 encoding=UTF-8?
| server
| mbean code=org.jboss.ha.framework.server.FarmMemberService
| name=jboss:service=FarmMember,PartitionName=DefaultPartition
|
The farimg works in my test case( I have trouble with double binding in the
JNDI Tree for the deployed packages afterwards).
Wich install and JBoss version do you run ?(my config:
http://www.jboss.com/index.html?module=bbop=viewtopict=81796 )
I did a all installation and since I needed EJB
You started both servers (on the same machine ?), copy the ear to your /farm
folder, does the first server then deploy the ear succesfully and ends like
this ?
| ...
| 11:32:36,859 INFO [EARDeployer] Started J2EE application:
file:/C:/work/_progra
|
It should be 2.0. But I don?t think that is the cause of the problem.
Maybe you are missing some libs, depending on your installation.
If you don?t have the all installation, II would try doing a second install
with the all option and use that folder on your existing JBoss installation,
that way
When you start up the first server, is the /farm empty ? if you delete the farm
folder, will it be created when you start up the server ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3939778#3939778
Reply to the post :
I Also noticed, but forgot to mention, that your second server has not found or
joint the cluster -
| 14:24:02,397 INFO [DefaultPartition] Number of cluster members: 1
| 14:24:02,413 INFO [DefaultPartition] Other members: 0
| 14:24:02,413 INFO [DefaultPartition] Fetching state (will
Never mind, I didnt see the last linesince it looks different on the 4.0.4.RC2
(like the New Member etc. lines at start up).
Your server does of course notive the other one
| [DefaultPartition] Originating groups: [[wks-nkhachat:2102 (additional
data: 16 b
| ytes)|0] [wks-nkhachat:2102
I'm sorry, then I dont see what else you could do (but as I said, I dont know
alot about this).
You might check via jmx consol if you can find the
service=FarmMember, too see if it gets started at all.
View the original post :
Depending on my config I also get this problem with the EJB3EntityTreeCache
on startup of the second server.
I really would appriciate a tip, since I still cant find any thing in the wiki,
the there linked documents or the other guides and handbooks I have (google
wont help either, and
Here it comes, but be aware that I am using the 4.0.4.rc2. I dont know if there
are version specific dependencies..
| ?xml version=1.0 encoding=UTF-8?
|
| !-- =
--
| !--
Hi,
my config in short:
I have configured a 4.0.4rc2 to run clustered on one machine with farming for
EJB 3 (followed the guides I found in the wiki and the admin guide. Merged the
all and EJB 3 clustered installations, which works so far). I have a small test
app which I wish to deploy via
This might actually rather fit into the JNDI area, but since I?m not sure, I'll
use this thread to continue my questioning:
The Problem that I am having is concerning the binding into the JNDI Tree via
annotations:
After the new naming schema in 4.0.4.RC2 ( RC6 EJB 3.0), my objects get hung as
Ok, I have the binding... seems like I missunderstud something there, sorry. I
placed the annotation in the class representing the remote interface for the
bean, that did not work. I now placed the annotation in the bean and so get the
binding I want in the JNDI Tree.
Thx
Marc
View the
hmm, next problem...
I would greatly appreciate a tip, link, hint or example for an efficient way of
doing the JNDI lookup on the 4.0.4.RC2 and EJB 3.0 RC 6, like the old style
of just asking for the name of the interface and looking this up
The problem that I have is, that I don?t wish to hard
Hi, I am new to JBoss, EJB3.0 and Co. (So the solution might be simpler, since
I might oversee something in the config)
I just tryed to move a simple test app from 4.0.3.sp1 to 4.0.4.RC2.
The Problem I am having now ist that I get a different naming in the JNDI Tree
and I have no idea why. The
Hi first off, thanks for the link. I checked it out, but...
Unfortunately it doesn?t clarify to me why the behaviour of the JNDI
Binding/Naming changed for my code when deploying in 4.0.3SP1 (where it works)
or 4.0.4.RC2 (where it does not work).
I have, of course, checked all config files I
Thx for the fast help !
I did it like this, since a direct lookup (NatPersLstBean/remote) didnt seem to
work, but this does the job:
| ...
| Object xyz = initCtx.lookup(NatPerLstBean);
| NamingContext myNamingContext = (NamingContext)xyz;
| xyz = myNamingContext.lookup(remote);
|
58 matches
Mail list logo
