[Messaging, JMS & JBossMQ] - Error persisting message in DB2
by kaobe
Hi there!
I have a JBoss 4.0.3 SP1 that does JMS with MDBs. The persistance is done with DB2. There is a message sent to a topic, an MDB reacts and - as a result - sends another message to a Queue. The first message is being sent and received, it is being saved in the database (jms_messages). When the answer message should be saved it is being sent and JBoss tries to store it, but gets an SQL error from DB2, because the unique index defined in deploy/jms/-jdbc2-service.xml for the fields txop and txid is being violated. There is no transaction running, that's why the values are null and 'A' both for the already stored message for the topic and the new one for the queue.
No my question: is this unique index neccessary? I have dropped it from the database for a test and it seemed to work. So I would like to know why there is such an index.
The funny thing is, it worked with hsqldb (with the index). Does that mean hsqldb violates the index definition or is there some other reason for this behaviour?
Thanks a lot for your help!
I wish everyone of you merry christmas and a happy new year!
Bye,
Peter
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995808#3995808
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995808
19 years, 7 months
[Messaging, JMS & JBossMQ] - Howto connect a EJB3 MDB to a remote queue?
by estiedi
Hi,
I need to make a EJB3 MDB that listens for messages coming from another JBoss server.
I'm pretty new to JBoss and an intense googling for examples and tutorials wasn't very helpful for me. Especially the possibility of doing things several different ways is confusing. Also it looks like it changes quite a lot between minor versions? (I'm currently using JBoss 4.0.5)
Anyway, so far I configured a JMSProviderLoader in jms-ds.xml:
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.mq:service=JMSProviderLoader,name=RemoteMQProvider,server=192.168.100.10">
| <attribute name="ProviderName">ISJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
| <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
| <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
| <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.100.10:25199
| </attribute>
| </mbean>
and an invoker proxy in the ejb jboss.xml:
| <message-driven>
| <ejb-name>TestMDB</ejb-name>
| <destination-jndi-name>queue/remotequeue</destination-jndi-name>
| <invoker-bindings>
| <invoker>
| <invoker-proxy-binding-name>TextMDBInvoker</invoker-proxy-binding-name>
| </invoker>
| </invoker-bindings>
| </message-driven>
| </enterprise-beans>
|
| <invoker-proxy-bindings>
| <invoker-proxy-binding>
| <name>TextMDBInvoker</name>
| <invoker-mbean>does-not-matter</invoker-mbean>
| <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
| <proxy-factory-config>
| <JMSProviderAdapterJNDI>ISJMSProvider</JMSProviderAdapterJNDI>
| <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
| <MinimumSize>1</MinimumSize>
| <MaximumSize>15</MaximumSize>
| <KeepAliveMillis>30000</KeepAliveMillis>
| <MaxMessages>1</MaxMessages>
| <MDBConfig>
| <ReconnectIntervalSec>5</ReconnectIntervalSec>
| <DLQConfig>
| <DestinationQueue>queue/DLQ</DestinationQueue>
| <MaxTimesRedelivered>10</MaxTimesRedelivered>
| <TimeToLive>0</TimeToLive>
| </DLQConfig>
| </MDBConfig>
| </proxy-factory-config>
| </invoker-proxy-binding>
| </invoker-proxy-bindings>
|
But now, how do I configure my EJB3 MDB to connect to this remote queue?
Also the remote JBoss server is version 3. I have been told that this should be no problem. But is it really no problem when using EJB3?
All tips and hints are greatly appreciated.
D.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995806#3995806
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995806
19 years, 7 months
[JNDI/Naming/Network] - Datasource Problem
by akmal
Hi,
i am trying to deploy a project in Myeclips with Jboss Server. I am facing the error for jndiname.
some one give me the solution.
Caused by: javax.naming.NameNotFoundException: @db.jndiname@ not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(Unknown Source)
at org.hibernate.connection.DatasourceConnectionProvider.configure(DatasourceConnectionProvider.java:52)
... 119 more
12:49:30,796 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=@db.jndiname@' to JNDI name 'java:@db.jndiname@'
12:49:30,953 ERROR [MainDeployer] Could not create deployment: file:/C:/Program Files/jboss-4.0.5.GA/server/default/deploy/Shop/sl-server/metadata/ejb/jboss-ds.xml
org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.jca:service=LocalTxCM,name=@db.jndiname@
at org.jboss.system.ServiceCreator.install(ServiceCreator.java:103)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:449)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
at org.jboss.system.ServiceController.install(ServiceController.java:226)
at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.install(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995802#3995802
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995802
19 years, 7 months
[JNDI/Naming/Network] - Twiddle executions throws NameNotFoundException: jmx not bou
by mahendra_kutare
While trying to run twiddle on my Jboss 4.0.4 installation it throws the following error -
sh ./twiddle.sh -s 10.129.50.4 serverinfo --count
04:29:29,352 ERROR [Twiddle] Exec failed
org.jboss.util.NestedRuntimeException: jmx not bound; - nested throwable: (javax.naming.NameNotFoundException: jmx not bound) at org.jboss.console.twiddle.Twiddle$1.getServer(Twiddle.java:143)
at org.jboss.console.twiddle.command.MBeanServerCommand.getMBeanServer(MBeanServerCommand.java:59)
at org.jboss.console.twiddle.command.ServerInfoCommand.execute(ServerInfoCommand.java:130)
at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:305)
Caused by: javax.naming.NameNotFoundException: jmx not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
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:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.console.twiddle.Twiddle.createMBeanServerConnection(Twiddle.java:250)
at org.jboss.console.twiddle.Twiddle.connect(Twiddle.java:268)
at org.jboss.console.twiddle.Twiddle.access$300(Twiddle.java:62)
at org.jboss.console.twiddle.Twiddle$1.getServer(Twiddle.java:139)
... 3 more
Can anyone please explain this and possible solution ?
- Mahendra
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995799#3995799
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995799
19 years, 7 months
[JBoss.NET] - NoClassDefFoundError: org/jboss/axis/encoding/ser/BaseSerial
by eogreen
Hello,
I am currently experiencing a perplexing error in attempting to run a straight Axis1.1 client on JBoss3.2.8. I have scoured the web for 2 days to productive end.
Here is my stack trace caught in createCall() in my soapbindingstub when invoked:
java.lang.NoClassDefFoundError: org/jboss/axis/encoding/ser/BaseSerializerFactory
| at java.lang.ClassLoader.defineClass0(Native Method)
| at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
| at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
| at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
| at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
| at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
| at java.security.AccessController.doPrivileged(Native Method)
| at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
| at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
| at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
| at java.lang.Class.forName0(Native Method)
| at java.lang.Class.forName(Class.java:219)
| at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:200)
| at java.security.AccessController.doPrivileged(Native Method)
| at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:179)
| at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:120)
| at org.apache.axis.deployment.wsdd.WSDDTypeMapping.getSerializer(WSDDTypeMapping.java:2
| at org.apache.axis.deployment.wsdd.WSDDDeployment.deployMapping(WSDDDeployment.java:372
| at org.apache.axis.deployment.wsdd.WSDDDeployment.getTypeMappingRegistry(WSDDDeployment
| at org.apache.axis.configuration.FileProvider.getTypeMappingRegistry(FileProvider.java:
| at org.apache.axis.AxisEngine.getTypeMappingRegistry(AxisEngine.java:325)
| at org.apache.axis.MessageContext.getTypeMappingRegistry(MessageContext.java:479)
| at org.apache.axis.client.Call.getTypeMapping(Call.java:2399)
| at org.apache.axis.client.Call.registerTypeMapping(Call.java:2436)
| at org.apache.axis.client.Call.registerTypeMapping(Call.java:2465)
| at com.amd.mte.axis.service.MTEWSSoapBindingStub.createCall(MTEWSSoapBindingStub.java:2
| at com.amd.mte.axis.service.MTEWSSoapBindingStub.get(MTEWSSoapBindingStub.java:303)
| at com.amd.catalyst.fdc.MTEInterface.retrieveData(MTEInterface.java:139)
| at com.amd.catalyst.fdc.MTEInterface.<init>(MTEInterface.java:54)
| at com.amd.catalyst.jacl.JCatalyst.FDCMTEInterface.test(FDCMTEInterface.java:52)
| 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:324)
| at tcl.lang.reflect.PkgInvoker.invokeMethod(PkgInvoker.java:128)
| at tcl.lang.JavaInvoke.call(JavaInvoke.java:304)
| at tcl.lang.JavaInvoke.callMethod(JavaInvoke.java:161)
| at tcl.lang.ReflectObject.cmdProc(ReflectObject.java:916)
| at tcl.lang.Interp.callCommand(Interp.java:1266)
I have noted that:
org.jboss.axis.encoding.ser.BaseSerializerFactory
is present in the JBoss 4.0.2+ soap stack, but I am NOT using 4.0.2+
I have reviewed:
http://www.jboss.org/?module=bb&op=viewtopic&p=3876437
http://wiki.jboss.org/wiki/Wiki.jsp?page=WebServiceStacks
MY QUESTION: Where is the reference coming from in my 3.2.8 deployment to:
org.jboss.axis.encoding.ser.BaseSerializerFactory
??
There are no references to the org.jboss.axis package in any of the Axis code. This is has perplexed me (and colleagues) for the last 48+ hours (almost straight).
I would greatly appreciate any knowledge shared.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995797#3995797
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995797
19 years, 7 months
[JBoss Seam] - Change Locale sequence
by rengar
When change language, in an action in the same page catch old language, that have it before, with method "Locale.instance().getLanguage()"
I change language with localeSelector :
| <h:form id="selectLanguage">
| <h:selectOneMenu value="#{localeSelector.language}">
| <f:selectItems value="#{localeSelector.supportedLocales}"/>
| </h:selectOneMenu>
| <h:commandButton action="#{localeSelector.select}" value="#{messages['ChangeLanguage']}"/>
| </h:form>
|
After in action I have :
| String language = Locale.instance().getLanguage();
|
When change language the action is executed too.
I explain :
1º
View : Default "es" -> selectOneMenu = "español", properties = messages_es
Action : Locale.instance().getLanguage() = "es"
2º
View: Change "en" -> selectOneMenu = "English", properties = messages_en
Action: Locale.instance().getLanguage() = "es"
3º
View: Change "es" -> selectOneMenu = "español", properties = messages_es
Action: Locale.instance().getLanguage() = "en"
4º
View: Change "en" -> selectOneMenu = "English", properties = messages_en
Action: Locale.instance().getLanguage() = "es"
.
.
.
.
How change language before enter in my action?
Or any other idea?
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995796#3995796
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995796
19 years, 7 months
[Tomcat, HTTPD, Servlets & JSP] - "struts forward.setPath" problem:
by augustfox
I have a project which has been develped by WSAD5.1.2(ibm).
Now I want to import this project into eclipse3.1.2+jboss4.0.1sp1+myeclipse4.1.1.
All has runned well,except one problem as follows:
In my DispatchAction when forward.setPath(url);
the url must begin with "/",
such as forward.setPath("/success.jsp"),not forward.setPath("success.jsp").
But all is well in WSAD,I searched some struts/servlet source code,but have
no idea of it.
My project uses lots of DispatchActions,all as above,and not want add "/"
for every forward.setPath().
Any help is appreciated,thanks all.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995787#3995787
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995787
19 years, 7 months
[JBoss Seam] - Re: Project setup with Icefaces
by PatrickMadden
I would download the latest 1.1.0.GA of Seam. I too was just using the CR2 version. As with any software there are a few other hoops you will have to jump through.
My faces-config.xml has the following:
|
| <faces-config>
|
| <managed-bean>
| <managed-bean-name>highlight</managed-bean-name>
| <managed-bean-class>com.icesoft.faces.context.effects.Highlight</managed-bean-class>
| <managed-bean-scope>application</managed-bean-scope>
| </managed-bean>
|
| <application>
| <message-bundle>messages</message-bundle>
| <!-- view-handler>com.sun.facelets.FaceletViewHandler</view-handler -->
| <view-handler>com.icesoft.faces.facelets.D2DSeamFaceletViewHandler</view-handler>
| </application>
|
| <!-- Seam transaction management -->
| <lifecycle>
| <phase-listener>org.jboss.seam.jsf.TransactionalSeamPhaseListener</phase-listener>
| </lifecycle>
| </faces-config>
|
My application.xml has the following:
|
| <application>
| <display-name>Seam Generated Application</display-name>
| <description>created by seam-gen</description>
|
| <module>
| <web>
| <web-uri>CloosterWeb20.war</web-uri>
| <context-root>/Clooster</context-root>
| </web>
| </module>
| <module>
| <java>jboss-seam.jar</java>
| </module>
| <module>
| <ejb>CloosterWeb20.jar</ejb>
| </module>
| <module>
| <java>icefaces.jar</java>
| </module>
| <module>
| <java>icefaces-facelets.jar</java>
| </module>
| <module>
| <java>icefaces-comps.jar</java>
| </module>
| <module>
| <java>jbpm-3.1.2.jar</java>
| </module>
| <module>
| <java>el-api.jar</java>
| </module>
| <module>
| <java>el-ri.jar</java>
| </module>
| </application>
|
And here is my web.xml
|
| <?xml version="1.0" ?>
| <web-app version="2.5"
| 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_5.xsd">
|
| <context-param>
| <param-name>javax.faces.CONFIG_FILES</param-name>
| <param-value>/WEB-INF/navigation.xml</param-value>
| </context-param>
|
| <!-- Seam -->
| <listener>
| <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>
| </listener>
|
| <!-- Propagate conversations across redirects -->
|
| <!--
| <filter>
| <filter-name>Seam Redirect Filter</filter-name>
| <filter-class>org.jboss.seam.servlet.SeamRedirectFilter</filter-class>
| </filter>
|
| <filter-mapping>
| <filter-name>Seam Redirect Filter</filter-name>
| <url-pattern>*.seam</url-pattern>
| </filter-mapping>
| -->
|
| <!-- propogate seam context to servlets (pvm) addition -->
| <filter>
| <filter-name>Seam Servlet Filter</filter-name>
| <filter-class>org.jboss.seam.servlet.SeamServletFilter</filter-class>
| </filter>
| <filter-mapping>
| <filter-name>Seam Servlet Filter</filter-name>
| <url-pattern>/servlet/*</url-pattern>
| </filter-mapping>
| <!-- end seam context to servlets -->
|
| <filter>
| <filter-name>Seam Exception Filter</filter-name>
| <filter-class>org.jboss.seam.servlet.SeamExceptionFilter</filter-class>
| </filter>
|
| <filter-mapping>
| <filter-name>Seam Exception Filter</filter-name>
| <url-pattern>*.seam</url-pattern>
| </filter-mapping>
|
| <!-- End Seam -->
|
|
| <!-- JSF -->
| <context-param>
| <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
| <param-value>client</param-value>
| </context-param>
|
| <context-param>
| <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
| <param-value>.xhtml</param-value>
| </context-param>
|
| <context-param>
| <param-name>facelets.DEVELOPMENT</param-name>
| <param-value>true</param-value>
| </context-param>
|
| <context-param>
| <param-name>com.icesoft.faces.actionURLSuffix</param-name>
| <param-value>.seam</param-value>
| </context-param>
|
| <context-param>
| <param-name>com.icesoft.faces.synchronousUpdate</param-name>
| <param-value>true</param-value>
| </context-param>
|
| <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>*.seam</url-pattern>
| </servlet-mapping>
|
| -->
|
| <servlet>
| <servlet-name>Blocking Servlet</servlet-name>
| <servlet-class>com.icesoft.faces.webapp.xmlhttp.BlockingServlet</servlet-class>
| <load-on-startup> 1 </load-on-startup>
| </servlet>
|
| <servlet>
| <servlet-name>Persistent Faces Servlet</servlet-name>
| <servlet-class>com.icesoft.faces.webapp.xmlhttp.PersistentFacesServlet</servlet-class>
| <load-on-startup>1</load-on-startup>
| </servlet>
|
| <servlet-mapping>
| <servlet-name>Persistent Faces Servlet</servlet-name>
| <url-pattern>/xmlhttp/*</url-pattern>
| </servlet-mapping>
|
| <servlet-mapping>
| <servlet-name>Persistent Faces Servlet</servlet-name>
| <url-pattern>/xmlhttp/*</url-pattern>
| </servlet-mapping>
|
| <servlet-mapping>
| <servlet-name>Persistent Faces Servlet</servlet-name>
| <url-pattern>*.iface</url-pattern>
| </servlet-mapping>
|
| <!-- Blocking Servlet Mapping -->
| <servlet-mapping>
| <servlet-name>Blocking Servlet</servlet-name>
| <url-pattern>/block/*</url-pattern>
| </servlet-mapping>
|
|
| <!-- Faces Servlet Mapping -->
| <servlet-mapping>
| <servlet-name>Persistent Faces Servlet</servlet-name>
| <url-pattern>*.seam</url-pattern>
| </servlet-mapping>
|
| <!-- MyFaces -->
| <listener>
| <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
| </listener>
| <!-- End MyFaces -->
|
| <!-- JSF RI -->
| <!--
| <listener>
| <listener-class>com.sun.faces.config.ConfigureListener</listener-class>
| </listener
| -->
| </web-app>
|
|
When upgrading from CR2 to GA I just made sure to copy my seam-gen/build.properties to from my CR2 to GA directory. I also then copied the GA jboss-seam*.jar (minus the sem-gen.jar) to my own eclipse project's lib directory.
I'm no expert, in fact I'm a seam newbie. Only been using it for 2 weeks max. Regardless, I was able to get my project running with Icefaces. You'll notice a pretty significant difference when jboss starts up. I'm using 4.0.5 GA.
Hope this is of help.
PVM
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995781#3995781
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995781
19 years, 7 months
[Messaging, JMS & JBossMQ] - JBoss doesnt release threads after executing MDB (out of Mem
by suhail
Hi,
I am using JBoss AS jboss-4.0.2.
I am getting OutOfMemoryError when I send the messages to an MDB. It happens after i send 30-40 messages. What I have observed on the web-console of Jboss is that #Threads increases by some 30 whenever I sent one message to a queue. Even though message is getting consumed instantly, the thread count doesn?t come down but keep on increasing by a factor of approx 30 or more with each message. After sometime it reaches some 2000 figure and server starts giving out of memory error. If I make process synchronous (I mean not use MDB) , thread count doesnt increase.
It implies that each message is adding approx. 30 threads and threads are not released after messages are getting consumed. Can anybody explain it and give a fix ?
Please find the stack of errors below. I get either of these two stacks.
Any help will be appreciated.
Thank you
Suhail
20 Dec 2006 16:20:10,176 WARN (UILServerILService Accept Thread:) [org.jboss.mq.il.uil2.UILServerILService] Unexpected error in setup of client connection
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:574)
at org.jboss.mq.il.uil2.SocketManager.start(SocketManager.java:147)
at org.jboss.mq.il.uil2.UILServerILService.run(UILServerILService.java:162)
at java.lang.Thread.run(Thread.java:595)
20 Dec 2006 13:18:35,031 ERROR (TimeoutFactory-0:) [org.jboss.logging.Log4jService$ThrowableListenerLoggingAdapter] Unhandled Throwable
org.jboss.util.threadpool.ThreadPoolFullException: java.lang.OutOfMemoryError: unable to create new native thread
at org.jboss.util.threadpool.BasicThreadPool.execute(BasicThreadPool.java:417)
at org.jboss.util.threadpool.BasicThreadPool.runTaskWrapper(BasicThreadPool.java:192)
at org.jboss.util.threadpool.BasicThreadPool.run(BasicThreadPool.java:212)
at org.jboss.util.threadpool.BasicThreadPool.run(BasicThreadPool.java:206)
at org.jboss.util.timeout.TimeoutFactory.doWork(TimeoutFactory.java:223)
at org.jboss.util.timeout.TimeoutFactory.access$000(TimeoutFactory.java:41)
at org.jboss.util.timeout.TimeoutFactory$1.run(TimeoutFactory.java:136)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995779#3995779
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995779
19 years, 7 months
[EJB 3.0] - 5.0.0Beta1: ejb3-timer-service.xml with PostgreSQL fails
by Juergen.Zimmermann
In ejb3-timer-service.xml I made these changes:HSQLDBDelegate -> PostgreSQLDelegate
| qrtz_job_details: BINARY -> oid
| IS_VOLATILE VARCHAR(1) -> IS_VOLATILE boolean
| qrtz_triggers: BINARY -> oid
| IS_VOLATILE VARCHAR(1) -> IS_VOLATILE boolean
| qrtz_blob_triggers: BINARY -> oid
| qrtz_calendars: BINARY -> oid
| qrtz_fired_triggers: IS_VOLATILE VARCHAR(1) -> IS_VOLATILE boolean
| REQUESTS_RECOVERY VARCHAR(1) -> REQUESTS_RECOVERY boolean
When starting JBossAS I get this error message and stack trace although server/default/deploy/postgres-ds.xml defines DefaultDS:2006-12-21 18:22:27,853 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=jboss.ejb:persistencePolicy=database,service=EJBTimerService state=Create mode=Manual requiredState=Installed
| java.lang.IllegalStateException: Cannot find datasource meta data: jboss.jdbc:datasource=DefaultDS,service=metadata
| at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.init(GeneralPurposeDatabasePersistencePlugin.java:101)
| at org.jboss.ejb.txtimer.DatabasePersistencePolicy.startService(DatabasePersistencePolicy.java:92)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
| 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:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
| at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
| at org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
| at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:198)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:320)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190)
| at org.jboss.system.ServiceController.doChange(ServiceController.java:656)
| at org.jboss.system.ServiceController.start(ServiceController.java:431)
| at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:124)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:85)
| at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:44)
| at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:53)
| at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
| at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:451)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
| at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
| at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
| at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
| at org.jboss.Main.boot(Main.java:210)
| at org.jboss.Main$1.run(Main.java:508)
| at java.lang.Thread.run(Thread.java:595)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995778#3995778
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995778
19 years, 7 months
[Security & JAAS/JBoss] - Re: SSO in JBoss 4.0.5
by sohil.shah＠jboss.com
anonymous wrote :
| 1. What are the limitations of this jBoss Federated SSO framework.
|
Currently, the integration point for the SSO Token Management functions is inside of Tomcat. Hence, currently Tomcat depedency is needed. JBoss ships with Tomcat out-of-the-box so, you should be ok on this.
anonymous wrote :
| 2. Does this support different apps in different domains.
|
Yes, the framework was designed with cross-domain integration from the ground up
anonymous wrote :
| 3. Any support for XACML (1.0, 2.0).
|
XACML is in the Authorization domain. SSO primarily is associated with the Authentication aspect of security. As such XACL is out of scope for SSO. But integration is possible.
Hence, if you have an Authorization framework based on XACML then, integration point for SSO would be to generate the Principal used by XACML to enforce Authorization decisions
anonymous wrote :
| 4. Can I get some reference implementations for federated SSO..other the one in the flash demo.
|
In its current form, the framework ships with the actual implementation of the two Seam apps that are featured in the flash demo.
It also has a test application that is used for testing scenarios during development
anonymous wrote :
| 5. Do we need a portal (customized or any product driven like Oracle portal, weblogic etc).
|
No. portal or any custom thirdparty product is not a requirement. The only requirement at this point is Tomcat
anonymous wrote :
| We have 5 applications using different login mechanisms like JAAS, Database etc running in different servers including jBoss, Tomcat, web logic.
|
| Can we use the beta Federated SSO beta for implementing SSO and SAML to support existing apps and also future apps..
|
Absolutely. Although I am not too familiar with WebLogic. As long as you run Tomcat you should be fine.
Also please refer here for more detailed documentation:
http://labs.jboss.com/portal/index.html?ctrl:cmd=render&ctrl:window=defau...
Thanks
Sohil
Project Lead, JBoss Federated SSO
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995774#3995774
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995774
19 years, 7 months
[JBoss Seam] - EL enhancement of parameters working?
by dandiodati
Hi was trying out the s:link tag and noticed that it did not support actionListener events(By the way will this be supported?) So I noticed that
you can pass parameters to methods since seam adds some enhancements to
EL. When trying it I end up getting a null parameter passed into my getAction method. Here is the code segment:
<c:forEach items="#{TopNavViewHelper.navBar}" var="item">
| <c:set var="navItemStyle" value=""/>
| <c:if test="#{item.name == TopNavViewHelper.selectedName}">
| <c:set var="navItemStyle" value="selected"/>
| </c:if>
|
| <li class="#{navItemStyle}" id="#{item.name}" >
| <s:link id="#{item.name}" title="#{item.descr}" action="#{TopNavViewHelper.getAction(item.name)}" actionListener="#{TopNavViewHelper.clicked}"><span>#{item.label}</span>
| </s:link>
| <div>
| <ul/>
| </div>
| </li>
| </c:forEach>
The item.name in the getAction method call ends up being null instead
of have the name of the item. Does this not work within forEach loops?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995767#3995767
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995767
19 years, 7 months
[EJB 3.0] - Urgent Help needed !! ejb3 lookup problem from remote clien
by sursha
Hi,
I've the following code to lookup an ejb. Using JBOSS 4.0.5GA and ejb3.
Properties p=new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
p.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
p.put(Context.PROVIDER_URL,"jnp://host:1099");
InitialContext ctx = new InitialContext(p);
IReportService report = (IReportService) ctx.lookup(
"ejb3/com/aaa/MyService");
System.out.println("report.resubmit.."+report.resubmit());
------------------------------------------------------------
It works fine if jboss server and client is running on the same machine.
If I run the client from a remote machine, I get the following error
javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectExce ption: no such object in table]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:722)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at reportclient.ReportClient.main(ReportClient.java:20)
Caused by: java.rmi.NoSuchObjectException: no such object in table
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Stream RemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java: 223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
... 3 more
Any help will be appreciated
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995760#3995760
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995760
19 years, 7 months