Communication glassfish v2 - jboss 4.2.2GA

to delete
Edited by: user4449 on Oct 1, 2009 11:08 PM

Hi Carsten,
Please make sure you use the JROCKIT_HOME/bin/jrmc launcher to start Mission Control.
If that fails, try using the external management agent, i.e. starting with -Xmanagement:ssl=false,authenticate=false,port=7091
,then create a connection in JRMC manually.
What version of JRockit do you use (java -version), and what version of JRMC (jrmc -version | more)?
Kind regards,
Marcus

Similar Messages

Problem to get Mission Control 3.0.1 running with JBoss 4.2.2GA

Hello,
I'm using JRockit R27.04 to run JBoss 4.2.2GA with the following VM parameters:
-Xmanagement:ssl=false,authenticate=false,port=7091,autodiscovery=true -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl -Djboss.platform.mbeanserver
It's working fine but when I try to use any feature of Mission Control (console, memleak, JRA, ...) pointing to JBoss, I get a ClassNotFoundException:
Could not open Memory Leak Detector for (1.6) org.jboss.Main (4460).
java.rmi.UnmarshalException: error unmarshalling return; nested exception is:
 java.lang.ClassNotFoundException: org.apache.xerces.dom.DeferredElementImpl (no security manager: RMI class loader disabled)
java.rmi.UnmarshalException: error unmarshalling return; nested exception is:
 java.lang.ClassNotFoundException: org.apache.xerces.dom.DeferredElementImpl (no security manager: RMI class loader disabled)
 at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:178)
 at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
 at javax.management.remote.rmi.RMIConnectionImpl_Stub.getMBeanInfo(Unknown Source)
 at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getMBeanInfo(RMIConnector.java:1037)
 at com.jrockit.console.rjmx.RJMXConnection.getMBeanInfos(RJMXConnection.java:279)
 at com.jrockit.console.rjmx.RJMXConnection.getMBeanInfos(RJMXConnection.java:314)
 at com.jrockit.console.rjmx.RJMXConnectorModel.initializeAttributeInfos(RJMXConnectorModel.java:294)
 at com.jrockit.console.rjmx.RJMXConnectorModel.<init>(RJMXConnectorModel.java:99)
 at com.jrockit.console.rjmx.RJMXConnectorModel.<init>(RJMXConnectorModel.java:113)
 at com.jrockit.mc.memleak.ui.RjmxMemleakEditorInput.connect(Unknown Source)
 at com.jrockit.mc.memleak.ui.actions.StartMemleak$1.preConnect(Unknown Source)
 at com.jrockit.mc.browser.utils.PreConnectJob.run(PreConnectJob.java:73)
 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Caused by: java.lang.ClassNotFoundException: org.apache.xerces.dom.DeferredElementImpl (no security manager: RMI class loader disabled)
 at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:375)
 at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:165)
 at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:620)
 at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:247)
 at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:197)
 at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
 at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
 at java.util.HashMap.readObject(HashMap.java:1157)
 at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1846)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
 at java.io.ObjectInputStream.access$300(ObjectInputStream.java:188)
 at java.io.ObjectInputStream$GetFieldImpl.readFields(ObjectInputStream.java:2107)
 at java.io.ObjectInputStream.readFields(ObjectInputStream.java:519)
 at javax.management.modelmbean.DescriptorSupport.readObject(DescriptorSupport.java:1270)
 at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1846)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
 at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:480)
 at javax.management.modelmbean.ModelMBeanAttributeInfo.readObject(ModelMBeanAttributeInfo.java:524)
 at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1846)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
 at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1667)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1323)
 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
 at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:480)
 at javax.management.MBeanInfo.readObject(MBeanInfo.java:669)
 at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1846)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
 at sun.rmi.server.UnicastRef.unmarshalValue(UnicastRef.java:306)
 at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:155)
 ... 12 more
If I put xerces in jrockit classpath (putting the jar in jrockit-R27.4.0-jdk1.6.0_02\jre\lib\ext dir) just to workaround ClassNotFoundException and test again I get a new error:
Could not open Memory Leak Detector for (1.6) org.jboss.Main (4460).
java.rmi.UnmarshalException: error unmarshalling return; nested exception is:
 java.io.IOException: unknown protocol: resource
java.rmi.UnmarshalException: error unmarshalling return; nested exception is:
 java.io.IOException: unknown protocol: resource
 at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:173)
 at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
 at javax.management.remote.rmi.RMIConnectionImpl_Stub.getMBeanInfo(Unknown Source)
 at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getMBeanInfo(RMIConnector.java:1037)
 at com.jrockit.console.rjmx.RJMXConnection.getMBeanInfos(RJMXConnection.java:279)
 at com.jrockit.console.rjmx.RJMXConnection.getMBeanInfos(RJMXConnection.java:314)
 at com.jrockit.console.rjmx.RJMXConnectorModel.initializeAttributeInfos(RJMXConnectorModel.java:294)
 at com.jrockit.console.rjmx.RJMXConnectorModel.<init>(RJMXConnectorModel.java:99)
 at com.jrockit.console.rjmx.RJMXConnectorModel.<init>(RJMXConnectorModel.java:113)
 at com.jrockit.mc.memleak.ui.RjmxMemleakEditorInput.connect(Unknown Source)
 at com.jrockit.mc.memleak.ui.actions.StartMemleak$1.preConnect(Unknown Source)
 at com.jrockit.mc.browser.utils.PreConnectJob.run(PreConnectJob.java:73)
 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Caused by: java.io.IOException: unknown protocol: resource
 at java.net.URL.readObject(URL.java:1219)
 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 java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1846)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
 at java.util.HashMap.readObject(HashMap.java:1157)
 at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1846)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
 at java.io.ObjectInputStream.access$300(ObjectInputStream.java:188)
 at java.io.ObjectInputStream$GetFieldImpl.readFields(ObjectInputStream.java:2107)
 at java.io.ObjectInputStream.readFields(ObjectInputStream.java:519)
 at javax.management.modelmbean.DescriptorSupport.readObject(DescriptorSupport.java:1270)
 at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1846)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
 at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:480)
 at javax.management.modelmbean.ModelMBeanAttributeInfo.readObject(ModelMBeanAttributeInfo.java:524)
 at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1846)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
 at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1667)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1323)
 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
 at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:480)
 at javax.management.MBeanInfo.readObject(MBeanInfo.java:669)
 at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1846)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
 at sun.rmi.server.UnicastRef.unmarshalValue(UnicastRef.java:306)
 at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:155)
 ... 12 more
