[jboss-user] [Clustering] - Re: HA Singleton service lookup in cluster
If the SLSB depends on the cluster-wide singleton (due to eg @EJB IYoursingleton ... in its implementation class) then it "becomes a cluster-wide singleton" of its own. To make this SLSB available on all nodes, remove the @EJB, and perform a HA lookup (manually, without injection) whenever you need to talk to the singleton. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258325#4258325 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258325 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering] - Re: cluster networking with 2 interface
-Djgroups.bind_addr=172.0.0.2 forces all cluster-communication over this interface -Djboss.bind.address=10.0.0.2 binds jboss only on this interface View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258323#4258323 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258323 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering] - Re: Message Selector based on the host name in clustered env
Maybe you dont need jms / mdb for this: you have all handlers in the same vm as the senders. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258322#4258322 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258322 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering] - client takes long to fail over to other node
I read about jnp.timeout and jnp.sotimeout here http://www.jboss.org/community/wiki/NamingContextFactory but these timeouts seem only to affect the lookup of the Naming object; this does not seem to affect the time it takes, for a proxy to decide that node A is no longer reachable, and node B should be tried. Say i have a 2-node cluster, i lookup "MyService/remote" (using the HA context :1100) and store this proxy for later use. Then I remove one node from the cluster (disconnect it from the network): the proxy should be aware of 2 server nodes (since both were up when i created it) and it should try them both, before failing. This often takes much longer than my configured timeouts. Is there any way to influence this: configure the socket-timeout of a communication-attempt for a particular proxy? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257948#4257948 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257948 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Persistence, JBoss/CMP, Hibernate, Database] - Re: Problem with CMP
I think it all depends on the transaction attributes. You have to make sure that the fetching and modification of the entity happen within the same transaction, by annotating the outer ejb with | @TransactionAttribute(javax.ejb.TransactionAttributeType.REQUIRED) | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235191#4235191 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235191 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Re: Clustered Beans with Local Interface
I think so, but you'ld have to lookup the @Remote interface, i don't think @Local interfaces appear in the ha jndi. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182783#4182783 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4182783 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Re: Need proper clustering document
http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/Clustering_Guide/beta422/html/index.html http://www.theserverside.com/tt/articles/article.tss?l=J2EEClustering View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180176#4180176 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180176 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Re: Annoying
Edit server/.../conf/jboss-log4j.xml and add a node that limits the logging of this category to INFO. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180175#4180175 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180175 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossMQ] - race condition msg delivery / db tx commit
I believe that there is no way to guarantee that a jms message gets delivered only after the db-tx has completed (and made its changes visible), even if java:/JmsXA is used. Therefore, my MDB can not find the data created in the tx in the database, because the message delivery is too fast. So my explanation for this is: 2 phase commit guarantees that all resources will commit (end of phase 1), but it does not guarantee any timing about it, therefore the thread handling the message may read the db sooner than the db makes its changes visible. Is this a valid statement? If so, can i tweak the db tx isolation level somehow to see these "promised to get committed, but not yet committed" data? Or is it just wrong, and why? This problem has been described here as well http://www.jboss.com/index.html?module=bb&op=viewtopic&t=138173 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180169#4180169 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180169 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB/JBoss] - Re: send jms message after tx commit
jaikiran, i think your statement is incorrect: even though i am using @Resource(mappedName="java:/JmsXA"), my messages still get processed before the data is actually visible in the database. When i add logging, it's a matter of 100 ms. So my explanation for this is: 2 phase commit guarantees that all resources will commit (end of phase 1), but it does not guarantee any timing about it, therefore the thread handling the message may read the db sooner than the db makes its changes visible. I'm not sure if this reasoning is correct, please give me your thoughts on it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180167#4180167 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180167 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Re: EJB3 Injection and HA-JNDI
Hm, correction about MDB: has nothing to do with @Resource, it's about @MessageDriven in the all-deployment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180165#4180165 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180165 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Re: EJB3 Injection and HA-JNDI
For MDB's deployed in the all folder you don't need to do anything: they find the destination and subscribe, whether it is remote or local; and when the coordinator-node dies, they resubscribe as soon as the new coordinator-node is ready hosting the destinations. So this makes me believe that the @Resource ConnectionFactory injection is cluster-aware somehow. For client side lookups you should use the right jndi parameters and port 1100 instead of 1099: this will make sure the client-side proxy finds a working node. For @EJB i dont think this would make sense since it meant for injecting local dependencies. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180163#4180163 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180163 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - suggest failover to caller
Can i throw some kind of exception in my stateless ejb, that will be handled in the client-ha-proxy by retrying on the next node (as if the first jboss node was not up)? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179598#4179598 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179598 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - MDB load balancing
http://docs.jboss.org/jbossas/jboss4guide/r4/html/cluster.chapt.html and 16.6.1.3 suggest that mdb's on all node's might be consuming from a single queue (on the master node). Is that by default so; and what is this unclear explanation in 16.6.1.3 about? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175442#4175442 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175442 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Advanced Documentation] - clustering tutorial : can not login
On the 4th page of this tutorial http://clusterstore.demo.jboss.com/app/browse.faces you need to login. The page says So, enter username "demo" and password "demopass" in this page to sign in. but this login doesn't work for me. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175423#4175423 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175423 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Re: jmx clustering
A simple load-balancing solution is to "schedule your jobs to the cluster" by
posting your job-objects on a queue, and use an MDB to process these jobs.
Jboss jms will load-balance the jobs over all available mdb's, and redeliver
the job if a node dies during the handling.
Note that you may want to restrict the nb of MDB's within each node to 1, using
the maxSession attribute:
@MessageDriven(activationConfig = { @ActivationConfigProperty(propertyName =
"destinationType", propertyValue = "javax.jms.Topic"),
@ActivationConfigProperty(propertyName = "destination",
propertyValue = "queue/jobs"),
@ActivationConfigProperty(propertyName = "maxSession",
propertyValue = "1")})
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175053#4175053
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175053
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Re: Failover working for JMS Client but not for Statless Ses
Perhaps you forgot your client should use the HA-jndi to lookup the bean = use port 1100, not 1099 in the Context.PROVIDER_URL property of the jndi context. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174005#4174005 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174005 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Re: Clustering in a distributed system
When a client uses jndi to reach a clustered jboss service or ejb, the Context.PROVIDER_URL property of the jndi context refers to a comma-separated list of hosts in the cluster. So if you want clients on some site to see only host A, then you can pass only node A in there. Or if host B should still be used for these clients when node A is down, then set the property to A:1100,B:1100. And change the order for clients on the other site. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173998#4173998 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173998 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Re: How to define HAJNDI
Just like any ejb in jboss: Annotate the service pojo com.my.Thing with @Service and @Remote(ThingRemote.class), and a (ThingRemote) can be found in that jndi under the name "Thing/remote". View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173992#4173992 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173992 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Re: How to run a Queue and MDB into a cluster
This works for me: i pack all in one single ear: the code, and the myqueue-service.xml (this one must be mentioned in the jboss-app.xml in order toget deployed). You should not deploy the queue in the singleton-deploy folder, but in the farm folder (like any other code). Since it depends on jms, it will only be "running" on _the_ cluster-coordinator (that runs jms in jboss 4), but all other nodes will be able to subscribe or produce into that queue. If you want a queue that is only visible on one single node, perhaps you should think it over, and change it into service holding a java-util-Queue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173989#4173989 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173989 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Re: How can I deploy a MDB to only one instance in a cluster
Annotate with
@Depends("jboss.ha:service=HASingletonDeployer,type=Barrier")
If you want only one instance within the jvm, also annotate with
@MessageDriven(activationConfig = {
@ActivationConfigProperty(propertyName = "maxSession", propertyValue = "1")})
A second node in the cluster will not run this mdb, till the first master node
goes away.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173986#4173986
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173986
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Re: Clusterwide File Transfer
I also would like to do that: reuse that jboss code to distribute my config
files to all nodes in the cluster.
What i currently do is this: i just put them in the farm folder, and ignore the
deployment-errors about them :)
then i make a softlink deploy/data.war to the farm folder; this way, my remote
java client application can also download these config files (but of course
also my ear file huh)
I read the file in my server code like this:
properties.load(new FileInputStream(new
File(System.getProperty("jboss.server.home.dir") +
"/deploy/data.war/config.properties")));
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173982#4173982
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173982
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB/JBoss] - Re: send jms message after tx commit
http://www.odi.ch/prog/jms-tx.php explains transactional jms quite well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160862#4160862 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160862 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB/JBoss] - send jms message after tx commit
Example: after the invocation of a Person insertPerson() method on a @Stateless
or @Service, i would like to broadcast this new person to a jms topic. But this
notification should only happen if the transaction commits, not if it rolls
back.
EJB3 interceptors are always inbetween the container tx interception and the
implementation, so they dont know whether the tx committed, since it has not
yet been committed when they get control again, after the invocation.
1. I read about the SessionSynchronisation interface, but it's for @Stateful
ejbs only. Any particular way i could enable this on @Service?
2. Perhaps the jms-sender code needs to be transaction-aware, and postpone the
send until the tx commits? Is this possible?
3. I could insert an ejb3 handcoded transaction interceptor, (and annotate the
ejb "supports") so that i can order it after my jms-sending interceptor. Can i
re-use jboss code, or do i have to reimplement this transaction-interceptor as
ejb3 interceptor?
4. Or i can make a "NotifyingEJB3" that has "supports", and takes care of
forwarding to the actual implementation ("required"), and then sends out the
jms message.
Other possibilities?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160840#4160840
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160840
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - jboss 4.2.2 with jgroups 2.5
Is it okay to replace the jgroups 2.4.1.sp-4 inside jboss 4.2.2, with a newer version 2.5, or will jboss get into trouble if we use clustering? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149428#4149428 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149428 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Messaging, JMS & JBossMQ] - Re: message ordering wrong 4.2.0
http://wiki.jboss.org/wiki/Wiki.jsp?page=HowDoIGetAnMDBSingleton @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "1") View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141325#4141325 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141325 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Messaging, JMS & JBossMQ] - Re: message ordering wrong 4.2.0
The actual problem is that there are 2 instances of my MDB working. They may get the messages out in the right order, but then these threads get scheduled in such way that the processing order is no longer like the queue order. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141318#4141318 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141318 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Messaging, JMS & JBossMQ] - message ordering wrong 4.2.0
We use an mdb to process messages from a queue. If the messaages arrive fast in the queue, they are delivered in reverse order sometimes. Do we have to specify that order is important somehow, when declaring the queue? On the wiki http://wiki.jboss.org/wiki/Wiki.jsp?page=JMSPriority it says that they should be delivered in order, if messages are sent from the same session. We send messages from one single session, but the session is created in a different thread than the thread that sends the messages. Could that cause the ordering to break? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141273#4141273 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141273 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Management, JMX/JBoss] - Re: ports for application and consoles
I'ld use 8080 for jboss, and put an Apache in front of jboss, and configure it there: which "external ports" should accept which urls. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121264#4121264 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121264 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Management, JMX/JBoss] - attribute persistence for @Management annotated @Service
Is it possible to connect the attribute persistence mechanism to my jboss/ejb3 @Services annotated with @Management? Or does this kind of jmx-exposure have noting to do with the xmbeans in jboss? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4120477#4120477 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4120477 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration & DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit
Works great! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110606#4110606 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110606 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration & DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit
Ah its a zip! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110601#4110601 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110601 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration & DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit
Thanks. I decoded your base64, but my decompiler says its not a class file. Perhaps you could make your patched class file online available some other way, or mail it to mynickname / yahoo / com? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110600#4110600 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110600 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration & DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit
Yes something changed in the packaging interpretation. In 4.2.1, we had to package the jars containing the ejbs (beans.jar) twice: - q.ear/lib/utils.jar - q.ear/META-INF/application.xml (module/ejb=app.jar) - q.ear/beans.jar <- duplicate - q.ear/app.jar/ejb3/beans.jar - q.ear/app.jar/META-INF/persistence.xml (jar-file=../ejb3/beans.jar) In 4.2.2 the packaging above results in deployment errors, so i changed the packaging into what i believe is the correct ejb3-packaging - q.ear/lib/utils.jar - q.ear/META-INF/application.xml (module/ejb=app.jar) - q.ear/app.jar/ejb3/beans.jar - q.ear/app.jar/META-INF/persistence.xml (jar-file=ejb3/beans.jar) and then i got the jndi-factory-naming error. So perhaps, the difference is that my persistence.xml is in a .jar inside an .ear (that also contains lib/.jars). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106443#4106443 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106443 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration & DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247) at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:284) at javax.naming.InitialContext.lookup(InitialContext.java:351) at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:216) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:103) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy82.start(Unknown Source) at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:120) at org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:627) at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:351) at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy35.start(Unknown Source) at org.jboss.ejb3.EJB3Deployer.st
[jboss-user] [Installation, Configuration & DEPLOYMENT] - 4.2.2 wont deploy my persistency unit
Migration from 4.2.1 to 4.2.2 using linux, java 1.5.0_13-b05 I try to deploy an .ear with a .jar inside, containing the META-INF/persistence.xml below. 15:20:27,725 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.units:ear=q.ear,unitName=manager1 15:20:27,741 WARN [ServiceController] Problem starting service persistence.units:ear=q.ear,unitName=manager1 javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial | | | ../ejb3/beans.jar | ../ejb3/beans2.jar | java:/DefaultDS | | | | | | | | | | Since it's complaining about jndi-factory properties, i tried to add these properties in the persistence.xml, or add a jndi.properties inside beans.jar | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces | That didn't help. The ear deploys on 4.2.1, but there i need to add ejb3/beans.jar in the .ear as well as in the nested .jar. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106001#4106001 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106001 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JNDI/Naming/Network] - Listen to binding events: EventContext
Does jboss have some context-implementation that implements EventContext? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011838#4011838 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011838 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: slow remote communication
Appearently it takes 9 seconds to process flush-time cascades... whatever that may be? I'm only fetching data, it's a query. 2006-09-26 12:29:47,308 INFO [STDOUT] 2218 ms: findLayout ([/Default/giant2.layout]) = null 2006-09-26 12:29:47,308 DEBUG [org.hibernate.event.def.AbstractFlushingEventListener] processing flush-time cascades 2006-09-26 12:29:56,808 DEBUG [org.hibernate.event.def.AbstractFlushingEventListener] dirty checking collections View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974167#3974167 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974167 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: slow remote communication
I was able to skip this useless processing of cascades, by clearing the session (entitymanager.clear()) before returning. Using trace logging, i found out that the 9 seconds were all used to handle about 400 entities. Hibernate, i think you got a little problem here. Note: with trace logging enabled it took over 2 minutes. 2006-09-26 13:01:10,410 TRACE [org.hibernate.transaction.CacheSynchronization] transaction before completion callback 2006-09-26 13:01:10,410 TRACE [org.hibernate.jdbc.JDBCContext] before transaction completion 2006-09-26 13:01:10,410 TRACE [org.hibernate.impl.SessionImpl] before transaction completion 2006-09-26 13:01:10,410 TRACE [org.hibernate.ejb.AbstractEntityManagerImpl] automatically flushing session 2006-09-26 13:01:10,410 TRACE [org.hibernate.impl.SessionImpl] automatically flushing session 2006-09-26 13:01:10,410 TRACE [org.hibernate.event.def.AbstractFlushingEventListener] flushing session 2006-09-26 13:01:10,410 DEBUG [org.hibernate.event.def.AbstractFlushingEventListener] processing flush-time cascades ... 2006-09-26 13:03:49,101 TRACE [org.hibernate.event.def.AbstractFlushingEventListener] Processing unreferenced collections 2006-09-26 13:03:49,101 TRACE [org.hibernate.event.def.AbstractFlushingEventListener] Scheduling collection removes/(re)creates/updates 2006-09-26 13:03:49,101 DEBUG [org.hibernate.event.def.AbstractFlushingEventListener] Flushed: 0 insertions, 0 updates, 0 deletions to 418 objects 2006-09-26 13:03:49,101 DEBUG [org.hibernate.event.def.AbstractFlushingEventListener] Flushed: 0 (re)creations, 0 updates, 0 removals to 417 collections 2006-09-26 13:03:49,101 DEBUG [org.hibernate.pretty.Printer] listing entities: View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974187#3974187 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974187 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - slow remote communication
I have a stateless facade bean that fetches a deep hierarchic structure from my database using ejb3 with eager-mapped relations. This takes 2 seconds (timed with an ejb interceptor). On the client, i wrapped the ejb-proxy in a dynamic proxy, to time remote calls: 11 seconds. What is going on, in between the ejb-interceptor, and the client? Java-serialisation: i timed this, by serialising the fetched data into a byte-array-stream (and deserialising it again): 140ms. (using 4.0.4, rc8 and rc9, hsqldb or mysql, all the same) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974161#3974161 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974161 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB/JBoss] - serlialize extended persistence context to client
Is it possible to (de)serialize the extended persistence manager, in order to make an "offline" application that remembers (queues) the entity updates and deletions, and executes them later on, when the context is sent back to the server? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957697#3957697 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957697 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
