[JBossMQ] - UILClientILService Stopping
by mohan.nara
I use jboss-4.0.5.GA as my JMS server. i am getting below MDB (EJB3) error when onMessage() triggered. Can anyone help me to trace the issue?
[org.jboss.mq.il.uil2.UILClientILService] Stopping
2009-06-11 10:51:22,360 DEBUG [org.jboss.mq.il.uil2.SocketManager] Failed to send error reply
java.io.IOException: Client is not connected
at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:264)
at org.jboss.mq.il.uil2.SocketManager.access$800(SocketManager.java:53)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:408)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:398)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:595)
2009-06-11 10:51:22,360 ERROR [lk.dialog.sc.client.log.SCLogger] [FAILED] [PIN ALREADY REGISTRED] Requester No777060132
2009-06-11 10:51:22,360 DEBUG [org.jboss.mq.il.uil2.SocketManager] End ReadTask.run
2009-06-11 10:51:22,360 DEBUG [org.jboss.mq.il.uil2.SocketManager] End WriteTask.run
2009-06-11 10:51:22,359 DEBUG [org.jboss.mq.il.uil2.SocketManager] End WriteTask.run
2009-06-11 10:51:22,359 INFO [lk.dialog.smpp.gateway.core.util.SmppHandler] Sending SMS ->: 94777060132|Y
2009-06-11 10:51:22,359 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Exiting on IOE
java.io.InterruptedIOException: Operation interrupted
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
at org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBufferedInputStream.java:79)
at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2196)
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2376)
at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2443)
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2515)
at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2664)
at java.io.ObjectInputStream.readByte(ObjectInputStream.java:875)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:316)
at java.lang.Thread.run(Thread.java:595)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236885#4236885
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236885
17 years, 1 month
[JBoss Tools (users)] - Re: Problem with Jboss 5.0.1.GA under elipse 3.4.2
by Torleif
java.class.version=49.0
java.endorsed.dirs=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/endorsed
java.ext.dirs=/Library/Java/Extensions:/System/Library/Java/Extensions:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext
java.home=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
java.io.tmpdir=/tmp
java.library.path=.:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version=1.5.0_16-b06-284
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.5
java.vendor=Apple Inc.
java.vendor.url=http://www.apple.com/
In /Application/eclipse/configuration/config.ini it says this:
#This configuration file was written by: org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxFwConfigFileParser
#Tue Jun 09 17:15:38 PHT 2009
org.eclipse.update.reconcile=false
eclipse.p2.profile=SDKProfile
osgi.instance.area.default=(a)user.home/Documents/workspace
osgi.framework=file\:plugins/org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar
eclipse.buildId=M20090211-1700
osgi.bundles=reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.0.v20080604.jar@1\:start
org.eclipse.equinox.simpleconfigurator.configUrl=file\:org.eclipse.equinox.simpleconfigurator/bundles.info
eclipse.product=org.eclipse.sdk.ide
osgi.splashPath=platform\:/base/plugins/org.eclipse.platform
eclipse.p2.data.area=@config.dir/../p2
osgi.bundles.defaultStartLevel=4
In eclipse under help, configuration it says this:
java.vendor.url.bug=http://bugreport.apple.com/
java.version=1.5.0_16
java.vm.info=mixed mode
java.vm.name=Java HotSpot(TM) Client VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=Apple Inc.
java.vm.version=1.5.0_16-133
Yes is start jboss from within eclipse. This is what i see from the debug view:
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/java -agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:50503 "-Dprogram.name=JBossTools JBoss 5.0 Runtime" -server -Xms256m -Xmx512m -XX:MaxPermSize=256m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.endorsed.dirs=/Applications/jboss-5.1.0.GA/lib/endorsed -Dfile.encoding=MacRoman -classpath /Applications/jboss-5.1.0.GA/bin/run.jar org.jboss.Main --configuration=default -b localhost
It also says:
Classloader.findbootstrapClass(String) line: not available [native method]
Luancher$ExtClassLoader(ClassLoader).findBootstrapClass0(String) line: 946
Luancher$ExtClassLoader(ClassLoader).findBootstrapClass(String) line: 251
These one are not ticked like the other. It seems to be a problem here with something. Further down it also says that the Source not found for Classloader.findbootstrapClass(String) line: not available [native method] . You can edit source lookup path but i don't know what this is.
It seems to be allot of conflicts here with both eclipse, jboss and jboss tools. Maybe i should uninstall them all and then re-install everything from the beginning again? Is there a good web site where i can read how to install eclipse, jboss and jboss tools from a beginners point of view, easy to follow? Please let me know what you think of this.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236884#4236884
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236884
17 years, 1 month
[Security & JAAS/JBoss] - Authentication in ejb container fails to use security domain
by clin1
We found this problem when moving from JBoss 4 to JBoss 5.0.1.
Here is the server.log:
2009-06-10 21:15:16,822 DEBUG [org.jboss.security.integration.JNDIBasedSecurityManagement] (http-0.0.0.0-8080-1) Creating SDC for domain=CLIENT_LOGIN_MODULE
2009-06-10 21:15:16,822 DEBUG [org.jboss.security.plugins.auth.JaasSecurityManagerBase.CLIENT_LOGIN_MODULE] (http-0.0.0.0-8080-1) CallbackHandler: org.jboss.security.auth.callback.JBossCallbackHandler@1298c7d
2009-06-10 21:15:16,822 DEBUG [org.jboss.security.plugins.auth.JaasSecurityManagerBase.CLIENT_LOGIN_MODULE] (http-0.0.0.0-8080-1) CachePolicy set to: org.jboss.util.TimedCachePolicy@c677a7
2009-06-10 21:15:16,822 DEBUG [org.jboss.security.integration.JNDIBasedSecurityManagement] (http-0.0.0.0-8080-1) setCachePolicy, c=org.jboss.util.TimedCachePolicy@c677a7
2009-06-10 21:15:16,838 ERROR [org.jboss.security.auth.spi.UsersRolesLoginModule] (http-0.0.0.0-8080-1) Failed to load users/passwords/role files
java.io.IOException: No properties file: users.properties or defaults: defaultUsers.properties found
at org.jboss.security.auth.spi.Util.loadProperties(Util.java:198)
at org.jboss.security.auth.spi.UsersRolesLoginModule.loadUsers(UsersRolesLoginModule.java:186)
at org.jboss.security.auth.spi.UsersRolesLoginModule.createUsers(UsersRolesLoginModule.java:200)
at org.jboss.security.auth.spi.UsersRolesLoginModule.initialize(UsersRolesLoginModule.java:127)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:756)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at org.jboss.security.plugins.auth.JaasSecurityManagerBase.defaultLogin(JaasSecurityManagerBase.java:552)
at org.jboss.security.plugins.auth.JaasSecurityManagerBase.authenticate(JaasSecurityManagerBase.java:486)
at org.jboss.security.plugins.auth.JaasSecurityManagerBase.isValid(JaasSecurityManagerBase.java:365)
at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:160)
at org.jboss.security.javaee.EJBAuthenticationHelper.isValid(EJBAuthenticationHelper.java:87)
at org.jboss.ejb.plugins.SecurityActions$13.run(SecurityActions.java:543)
at org.jboss.ejb.plugins.SecurityActions$13.run(SecurityActions.java:540)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.ejb.plugins.SecurityActions.isValid(SecurityActions.java:539)
at org.jboss.ejb.plugins.SecurityInterceptor.checkSecurityContext(SecurityInterceptor.java:314)
at org.jboss.ejb.plugins.SecurityInterceptor.process(SecurityInterceptor.java:243)
at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:205)
at org.jboss.ejb.plugins.security.PreSecurityInterceptor.process(PreSecurityInterceptor.java:136)
at org.jboss.ejb.plugins.security.PreSecurityInterceptor.invokeHome(PreSecurityInterceptor.java:88)
at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:132)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:107)
at org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:639)
at org.jboss.ejb.Container.invoke(Container.java:1046)
at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invokeHome(BaseLocalProxyFactory.java:362)
at org.jboss.ejb.plugins.local.LocalHomeProxy.invoke(LocalHomeProxy.java:133)
at $Proxy120.create(Unknown Source)
at com.filenet.apiimpl.transport.ejb.EnginePortFactory.create(EnginePortFactory.java:36)
at com.filenet.apiimpl.wsi.ServerHelperNst.getEnginePort(ServerHelperNst.java:90)
at com.filenet.apiimpl.wsi.ServiceSessionNst$1.run(ServiceSessionNst.java:1050)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.filenet.apiimpl.authentication.util.J2EEAuthnUtil.runAs(J2EEAuthnUtil.java:533)
at com.filenet.apiimpl.authentication.util.J2EEAuthnUtilJB.runAs(J2EEAuthnUtilJB.java:280)
at com.filenet.apiimpl.util.J2EEUtilJB.doAs(J2EEUtilJB.java:103)
at com.filenet.apiimpl.wsi.ServiceSessionNst.makeServerInternalEJBCall(ServiceSessionNst.java:961)
at com.filenet.apiimpl.wsi.ServiceSessionNst.incomingRequestToServer(ServiceSessionNst.java:917)
at com.filenet.engine.wsi.ListenerNst.service(ListenerNst.java:101)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
2009-06-10 21:15:16,853 ERROR [org.jboss.ejb.plugins.SecurityInterceptor] (http-0.0.0.0-8080-1) Error in Security Interceptor
java.lang.SecurityException: Authentication exception, principal=CEAdmin
at org.jboss.ejb.plugins.SecurityInterceptor.checkSecurityContext(SecurityInterceptor.java:321)
at org.jboss.ejb.plugins.SecurityInterceptor.process(SecurityInterceptor.java:243)
at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:205)
at org.jboss.ejb.plugins.security.PreSecurityInterceptor.process(PreSecurityInterceptor.java:136)
at org.jboss.ejb.plugins.security.PreSecurityInterceptor.invokeHome(PreSecurityInterceptor.java:88)
at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:132)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:107)
at org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:639)
at org.jboss.ejb.Container.invoke(Container.java:1046)
at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invokeHome(BaseLocalProxyFactory.java:362)
at org.jboss.ejb.plugins.local.LocalHomeProxy.invoke(LocalHomeProxy.java:133)
at $Proxy120.create(Unknown Source)
at com.filenet.apiimpl.transport.ejb.EnginePortFactory.create(EnginePortFactory.java:36)
at com.filenet.apiimpl.wsi.ServerHelperNst.getEnginePort(ServerHelperNst.java:90)
at com.filenet.apiimpl.wsi.ServiceSessionNst$1.run(ServiceSessionNst.java:1050)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.filenet.apiimpl.authentication.util.J2EEAuthnUtil.runAs(J2EEAuthnUtil.java:533)
at com.filenet.apiimpl.authentication.util.J2EEAuthnUtilJB.runAs(J2EEAuthnUtilJB.java:280)
at com.filenet.apiimpl.util.J2EEUtilJB.doAs(J2EEUtilJB.java:103)
at com.filenet.apiimpl.wsi.ServiceSessionNst.makeServerInternalEJBCall(ServiceSessionNst.java:961)
at com.filenet.apiimpl.wsi.ServiceSessionNst.incomingRequestToServer(ServiceSessionNst.java:917)
at com.filenet.engine.wsi.ListenerNst.service(ListenerNst.java:101)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
The jboss.xml file in our server ejb's META-INF:
<?xml version="1.0"?>
<enterprise-beans>
<ejb-name>Engine</ejb-name>
<jndi-name>FileNet/Engine</jndi-name>
<local-jndi-name>FileNet/Local/Engine</local-jndi-name>
<ejb-name>EngineCore</ejb-name>
<local-jndi-name>FileNet/Local/EngineCore</local-jndi-name>
<ejb-name>EngineContent</ejb-name>
<jndi-name>FileNet/EngineContent</jndi-name>
<local-jndi-name>FileNet/Local/EngineContent</local-jndi-name>
<ejb-name>EngineContentCore</ejb-name>
<local-jndi-name>FileNet/Local/EngineContentCore</local-jndi-name>
</enterprise-beans>
<container-configurations>
<container-configuration>
<container-name>Standard Stateless SessionBean</container-name>
<security-domain>java:/jaas/FileNet</security-domain>
</container-configuration>
</container-configurations>
In JBoss 5.0.1, we found that the SecurityInterceptor correctly retrieved the security domain from jboss.xml. However, when it is inside EJBAuthenticationHelper.isValid() the security domain is "CLIENT_LOGIN_MODULE".
Since there is no "CLIENT_LOGIN_MODULE" application-policy defined in our login-config.xml file, it falls back to "other" and executes the wrong login module - UsersRolesLoginModule.
Does anyone know why the security domain override via jboss.xml is not working in JBoss 5?
How do we get the ejb authentication to use "FileNet" as specified in the jboss.xml?
We tried adding <security-domain>java:/jaas/FileNet</security-domain> as a top level element in jboss.xml to no avail.
Does anyone experience the same issue when migrating from JBoss 4 to 5?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236880#4236880
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236880
17 years, 1 month
[Installation, Configuration & DEPLOYMENT] - cannot load classes located in WEB-INF/lib
by jbosshog98
I am not sure if this is a JBoss or Railo thing, I'm leaning toward JBoss, but here's the basic situation.
I have an EAR deployment with a WAR inside the EAR, when I start up JBoss with some custom JAR files in the WEB-INF/lib folder of the WAR, it starts up fine. JBoss uses the files as it should to create classes that are created at startup (servlets defined in web.xml in WEB-INF of the WAR)
However, if I attempt to load those classes from within a Railo page with createObject() Railo throws an error that it cannot see them.
If I place the JAR files in the lib folder for the EAR, Railo can see them fine and use them with createObjstarect()
So, is Railo not able to see classes in WEB-INF/lib after the startup? Or is this a JBoss issue?
The reason I need to do this is that I want some WARs to have the libraries and some not.
My actual issue is that I want to have WEB-INF/lib/customjars1, WEB-INF/lib/customjars2, etc I want a /lib/hibernate folder, etc I have too many JARs and I want to keep them organized.
I can't figure out how to get JBoss to look in sub folders of WEB-INF/lib for folders in each WAR.
In JBoss in the jboss-service.xml I can specify additional classpaths, which works, but the problem is that you then have to modify the jboss-service.xml file and add a path for each WAR that you add. I want the WARs to contain all of the needed information without having to modify JBoss for each one.
I can work around this by putting the JARs in the lib folder for the EAR, but like I said, I don't want all the WARs to have them and there are conflicts in some.
So, what's going on here? How can I get Railo to see the classes in WEB-INF/lib at runtime?
Thanks!!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236872#4236872
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236872
17 years, 1 month
[Tomcat, HTTPD, Servlets & JSP] - Tomcat / JBoss mod_jk with Apache Bad Gateway
by jbosshog98
Thanks ahead of time for anything anyone can do to help me!
I am running Apache 2.2 in front of JBoss 4.2.3 that uses Tomcat as its web server. I am using Apache to connect my virtual hosts to JBoss through mod_jk.
I can access most of my pages fine, I type in foo2.com (my test domain) and I receive my pages lightning fast, no problem.
However, some pages that have longer requests, such as those that initialize lots of libraries or make calls to another server (in this case, either setting up or verifying a database connection) are intermittently giving me this error:
Bad Gateway
The proxy server received an invalid response from an upstream server.
Apache/2.2.3 (CentOS) Server at www.foo2.com Port 80
So, like I said, almost all requests go through perfectly fine, so I know the mod_jk is working. Here is my mod_jk.log file:
The first block is my failed request, the second block are successful requests on the same domain:
[Wed Jun 10 16:23:02 2009][17806:4090746208] [info] init_jk::mod_jk.c (3183): mod_jk/1.2.28 initialized
[Wed Jun 10 16:23:02 2009][17808:4090746208] [info] init_jk::mod_jk.c (3183): mod_jk/1.2.28 initialized
[Wed Jun 10 16:23:19 2009][17810:4090746208] [info] ajp_connection_tcp_get_message::jk_ajp_common.c (1150): (node1) can't receive the response header message from tomcat, network problems or tomcat (127.0.0.1:8009) is down (errno=11)
[Wed Jun 10 16:23:19 2009][17810:4090746208] [error] ajp_get_reply::jk_ajp_common.c (1962): (node1) Tomcat is down or refused connection. No response has been sent to the client (yet)
[Wed Jun 10 16:23:19 2009][17810:4090746208] [error] ajp_service::jk_ajp_common.c (2440): (node1) sending request to tomcat failed (unrecoverable), (attempt=1)
[Wed Jun 10 16:23:19 2009]node1 www.foo2.com 12.051237
[Wed Jun 10 16:23:19 2009][17810:4090746208] [info] jk_handler::mod_jk.c (2615): Service error=0 for worker=node1
[Wed Jun 10 16:23:39 2009]node1 www.foo2.com 0.027028
[Wed Jun 10 16:23:39 2009]node1 www.foo2.com 0.035305
[Wed Jun 10 16:23:40 2009]node1 www.foo2.com 0.024485
The successful attempts are from trying to access any other page that doesn't take longer. This particular page that gives me the error talks to another server to get database information.
So, I'm not sure what is going on here. I have read online qabout things like keepalive and have put:
worker.node1.socket_keepalive=1
in my workers.properties file, but to no avail. I have also put SetEnv proxy-nokeepalive 1 in my virtual host, also to no avail. Also, I am using AJAX, so I don't want any keepalive configuration to cause problems with AJAX. I'm not sure how all of this works.
So, I'm wondering how to resolve this issue. One note, when I try to request a page that gives me the gateway upstream error, the code on the page will execute (most of the time) but I still receive the error in my browser. (If I write a file to disk or update a database from within the page, it does write the file and update the database)
I am no expert in this area, so please go easy with the terminology and assumptions that I know how most of this works... I don't :)
The connection is going to JBoss, and I have the following in my server.xml:
<Engine name="jboss.web" defaultHost="localhost" jvmRoute="node1"
My config files are below:
>From my httpd-vhosts.conf:
<VirtualHost *:80>
ServerAdmin webmaster(a)dummy-host.example.com
ServerName foo2.com
ServerAlias www.foo2.com
ErrorLog "logs/dummy-host.example.com-error_log"
CustomLog "logs/dummy-host.example.com-access_log" common
DirectoryIndex index.cfm index.htm
JkMount /* node1
mod-jk.conf:
# Load mod_jk module
# Specify the filename of the mod_jk lib
LoadModule jk_module modules/mod_jk.so
# Where to find workers.properties
JkWorkersFile conf/workers.properties
# Where to put jk logs
JkLogFile logs/mod_jk.log
# Set the jk log level [debug/error/info]
JkLogLevel info
# Select the log format
JkLogStampFormat "[%a %b %d %H:%M:%S %Y]"
# JkOptions indicates to send SSK KEY SIZE
# Notes:
# 1) Changed from +ForwardURICompat.
# 2) For mod_rewrite compatibility, use +ForwardURIProxy (default since 1.2.24)
# See http://tomcat.apache.org/security-jk.html
JkOptions +ForwardKeySize +ForwardURICompatUnparsed -ForwardDirectories
# JkRequestLogFormat
JkRequestLogFormat "%w %V %T"
# Mount your applications
JkMount /__application__/* loadbalancer
# Let Apache serve the images
JkUnMount /__application__/images/* loadbalancer
# You can use external file for mount points.
# It will be checked for updates each 60 seconds.
# The format of the file is: /url=worker
# /examples/*=loadbalancer
JkMountFile conf/uriworkermap.properties
# Add shared memory.
# This directive is present with 1.2.10 and
# later versions of mod_jk, and is needed for
# for load balancing to work properly
# Note: Replaced JkShmFile logs/jk.shm due to SELinux issues. Refer to
# https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=225452
JkShmFile run/jk.shm
# Add jkstatus for managing runtime data
<Location /jkstatus>
JkMount status
Order deny,allow
Deny from all
Allow from 127.0.0.1
workers.properties:
# Define list of workers that will be used
# for mapping requests
# The configuration directives are valid
# for the mod_jk version 1.2.18 and later
#
worker.list=loadbalancer,status,node1
# Define Node1
# modify the host as your host IP or DNS name.
worker.node1.port=8009
worker.node1.host=localhost
worker.node1.type=ajp13
worker.node1.lbfactor=1
worker.node1.socket_timeout=10
worker.node1.prepost_timeout=10000 #Not required if using ping_mode=A
worker.node1.connect_timeout=10000 #Not required if using ping_mode=A
worker.node1.ping_mode=A #As of mod_jk 1.2.27
# worker.node1.connection_pool_size=10 (1)
# Load-balancing behaviour
worker.loadbalancer.type=lb
worker.loadbalancer.balance_workers=node1
# Status worker for managing load balancer
worker.status.type=status
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236864#4236864
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236864
17 years, 1 month
[JBoss Messaging] - MDB Reading On Remote Topic
by Chopper
Hello, my name is Giuseppe,
This is the situation:
I have 2 JBoss installed on my PC (kubuntu 9.04).
JBoss A (v 4.2.3) updated with Messaging and JBoss B (v 5.0.0, native Messaging, JBPM installed).
With this commands i obtain 2 "virtual" ip address on my pc:
sudo ip addr add 192.168.0.203 dev lo
sudo ip addr add 192.168.0.209 dev lo
A Java web application with servlet must be deployed on JBoss A: it sends messages on a topic.
I made this topic adding this code to the file destination-services.xml into directory...deploy/messaging of JBoss A
| <mbean code="org.jboss.jms.server.destination.TopicService"
| name="jboss.messaging.destination:service=Topic,name=pyTopic"
| xmbean-dd="xmdesc/Topic-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
|
then i added into jms-ds.xml in JBoss B the following JMSProvider:
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider,server=http://192.168.0.203">
| <attribute name="ProviderName">RemoteJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
| <!-- The connection factory -->
| <attribute name="FactoryRef">XAConnectionFactory</attribute>
| <!-- The queue connection factory -->
| <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
| <!-- The topic factory -->
| <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
| <!-- Connect to JNDI on the host "the-remote-host-name" port 1099-->
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jnp.interfaces
| java.naming.provider.url=192.168.0.203:1099
| </attribute>
| </mbean>
|
and Into my standardjboss.xml (JBoss B) i added an
| <invoker-proxy-binding>
| <name>my-mdb-invoker</name>
| <invoker-mbean>does-not-matter</invoker-mbean>
| <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
| <proxy-factory-config>
| <JMSProviderAdapterJNDI>RemoteJMSProvider</JMSProviderAdapterJNDI>
| <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
| <MinimumSize>1</MinimumSize>
| <MaximumSize>15</MaximumSize>
| <KeepAliveMillis>30000</KeepAliveMillis>
| <MaxMessages>1</MaxMessages>
| <MDBConfig>
| <ReconnectIntervalSec>10</ReconnectIntervalSec>
| <DLQConfig>
| <DestinationQueue>queue/DLQ</DestinationQueue>
| <MaxTimesRedelivered>10</MaxTimesRedelivered>
| <TimeToLive>0</TimeToLive>
| </DLQConfig>
| </MDBConfig>
| </proxy-factory-config>
| </invoker-proxy-binding>
|
finally in jboss.xml (into the MDB) i have something like this:
| <?xml version="1.0" encoding="UTF-8"?>
| <jboss>
| <enterprise-beans>
| <message-driven>
| <ejb-name>NotificationHandlerBean</ejb-name>
| <destination-jndi-name>topic/pyTopic</destination-jndi-name>
| <invoker-bindings>
| <invoker>
| <invoker-proxy-binding-name>my-mdb-invoker</invoker-proxy-binding-name>
| </invoker>
| </invoker-bindings>
| </message-driven>
| </enterprise-beans>
| </jboss>
|
|
I used Netbeans 6.5.1 developing both Sender (servlet) and Receiver (MDB) application.
Now i execute jbossA on 192.168.0.203 and jbossB on 192.168.0.209..
I tryed different solution but the error seems to be always the same:
*** CONTEXTS IN ERROR: Name -> Error
jboss.j2ee:binding=my-mdb-invoker,jndiName=local/NotificationHandlerBean@2732525,plugin=invoker,service=EJB -> org.jboss.deployment.DeploymentException: Themessage-destination 'pyTopic' has no jndi-name in jboss.xml
Please help me..i'm in trouble!!!
Thanks a lot...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236859#4236859
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236859
17 years, 1 month