Can anyone help me?
Thank's,
Anderson Souza
Java/JEE Architect - Brasil

It was a good attempt, but I'm still getting the same exceptions.
I tried to create a new service file, and it was successful deployed:
<?xml version="1.0"?>
<server>
<mbean code="bea.jrockit.management.JRockitConsole" name="bea.jrockit.management:type=JRockitConsole">
</mbean>
</server>
After it I opened JBoss JMX Console and I saw the following mbeans published:
bea.jrockit.management
type=Compilation
type=DiagnosticCommand
type=GarbageCollector
type=JRA
type=JRockitConsole
type=Log
type=MemLeak
type=Memory
type=PerfCounters
type=Profiler
type=Runtime
So, it appears that all jkrockit MBeans are published, but the problem persist.
Any other suggestion?
Thanks,
Anderson Souza

Configure Remote OpenMq with Glassfish or JBoss as7

Hi,
I want to configure Glassfish 3.1 or JBoss as7 for OpenMQ as Remote Queue (Same m/c diff JVM). I've successfully created queue and queueconnection factory in Standalone OpenMQ at port 7677 and can access it( writing to and reading from the queue) from Standalone spring project .
Now I want to configure that remote queue (OpenMQ) any of the above mentioned Apps Server. I don't want to use embedded queue and I like to use JTA transaction
manager as well because I want to do 2-phase commit at my Oracle database.
I have tried mutiple ways but could not failing at jndi lookup for connection factory or proper transaction setup.
Could anyone provide me detailed information on remote openMQ queue setup at app server please?
Problem faced:
Glassfish 3.1 is very very slow. hangs everything in my machine. Please help to make it fast. I use asadmin commands still no luck.
JBoss AS7 : This version provides MDB support. Always ends up finding HornetQ and causing exception.. But I want to use OpenMQ remotely and also with JTA Transaction manager.
I know I am asking for huge details but It'll help me a lot as we can get rid of Webspere MQ and sWAS erver in developement environment. FYI I'd like to use jee-jndi lookup in spring config file of my project (generating EAR) so that when we change from Glassfish/JBoss the config file change will be minimal.

EJP wrote:
#{..} is a Facelets syntax. JSP uses ${..}.Wasn't that made universal since JEE 6?
In any case:
I still don't understand why these differences between two "standard" JSF implementations.Its the same JSF implementation, but different implementations of the JEE specification. With each version of the JEE spec things are standardized further, but containers have never been 100% cross-compatible and likely never will be. Its the same with databases really, same standard (SQL) but woefully different implementations of it regardless. That hasn't changed either after decades of existence.
The heart of the matter is: only migrate if you have a really good reason and when you do migrate - expect to need to do migration steps which will be different and mostly undocumented depending on which vendor you choose.

Need migrate application from glassfish to jboss

I need to migrate some applications that currently run on glassfish to the application server jboss. if there is someone who knows both environment and who can help me solve some problems ?
Thank you

Hi, Its no so easy to migrate from tomcat to webserver 4.1, because the webserver4.1 doesnt admit j2ee modules.
If you want to use j2EE maybe you have to use webserver 6.x

CMP Datasource configuration in jboss

