Originally posted by Ole Hornischer:
After a bit more research, I stumbled over the jndi.properties file in the JBoss conf-folder. It seems to override the file in my ear, since after I added the Provider URL to it my topic posting works.
In the jndi.properties in the conf-folder it says I should not alter the file unless I know what I am doing. What consequences can arise if i add the provider URL in it?
Originally posted by Ole Hornischer:
Or did it not override my own jndi.properties in the ear, but the server simply did not find the one in the .ear?
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming.jnp.interfaces
java.naming.provider.url= 11.22.33.44:1099
Regards,<br />Andrea<br /> <br /><a href="http://www.linkedin.com/in/andreagazzarini" target="_blank" rel="nofollow">Andrea Gazzarini</a><br />Skype ID : gazzax72<br />Google Talk ID : a.gazzarini@gmail.com<br /><a href="http://www.andreagazzarini.blogspot.com" target="_blank" rel="nofollow">My Blog</a>
Originally posted by a.gazzarini:
Anyway, I'm not understanding why don't you edit the conf/jndi.properties under the jboss installation? It's more flexible of inserting that directly inside the ear...
Originally posted by Ole Hornischer:
No more ideas what could be wrong?
Though changing the conf/jndi.properties in the jboss installation is going to work, its not the correct place to do this
Regards,<br />Andrea<br /> <br /><a href="http://www.linkedin.com/in/andreagazzarini" target="_blank" rel="nofollow">Andrea Gazzarini</a><br />Skype ID : gazzax72<br />Google Talk ID : a.gazzarini@gmail.com<br /><a href="http://www.andreagazzarini.blogspot.com" target="_blank" rel="nofollow">My Blog</a>
Originally posted by Andrea Gazzarini:
If the naming service is located on 11.22.33.44:1099 JBoss is supposed to run with that naming service and therefore it doesn't make sense to have an implicit "default" value of localhost:1099.
2008-11-17 12:18:40,435 ERROR [STDERR] at com.tza.server.ServerMain.run(Unknown Source)
2008-11-17 12:18:40,435 ERROR [STDERR] at java.lang.Thread.run(Unknown Source)
I just tried this on my local setup of 4.2.3 GA. I started the server with -b <IP Address> and then did not change any jndi.properties file nor did i include any jndi.properties in my application deployed on JBoss. Then from a servlet within the application deployed on the same server, i did a simple JNDI lookup
Where are you doing this lookup from? Is it a standalone client or from some servlet/jsp on the same server?
Putting the file on the ear has moreless the same meaning of hard-coding that. If you want to change the address(run for example this application on another machine) you must rebuild the archive.
Simply I think that the information related to the external environment shoudln't be inside your archive (if it is a file or you hard-coded that there's a little difference IMO)
quote:2008-11-17 12:18:40,435 ERROR [STDERR] at com.tza.server.ServerMain.run(Unknown Source)
2008-11-17 12:18:40,435 ERROR [STDERR] at java.lang.Thread.run(Unknown Source)
How is this thread started/created and by whom?
Originally posted by Ole Hornischer:
Concerning this another question has been on my mind for a while now: Is it possible to start a "main" class or call a method in the server app after booting the JBoss? I have a few backgroubd processes I need to have running continously as soon as the server started. Right now I still need to trigger the start of these processes via EJB service from a client. But I'd rather have them started after JBoss boot, if possible.
Originally posted by Ole Hornischer:
Now the bean is started at deployment and my processes are triggered.
If you settle for what they are giving you, you deserve what you get. Fight for this tiny ad!
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
|