[JBoss Messaging] - Re: JBM exception
by TheOverlord
And more errors:
| ERROR org.jboss.messaging.util.ExceptionUtil - SessionEndpoint[r72-wf8uddjf-1-le525djf-g3buv3-s36hs4] deleteTemporaryDestination [x72-g36wddjf-1-le525djf-g3buv3-s36hs4]
| java.lang.IllegalStateException: org.jboss.messaging.core.impl.postoffice.GroupMember@1e0fe7d response not received from XXX.XXX.XXX.XXX:XXXXX - there may be others
| at org.jboss.messaging.core.impl.postoffice.GroupMember.multicastControl(GroupMember.java:246)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.internalRemoveBinding(MessagingPostOffice.java:1932)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.removeBinding(MessagingPostOffice.java:469)
| at org.jboss.jms.server.endpoint.ServerSessionEndpoint.deleteTemporaryDestination(ServerSessionEndpoint.java:736)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$deleteTemporaryDestination$aop(SessionAdvised.java:130)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised$deleteTemporaryDestination_N5233806045047796315.invokeNext(SessionAdvised$deleteTemporaryDestination_N5233806045047796315.java)
| at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised$deleteTemporaryDestination_N5233806045047796315.invokeNext(SessionAdvised$deleteTemporaryDestination_N5233806045047796315.java)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised.deleteTemporaryDestination(SessionAdvised.java)
| at org.jboss.jms.wireformat.SessionDeleteTemporaryDestinationRequest.serverInvoke(SessionDeleteTemporaryDestinationRequest.java:75)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809)
| at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101)
| at org.jboss.remoting.Client.invoke(Client.java:1634)
| at org.jboss.remoting.Client.invoke(Client.java:548)
| at org.jboss.remoting.Client.invoke(Client.java:536)
| at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)
| at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)
| at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$deleteTemporaryDestination$aop(ClientSessionDelegate.java:338)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$deleteTemporaryDestination_N5233806045047796315.invokeNext(ClientSessionDelegate$deleteTemporaryDestination_N5233806045047796315.java)
| at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$deleteTemporaryDestination_N5233806045047796315.invokeNext(ClientSessionDelegate$deleteTemporaryDestination_N5233806045047796315.java)
| at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$deleteTemporaryDestination_N5233806045047796315.invokeNext(ClientSessionDelegate$deleteTemporaryDestination_N5233806045047796315.java)
| at org.jboss.jms.client.delegate.ClientSessionDelegate.deleteTemporaryDestination(ClientSessionDelegate.java)
| at org.jboss.jms.destination.JBossTemporaryQueue.delete(JBossTemporaryQueue.java:71)
| at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.close(JmsSessionFactoryImpl.java:299)
|
Why all these errors?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168259#4168259
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168259
17 years, 4 months
[Beginners Corner] - Re: Application Error - Resource not Found
by PeterJ
First, the directory locations are incorrect. The 'tmp' directory is a temporary, working directory. I hope that you did not place the files there. You should have placed them into the /usr/local/jboss/server/default/deploy directory. If you did place the file in the 'tmp' directory, stop the app server, remove the /usr/local/jboss/server/default/tmp, /usr/local/jboss/server/default/work, and /usr/local/jboss/server/default/data directories. Then place the EAR archive into the the /usr/local/jboss/server/default/deploy directory. Then start the app server again.
Since you have the WARs embedded within an EAR, post your application.xml file. Also, post the jboss-app.xml file, if you have one. Both should be in the meta-inf directory.
I assume that since you did not post any jboss-web.xml files that you don't have any (earlier you implied that you did have jboss-web.xml file).
I also assume that the file names (turtle.war/web-xml, csa.war.web-xml) are typos, and that they are both actually named web.xml.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168255#4168255
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168255
17 years, 4 months
[Beginners Corner] - Re: Application Error - Resource not Found
by shawn.geraghty
Here are the links to the turtle.war and csa.war directories.
/usr/local/jboss/server/default/tmp/deploy/tmp52561turtle-turtle.ear-contents/turtle.war
and
/usr/local/jboss/server/default/tmp/deploy/tmp52560csa-turtle.ear-contents/csa.war
Inside each directory is the expanded war file ... jsp pages and xml files.
Here is the turtle.war/web-xml file:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <!DOCTYPE web-app
| PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
| "http://java.sun.com/dtd/web-app_2_3.dtd">
|
| <web-app>
| <display-name>Trufina</display-name>
| <description>Trufina website version1.0</description>
|
| <servlet>
| <servlet-name>SessionController</servlet-name>
| <display-name>SessionController</display-name>
| <servlet-class>com.trufina.web.controller.SessionController</servlet-class>
| <!--
| <jsp-file>/reg/controller.jsp</jsp-file>
| -->
| </servlet>
|
| <!-- Trufina API Server -->
| <servlet>
| <servlet-name>TrufinaAPIServer</servlet-name>
| <display-name>Trufina API Server</display-name>
| <servlet-class>com.trufina.webservice.api.TrufinaAPIServer</servlet-class>
| </servlet>
|
| <!-- Trufina API Validator -->
| <servlet>
| <servlet-name>TrufinaAPIValidator</servlet-name>
| <display-name>Trufina API Validator</display-name>
| <servlet-class>com.trufina.webservice.api.TrufinaAPIValidator</servlet-class>
| </servlet>
|
| <!-- Trufina Free Look Server -->
| <servlet>
| <servlet-name>TrufinaIDServer</servlet-name>
| <display-name>Trufina Free Look Server</display-name>
| <servlet-class>com.trufina.webservice.freelook.TrufinaIDServer</servlet-class>
| </servlet>
|
| <servlet-mapping>
| <servlet-name>SessionController</servlet-name>
| <url-pattern>/reg/SessionController</url-pattern>
| </servlet-mapping>
|
| <servlet-mapping>
| <servlet-name>TrufinaAPIServer</servlet-name>
| <url-pattern>/TrufinaAPIServer</url-pattern>
| </servlet-mapping>
|
| <servlet-mapping>
| <servlet-name>TrufinaAPIValidator</servlet-name>
| <url-pattern>/TrufinaAPIValidator</url-pattern>
| </servlet-mapping>
|
| <servlet-mapping>
| <servlet-name>TrufinaIDServer</servlet-name>
| <url-pattern>/TrufinaIDServer</url-pattern>
| </servlet-mapping>
|
| <session-config>
| <session-timeout>30</session-timeout>
| </session-config>
|
| <error-page>
| <error-code>404</error-code>
| <location>/404.htm</location>
| </error-page>
|
| <security-constraint>
| <web-resource-collection>
| <web-resource-name>Trufina Protected Areas</web-resource-name>
| <url-pattern>/mytrufina/*</url-pattern>
| <url-pattern>/test/snoop2.jsp</url-pattern>
| <http-method>DELETE</http-method>
| <http-method>GET</http-method>
| <http-method>POST</http-method>
| <http-method>PUT</http-method>
| </web-resource-collection>
| <auth-constraint>
| <role-name>*</role-name>
| </auth-constraint>
| </security-constraint>
|
| <login-config>
| <auth-method>FORM</auth-method>
| <form-login-config>
| <form-login-page>/LoginForm.jsp</form-login-page>
| <form-error-page>/LoginError.jsp</form-error-page>
| </form-login-config>
| </login-config>
|
| <security-role>
| <description>Trufina Roles</description>
| <role-name>trufina_guest</role-name>
| </security-role>
|
| </web-app>
|
|
Here is the csa.war.web-xml file:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <!DOCTYPE web-app
| PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
| "http://java.sun.com/dtd/web-app_2_3.dtd">
|
| <web-app>
| <display-name>TrufinaCSA</display-name>
| <description>TrufinaCSA website version1.0</description>
| <distributable/>
| <context-param>
| <param-name>basePath</param-name>
| <param-value>http://localhost:8080/</param-value>
| <description>TrufinaCSA root context path</description>
| </context-param>
| <context-param>
| <param-name>rootPathSecured</param-name>
| <param-value>@rootPathSecured@</param-value>
| <description>TrufinaCSA secured (SSL) root context path with the IP address or site name</description>
| </context-param>
| <context-param>
| <param-name>rootPathNonSecured</param-name>
| <param-value>@rootPathNonSecured@</param-value>
| <description>TrufinaCSA non-secured root context path with the IP address or site name, usually used to break the
| https secure linking when exiting from it.
| </description>
| </context-param>
| <session-config>
| <session-timeout>30</session-timeout>
| </session-config>
| <welcome-file-list>
| <welcome-file>index.jsp</welcome-file>
| <welcome-file>index.htm</welcome-file>
| <welcome-file>index.html</welcome-file>
| <welcome-file>default.htm</welcome-file>
| <welcome-file>default.html</welcome-file>
| <welcome-file>default.jsp</welcome-file>
| </welcome-file-list>
| <error-page>
| <error-code>404</error-code>
| <location>/errorpages/err404.jsp</location>
| </error-page>
| <error-page>
| <error-code>500</error-code>
| <location>/errorpages/err500.jsp</location>
| </error-page>
| <!--
| <taglib>
| <taglib-uri>http://java.sun.com/jstl/core</taglib-uri>
| <taglib-location>/WEB-INF/c.tld</taglib-location>
| </taglib>
| <taglib>
| <taglib-uri>http://java.sun.com/jstl/core_rt</taglib-uri>
| <taglib-location>/WEB-INF/c-rt.tld</taglib-location>
| </taglib>
| <taglib>
| <taglib-uri>http://java.sun.com/jstl/xml</taglib-uri>
| <taglib-location>/WEB-INF/x.tld</taglib-location>
| </taglib>
| <taglib>
| <taglib-uri>http://java.sun.com/jstl/xml_rt</taglib-uri>
| <taglib-location>/WEB-INF/x-rt.tld</taglib-location>
| </taglib>
| <taglib>
| <taglib-uri>http://java.sun.com/jstl/fmt</taglib-uri>
| <taglib-location>/WEB-INF/fmt.tld</taglib-location>
| </taglib>
| <taglib>
| <taglib-uri>http://java.sun.com/jstl/fmt_rt</taglib-uri>
| <taglib-location>/WEB-INF/fmt-rt.tld</taglib-location>
| </taglib>
| <taglib>
| <taglib-uri>http://java.sun.com/jstl/sql</taglib-uri>
| <taglib-location>/WEB-INF/sql.tld</taglib-location>
| </taglib>
| <taglib>
| <taglib-uri>http://java.sun.com/jstl/sql_rt</taglib-uri>
| <taglib-location>/WEB-INF/sql-rt.tld</taglib-location>
| </taglib>
| <taglib>
| <taglib-uri>http://jakarta.apache.org/taglibs/request-1.0</taglib-uri>
| <taglib-location>/WEB-INF/request.tld</taglib-location>
| </taglib>
| <taglib>
| <taglib-uri>http://jakarta.apache.org/taglibs/xtags-1.0</taglib-uri>
| <taglib-location>/WEB-INF/xtags.tld</taglib-location>
| </taglib>
| <taglib>
| <taglib-uri>http://jakarta.apache.org/taglibs/string-1.0.1</taglib-uri>
| <taglib-location>/WEB-INF/string.tld</taglib-location>
| </taglib>
| <taglib>
| <taglib-uri>http://jakarta.apache.org/taglibs/session-1.0</taglib-uri>
| <taglib-location>/WEB-INF/session.tld</taglib-location>
| </taglib>
| <taglib>
| <taglib-uri>http://jakarta.apache.org/taglibs/image-1.0</taglib-uri>
| <taglib-location>/WEB-INF/image.tld</taglib-location>
| </taglib>
| -->
| </web-app>
|
There are frames in this app, but no iframes.
I also notice one other thing ... my turtle app runs perfect until I use the
[url]
http://localhost:8080/turtle/csa
[/url]
URL. Once I get hit that URL the turtle app ceases to work and only csa app pages, or actually, csa pages with 404 errors on them appear. It appear as though the turtle and csa apps are sharing the same turtle context. But it doesn't make sense since both the turtle app and csa app have equivalent directory structures and I am assuming that to mean that accessing them should be done using
http://localhost:8080/turtle
and
http://localhost:8080/csa
Thanks.
sg
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168254#4168254
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168254
17 years, 4 months