Hi every body,
I am running CMP entity bean in jboss server4.2.2GA in netbeans and i am getting the following error.....
[QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
14:37:26,702 INFO [ConnectionFactoryBindingService] {color:#ff0000}*Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'*{color}
{color:#ff0000}*14:37:26,797 WARN [JBossManagedConnectionPool] Throwable while attempting to get a new connection: null*{color}
org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: Access is denied)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:179)
i did some of the modifications in configuration files like login....xml and standardjboss.....xml.
but still it gives the same error message..............
and even it is not taking the jndi given instead it took DefaultDS
please help me in this regard.................
Edited by: sathishsona on Dec 10, 2008 9:27 AM
Edited by: sathishsona on Dec 10, 2008 9:29 AM

Hi every body,
I am running CMP entity bean in jboss server4.2.2GA in netbeans and i am getting the following error.....
[QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
14:37:26,702 INFO [ConnectionFactoryBindingService] {color:#ff0000}*Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'*{color}
{color:#ff0000}*14:37:26,797 WARN [JBossManagedConnectionPool] Throwable while attempting to get a new connection: null*{color}
org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: Access is denied)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:179)
i did some of the modifications in configuration files like login....xml and standardjboss.....xml.
but still it gives the same error message..............
and even it is not taking the jndi given instead it took DefaultDS
please help me in this regard.................
Edited by: sathishsona on Dec 10, 2008 9:27 AM
Edited by: sathishsona on Dec 10, 2008 9:29 AM

How to configure destionation to connect jboss messaging

first,I install jboss 4.2.2GA ,and Jboss messaging 1.4.2sp3 ,and test they are ok. seconde, I deploy blazeds to jboss and run traderdektop samples,it also ok. third(the problem), I want use jms for flex client consume jMS ,the I try write a flex client use jms,but run the flex client,it can't consume jms message (but use other java client ok),how to solve this? my config file and flex client code as following: 1 . message-config.xml <?xml version="1.0" encoding="UTF-8"?> <service id="message-service" class="flex.messaging.services.MessageService"> <adapters> <adapter-definition id="actionscript" class="flex.messaging.services.messaging.adapters.ActionScriptAdapter" default="true" /> <adapter-definition id="jms" class="flex.messaging.services.messaging.adapters.JMSAdapter"/> </adapters> <default-channels> <channel ref="my-streaming-amf"/> <channel ref="my-polling-amf"/> </default-channels> <destination id="dashboard_chat"> <properties> <server> <durable>false</durable> </server> <jms> <destination-type>Topic</destination-type> <message-type>javax.jms.TextMessage</message-type> <connection-factory>ConnectionFactory</connection-factory> <destination-jndi-name>topic/testTopic</destination-jndi-name> <delivery-mode>NON_PERSISTENT</delivery-mode> <message-priority>DEFAULT_PRIORITY</message-priority> <acknowledge-mode>AUTO_ACKNOWLEDGE</acknowledge-mode> <transacted-sessions>false</transacted-sessions> </jms> </properties> <channels> <channel ref="my-polling-amf"/> </channels> <adapter ref="jms"/> </destination> </service> 2. write chatclient.mxml <?xml version="1.0"?> <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" width="100%" height="100%" creationComplete="creationCompleteHandler();"> <mx:Panel id="mainPanel" height="100%" width="100%"> <mx:HBox> <mx:Label text="Consumer"/> <mx:Button label="Subcribe" click="consumer.subscribe();" enabled="{!consumer.subscribed}"/> <mx:Button label="Unsubscribe" click="consumer.unsubscribe();" enabled="{consumer.subscribed}"/> <mx:Button label="Disconnect" click="consumer.disconnect();" enabled="{consumer.connected}"/> <mx:CheckBox label="Connected?" selected="{consumer.connected}"/> <mx:CheckBox label="Subscribed?" selected="{consumer.subscribed}"/> </mx:HBox> <mx:Button label="Clear" click='ta.text = ""'/> <mx:TextArea id="ta" width="100%" height="100%"/> </mx:Panel> <mx:Consumer id="consumer" destination="dashboard_chat" fault="faultHandler(event)" message="messageHandler(event)"/> <mx:Script> import mx.messaging.events.MessageFaultEvent; import mx.messaging.events.MessageEvent; import mx.messaging.messages.AsyncMessage; import mx.messaging.Producer; import mx.messaging.Consumer; import mx.logging.Log; import mx.logging.targets.TraceTarget; private function creationCompleteHandler():void { var target:TraceTarget = new TraceTarget(); target.includeLevel = true; target.filters = ["mx.messaging.*", "mx.rpc.*"]; Log.addTarget(target); } private function messageHandler(event:MessageEvent):void { ta.text += "Consumer received message: "+ event.message.body + "\n"; } private function faultHandler(event:MessageFaultEvent):void { ta.text += "Received fault: " + event.faultString + "\n"; } </mx:Script> </mx:Application>

try but cant't success,btw use weborb success,i don't know why. I also try to modify blazeds messaging-config.xml ,make it like the weborb's config,but not success,the weborb messaging-config.xml as following: <destination id="JbossChat"> <properties> <server> <durable>false</durable> </server> <jms> <initial-context-environment> <property> <name>java.naming.factory.initial</name> <value>org.jnp.interfaces.NamingContextFactory</value> </property> <property> <name>Context.URL_PKG_PREFIXES</name> <value>org.jboss.naming:org.jnp.interfaces</value> </property> <property> <name>java.naming.provider.url</name> <value>jnp://127.0.0.1:1099</value> </property> </initial-context-environment> <connection-factory>ConnectionFactory</connection-factory> <destination-jndi-name>topic/testTopic</destination-jndi-name> <acknowledge-mode>AUTO_ACKNOWLEDGE</acknowledge-mode> <transacted-sessions>false</transacted-sessions> <delivery-mode>NON_PERSISTENT</delivery-mode> <message-priority>6</message-priority> <message-factory>weborb.messaging.v3.jms.JmsObjectMessageFactory</message-factory> </jms> <message-service-handler>weborb.messaging.v3.jms.JmsServiceHandler</message-service-handl er> </properties> the blazeds messaging-config.xml as following: <destination id="JbossChat"> <properties> <server> <durable>false</durable> </server> <jms> <initial-context-environment> <property> <name>java.naming.factory.initial</name> <value>org.jnp.interfaces.NamingContextFactory</value> </property> <property> <name>Context.URL_PKG_PREFIXES</name> <value>org.jboss.naming:org.jnp.interfaces</value> </property> <property> <name>java.naming.provider.url</name> <value>jnp://127.0.0.1:1099</value> </property> </initial-context-environment> <connection-factory>ConnectionFactory</connection-factory> <destination-jndi-name>topic/testTopic</destination-jndi-name> <acknowledge-mode>AUTO_ACKNOWLEDGE</acknowledge-mode> <transacted-sessions>false</transacted-sessions> <delivery-mode>NON_PERSISTENT</delivery-mode> <message-priority>6</message-priority> </jms> </properties>

DL - JBoss4.0.5.GA startup & deployment problem

App Server used is JBoss4.0.5.GA
Please help in resolving below errors --->
C:\jboss-4.0.5.GA.new\bin>run
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\jboss-4.0.5.GA.new\bin\..
JAVA: C:\Program Files\Java\jdk1.5.0_07\bin\java
JAVA_OPTS: -Djava.io.tmpdir=C:\jboss-4.0.5.GA.new\bin\..\server\default\tmp -Dprogram.name=run.bat -Dserver.rootDir=C:\jbo
ss-4.0.5.GA.new\bin\.. -Dlog4j.configuration=log4j-startup.properties -Dhttp.browser.port=80 -Dhttp.sslaccel.port=81 -Dhttp.w
ebservice.port=8080 -server -Xms256m -Xmx512m -XX:MaxPermSize=128m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.serv
er.gcInterval=3600000
CLASSPATH: C:\Program Files\Java\jdk1.5.0_07\lib\tools.jar;C:\jboss-4.0.5.GA.new\bin\\run.jar
===============================================================================
The MICROS Portal is starting ...
[Dec/13 16:34:24] - MicrosLoader is running
[Dec/13 16:34:24] - ConfigClient update override to: NEVER
[Dec/13 16:34:24] - micros-login-config.xml is current
[Dec/13 16:34:24] - database-ds.xml is current
[Dec/13 16:34:24] - inventory-ds.xml is current
[Dec/13 16:34:24] - Launching JBoss
[Dec/13 16:34:24] - MicrosLoader exiting
log4j:WARN No appenders could be found for logger (org.jboss.system.server.Server).
log4j:WARN Please initialize the log4j system properly.
16:34:37,984 ERROR [AbstractKernelController] Error installing to Described: name=WSServerConfig state=Not Installed mode=Man
ual requiredState=Create
java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.wsf.stack.jbws.NativeServerConfig
at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212)
at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:511)
at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:405)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getTypeInfo(IntrospectionTypeInfoFactoryI
mpl.java:216)
at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactory.getTypeInfo(IntrospectionTypeInfoFactory.java
:47)
at org.jboss.classadapter.plugins.reflect.ReflectClassAdapterFactory.getClassAdapter(ReflectClassAdapterFactory.java:
61)
at org.jboss.kernel.plugins.config.AbstractKernelConfig.getBeanInfo(AbstractKernelConfig.java:59)
at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.getBeanInfo(AbstractKernelConfigurator.java:64)
at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.getBeanInfo(AbstractKernelConfigurator.java:76)
at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$DescribeAction.installAction(KernelControllerCo
ntextActions.java:227)
at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$KernelControllerContextAction.install(KernelCon
trollerContextActions.java:147)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:593)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:346)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:438)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:379)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:225)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:151)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:291)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:261)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:117)
at org.jboss.kernel.deployment.jboss.JBossBeanDeployment.createService(JBossBeanDeployment.java:69)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
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: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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.create(Unknown Source)
at org.jboss.system.ServiceController.create(ServiceController.java:330)
at org.jboss.system.ServiceController.create(ServiceController.java:273)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
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: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 $Proxy16.create(Unknown Source)
at org.jboss.deployment.SimpleSubDeployerSupport.createService(SimpleSubDeployerSupport.java:338)
at org.jboss.deployment.SimpleSubDeployerSupport.create(SimpleSubDeployerSupport.java:102)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
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:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
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:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
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: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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
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: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.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
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:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
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:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Thread.java:595)
16:34:38,343 ERROR [AbstractKernelController] Error installing to Described: name=WSEndpointRegistry state=Not Installed mode
=Manual requiredState=Create
java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.wsf.framework.management.ManagedEndpointRegistry
at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212)
at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:511)
at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:405)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getTypeInfo(IntrospectionTypeInfoFactoryI
mpl.java:216)
at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactory.getTypeInfo(IntrospectionTypeInfoFactory.java
:47)
at org.jboss.classadapter.plugins.reflect.ReflectClassAdapterFactory.getClassAdapter(ReflectClassAdapterFactory.java:
61)
at org.jboss.kernel.plugins.config.AbstractKernelConfig.getBeanInfo(AbstractKernelConfig.java:59)
at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.getBeanInfo(AbstractKernelConfigurator.java:64)
at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.getBeanInfo(AbstractKernelConfigurator.java:76)
at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$DescribeAction.installAction(KernelControllerCo
ntextActions.java:227)
at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$KernelControllerContextAction.install(KernelCon
trollerContextActions.java:147)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:593)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:346)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:438)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:379)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:225)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:151)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:291)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:261)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:117)
at org.jboss.kernel.deployment.jboss.JBossBeanDeployment.createService(JBossBeanDeployment.java:69)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
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: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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.create(Unknown Source)
at org.jboss.system.ServiceController.create(ServiceController.java:330)
at org.jboss.system.ServiceController.create(ServiceController.java:273)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
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: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 $Proxy16.create(Unknown Source)
at org.jboss.deployment.SimpleSubDeployerSupport.createService(SimpleSubDeployerSupport.java:338)
at org.jboss.deployment.SimpleSubDeployerSupport.create(SimpleSubDeployerSupport.java:102)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
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:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
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:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
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: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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
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: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.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
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:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
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:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Thread.java:595)
16:34:38,765 ERROR [AbstractKernelController] Error installing to Configured: name=WSSubscriptionManager state=Instantiated m
ode=Manual requiredState=Create
org.jboss.joinpoint.spi.JoinpointException: Property bindAddress not found for AbstractBeanInfo@a9a32c{name=org.jboss.ws.exte
nsions.eventing.mgmt.SubscriptionManager classInfo= properties=[completedTaskCount, largestPoolSize, activeCount, eventKeepAl
ive, class, validateNotifications, maxPoolSize, maximumPoolSize, corePoolSize] methods=[, , , , , , , , , , , , , , , , , , ,
, , , , , , , , , , , , , , , , , , , , , , , , , , ] constructors=[] events=}
at org.jboss.kernel.plugins.config.Configurator.resolveProperty(Configurator.java:659)
at org.jboss.kernel.plugins.config.Configurator.getPropertySetterJoinPoint(Configurator.java:433)
at org.jboss.kernel.plugins.config.Configurator.getPropertySetterJoinPoints(Configurator.java:398)
at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.getPropertySetterJoinPoints(AbstractKernelConfigurator.
java:112)
at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$ConfigureAction.installAction(KernelControllerC
ontextActions.java:313)
at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$KernelControllerContextAction.install(KernelCon
trollerContextActions.java:147)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:593)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:346)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:438)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:379)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:225)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:151)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:291)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:261)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:117)
at org.jboss.kernel.deployment.jboss.JBossBeanDeployment.createService(JBossBeanDeployment.java:69)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
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: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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.create(Unknown Source)
at org.jboss.system.ServiceController.create(ServiceController.java:330)
at org.jboss.system.ServiceController.create(ServiceController.java:273)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
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: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 $Proxy16.create(Unknown Source)
at org.jboss.deployment.SimpleSubDeployerSupport.createService(SimpleSubDeployerSupport.java:338)
at org.jboss.deployment.SimpleSubDeployerSupport.create(SimpleSubDeployerSupport.java:102)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
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:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
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:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
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: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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Deleg

