I've had similar problems with Jboss authentication I inherited from another developer. I'm very interested in the answers to this problem, as currently my webapp doesn't seem to have any kind of timeout on logins.
Currently I stay logged into the website until I either close the brower, or clear out all cookies and invalidate my session via my browser. I'm not using any EJBs, though I did find some references to login timeouts if you are using EJBs
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038566#4038566
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038566
Quick check of the code looks like it was added at some point so it will check for lib unless this check is explicitly disabled. You also have the option of overriding this in your jboss-app.xml file. It would look something along the lines of:
| <library-directory>dir</library-directory>
|
Again this is a non-standard JBoss approach but if you aren't porting your app to another environment it's probably cool.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038563#4038563
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038563
Using ej3 timer service, I am creating a recurring hourly timer. Its working fine if I leave my application running, i.e. I get the initial timer callback as specified and then hourly from then on.
However, after getting my initial timer callback, if I re-deploy my app or re-start jboss before the next due hourly callback time, I do get called back right away. I was expecting that I should be called back only when my next hourly callback is due, since initial callback had already been delivered.
Is this a bug or as per specs?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038562#4038562
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038562
This is just a guess but I think the problem is that NetBeans is not able to manage or signal to/from JBoss. So it deploys the first time (starting Jboss) but is not receiving any further communication with JBoss and thinks it is not started.
The only clue I've found is that there is a Tomcat account that NetBeans looks like it uses to communicate with Jboss. The account name is "ide", and it seems to be supplying a hidden password. Perhaps resetting or recreating this account is the key?
I'm posting this because I'm having the same problem as of yesterday and looking for help on fixing it. Up until then, I generally had good interaction between Netbeans and JBoss.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038555#4038555
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038555
"weston.price(a)jboss.com" wrote : anonymous wrote :
| | Interesting ... it works for .JAR files, but not .EAR files.
| |
|
| Could you explain what you mean by this? I am assuming you added the Class-Path: entry to the EJB.jar files MANIFEST.MF.
|
|
I did, but I found that to be unnecessary. Just so long as I put my lib files in the Jar file (under the root/lib) JBoss was then able to see the lib files on deploy. My manifest.mf file doesn't reflect any class path options. Does JBoss introspect that folder on default?
- Graeme.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038553#4038553
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038553