[JBoss Messaging] - Re: can not catch excption when jboss as is down
by nkhadakk
JBoss AS 4.2.1/JBM 1.3 GA/ Spring 2.x
I am running into a similar issue(i think).
My application has a listener on a remote client (coded as per jboss doc) connected to the JMS provider (jboss 4.2.x/jbm 1.3). Everything works fine as long as certain
sequence of operations is maintained. Specifically if the JBoss server is shutdown and restarted, i see the following errors in the LIstener logs :
13:35:16,396 DEBUG [Timer-0]: org.jboss.remoting.LeasePinger - LeasePinger[SocketClientInvoker[57e787, bisocket://127.0.0.1:4458](3j001-8mwhow-f893r9kl-1-f893r9yr-5)] failed to ping to server
| org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://127.0.0.1:4458/?clientMaxPoolSize=50&clientSocketClass=\
| org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&\
| marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&\
| numberOfRetries=1&socket.check_connection=false&timeout=10000&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:530)
| at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:353)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
| at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:283)
| at org.jboss.remoting.LeasePinger.access$000(LeasePinger.java:20)
| at org.jboss.remoting.LeasePinger$LeaseTimerTask.run(LeasePinger.java:315)
| at java.util.TimerThread.mainLoop(Timer.java:512)
| at java.util.TimerThread.run(Timer.java:462)
| Caused by: java.net.ConnectException: Connection refused
| at java.net.PlainSocketImpl.socketConnect(Native Method)
| at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
| at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
| at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
| at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
| at java.net.Socket.connect(Socket.java:519)
| at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
| at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:360)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:801)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:526)
| ... 7 more
| 13:35:16,397 WARN [Timer-0]: org.jboss.remoting.LeasePinger - LeasePinger[SocketClientInvoker[57e787, bisocket://127.0.0.1:4458](3j001-8mwhow-f893r9kl-1-f893r9yr-5)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://127.0.0.1:4458/?clientMaxPoolSize=50&clientSocketClass=\
| org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&\
| marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&\
| numberOfRetries=1&socket.check_connection=false&timeout=10000&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
| 13:35:17,171 DEBUG [URIListener-2]: org.springframework.jms.listener.DefaultMessageListenerContainer - Consumer [JBossMessageConsumer->ConsumerDelegate[28384121, ID=73]] of session [JBossSession->SessionDelegate[8574467, ID=71]] did not receive a message
| 13:35:17,184 DEBUG [URIListener-1]: org.springframework.jms.listener.DefaultMessageListenerContainer - Consumer
Now if the JBoss AS comes up again, the JBoss Remoting client code appears to connect
successfully to JBM. Only issue is since the above stack trace is never bubbled up to my Listener code, my listener continues to be registered to a legacy provider.. and as a result never gets any new messages.
This issue is solvable(with a hack) IF i stop pooling JMS consumers in my listener code and create new JMS Consumer for every recieve poll.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099484#4099484
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099484
18Â years, 6Â months
[JBoss Seam] - Re: DataTable Sorting Example
by griffitm
Update to my problem: Adding action="pageControllerBean.action" fixed the pagination problem.
This is strange, maybe a bug? The initial result set that I was trying to paginate was being managed by a stateful session bean that encapsulated an EntityQuery object. I had some logging code in the search() method of my bean to display the query parameters, and everything looked as I suspected -- however I could not get my page to sort or paginate correctly until I added the attribute action to the link.
So my source went from:
<s:link view="/DeliverableSearch.xhtml"
| rendered="#{deliverableSearch.previousExists}"
| value="#{messages.left}#{messages.left} First Page"
| id="firstPage">
| <f:param name="firstResult" value="0"/>
| </s:link>
To:
| <s:link view="/DeliverableSearch.xhtml" action="#{deliverableSearch.search}"
| rendered="#{deliverableSearch.previousExists}"
| value="#{messages.left}#{messages.left} First Page"
| id="firstPage">
| <f:param name="firstResult" value="0"/>
| </s:link>
I added the same action attribute to the link that sorted the data as well. This fixed both the pagination and sorting issue. The question is, why was the page not performing as expected before, when clearly I know the search method on the bean was being called because I could see the output in the log file...
Best Regards,
MG
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099478#4099478
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099478
18Â years, 6Â months
[JBoss Portal] - Re: Feedback wanted. Would you choose JB Portal again?
by chris.laprunï¼ jboss.com
"wheezer" wrote : All of the portals have fewer open source portlets than we imagined they would have. Logic says that Red hat's involvement might rev up the portlet development, and probably here at JBP first, but logic has been wrong before. It's been a year and a half. Is that happening, or....?
Just a personal opinion, not necessarily representing my employer's ^_^: why does it stand to logic that Red Hat would rev up portlet development?
When considering a Portal, should you be looking at the gadget portlets that are bundled and that you will probably not use in your actual portal or at the capabilities of the portal server? Should portal developers spend their time developing portlets or make sure that the actual portal server works properly, scales, is well tested, etc.? To me, the portlet market is completely separate from the portal one. "Interesting" (i.e. portlets that you would use in a business environment) portlets are products with their own lifecycle, independent of portals.
Any JSR 168 portlets should work on any JSR-168 compliant portal. If they don't, then either the portlet is not conforming or the portal is wrongly advertising compliance. So my opinion is that you should choose a portal on its technical merits, not on the set of bundled portlets. But then, that's just me! :)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099477#4099477
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099477
18Â years, 6Â months
[Security & JAAS/JBoss] - Re: Http status error 404: you requested resources are not a
by jdsignature
Thanks for your reply,
Can you tell me how I can have the container invoke the customized login module? you can see all my config files in the previous thread.
Does the container invoke a hidden servlet to handle the j_security_check action from the form?
where i should place the customized login module? under \jboss_home\server\default\deploy?
how many places need to be configured? jboss-web.xml, web.xml,login-config.xml, anywhere else?
<?xml version="1.0"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<web-app>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
</welcome-file-list>
<security-constraint>
<web-resource-collection>
<web-resource-name>SecurePages</web-resource-name>
Security constraint for resources in the secure directory
<url-pattern>/secure/*</url-pattern>
<http-method>POST</http-method>
<http-method>GET</http-method>
</web-resource-collection>
<auth-constraint>
only let the system user login
<role-name>admin</role-name>
</auth-constraint>
<user-data-constraint>
SSL not required
<transport-guarantee>NONE</transport-guarantee>
</user-data-constraint>
</security-constraint>
<login-config>
<auth-method>FORM</auth-method>
<form-login-config>
<form-login-page>/login.html</form-login-page>
<form-error-page>/LoginError.html</form-error-page>
</form-login-config>
</login-config>
<security-role>
The Secure ROLE
<role-name>admin</role-name>
</security-role>
</web-app>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099475#4099475
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099475
18Â years, 6Â months