Odd place to post this I'd have used JBoss forums would have served you better perhaps :)
I've recently experienced similar issues with JBoss 4.2.2.GA
In terms of comparing notes, did you do anything similar to this?
I was trying to run Core JSF 2nd edition's Seam example from Chapter 12.
I had initially tried to deploy in Glassfish, and it complained about el.Logger class not found, so I added commons-el.jar to WEB-INF\lib and when I read on I
saw a note in the book about deploying with Tomcat 5 & JBoss embedded Server. Since I already had JBoss 4.2.2GA installed, I figured I'd give this a whirl instead.
Then I got messages in JBoss log about myfaces jars not being compatible:
MyFaces JSF implementation found!
This version of JBoss AS ships with the java.net implementation of JSF.
There are known issues when mixing JSF implementations.
This warning does not apply to MyFaces component libraries such as Tomahawk.
However, myfaces-impl.jar and myfaces-api.jar should not be used without disabling the built-in JSF implementation.
See the JBoss wiki for more details. I initially posted in [JBoss Beginners forum post here|http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4158195#4158195] because initially I couldn't find
the wiki reference. But then happened to Google in on this
So I modified web.xml to include following code:
<context-param>
 <param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
 <param-value>true</param-value>
</context-param>and redeployed.
Then I got reams of similar messages to yourself starting with:
ERROR 15-06 11:23:48,109 (AbstractController.java:incrementState:350) -Error installing to Create: name=WSSubscriptionManager state=Configured
javax.management.InstanceAlreadyExistsException: jboss.ws:service=SubscriptionManager,module=eventing already registered.
 at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistry.java:761)
 at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:225)
 at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)Did you ever resolve this issue?
