1. JMX-Console is asking for username and password(even after disabling the security code in the respective xml file as per the configuration guide)
2. Data source creation for Oracle 10g – Steps how to configure with an example, since I tried as instructed generally in the guide but did not work
3. I am using Apache HTTP server 2.0.63 for load balancing. I have downloaded mod_jk-1.2.28-httpd-2.0.52.so from the below mentioned link and renamed to mod_jk.so and placed in <Apache_Home>/modules folders as indicated in the guide, but URLs are not accessible. But I am able to access the individual node URLS.
The following error I have observed in the apache log file.
[Tue Apr 28 21:56:08 2009][6644:7460] [info] jk_connect.c (594): connect to 127.0.0.1:8009 failed (errno=61)
[Tue Apr 28 21:56:08 2009][6644:7460] [info] jk_ajp_common.c (922): Failed opening socket to (127.0.0.1:8009) (errno=61)
[Tue Apr 28 21:56:08 2009][6644:7460] [error] jk_ajp_common.c (1507): (node1) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
Can any one please provide solutions for the above problems.
1) If you did it correctly, it would have worked.
2) If you .. (oh, I already said that)
Anyway, without telling us exactly what you did how can we point out to you what you did incorrectly? So for item 1 please post all of the changes that you made. For item 2, please post the oracle-ds.xml file and also post any exception stack traces shown in the console log when you used the *-ds.xml file. Also, I assume you started from docs/examples/jca/oracel-ds.xml
I'll leave item #3 to someone who has working with mod_jk.
1. Now I am able to access JMX Console after uncommenting the line admin=admin in jmx-console-users.properties file available under folderE:\jboss-eap-4.3\jboss-as\server\production\conf\props.
But I am unable to access web console and I observe the following error in the server.log file.
2009-05-02 14:45:36,934 DEBUG [org.jboss.system.ServiceController] Creating service jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory
2009-05-02 14:45:36,934 DEBUG [org.jboss.invocation.jrmp.server.JRMPProxyFactory] Creating jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory
2009-05-02 14:45:36,934 DEBUG [org.jboss.invocation.jrmp.server.JRMPProxyFactory] Created jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory
2009-05-02 14:45:36,934 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory dependents are: [ObjectName: jboss.admin:service=PluginManager
I Depend On:
Depends On Me:
, ObjectName: jboss.jmx:type=adaptor,name=MBeanProxyRemote,protocol=jrmp
I Depend On:
2009-05-02 14:45:36,934 DEBUG [org.jboss.system.ServiceController] Creating service jboss.admin:service=PluginManager
2009-05-02 14:45:36,934 DEBUG [org.jboss.console.manager.PluginManager] Creating jboss.admin:service=PluginManager
2009-05-02 14:45:36,934 DEBUG [org.jboss.console.manager.PluginManager] Created jboss.admin:service=PluginManager
2009-05-02 14:45:36,934 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.admin:service=PluginManager dependents are: [ObjectName: jboss.web.deployment:war=web-console.war,id=-1004038194
I Depend On:
2. JDBC configuration, I have just placed default(from folder E:\jboss-eap-4.3_old\jboss-as\docs\examples\jca) oralce-ds.xml file into the folder E:\jboss-eap-4.3\jboss-as\server\production\deploy. The following is the content after modifications.
How do I know this data source is working or not and how can I access this data source.
1) The security config settings for the web console as screwed up. It's jboss-web.xml file references a login module named "web-console", and if you look in server/xxx/conf/login-config.xml, you will see that web-console references the non-existent files server/xxx/conf/web-console-users.properties and .../web-console-roles.properties. Thus it is fated to not work unless you fix it. Why is this? Because web console is an orphan and has not been updated in years. You would probably be better off installing Embedded Jopr. Caveat: I haven't tried Embedded Jopr on EAP 4.3; and since EAP 4.3 uses JBoss Messaging in place of JBossMQ, I'm not sure what Embedded Jopr would do.
2) Look in the console log - you should see the AG_AGX_MAIN_DS datasource being deploy. (I see you are using the "production" config. Are you starting as "run -c production"?) Here is an example of what you should see (my datasource is named "jdbc/messagingDS"):
09:03:41,503 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=jdbc/messagingDS' to JNDI name 'java:jdbc/messagingDS'
To access it in your code (or config files) look up that JNDI name AG_AGX_MAIN_DS.
I have used the default oracle-ds file available in sample\jca for configuring the oracle ds. Now I have one doubt, I am deploying a war(named Admin_258.war) file by placing in the farm folder. and the file is being pushed into the cluster successfully. but on restart the deployment is getting undeployed.
Due to above problem, whatever changes we made to the deployment in the folder jboss-eap-4.3\jboss-as\server\node1\tmp\deploy\tmp51124Admin_258-exp.war are getting deleted. and we need to do theses property settings each time whenever the application server gets restarted.
Can some one suggest how to avoid this deployment deletion from the temp folder. So that even if we restart the jboss also we can make use of the same deployment.
The tmp directory is named that for a reason - it is a temporary working directory and you should not reply one any changes to make to it to be persistent. There is no way to make it persistent. The usual answer to this problem is to used an exploded deployment, but I do not think that will work in the farm directory. You will have to use some other mechanism, such asp lacing the configuration file in the conf directory and accessing it from there. If I recall correctly, the conf directory is in the classpath so you should not have ot change your code if you are loading the properties as a classpath resource.
Thanks for the reply. It is not only the configuration/properties file. The application was designed in such a way that say for example if you generate a report from the application, it will send the request to another report generation engine which will generate the report and hand it over to the application, which in turn place the reports in the reports folder of the exploded war file directory(folder structure looks to be Aris\reports). So always the application reads the reports from the reports folder location which is available in the exploded war file location(i.e., in the temp folder).
I hope it makes clear to you. Till now we are using weblogic cluster where the deployment would be available in exploded format in the weblogic temp folder. We are managing with that. Since we are using JBOSS for the first time we are facing this problem.
Based on your answer it seems that there is no option to stop the undeployment/re-deployment during stop/start of JBOSS for existing deployments. Please confirm.