[JBoss Messaging] - Re: Remote JMS server
by jeanbobby
Hi guys,
Im trying to setup a remote-standalone JBossMessaging 1.1 Instance.
The 'hosting' standalone server is 4.0.4.GA.
The client(s) are 4.0.4.GAs, with the jms RAR and jms-ds defined as indicated in the remote-messaging wiki.
I want my applications to be able to send/receive msgs first 'programatically', and maybe later with 3.0 MDBs.
My main application is a spring-based war, for my tests it intializes a simple bean injecting a jms template which is based on the JmsXA bound in the private internal namespace.
when sending the test message I first got classpath pbs, included messaging-client to server/myserver/lib, and then got into :
java.lang.RuntimeException: Failed to config client side AOP
|
| 15:43:39,643 ERROR [SocketClientInvoker] Got marshalling exception, exiting
| java.io.EOFException
| at java.io.DataInputStream.readByte(DataInputStream.java:243)
| at org.jboss.serial.io.JBossObjectInputStream.readByte(JBossObjectInputStream.java:227)
| at org.jboss.jms.server.remoting.JMSWireFormat.read(JMSWireFormat.java:411)
| at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.jav
| a:279)
| at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
| at org.jboss.remoting.Client.invoke(Client.java:525)
| at org.jboss.remoting.Client.invoke(Client.java:488)
| at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.invoke(ClientConnectionFact
| oryDelegate.java:199)
| at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$getClientAOPConfig_86975327
| 01842707646.invokeNext(ClientConnectionFactoryDelegate$getClientAOPConfig_8697532701842707646.java)
| at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.getClientAOPConfig(ClientCo
| nnectionFactoryDelegate.java)
| at org.jboss.jms.client.JBossConnectionFactory.ensureAOPConfigLoaded(JBossConnectionFactory.
| java:233)
| at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFacto
| ry.java:196)
| at org.jboss.jms.client.JBossConnectionFactory.createXAQueueConnection(JBossConnectionFactor
| y.java:144)
| at org.jboss.jms.ConnectionFactoryHelper.createQueueConnection(ConnectionFactoryHelper.java:
| 147)
| at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:709)
| at org.jboss.resource.adapter.jms.JmsManagedConnection.<init>(JmsManagedConnection.java:184)
|
| at org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsMan
| agedConnectionFactory.java:106)
| at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventL
| istener(InternalManagedConnectionPool.java:539)
| at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(Internal
| ManagedConnectionPool.java:228)
| at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JB
| ossManagedConnectionPool.java:417)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConn
| ectionManager2.java:324)
| at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectio
| nManager.java:301)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnec
| tionManager2.java:379)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.alloca
| teConnection(BaseConnectionManager2.java:812)
| at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.allocateConnection(JmsSessionFactory
| Impl.java:389)
| at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactory
| Impl.java:144)
| at org.springframework.jms.core.JmsTemplate102.createSession(JmsTemplate102.java:166)
| at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:424)
| at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:486)
| at com.digiplug.repository.JmsTest.afterPropertiesSet(JmsTest.java:27)
On the client and on the messaging server :
15:58:00,611 ERROR [ServerThread] failed to process invocation.
| java.io.IOException: Can not read data for version 6. Supported versions: 1,2
| at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:394)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:446)
|
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:527)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:261)
which seems to show a conflict between jboss-remoting versions between client and server... but I saw no directive concerning jboss-remoting in the wiki.
Any help would be appreciated,
Best Regards
Olivier Cuzacq
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982116#3982116
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982116
19 years, 1 month
[JBoss Seam] - Re: Submitting using SelectOneRadio
by monkeyden
Here is the runtime memory (up to the call to org.apache.myfaces.el.MethodBindingImpl.getMethod()). _argClasses is null, which tells me that it might be expecting to call a no-arg method, when the actual method takes a ValueChangeEvent.
this MethodBindingImpl (id=346)
| facesContext ServletFacesContextImpl (id=347)
| args Object[0] (id=348)
| baseAndProperty Object[2] (id=349)
| [0] Proxy$$EnhancerByCGLIB$$f38c8c2a (id=298)
| CGLIB$BOUND true
| CGLIB$CALLBACK_0 ClientSideInterceptor (id=310)
| CGLIB$CONSTRUCTED true
| [1] "updateStateRadioChange"
| base Proxy$$EnhancerByCGLIB$$f38c8c2a (id=298)
| CGLIB$BOUND true
| CGLIB$CALLBACK_0 ClientSideInterceptor (id=310)
| bean $Proxy116 (id=319)
| component Component (id=317)
| beanClass Class<T> (com.project.actions.EditUserRecordAction) (id=264)
| businessInterfaces HashSet<E> (id=357)
| clientSideInterceptors ArrayList<E> (id=361)
| createMethod null
| dataModelFieldAnnotations HashMap<K,V> (id=362)
| dataModelFields ArrayList<E> (id=366)
| dataModelGetterAnnotations HashMap<K,V> (id=376)
| dataModelGetters ArrayList<E> (id=377)
| dataModelSelectionFieldAnnotations HashMap<K,V> (id=378)
| dataModelSelectionFields HashMap<K,V> (id=379)
| dataModelSelectionSetterAnnotations HashMap<K,V> (id=380)
| dataModelSelectionSetters HashMap<K,V> (id=381)
| dependencies null
| destroyMethod Method (id=382)
| factory Class<T> (org.jboss.seam.intercept.Proxy$$EnhancerByCGLIB$$f38c8c2a) (id=299)
| inFields HashSet<E> (id=383)
| initializerFields HashMap<K,V> (id=384)
| initializerSetters HashMap<K,V> (id=385)
| inMethods HashSet<E> (id=386)
| interceptionType InterceptionType (id=387)
| interceptors ArrayList<E> (id=389)
| jndiName "pipeline/EditUserRecordAction/local"
| logField Field (id=391)
| logInstance LogImpl (id=393)
| name "editProfileAction"
| outFields HashSet<E> (id=395)
| outMethods HashSet<E> (id=396)
| parameterFields HashSet<E> (id=397)
| parameterSetters HashSet<E> (id=398)
| postActivateMethod null
| postConstructMethod null
| preDestroyMethod null
| prePassivateMethod null
| removeMethods HashSet<E> (id=399)
| scope ScopeType (id=400)
| startup false
| synchronize true
| timeout 1000
| type ComponentType (id=402)
| unwrapMethod null
| validateMethods HashSet<E> (id=404)
| validators Hashtable<K,V> (id=405)
| componentName "editProfileAction"
| isSeamComponent true
| type InterceptorType (id=326)
| userInterceptors ArrayList<E> (id=330)
| CGLIB$CONSTRUCTED true
| property "updateStateRadioChange"
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982114#3982114
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982114
19 years, 1 month
[JBoss Portal] - Re: Portal 2.4 + JSF + IPC Navigation not properly navigatin
by emdlc
It seems that I had to change the web.xml to declare the elements necessary to a MyFaces webapp. I think the examples don't require them because they have them declared elsewhere in JBoss Portal? But for some reason it started navigating properly between portlets when I used this:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <web-app id="web-app_1" xmlns="http://java.sun.com/xml/ns/j2ee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
| version="2.4">
|
| <context-param>
| <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
| <param-value>client</param-value>
| </context-param>
|
| <context-param>
| <param-name>javax.faces.application.CONFIG_FILES</param-name>
| <param-value>/WEB-INF/faces-config.xml</param-value>
| </context-param>
|
| <listener>
| <listener-class>
| org.apache.myfaces.webapp.StartupServletContextListener
| </listener-class>
| </listener>
|
| <!-- Faces Servlet -->
| <servlet>
| <servlet-name>Faces Servlet</servlet-name>
| <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
| <load-on-startup>1</load-on-startup>
| </servlet>
|
| <!-- Faces Servlet Mapping -->
| <servlet-mapping>
| <servlet-name>Faces Servlet</servlet-name>
| <url-pattern>*.faces</url-pattern>
| </servlet-mapping>
|
| </web-app>
|
Maybe it is the STATE_SAVING_METHOD being set to client? The way I'm seeing this is that even though it is deployed as one SAR, each portlet is deployed as a separate application. So when I set it to client, MyFaces embeds the appropriate values in the page itself, instead of server-side, so the destination portlet gets page parameters that help it navigate opposed to request attributes, which it cannot see since they are different apps?
But this doesn't seem to handle the case when you need to pass parameters, or ideally, managed-beans across. I can't even get regular parameters to go across (or at least how to access them). Any ideas?
Navigation still doesn't work when it references something from a managed bean, for example, I get this in the log if I click on it:
| link:
| <h:form>
| <h:commandLink action="addItem">
| <f:param name="mainPortlet" value="true" />
| <f:param name="urlVal" value="#{item.url}" />
| <f:verbatim>Add</f:verbatim>
| </h:commandLink>
| </h:form>
|
| log:
| 10:15:33,218 INFO [[/query-portlet]] WARNING: Component jbpa61aafa8_id26 just got an automatic id, because there was no id assigned yet. If this component was created dynamically (i.e. not by a JSP tag) you should assign it an explicit static id or assign it the id you get from the createUniqueId from the current UIViewRoot component right after creation!
|
...and the navigation goes to the from-view-id instead of the to-view-id. When looking this warning up, I get advice from non-portlet applications, to set the ID if you generate it using Java code. I imagine it reacts like this because the destination portlet is unaware of any JSF actions and managed beans that the source portlet has.
So my questions are:
- Do separate FacesContext objects exists for each portlet, or are they shared?
- If they are shared, can we have the portlets view the same managed-beans by setting id's?
- How do I pass and retrieve parameters from one portlet to another using JSTL and/or JSF tags?
- Are all these assumptions close to reality? Or am I way off?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982110#3982110
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982110
19 years, 1 month