Regards, Jeremy

Any good books on web application using JSP/servlet?

Does anyone know good books on how-to build enterprise web application using JSP/servlet? Aside from the book "Head First JSP/Servlet". Development using Netbeans is more preferrable.

801264 wrote:
What about the free web server? JBoss or Glassfish or something else? I prefer web/application server that is fully compatible with JEE6 (unlike Tomcat that can't handle EJB). thanksI'm a JBoss user myself, so naturally I would advise that to you if I were ignorant. I'm not however, so in stead I'll tell you to investigate yourself and see which one you prefer. Nobody is going to tell you which one to use as there is no such thing as a 'better' or 'best' server. Just different servers each with different issues.
And the community edition of JBoss has had many issues in the past (because Red Hat of course wants to advise you to go to the enterprise platform which ain't cheap), but JBoss 5.1 was a rock solid piece of software that I have had zero problems with (after reading the odd forum or two). JBoss 6 builds on top of JBoss 5.1 and provides the full JEE6 web profile; this means it does NOT provide a certified 'full' JEE6 stack yet. This means nothing however as all the services you may need in an enterprise application are already there.
BTW: for simple servlet programming, don't neglect Apache Tomcat. Its a lightweight server that just works.

Strange error while deploying on Weblogic

Hello,
We have a simple JEE project (JSF, JEE), and we are using the Weblogic deployer (used by jenkins) to deploy a simple ear on WebLogic. The project is running perfectly under Glassfish on a local desktop. But when we try to deploy it on our dev server, we get this strange exception:
"Exception message for key INJECTION_POINT_HAS_UNSATISFIED_DEPENDENCIES not found due to Failed to locate resource bundle [org.jboss.weld.messages.validator] for locale [en] for enum type [org.jboss.weld.logging.messages.ValidatorMessage]"
The Weblogic deployment was working perfectly (under jenkins) before we add the sub-project dependencies by putting the resources/WEB-INF/beans.xml in each sub-project. So it seems that :
1) The dependency injection is not working under Weblogic, but under glassfish (and Jboss) it do works.
2) The resource bundle [org.jboss.weld.messages.validator] is not available! (??!) for the key INJECTION_POINT_HAS_UNSATISFIED_DEPENDENCIES.
This is our structure:
- ear
- - war
- - - business
- - - persistence
- - - web-services
- - - commons
- - - etc.
So there's nothing original here. I have googled the exception, but there's nothing abnormal here. Jenkins is using a pre-compiled wlfullclient.jar to deployed everything.
Thanks for any advices
Etienne
Stack trace:
weblogic.Deployer invoked with options: -debug -stage -remote -verbose -upload -name obe -source /root/.jenkins/jobs/obe/modules/com.xxx.obe$obe-ear/builds/2013-05-22_16-43-19/archive/com.xxx.obe/obe-ear/0.1-SNAPSHOT/obe-ear-0.1-SNAPSHOT.ear -targets OBEServer -adminurl t3://xxxxxxxxxxxxx:7333 -user weblogic -deploy
[WebLogicDeploymentManagerImpl.():119] : Constructing DeploymentManager for J2EE version V1_4 deployments
[WebLogicDeploymentManagerImpl.getNewConnection():162] : Connecting to admin server at xxxxxxxxxxxxx:7333, as user weblogic
[ServerConnectionImpl.getEnvironment():286] : setting environment
[ServerConnectionImpl.getEnvironment():289] : getting context using t3://xxxxxxxxxxx:7333
[ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://xxxxxxxxxxxxx:7333/jndi/weblogic.management.mbeanservers.domainruntime
[ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://xxxxxxxxxxxxx:7333/jndi/weblogic.management.mbeanservers.runtime
[DomainManager.resetDomain():36] : Getting new domain
[DomainManager.resetDomain():39] : Using pending domain: false
[MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@5d61fb38
[MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@5d61fb38
[MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@1b9ced28
[MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@1b9ced28
[ServerConnectionImpl.initialize():169] : Connected to WLS domain: OBEDomain
[ServerConnectionImpl.setRemote():480] : Running in remote mode
[ServerConnectionImpl.init():159] : Initializing ServerConnection : [email protected]4078
[BasicOperation.dumpTmids():740] : Incoming tmids:
[BasicOperation.dumpTmids():742] : {Target=OBEServer, WebLogicTargetType=server, Name=obe}, targeted=true
[BasicOperation.deriveAppName():143] : appname established as: obe
<22-May-2013 4:43:58 o'clock PM EDT>
[BasicOperation.dumpTmids():740] : Incoming tmids:
[BasicOperation.dumpTmids():742] : {Target=OBEServer, WebLogicTargetType=server, Name=obe}, targeted=true
[BasicOperation.loadGeneralOptions():655] : Delete Files:false
Timeout :3600000
Targets:
OBEServer
ModuleTargets={}
SubModuleTargets={}
Files:
null
Deployment Plan: null
App root: /tmp/root/./config/deployments/obe
App config: /tmp/root/./config/deployments/obe/plan
Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=stage,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=obe,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=false}
[ServerConnectionImpl.upload():849] : Uploaded app to /bea_OBE/obedev/OBEDomain/./servers/OBEServer/upload/obe
[BasicOperation.execute():472] : Initiating deploy operation for app, obe, on targets:
[BasicOperation.execute():474] : OBEServer
Task 53 initiated: [Deployer:149026]deploy application obe on OBEServer.
dumping Exception stack
Task 53 failed: [Deployer:149026]deploy application obe on OBEServer.
Target state: deploy failed on Server OBEServer
org.jboss.weld.exceptions.DeploymentException: Exception message for key INJECTION_POINT_HAS_UNSATISFIED_DEPENDENCIES not found due to Failed to locate resource bundle [org.jboss.weld.messages.validator] for locale [en] for enum type [org.jboss.weld.logging.messages.ValidatorMessage]
 at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:258)
 at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:105)
 at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:125)
 at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:324)
 at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:309)
 at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:361)
 at com.oracle.injection.provider.weld.WeldInjectionContainer.start(WeldInjectionContainer.java:105)
 at com.oracle.injection.integration.CDIAppDeploymentExtension.prepare(Unknown Source)
 at weblogic.application.internal.flow.AppDeploymentExtensionFlow.prepare(AppDeploymentExtensionFlow.java:23)
 at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:706)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:35)
 at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:237)
 at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:61)
 at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:158)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:96)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:229)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
 at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Target Assignments:
