[Installation, Configuration & DEPLOYMENT] - Re: JBoss process suddenly terminates from time to time
by PeterJ
In the server.log file, was there a shutdown message like the following:
2008-10-22 11:27:18,253 INFO [org.jboss.system.server.Server] Shutting down the server, blockingShutdown: false
2008-10-22 11:27:18,269 INFO [org.jboss.system.server.Server] Server exit(0) called
2008-10-22 11:27:18,269 INFO [org.jboss.system.server.Server] Runtime shutdown hook called, forceHalt: true
2008-10-22 11:27:18,269 INFO [org.jboss.system.server.Server] JBoss SHUTDOWN: Undeploying all packages
If there was, then something is signaling the app server to shut down. If not, then either the JVM is crashing or something else in the operating system is forcefully terminating the process.
How is the app server being started? Others have started using a remote shell and have had the app server terminate when closing the shell.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184517#4184517
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184517
17 years, 6 months
[EJB 3.0] - Re: @EJB injection in JBoss 5 application clients?
by ALRubinger
Jaikiran, you give a good example of why the spec dictates the fields must be injected into static members. But it's OK to criticize something for being stupid.
"bcn" wrote : In real-world application that would make it almost useless.
Yep.
Imagine if MC or Spring or any injection container limited you in this regard. The difference is whether your object is managed or not; if you create your own objects, they're not managed and you can't expect injection. If you get it from a container or other lookup store, then that's another story.
I've never liked Application Clients as they are. In addition to these programmatic limitations with injection into the Main class (which completely destroys good program design), you're limited to obtaining services from only one host.
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184515#4184515
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184515
17 years, 6 months
[JBossWS] - Re: Full control of client and server certificates with a JB
by jeckles933
Trying to do the same thing. I can't understand what other people are doing to get around this problem. We have multiple keystores, so i have to override the default behavior for the SSLContext...
This is what i need to do, but i can't figure out how/when to call this to set the socket factory.
| KeyStore ts = KeyStore.getInstance("JKS");
| ts.load(new FileInputStream(trustStoreFullName), trustStorePassword.toCharArray());
| TrustManager[] tm;
| TrustManagerFactory tmf = TrustManagerFactory.getInstance(TrustManagerFactory.getDefaultAlgorithm());
| tmf.init(ts);
| tm = tmf.getTrustManagers();
|
| SSLContext sslContext = SSLContext.getInstance("SSL");
| sslContext.init(kmf.getKeyManagers(), tm, null);
|
| SSLSocketFactory sslSocketFactory = sslContext.getSocketFactory();
|
| HttpsURLConnection urlc = (HttpsURLConnection) url.openConnection();
| urlc.setSSLSocketFactory(sslSocketFactory);
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184514#4184514
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184514
17 years, 6 months