I am very new to the product, got it up and running, and was going through the tutorial. I have 3.2.2 and the tutorial itself seems outdated to another version. There are all kinds of things not mentioned, and things that are mentioned that don't exist in the same way. For instance right clicking and creating a task on a node.
I worked my way through myself and somewhat got the hang of things. But I wanted to bring attention that this needs to be badly updated because I cannot find another tutorial. Does anyone have a better tutorial that is updated I can look at?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105648#4105648
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105648
Glad it worked.
I can only speculate on the MDB undeploy behavior; for a better answer you'd probably need to post on EJB or JMS forums. :)
Pure speculation:
As you undeploy it's in the stop() method for the container. Sees there are active beans so the deployer thread blocks waiting for that to clear. It happens that stop() is coded in such a way that the blocking occurs before the step gets executed that prevents creating new MDB instances to handle the new messages you generate.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105645#4105645
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105645
I stand corrected. It finally DID undeploy the MDBs.
One MDB was running when I undeployed. That MDB continued to run (which is correct) and then when it was finished, it sent 2 messages on the Queue which spawned 2 new MDBs. Once those had finished, it undeployed.
Is there something inside JBoss that causes the JMS Messages sent from inside a MDB to continue running while a JMS Message sent from outside the MDB waits until the MDBs are undeployed/redeployed again?
Very interesting behavior, but I'll take it!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105640#4105640
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105640
well, i'm not a JMX guru, but i had to add the following to my run.conf to enable remote JMX in jboss:
#added for remote access to JMX (for example Hyperic)
| JAVA_OPTS="$JAVA_OPTS -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl"
| JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"
| JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote"
|
| JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.authenticate=false"
| JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.ssl=false"
| JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.port=3099"
with that i was able to use jconsole to connect to the JMX server in jboss (there's nothing special about the port, i think)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105634#4105634
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105634
hmmm, this didn't seem to have anything to do with it.
I added jaxen jar file, but the error persisted. (I guess this one is already included in the seam/jboss libs, no?).
As I mentioned before, the error occurred after a file was uploaded, and not processed. Adding this to my stateful session bean fixed the problem:
| if (this.newUploadFile!=null) {
| try {
| this.newUploadFile.close();
| this.newUploadFile = null;
| }
| catch (Exception e) {
| }
| }
|
I guess I'm not the only one having this problem (InputStream doesn't seem to be serializable), since I'm using straightforward elements (s:fileUpload to an inputstream). Perhaps it can be included/mentioned in the docs?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105632#4105632
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105632