+ obe OBEServer
[ServerConnectionImpl.close():332] : Closing DM connection
[ServerConnectionImpl.close():352] : Unregistered all listeners
[ServerConnectionImpl.closeJMX():372] : Closed JMX connection
[ServerConnectionImpl.closeJMX():384] : Closed Runtime JMX connection

Hi all,
Any help?
Thanks

EJB 3.0 access problem

Hello!
I would like to know how I could access from a ManagedBean to the remote interface of a Session Bean. The structure of my ear file is de folowing:
-Prototipo.ear
-META-INF
 - MANIFEST.MF
 - application.xml
 - jboss-app.xml
-PrototipoEJB.jar
-entity
 -ProyectoCMP.class
-META-INF
 -MANIFEST.MF
 -ejb-jar.xml
 -persistence.xml
-session
 -GestorProyectosBean
 -GestorProyectosHome
 -GestorProyectosRemote
-PrototipoWeb
 -META-INF
 -MANIFEST.MF
 -WEB-INF
 -classes
 -ManagedBean.class
 -lib
 -faces-config.xml
 -web.xmlIn the class ManagedBean I would acces to the session bean GestorProyectosRemote but I don't know how. I try to import the package session.GestorProyectosRemote but this doesn't work.
I'm using JBoss 4.2.2GA + EJB3.0. In the ejb-jar.xml file there aren't any definition of a bean.This is not necesary for EJB3 doesn't true? This is the content of ejb-jar.xml
<?xml version="1.0" encoding="utf-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" version="3.0"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd">
</ejb-jar>How I can access to the Remote interface of my sessionBean (GestorProyectosRemote)? Because in the class ManagedBean if I put import session.*; Eclipse tells me that this is an error because cannot be resolved
Thanks,

Sorry!!! This is a stupid mistake! I forget establish the dependece between my web tier and my ejb tier. Thanks

Tutorial for creating a J2EE project with "Flex Builder 3 Beta 3 " ?

Hi,
I'm trying to set up a Flex environment with:
Flex Builder 3 Beta 3 stand alone
WTP (from eclipse update manager)
LCDS 2.5 (with JRun)
JBoss 4.2.2GA
At this moment I successful installed everything (but not set up). I added WTP at Flex Builder3 (with the eclipse update manager). I copied the two flex-tomcat files in jboss.
Then in Flex Builder 3 I created a new Flex Project. In the wizard first window, I selected J2EE, Livecycle and WTP. Then in the next window I need to configurate the J2EE server.
I couldn't find any information/tutorial for this window? Is there a tutorial for this?
This window ask me:
Target Runtime: I created a new one for JBoss 4.2.2 (during this process flex builder asked me to add a project but actually I'm creating this project so I hadn't any project to add (??)).
ContextRoot: name of the project I'm creating (default). Is it good?
Content Folder: the default is "WebContent". Is it good?
Flex War File: What is that? Where do I find it?
Thanks a lot,
Jerome

The settings you mention all sound fine, but the I believe the Flex War file may be what you referred to as the flex-tomcat files (specifically the one should be called flex.war from the install folder).
You don't need to deploy the flex.war file to JBoss manually, when you create a project, you just select the file in the wizard and it is extracted and used as a template for the new project. In fact, it may cause a port conflict with your project if you do deploy manually it (unless you tweak some of the config files), so it's probably worth removing it from the deploy folder if you did put it there. The other file, flex-admin.war, can stay without causing issue.
The closest to a tutorial that I am aware of is if you search "New Flex Project" in the help system, it talks about what each of the options should be when creating LCDS projects.

ServletFileUpload.parseRequest return empty list in Struts 1.3?

I used ServletFileUpload.parseRequest(request) to get my list of items, with Struts 1.3, JBoss 4.2.2GA(migrated from JBoss 4.0.5GA) I am using JDK 1.5, on myEclipse 6.6 ( migrated from myEclipse 5.5.1GA).
My file upload application used to work and ServletFileUpload.parseRequest(request) used to return non empty results as a List<FileItem>. I am not sure ( that's the frustrating part) what has changed, but now I am getting a empty list!
I have switched to previous version of JBoss 4.0.5.GA, and myEclipse 5.5.GA and still it didn't work. I know what I need to have for this to work, i.e. :
JSTL tag in JSP:
<html:form enctype="multipart/form-data"....>
<html:file styleId="uploadFile" property="uploadFile" size="40" />
My FormBean has uploadFile as FormFile and getter and setter for it.
I wrote a Utility class to include this apache commons fileupload API and my action class calls the Util class.
The Util class looks like this:
DiskFileItemFactory factory = new DiskFileItemFactory();
ServletFileUpload upload = new ServletFileUpload(factory);
List<FileItem> items = (List<FileItem>) upload.parseRequest(request);
Like I said, items used to return non-empty results and I was uploading file just fine. I am using Struts 1.3, Spring 2.0, which hasn't changed. And even though my myEclipse and JBoss version changed, I did revert back to the previous version just to test them and still am getting empty list.
I am pulling my hair out on this, I'd really appreciate any input and if you need more info, I'd be happy to replenish them!
Thanks in advance!

The current release BEA Workshop 3.2 (build 569), does not bundle Struts 1.3.5 and is also not aware of Struts 1.3 release.
However, this should not stop you from manually importing the Struts 1.3 libraries or samples into Workshop.
Preferences | Workshop Studio Facet Libraries | Struts Libraries, is used by the New Web app and Project Facet wizard to import the libraries on creation. Instead you can manually copy/overwrite Struts 1.3 libraries in your existing Struts project.We will keep you posted on the 1.3 support release.

Security in JMS

Planning on using jms as means of communication between two jboss servers one facing internet and one internal.
Downloaded JMS for jboss and was able to successfully run the queue example on jboss 4.0.1 sp1.
Have few questions on securing jms on jboss:
1) The SSL example has the following note:
"A service configuration bug that exists in all JBoss versions prior to 4.0.4.RC1 prevents this example from working correctly"
Does this mean for versions prior to 4.0.4 JBoss Messaging thru Secure Socket Connection is not possible?
2) If i am correct, apart from SSL i believe i can setup a user/role based access to queues/messaging-resources that will limit the connections to only clients with proper credentials?
3) Any other suggestions on securing a JMS system
Also what are the alternatives to this solution.
TIA,
Raj

Hi,
The queuing series to be is based on the circumstances. If the client is already using MQ, then we need to go for MQ. Similarly for others too.
For deploying the drivers, go thro this How To guide:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
About security levels, i think normal Message Level and Network level securities can be handled with JMS adapters.
Regards,
P.Venkat

Pros and Cons of using REST over JMS (and other technologies)

Hey all,
I am working on a project where we were using JMS initially to send messages between servers. Our front end servers have a RESTful API and use JEE6, with EJB 3.1 entity beans connected to a mysql database and so forth. The back end servers are more like "agents" so to speak.. we send some work for them to do, they do it. They are deployed in GlassFish 3.1 as well, but initially I was using JMS to listen to messages. I learned that JMS onMessage() is not threaded, so in order to facilitate handling of potentially hundreds of messages at once, I had to implement my own threading framework. Basically I used the Executor class. I could have used MDBs, but they are a lot more heavyweight than I needed, as the code within the onMessage was not using any of the container services.
We ran into other issues, such as deploying our app in a distributed architecture in the cloud like EC2 was painful at best. Currently the cloud services we found don't support multi-cast so the nice "discover" feature for clustering JMS and other applications wasn't going to work. For some odd reason there seems to be little info on building out a scalable JEE application in the cloud. Even the EC2 techs, and RackSpace and two others had nobody that understood how to do it.
So in light of this, plus the data we were sending via JMS was a number of different types that had to all be together in a group to be processed.. I started looking at using REST. Java/Jersey (JAX-RS) is so easy to implement and has thus far had wide industry adoption. The fact that our API is already using it on the front end meant I could re-use some of the representations on the back end servers, while a few had to be modified as our public API was not quite needed in full on the back end. Replacing JMS took about a day or so to put the "onmessage" handler into a REST form on the back end servers. Being able to submit an object (via JAXB) from the front servers to the back servers was much nicer to work with than building up a MapMessage object full of Map objects to contain the variety of data elements we needed to send as a group to our back end servers. Since it goes as XML, I am looking at using gzip as well, which should compress it by about 90% or so, making it use much less bandwidth and thus be faster. I don't know how JMS handles large messages. We were using HornetQ server and client.
So I am curious what anyone thinks.. especially anyone that is knowledgeable with JMS and may understand REST as well. What benefits do we lose out on via JMS. Mind you, we were using a single queue and not broadcasting messages.. we wanted to make sure that one and only one end server got the message and handled it.
Thanks..look forward to anyone's thoughts on this.

851827 wrote:
Thank you for the reply. One of the main reasons to switch to REST was JMS is strongly tied to Java. While I believe it can work with other message brokers that other platforms/languages can also use, we didn't want to spend more time researching all those paths. REST is very simple, works very well and is easy to implement in almost any language and platform. Our architecture is basically a front end rest API consumed by clients, and the back end servers are more like worker threads. We apply a set of rules, validations, and such on the front end, then send the work to be done to the back end. We could do it all in one server tier, but we also want to allow other 3rd parties to implement the "worker" server pieces in their own domains with their own language/platform of choice. Now, with this model, they simply provide a URL to send some REST calls to, and send some REST calls back to our servers.well, this sounds like this would be one of those requirements which might make jms not a good fit. as ejp mentioned, message brokers usually have bindings in multiple languages, so jms does not necessarily restrict you from using other languages/platforms as the worker nodes. using a REST based api certainly makes that more simple, though.
As for load balancing, I am not entirely sure how glassfish or JBoss does it. Last time I did anything with scaling, it involved load balancers in front of servers that were session/cookie aware for stateful needs, and could round robin or based on some load factor on each server send requests to appropriate servers in a cluster. If you're saying that JBoss and/or GlassFish no longer need that.. then how is it done? I read up on HornetQ where a request sent to one ip/hornetq server could "discover" other servers in a cluster and balance the load by sending requests to other hornetq servers. I assume this is how the JEE containers are now doing it? The problem with that to me is.. you have one server that is loaded with all incoming traffic and then has to resend it on to other servers in the cluster. With enough load, it seems that the glassfish or jboss server become a load balancer and not doing what they were designed to do.. be a JEE container. I don't recall now if load balancing is in the spec or not..I would think it would not be required to be part of a container though, including session replication and such? Is that part of the spec now?you are confusing many different types of scaling. different layers of the jee stack scale in different ways. you usually scale/load balance at the web layer by putting a load balancer in front of your servers. at the ejb layer, however, you don't necessarily need that. in jboss, the client-side stub for invoking remote ejbs in a cluster will actually include the addresses for all the boxes and do some sort of work distribution itself. so, no given ejb server would be receiving all the incoming load. for jms, again, there are various points of work to consider. you have the message broker itself which is scaled/load balanced in whatever fashion it supports (don't know many details on actual message broker impls). but, for the mdbs themselves, each jee server is pretty independent. each jee server in the cluster will start a pool of mdbs and setup a connection to the relevant queue. then, the incoming messages will be distributed to the various servers and mdbs accordingly. again, no single box will be more loaded than any other.
load balancing/clustering is not part of the jee "spec", but it is one of the many features that a decent jee server will handle for you. the point of jee was to specify patterns for doing work which, if followed, allow the app server to do all the "hard" parts. some of those features are required (transactions, authentication, etc), and some of those features are not (clustering, load-balancing, other robustness features).
I still would think dedicated load balancers, whether physical hardware or virtual software running in a cloud/VM setup would be a better solution for handling load to different tiers?like i said, that depends on the tier. makes sense in some situations, not others. (for one thing, load-balancers tend to be http based, so they don't work so well for non-http protocols.)

JNDI obj not binding to initial context--10gRel 2 issue only,works in rel3

hi all,
The issue I am writing about is an issue only in OAS 10g release 2 (10.1.2.0.2) and not in release 3. I have an issue where in I am trying to bind a data source object to the initial context. This data source object reference is created dynamically and is not specified in any XML file (say like web.xml or server.xml). The business requirement driving this is that for each user we need to create a data source dynamically and attach it to the JNDI and then this JNDI name is passed on to Crystal Reports which will use this data source to retrieve its data from the DB. The code for creating the data source dynamically is as below,
private String setDataSource(String username, String password) throws NamingException {
          String prefix = "jdbc";
          InitialContext ic = new InitialContext();
          // Construct BasicDataSource reference
          Reference ref = new Reference("javax.sql.DataSource", CustomDataSourceFactory.class.getName(), null);
          ref.add(new StringRefAddr("url", xxxxxx));
          ref.add(new StringRefAddr("schema",xxxxx));
          ref.add(new StringRefAddr("xxxxxx", xxxxx));
          ref.add(new StringRefAddr("password", xxxxx));
          try {
               ic.listBindings(prefix);
          } catch (NameNotFoundException exp) {
               ic.createSubcontext(prefix);
          String datasourceName = prefix + "/" + oneNumber;
          ic.rebind(datasourceName, ref);
          return datasourceName;
As you can see the reference to the data source is added dynamically. Now when I try to obtain this object by looking up the context for its JNDI name I get a object not found error. This is how I look up the object through my code,
private void testDataSource(String dsName){
          Connection conn = null;
          Statement stmt = null;
          ResultSet rs = null;
          try {
               InitialContext ic = new InitialContext();
               javax.sql.DataSource ds = (javax.sql.DataSource) ic.lookup(dsName);
               conn = ds.getConnection();
               stmt = conn.createStatement();
               rs = stmt.executeQuery("select sysdate from dual");
               String result = rs.getString(1);
               System.out.println("----YOGI----Result of query execution is AAA -----" + result);
          } catch (Exception ex ){
               System.out.println("----YOGI----the exception from this specific block is " + ex.getLocalizedMessage());
          finally {
               try {
                    if (null!= rs)
                         rs.close();
                    if(null !=stmt)
                         stmt.close();
                    if(null !=conn)
                         conn.close();
               } catch (Exception ex){
                    System.out.println("Hopeless");
When I do this I get this exception message --> jdbc/1562 not found in MyAPP
jdbc/1562 is the data source JNDI name I generated in the first method and "MyAPP" is the name of my application. I decided to make the JNDI globally available in the context and hence I used "java:global/jdbc/1562" for my datasource name and even that did not work even though the JNDI name is not bound to the application in specific.
I am really at a loss here as this is a simple add/retrieve operation to a object bound to the context. Can someone tell what is wrong here? The same code works fine in release 3 OAS and also in tomcat and websphere. Any help will be appreciated.
Regards,
Yogi

OK, I seem to be getting a new exception, not sure if I did any change but ran into this exception in the logs,
11/08/24 18:45:08 ----YOGI----the exception from this specific block is javax.naming.Reference cannot be cast to javax.sql.DataSource*
From what I read on the web, this is prevalent in glassfish and jboss. The reason could be that missing j2ee.jar in classpath or duplicate jdbc jars. I added j2ee.jar to my application library in oc4j dint resolve the issue. I removed jdbc jar from the OAS lib folder and restarted, it dint help.
Any other clues, anyone?

Communication glassfish v2 - jboss 4.2.2GA

Similar Messages

Maybe you are looking for