Micheal John

Any idea/help?

Hi,

I am trying to get the datasource through a Java Standalone program from WebSphere 7.0 JNDI.
Below is my program and I successfully got the InitialContext, but getting the the below error while getting the datasource:
ANy idea / help on this will be helpful..

WARNING: jndiGetObjInstNoop java.lang.ClassCastException: javax.naming.Reference incompatible with javax.sql.DataSource at com.example.PolicyQuotes.getDBConnection(PolicyQuotes.java:47) at com.example.PolicyQuotes.main(PolicyQuotes.java:25) Exception: javax.naming.Reference incompatible with javax.sql.DataSource

import java.sql.Connection; import java.sql.ResultSet; import java.sql.Statement; import java.sql.PreparedStatement; import java.text.SimpleDateFormat; import java.util.*; import javax.naming.*; import javax.sql.DataSource; import java.text.*; public class PolicyQuotes{ private Connection conn = null; private StringBuffer query = null; private PreparedStatement pStatement = null; private Statement statementObj = null; private ResultSet dbResult = null; public static void main(String args[]){ new PolicyQuotes().getDBConnection(); } public Connection getDBConnection(){ try{ Context initialContext = getInitialContext(); System.out.println("initialContext: " +initialContext); Object obj = initialContext.lookup("jdbc/Policy_DB2"); System.out.println("obj: " +obj); javax.sql.DataSource ds = (javax.sql.DataSource)initialContext.lookup("jdbc/Policy_DB2"); Connection conn = ds.getConnection(); System.out.println("conn: " +conn); return conn; }catch(NamingException ne) { ne.printStackTrace(); System.out.println("NamingException: " + ne.getMessage()); }catch(Exception e){ e.printStackTrace(); System.out.println("Exception: " + e.getMessage()); } return null; } public Context getInitialContext() throws NamingException{ Context initialContext = null; try{ Hashtable properties = new Hashtable(); properties.put(Context.INITIAL_CONTEXT_FACTORY,"com.ibm.websphere.naming.WsnInitialContextFactory"); //properties.put(Context.PROVIDER_URL, "iiop://myhostname:21014"); //properties.put(Context.PROVIDER_URL, "iiop://myhostname:2809"); //properties.put(Context.PROVIDER_URL, "iiop://myhostname:2809"); //properties.put(Context.PROVIDER_URL, "corbaloc:iiop:myhostname:21014"); //properties.put(Context.PROVIDER_URL, "iiop://myhostname:21014"); properties.put(Context.PROVIDER_URL, "corbaloc:iiop:myhostname:21014"); //properties.put(Context.PROVIDER_URL, "iiop://myhostname:21014"); initialContext = new InitialContext(properties); }catch (NamingException ne) { ne.printStackTrace(); throw ne; }catch(Exception e){ e.printStackTrace(); } return initialContext; } }

Error Log:
=========
initialContext: javax.naming.InitialContext@11cd11cd Jul 27, 2011 6:08:09 PM null null WARNING: WSVR0072W Jul 27, 2011 6:08:10 PM null null INFO: Client code attempting to load security configuration Jul 27, 2011 6:08:11 PM null null WARNING: jndiGetObjInstNoop obj: Reference Class Name: javax.resource.cci.ConnectionFactory Type: connectorName Content: Policy_DB2 Type: classpath Content: /webhost/WAS7/opt/WebSphere/v700-64/lib/rsadapter.rar:/webhost/WAS7/opt/WebSphere/v700-64/lib/rsadapter.rar Type: FactoryJndiName Content: jdbc/Policy_DB2 The type of the address is: dd The content of the address is: ffffffac ffffffed 0 5 73 72 0 25 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 52 65 73 6f 75 72 63 65 41 64 61 70 74 65 72 44 44 49 6d 70 6c ffffffc3 ffffffac 4 ffffffb6 2c 65 30 ffffffd6 3 0 4 5a 0 17 72 65 61 75 74 68 65 6e 74 69 63 61 74 69 6f 6e 53 75 70 70 6f 72 74 49 0 12 74 72 61 6e 73 61 63 74 69 6f 6e 53 75 70 70 6f 72 74 4c 0 b 63 66 49 6e 74 65 72 66 61 63 65 74 0 12 4c 6a 61 76 61 2f 6c 61 The type of the address is: miscProps The content of the address is: ffffffac ffffffed 0 5 73 72 0 14 6a 61 76 61 2e 75 74 69 6c 2e 50 72 6f 70 65 72 74 69 65 73 39 12 ffffffd0 7a 70 36 3e ffffff98 2 0 1 4c 0 8 64 65 66 61 75 6c 74 73 74 0 16 4c 6a 61 76 61 2f 75 74 69 6c 2f 50 7 2 6f 70 65 72 74 69 65 73 3b 78 72 0 13 6a 61 76 61 2e 75 74 69 6c 2e 48 61 73 68 74 61 62 6c 65 13 ffffffbb f 25 21 4a f fffffe4 ffffffb8 3 0 2 46 0 a 6c 6f 61 64 46 61 63 74 6f 72 49 0 9 74 68 72 The type of the address is: poolProps The content of the address is: ffffffac ffffffed 0 5 73 72 0 27 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 43 6f 6e 6e 65 63 74 6f 72 50 6f 6f 6c 50 72 6f 70 65 72 74 69 65 73 e 2a ffffffd3 ffffff84 70 ffffffcb ffffffa9 15 3 0 15 4a 0 b 61 67 65 64 54 69 6d 65 6f 75 74 4a 0 11 63 6f 6e 6e 65 63 74 69 6f 6e 54 69 6d 65 6f 75 74 49 0 e 64 69 61 67 6e 6f 73 7 4 69 63 4d 6f 64 65 49 0 1d 66 72 65 65 50 6f 6f 6c 44 69 73 74 72 69 62 75 The type of the address is: configProps The content of the address is: ffffffac ffffffed 0 5 73 72 0 23 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 43 6f 6e 6e 65 63 74 6f 72 50 72 6f 70 65 72 74 69 65 73 fffffffc ffffff8d 1d ffffffaa 26 ffffff85 ffffffc7 34 2 0 0 78 72 0 10 6a 61 76 61 2e 75 74 69 6c 2e 56 65 63 74 6f 72 ffffffd9 ffffff97 7d 5b ffffff80 3b ffffffaf 1 3 0 3 49 0 11 63 61 70 61 63 69 74 79 49 6e 63 72 65 6d 65 6e 74 49 0 c 65 6c 65 6d 65 6e 74 43 6f 75 6e 74 5b 0 b 65 6c 65 6d 65 The type of the address is: mmProps The content of the address is: ffffffac ffffffed 0 5 73 72 0 14 6a 61 76 61 2e 75 74 69 6c 2e 50 72 6f 70 65 72 74 69 65 73 39 12 ffffffd0 7a 70 36 3e ffffff98 2 0 1 4c 0 8 64 65 66 61 75 6c 74 73 74 0 16 4c 6a 61 76 61 2f 75 74 69 6c 2f 50 7 2 6f 70 65 72 74 69 65 73 3b 78 72 0 13 6a 61 76 61 2e 75 74 69 6c 2e 48 61 73 68 74 61 62 6c 65 13 ffffffbb f 25 21 4a f fffffe4 ffffffb8 3 0 2 46 0 a 6c 6f 61 64 46 61 63 74 6f 72 49 0 9 74 68 72 The type of the address is: dsProps The content of the address is: ffffffac ffffffed 0 5 73 72 0 14 6a 61 76 61 2e 75 74 69 6c 2e 50 72 6f 70 65 72 74 69 65 73 39 12 ffffffd0 7a 70 36 3e ffffff98 2 0 1 4c 0 8 64 65 66 61 75 6c 74 73 74 0 16 4c 6a 61 76 61 2f 75 74 69 6c 2f 50 7 2 6f 70 65 72 74 69 65 73 3b 78 72 0 13 6a 61 76 61 2e 75 74 69 6c 2e 48 61 73 68 74 61 62 6c 65 13 ffffffbb f 25 21 4a f fffffe4 ffffffb8 3 0 2 46 0 a 6c 6f 61 64 46 61 63 74 6f 72 49 0 9 74 68 72 The type of the address is: mcfProps The content of the address is: ffffffac ffffffed 0 5 73 72 0 2d 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 4d 61 6e 61 67 65 64 43 6f 6e 6e 65 63 74 69 6f 6e 46 61 63 74 6f 72 79 50 72 6f 70 73 ffffffd3 21 53 ffffffb4 ffffffca ffffffd2 6 5 24 3 0 1 4c 0 15 43 6f 6e 6e 65 63 74 69 6f 6e 46 61 63 74 6f 72 79 54 79 70 65 74 0 13 4c 6a 61 76 61 2f 6c 61 6e 67 2 f 49 6e 74 65 67 65 72 3b 78 70 73 72 0 11 6a 61 76 61 2e 6c 61 6e 67 2e 49 6e The type of the address is: mbeanProps The content of the address is: ffffffac ffffffed 0 5 73 72 0 1a 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 4d 42 65 61 6e 50 72 6f 70 73 ffffffd1 ffffff83 7f ffffffe8 3e 14 ffffffca ffffff9f 3 0 b 4c 0 17 61 75 74 68 4d 65 63 68 61 6e 69 73 6d 50 72 65 66 65 72 65 6e 63 65 74 0 13 4c 6a 61 76 61 2f 6c 61 6e 67 2f 49 6e 74 65 67 65 72 3b 4c 0 8 63 61 74 65 67 6f 72 79 74 0 12 4c 6a 61 76 61 2f 6c 61 6e 67 2f 53 74 72 69 6e 67 3b 4c 0 9 Jul 27, 2011 6:08:11 PM null null WARNING: jndiGetObjInstNoop java.lang.ClassCastException: javax.naming.Reference incompatible with javax.sql.DataSource at com.example.PolicyQuotes.getDBConnection(PolicyQuotes.java:47) at com.example.PolicyQuotes.main(PolicyQuotes.java:25) Exception: javax.naming.Reference incompatible with javax.sql.DataSource

I am trying to parse the below xml file in java using DOM.
First, I am getting the root element using
Element rootElement = doc.getDocumentElement() System.out.println("rootElement ::"+rootElement.getNodeName());

Then, I am trying to find out how many children for the root element using
NodeList childNodeList = rootElement.getChildNodes(); System.out.println("childNodeList len ::"+childNodeList.getLength());

I am getting as 3 for the above. But the root element is printing as "MessageBean"
and the "MessageBean" root element have only one child node "Request", then why it's coming as 3?

I am trying get the <form> attribute values (name="emp1" and value="10") and the actual valus (St1).
I need to get all the children of <Request> only with the tag <form> adn not the <Unit>
Then I need to get the all the children of the <Unit> separatley.

Why the "childNode11111 ::#text" is coming as #text??

Please help on this. I don't uderstand how to process it. If someone explain how it works I can able to parse more complex xmls too.


<?xml version="1.0"?> <MessageBean> <Request> <form name="emp1" value="10">St1</form> <form name="emp2" value="20">St2</form> <Unit name="test"> <form name="emp3" value="30">St3</form> <form name="emp4" value="40">St4</form> </Unit> </Request> </MessageBean>


File file = new File("C:/Mike/test.xml"); DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance(); DocumentBuilder db = dbf.newDocumentBuilder(); Document doc = db.parse(file); doc.getDocumentElement().normalize(); Element rootElement = doc.getDocumentElement(); System.out.println("rootElement ::"+rootElement.getNodeName()); NodeList childNodeList = rootElement.getChildNodes(); System.out.println("childNodeList len ::"+childNodeList.getLength()); for(int i=0;i<childNodeList.getLength();i++){ Node childNode1 = childNodeList.item(i); System.out.println("childNode1 ::"+childNode1.getNodeName()); NodeList cNode = childNode1.getChildNodes(); for(int j=0;j<cNode.getLength();j++){ Node childNode2 = cNode.item(j); System.out.println("childNode11111 ::"+childNode2.getNodeName()); System.out.println("get child value1111::"+childNode2.getNodeValue()); } }


output
rootElement ::MessageBean childNodeList len ::3 childNode1 ::#text childNode1 ::Request childNode11111 ::#text get child value1111:: childNode11111 ::form get child value1111::null childNode11111 ::#text get child value1111:: childNode11111 ::form get child value1111::null childNode11111 ::#text get child value1111:: childNode11111 ::Unit get child value1111::null childNode11111 ::#text get child value1111:: childNode1 ::#text >

Actually, I am using the same JBoss4.2.2.GA in Windows Vista in my home note book. And it's staring properly.
Now I am trying same in Windows 2000, but in corporate network. Do you mean to say that JBoss 5.x will work?

Exception...
10:14:51,293 INFO [Server] Starting JBoss (MX MicroKernel)... 10:14:51,355 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139) 10:14:51,355 INFO [Server] Home Dir: C:\java\common\bin\jboss-4.2.2.GA 10:14:51,402 INFO [Server] Home URL: file:/C:/java/common/bin/jboss-4.2.2.GA/ 10:14:51,402 INFO [Server] Patch URL: null 10:14:51,402 INFO [Server] Server Name: default 10:14:51,402 INFO [Server] Server Home Dir: C:\java\common\bin\jboss-4.2.2.GA\server\default 10:14:51,402 INFO [Server] Server Home URL: file:/C:/java/common/bin/jboss-4.2.2.GA/server/default/ 10:14:51,402 INFO [Server] Server Log Dir: C:\java\common\bin\jboss-4.2.2.GA\server\default\log 10:14:51,402 INFO [Server] Server Temp Dir: C:\java\common\bin\jboss-4.2.2.GA\server\default\tmp 10:14:51,402 INFO [Server] Root Deployment Filename: jboss-service.xml 10:14:53,215 INFO [ServerInfo] Java version: 1.5.0_04,Sun Microsystems Inc. 10:14:53,215 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_04-b05,Sun Microsystems Inc. 10:14:53,215 INFO [ServerInfo] OS-System: Windows 2000 5.0,x86 10:14:54,965 INFO [Server] Core system initialized 10:15:01,310 INFO [ServiceBindingManager] Initializing store 10:15:01,310 INFO [ServiceBindingManager] Using StoreURL: file:/C:/java/common/bin/jboss-4.2.2.GA/server/default/conf/binding-manager.xml 10:15:06,185 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8183/ 10:15:06,185 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml 10:15:12,624 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. 10:15:12,624 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 10:15:13,687 INFO [TransactionManagerService] Starting recovery manager 10:15:14,390 INFO [TransactionManagerService] Recovery manager started 10:15:14,390 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference 10:15:16,531 ERROR [STDERR] Jan 7, 2009 10:15:16 AM com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init> WARNING: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: localhost; port: 3700" org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2257) at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2278) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:208) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:221) at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:104) at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:152) at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:146) at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:286) at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112) at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69) at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:89) at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:128) at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:380) at javax.naming.InitialContext.rebind(InitialContext.java:367) at com.arjuna.ats.jta.utils.JNDIManager.bindJTATransactionSynchronizationRegistryImplementation(JNDIManager.java:157) at com.arjuna.ats.jta.utils.JNDIManager.bindJTATransactionSynchronizationRegistryImplementation(JNDIManager.java:141) at com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService(TransactionManagerService.java:206) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor5.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.GeneratedMethodAccessor10.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:508) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused: connect at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:336) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:191) ... 61 more Caused by: java.net.ConnectException: Connection refused: connect at sun.nio.ch.Net.connect(Native Method) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:464) at java.nio.channels.SocketChannel.open(SocketChannel.java:146) at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:320) ... 62 more 10:15:17,609 ERROR [STDERR] Jan 7, 2009 10:15:17 AM com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init> WARNING: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: localhost; port: 3700" org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2257) at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2278) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:208) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:221) at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:104) at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:152) at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:146) at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:286) at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112) at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69) at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:89) at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:128) at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:380) at javax.naming.InitialContext.rebind(InitialContext.java:367) at com.arjuna.ats.jta.utils.JNDIManager.bindJTATransactionSynchronizationRegistryImplementation(JNDIManager.java:157) at com.arjuna.ats.jta.utils.JNDIManager.bindJTATransactionSynchronizationRegistryImplementation(JNDIManager.java:141) at com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService(TransactionManagerService.java:206) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor5.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.GeneratedMethodAccessor10.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:508) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused: connect at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:336) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:191) ... 61 more Caused by: java.net.ConnectException: Connection refused: connect at sun.nio.ch.Net.connect(Native Method) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:464) at java.nio.channels.SocketChannel.open(SocketChannel.java:146) at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:320) ... 62 more

jbossjta-properties.xml in C:\java\common\bin\jboss-4.2.2.GA\server\default\conf:
<?xml version="1.0" encoding="UTF-8"?> <transaction-service> <properties depends="common" name="arjuna"> <!-- Transaction Reaper Timeout (default is 120000 ms). --> <property name="com.arjuna.ats.arjuna.coordinator.txReaperTimeout" value="120000"/> <!-- Transaction Reaper Mode, can be: NORMAL or DYNAMIC (default is NORMAL). --> <property name="com.arjuna.ats.arjuna.coordinator.txReaperMode" value="DYNAMIC"/> <!-- (default is NO) --> <property name="com.arjuna.ats.arjuna.coordinator.asyncCommit" value="NO"/> <!-- (default is NO) --> <property name="com.arjuna.ats.arjuna.coordinator.asyncPrepare" value="NO"/> <!-- (default is YES) --> <property name="com.arjuna.ats.arjuna.coordinator.commitOnePhase" value="YES"/> <!-- (default is defaultStore) --> <property name="com.arjuna.ats.arjuna.objectstore.localOSRoot" value="defaultStore"/> <!-- default is under user.home - must be writeable!) --> <property name="com.arjuna.ats.arjuna.objectstore.objectStoreDir" value="PutObjectStoreDirHere"/> <!-- (default is ON) --> <property name="com.arjuna.ats.arjuna.objectstore.objectStoreSync" value="ON"/> <!-- (default is ShadowNoFileLockStore) --> <property name="com.arjuna.ats.arjuna.objectstore.objectStoreType" value="ShadowNoFileLockStore"/> <!-- (default is 255) --> <property name="com.arjuna.ats.arjuna.objectstore.hashedDirectories" value="255"/> <!-- (default is ON) --> <property name="com.arjuna.ats.arjuna.objectstore.transactionSync" value="ON"/> <!-- (Must be unique across all Arjuna instances.) --> <property name="com.arjuna.ats.arjuna.xa.nodeIdentifier" value="1"/> <!-- property name="com.arjuna.ats.arjuna.coordinator.actionStore" value="HashedActionStore" value="JDBCActionStore" --> <!-- property name="com.arjuna.ats.arjuna.objectstore.jdbcTxDbAccess" value="JDBCAccess" --> <!-- property name="com.arjuna.ats.arjuna.objectstore.objectStoreType" value="ShadowNoFileLockStore" value="JDBCStore" --> <!-- property name="com.arjuna.ats.arjuna.objectstore.jdbcUserDbAccess" value="JDBCAccess" --> <!-- property name="com.arjuna.ats.arjuna.objectstore.jdbcPoolSizeInitial" value="1" --> <!-- property name="com.arjuna.ats.arjuna.objectstore.jdbcPoolSizeMaximum" value="1" --> <!-- property name="com.arjuna.ats.arjuna.objectstore.jdbcPoolPutConnections" value="false" --> <!-- property name="com.arjuna.ats.arjuna.internal.arjuna.objectstore.cacheStore.size" value="" --> <!-- property name="com.arjuna.ats.arjuna.internal.arjuna.objectstore.cacheStore.period" value="" --> <!-- The location for creating temporary files, e.g., Uids. Default is under user.home. IMPORTANT: make sure the directory is lockable, e.g., /tmp on Unix may not be! --> <!-- <property name="com.arjuna.ats.arjuna.common.varDir" value="var"/> --> </properties> <properties name="common"> <!-- CLF 2.0 properties --> <property name="com.arjuna.common.util.logging.DebugLevel" type="System" value="0x00000000"/> <property name="com.arjuna.common.util.logging.FacilityLevel" type="System" value="0xffffffff"/> <property name="com.arjuna.common.util.logging.VisibilityLevel" type="System" value="0xffffffff"/> <property name="com.arjuna.common.util.logger" type="System" value="log4j"/> </properties> <properties depends="arjuna" name="txoj"> <!-- (default is LockStore of installation - must be writeable!) --> <!-- <property name="com.arjuna.ats.txoj.lockstore.lockStoreDir" value="LockStore"/> --> <!-- (default is BasicLockStore) --> <property name="com.arjuna.ats.txoj.lockstore.lockStoreType" value="BasicLockStore"/> <!-- (default is NO) --> <property name="com.arjuna.ats.txoj.lockstore.multipleLockStore" value="NO"/> <!-- (default is YES) --> <property name="com.arjuna.ats.txoj.lockstore.singleLockStore" value="YES"/> <!-- (default is YES) --> <property name="com.arjuna.ats.txoj.lockstore.allowNestedLocking" value="YES"/> </properties> <properties depends="arjuna" name="jta"> <!-- Support subtransactions in the JTA layer? Default is NO. --> <property name="com.arjuna.ats.jta.supportSubtransactions" value="NO"/> <property name="com.arjuna.ats.jta.jtaTMImplementation" value="com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple"/> <!-- com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple --> <property name="com.arjuna.ats.jta.jtaUTImplementation" value="com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple"/> <!-- com.arjuna.ats.internal.jta.transaction.jts.UserTransactionImple --> </properties> <properties depends="arjuna,txoj,jta" name="recoverymanager"> <!-- Properties used only by the RecoveryManager. --> <!-- Periodic recovery settings. Time values in this section are in seconds. --> <!-- Interval in seconds between initiating the periodic recovery modules. Default is 120 seconds. --> <property name="com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod" value="120"/> <!-- Interval in seconds between first and second pass of periodic recovery. Default is 10 seconds. --> <property name="com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod" value="10"/> <!-- Periodic recovery modules to use. Invoked in sort-order of names. --> <property name="com.arjuna.ats.arjuna.recovery.recoveryExtension1" value="com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule"/> <property name="com.arjuna.ats.arjuna.recovery.recoveryExtension2" value="com.arjuna.ats.internal.txoj.recovery.TORecoveryModule"/> <property name="com.arjuna.ats.arjuna.recovery.recoveryExtension3" value="com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule"/> <!-- Expired entry removal --> <!-- Expiry scanners to use (order of invocation is random). Names must begin with "com.arjuna.ats.arjuna.recovery.expiryScanner" --> <property name="com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager" value="com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner"/> <!-- Interval, in hours, between running the expiry scanners. This can be quite long. The absolute value determines the interval - if the value is negative, the scan will NOT be run until after one interval has elapsed. If positive the first scan will be immediately after startup. Zero will prevent any scanning. Default = 12 = run immediately, then every 12 hours. --> <property name="com.arjuna.ats.arjuna.recovery.expiryScanInterval" value="12"/> <!-- Age, in hours, for removal of transaction status manager item. This should be longer than any ts-using process will remain running. Zero = Never removed. Default is 12. --> <property name="com.arjuna.ats.arjuna.recovery.transactionStatusManagerExpiryTime" value="12"/> <!-- Use this to fix the port on which the TransactionStatusManager listens, The default behaviour is to use any free port. --> <property name="com.arjuna.ats.arjuna.recovery.transactionStatusManagerPort" value="0"/> </properties> <properties depends="jta" name="jdbc"> <!-- property name="com.arjuna.ats.jdbc.isolationLevel" value="TRANSACTION_SERIALIZABLE"/> --> </properties> <properties depends="arjuna,txoj,jta" name="recoverymanager"> <property name="com.arjuna.ats.arjuna.recovery.recoveryPort" value="3800"/> </properties> </transaction-service>

jboss-service.xml

<?xml version="1.0" encoding="UTF-8"?> <!-- $Id: jboss-service.xml 62434 2007-04-19 21:22:50Z dimitris@jboss.org $ --> <!-- ===================================================================== --> <!-- JBoss Server Configuration --> <!-- ===================================================================== --> <server> <!-- Load all jars from the JBOSS_DIST/server/<config>/lib directory. This can be restricted to specific jars by specifying them in the archives attribute. --> <classpath codebase="${jboss.server.lib.url:lib}" archives="*"/> <!-- ==================================================================== --> <!-- JSR-77 Single JBoss Server Management Domain --> <!-- ==================================================================== --> <mbean code="org.jboss.management.j2ee.LocalJBossServerDomain" name="jboss.management.local:j2eeType=J2EEDomain,name=Manager"> <attribute name="MainDeployer">jboss.system:service=MainDeployer</attribute> <attribute name="SARDeployer">jboss.system:service=ServiceDeployer</attribute> <attribute name="EARDeployer">jboss.j2ee:service=EARDeployer</attribute> <attribute name="EJBDeployer">jboss.ejb:service=EJBDeployer</attribute> <attribute name="RARDeployer">jboss.jca:service=RARDeployer</attribute> <attribute name="CMDeployer">jboss.jca:service=ConnectionFactoryDeployer</attribute> <attribute name="WARDeployer">jboss.web:service=WebServer</attribute> <attribute name="CARDeployer">jboss.j2ee:service=ClientDeployer</attribute> <attribute name="MailService">jboss:service=Mail</attribute> <attribute name="JMSService">jboss.mq:service=DestinationManager</attribute> <attribute name="JNDIService">jboss:service=Naming</attribute> <attribute name="JTAService">jboss:service=TransactionManager</attribute> <attribute name="UserTransactionService">jboss:service=ClientUserTransaction</attribute> <attribute name="RMI_IIOPService">jboss:service=CorbaORB</attribute> </mbean> <!-- ==================================================================== --> <!-- XMBean Persistence --> <!-- ==================================================================== --> <mbean code="org.jboss.system.pm.AttributePersistenceService" name="jboss:service=AttributePersistenceService" xmbean-dd="resource:xmdesc/AttributePersistenceService-xmbean.xml"> <!-- the AttributePersistenceService is persistent, itself --> <!-- <attribute name="AttributePersistenceManagerClass">org.jboss.system.pm.XMLAttributePersistenceManager</attribute> <attribute name="AttributePersistenceManagerConfig"> <data-directory>data/xmbean-attrs</data-directory> </attribute> <attribute name="ApmDestroyOnServiceStop">false</attribute> <attribute name="VersionTag"></attribute> --> </mbean> <!-- ==================================================================== --> <!-- Thread Pool --> <!-- ==================================================================== --> <!-- A Thread pool service --> <mbean code="org.jboss.util.threadpool.BasicThreadPool" name="jboss.system:service=ThreadPool"> <attribute name="Name">JBoss System Threads</attribute> <attribute name="ThreadGroupName">System Threads</attribute> <!-- How long a thread will live without any tasks in MS --> <attribute name="KeepAliveTime">60000</attribute> <!-- The max number of threads in the pool --> <attribute name="MaximumPoolSize">10</attribute> <!-- The max number of tasks before the queue is full --> <attribute name="MaximumQueueSize">1000</attribute> <!-- The behavior of the pool when a task is added and the queue is full. abort - a RuntimeException is thrown run - the calling thread executes the task wait - the calling thread blocks until the queue has room discard - the task is silently discarded without being run discardOldest - check to see if a task is about to complete and enque the new task if possible, else run the task in the calling thread --> <attribute name="BlockingMode">run</attribute> </mbean> <!-- Preload all custom editors for VMs that don't use the thread context class loader when searching for PropertyEditors. Uncomment if your JDK 1.3.0 VM fails to find JBoss PropertyEditors. <mbean code="org.jboss.varia.property.PropertyEditorManagerService" name="jboss:type=Service,name=BootstrapEditors"> <attribute name="BootstrapEditors"> java.math.BigDecimal=org.jboss.util.propertyeditor.BigDecimalEditor java.lang.Boolean=org.jboss.util.propertyeditor.BooleanEditor java.lang.Class=org.jboss.util.propertyeditor.ClassEditor java.util.Date=org.jboss.util.propertyeditor.DateEditor java.io.File=org.jboss.util.propertyeditor.FileEditor java.net.InetAddress=org.jboss.util.propertyeditor.InetAddressEditor java.lang.Integer=org.jboss.util.propertyeditor.IntegerEditor javax.management.ObjectName=org.jboss.mx.util.propertyeditor.ObjectNameEditor java.util.Properties=org.jboss.util.propertyeditor.PropertiesEditor [Ljava.lang.String;=org.jboss.util.propertyeditor.StringArrayEditor java.net.URL=org.jboss.util.propertyeditor.URLEditor </attribute> </mbean> --> <!-- ==================================================================== --> <!-- Log4j Initialization --> <!-- ==================================================================== --> <mbean code="org.jboss.logging.Log4jService" name="jboss.system:type=Log4jService,service=Logging" xmbean-dd="resource:xmdesc/Log4jService-xmbean.xml"> <attribute name="ConfigurationURL">resource:jboss-log4j.xml</attribute> <!-- Set the org.apache.log4j.helpers.LogLog.setQuiteMode. As of log4j1.2.8 this needs to be set to avoid a possible deadlock on exception at the appender level. See bug#696819. --> <attribute name="Log4jQuietMode">true</attribute> <!-- How frequently in seconds the ConfigurationURL is checked for changes --> <attribute name="RefreshPeriod">60</attribute> </mbean> <!-- ==================================================================== --> <!-- Active Alarm Table --> <!-- ==================================================================== --> <!-- | The ActiveAlarmTable service is a simple JMX notification listener | that maintains a table with the received notifications (alarms). | The alarms can be acknowledged through the jmx or the web console. | Modify the SubscriptionList below to subscribe for any notification | in the system and treat it as an alarm. | The JMXNotificationAppender is a log4j Appender that can be configured | in log4j.xml, that trasforms logging events to JMX notification so they | can be fed back into the table. By storing the WARN or higher level logging | events you can have a quick view of important system faults. | | The following attributes may be set: | | MaxTableSize (default 1000) | - set an upper limit to the number of stored alarms | LogLevel (default DEBUG) | - the log level to use for received notification, can be set to NONE | ServerId (default jboss) | - used to construct unique alarm ids | SubscriptionList | - subscribe for the notifications to be stored in the table <mbean code="org.jboss.monitor.services.ActiveAlarmTable" name="jboss.monitor:service=ActiveAlarmTable"> <attribute name="SubscriptionList"> <subscription-list> <mbean name="jboss.monitor:*"> <notification type="jboss.alarm"/> <notification type="JBOSS_MONITOR_NOTIFICATION"/> </mbean> <mbean name="jboss.system:service=Logging,type=JMXNotificationAppender"/> </subscription-list> </attribute> </mbean> --> <!-- ==================================================================== --> <!-- JBoss RMI Classloader - only install when available --> <!-- ==================================================================== --> <mbean code="org.jboss.util.property.jmx.SystemPropertyClassValue" name="jboss.rmi:type=RMIClassLoader"> <attribute name="Property">java.rmi.server.RMIClassLoaderSpi</attribute> <attribute name="ClassName">org.jboss.system.JBossRMIClassLoader</attribute> </mbean> <!-- ==================================================================== --> <!-- Service Binding --> <!-- ==================================================================== --> <!-- Automatically activated when generatting the clustering environment --> <!-- @TESTSUITE_CLUSTER_CONFIG@ --> | Binding service manager for port/host mapping. This is a sample | config that demonstrates a JBoss instances with a server name 'ports-01' | loading its bindings from an XML file using the ServicesStoreFactory | implementation returned by the XMLServicesStoreFactory. | | ServerName: The unique name assigned to a JBoss server instance for | lookup purposes. This allows a single ServicesStore to handle mulitiple | JBoss servers. | | StoreURL: The URL string passed to org.jboss.services.binding.ServicesStore | during initialization that specifies how to connect to the bindings store. | StoreFactory: The org.jboss.services.binding.ServicesStoreFactory interface | implementation to create to obtain the ServicesStore instance. <mbean code="org.jboss.services.binding.ServiceBindingManager" name="jboss.system:service=ServiceBindingManager"> <attribute name="ServerName">ports-01</attribute> <!--attribute name="StoreURL">${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml</attribute--> <attribute name="StoreURL">${jboss.server.base.dir}/${jboss.server.name}/conf/binding-manager.xml</attribute> <attribute name="StoreFactoryClassName"> org.jboss.services.binding.XMLServicesStoreFactory </attribute> </mbean> <!-- ==================================================================== --> <!-- Class Loading --> <!-- ==================================================================== --> <!-- A mini webserver used for dynamic and class and resource loading --> <mbean code="org.jboss.web.WebService" name="jboss:service=WebService"> <!-- The Bind address and Port --> <attribute name="BindAddress">${jboss.bind.address}</attribute> <attribute name="Port">18083</attribute> <!-- The address to use for the host portion of the RMI codebase URL --> <attribute name="Host">${java.rmi.server.hostname}</attribute> <!-- Should non-EJB .class files be downloadable --> <attribute name="DownloadServerClasses">true</attribute> <!-- Should resources other than .class files be downloadable. Both DownloadServerClasses and DownloadResources must be true for resources to be downloadable. This is false by default because its generally a bad idea as server configuration files that container security information can be accessed. --> <attribute name="DownloadResources">false</attribute> <!-- Use the default thread pool for dynamic class loading --> <depends optional-attribute-name="ThreadPool" proxy-type="attribute">jboss.system:service=ThreadPool</depends> </mbean> <!-- ==================================================================== --> <!-- JNDI --> <!-- ==================================================================== --> <!-- A simple mbean wrapper around the jndi Naming object. This only handles an in memory instance. The NamingService uses this as the JNDI store and exposes it remotely. --> <mbean code="org.jnp.server.NamingBeanImpl" name="jboss:service=NamingBeanImpl" xmbean-dd="resource:xmdesc/NamingBean-xmbean.xml"> </mbean> <mbean code="org.jboss.naming.NamingService" name="jboss:service=Naming" xmbean-dd="resource:xmdesc/NamingService-xmbean.xml"> <!-- The call by value mode. true if all lookups are unmarshalled using the caller's TCL, false if in VM lookups return the value by reference. --> <attribute name="CallByValue">false</attribute> <!-- The listening port for the bootstrap JNP service. Set this to -1 to run the NamingService without the JNP invoker listening port. --> <attribute name="Port">11099</attribute> <!-- The bootstrap JNP server bind address. This also sets the default RMI service bind address. Empty == all addresses --> <attribute name="BindAddress">${jboss.bind.address}</attribute> <!-- The port of the RMI naming service, 0 == anonymous --> <attribute name="RmiPort">1098</attribute> <!-- The RMI service bind address. Empty == all addresses --> <attribute name="RmiBindAddress">${jboss.bind.address}</attribute> <!-- The thread pool service used to control the bootstrap lookups --> <depends optional-attribute-name="LookupPool" proxy-type="attribute">jboss.system:service=ThreadPool</depends> <!-- An example of using the unifed invoker as the transport. <depends optional-attribute-name="InvokerProxyFactory" proxy-type="attribute">jboss:service=proxyFactory,type=unified,target=Naming</depends> --> <depends optional-attribute-name="Naming" proxy-type="attribute">jboss:service=NamingBeanImpl</depends> </mbean> <mbean code="org.jboss.naming.JNDIView" name="jboss:service=JNDIView" xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml"> <!-- The HANamingService service name --> <attribute name="HANamingService">jboss:service=HAJNDI</attribute> </mbean> <!-- ==================================================================== --> <!-- Security --> <!-- ==================================================================== --> <mbean code="org.jboss.security.plugins.SecurityConfig" name="jboss.security:service=SecurityConfig"> <attribute name="LoginConfig">jboss.security:service=XMLLoginConfig</attribute> </mbean> <mbean code="org.jboss.security.auth.login.XMLLoginConfig" name="jboss.security:service=XMLLoginConfig"> <attribute name="ConfigResource">login-config.xml</attribute> </mbean> <!-- JAAS security manager and realm mapping --> <mbean code="org.jboss.security.plugins.JaasSecurityManagerService" name="jboss.security:service=JaasSecurityManager"> <!-- A flag which indicates whether the SecurityAssociation server mode is set on service creation. This is true by default since the SecurityAssociation should be thread local for multi-threaded server operation. --> <attribute name="ServerMode">true</attribute> <attribute name="SecurityManagerClassName">org.jboss.security.plugins.JaasSecurityManager</attribute> <attribute name="DefaultUnauthenticatedPrincipal">anonymous</attribute> <!-- DefaultCacheTimeout: Specifies the default timed cache policy timeout in seconds. If you want to disable caching of security credentials, set this to 0 to force authentication to occur every time. This has no affect if the AuthenticationCacheJndiName has been changed from the default value. --> <attribute name="DefaultCacheTimeout">1800</attribute> <!-- DefaultCacheResolution: Specifies the default timed cache policy resolution in seconds. This controls the interval at which the cache current timestamp is updated and should be less than the DefaultCacheTimeout in order for the timeout to be meaningful. This has no affect if the AuthenticationCacheJndiName has been changed from the default value. --> <attribute name="DefaultCacheResolution">60</attribute> <!-- DeepCopySubjectMode: This set the copy mode of subjects done by the security managers to be deep copies that makes copies of the subject principals and credentials if they are cloneable. It should be set to true if subject include mutable content that can be corrupted when multiple threads have the same identity and cache flushes/logout clearing the subject in one thread results in subject references affecting other threads. --> <attribute name="DeepCopySubjectMode">false</attribute> </mbean> <!-- ==================================================================== --> <!-- Transactions --> <!-- ==================================================================== --> <!-- The configurable Xid factory. For use with Oracle, set pad to true --> <mbean code="org.jboss.tm.XidFactory" name="jboss:service=XidFactory"> <!--attribute name="Pad">true</attribute--> </mbean> <!-- | The fast in-memory transaction manager. | Deprecated in JBossAS v4.2. Use JBossTS JTA instead. - -> <mbean code="org.jboss.tm.TransactionManagerService" name="jboss:service=TransactionManager" xmbean-dd="resource:xmdesc/TransactionManagerService-xmbean.xml"> <attribute name="TransactionTimeout">300</attribute> <!- - set to false to disable transaction demarcation over IIOP - -> <attribute name="GlobalIdsEnabled">true</attribute> <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends> <!- - Transaction Integrity Checking - -> <!- - Force a rollback if another thread is associated with the transaction at commit - -> <!- - <depends optional-attribute-name="TransactionIntegrityFactory" proxy-type="org.jboss.tm.integrity.TransactionIntegrityFactory"> <mbean code="org.jboss.tm.integrity.FailIncompleteTransaction" name="jboss:service=TransactionManager,plugin=TransactionIntegrity"/> </depends> - -> </mbean> --> <!-- JBoss Transactions JTA --> <mbean code="com.arjuna.ats.jbossatx.jta.TransactionManagerService" name="jboss:service=TransactionManager"> <attribute name="TransactionTimeout">300</attribute> <attribute name="ObjectStoreDir">${jboss.server.data.dir}/tx-object-store</attribute> </mbean> <!-- | UserTransaction support. --> <mbean code="org.jboss.tm.usertx.server.ClientUserTransactionService" name="jboss:service=ClientUserTransaction" xmbean-dd="resource:xmdesc/ClientUserTransaction-xmbean.xml"> <depends> <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory" name="jboss:service=proxyFactory,target=ClientUserTransactionFactory"> <attribute name="InvokerName">jboss:service=invoker,type=jrmp</attribute> <attribute name="TargetName">jboss:service=ClientUserTransaction</attribute> <attribute name="JndiName">UserTransactionSessionFactory</attribute> <attribute name="ExportedInterface">org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory</attribute> <attribute name="ClientInterceptors"> <interceptors> <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor> <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor> </interceptors> </attribute> <depends>jboss:service=invoker,type=jrmp</depends> </mbean> </depends> <depends optional-attribute-name="TxProxyName"> <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory" name="jboss:service=proxyFactory,target=ClientUserTransaction"> <attribute name="InvokerName">jboss:service=invoker,type=jrmp</attribute> <attribute name="TargetName">jboss:service=ClientUserTransaction</attribute> <attribute name="JndiName"></attribute> <attribute name="ExportedInterface">org.jboss.tm.usertx.interfaces.UserTransactionSession</attribute> <attribute name="ClientInterceptors"> <interceptors> <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor> <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor> </interceptors> </attribute> <depends>jboss:service=invoker,type=jrmp</depends> </mbean> </depends> </mbean> <!-- ==================================================================== --> <!-- Invokers to the JMX node --> <!-- ==================================================================== --> <!-- Unified invoker (based on remoting) --> <mbean code="org.jboss.invocation.unified.server.UnifiedInvoker" name="jboss:service=invoker,type=unified"> <!-- To turn on strict RMI exception propagation uncomment block below --> <!-- This will cause the UnifiedInvokerProxy to wrap RemoteExceptions --> <!-- within a ServerException, otherwise will throw root exception --> <!-- (not RemoteException) --> <!-- <attribute name="StrictRMIException">true</attribute> --> <depends>jboss:service=TransactionManager</depends> <depends>jboss.remoting:service=Connector,transport=socket</depends> </mbean> <!-- RMI/JRMP invoker --> <mbean code="org.jboss.invocation.jrmp.server.JRMPInvoker" name="jboss:service=invoker,type=jrmp"> <attribute name="RMIObjectPort">14444</attribute> <attribute name="ServerAddress">${jboss.bind.address}</attribute> <!-- <attribute name="RMIClientSocketFactory">custom</attribute> <attribute name="RMIServerSocketFactory">custom</attribute> <attribute name="RMIServerSocketAddr">custom</attribute> <attribute name="SecurityDomain">ssl-domain-name</attribute> --> <depends>jboss:service=TransactionManager</depends> </mbean> <mbean code="org.jboss.invocation.local.LocalInvoker" name="jboss:service=invoker,type=local"> <depends>jboss:service=TransactionManager</depends> </mbean> <mbean code="org.jboss.invocation.pooled.server.PooledInvoker" name="jboss:service=invoker,type=pooled"> <attribute name="NumAcceptThreads">1</attribute> <attribute name="MaxPoolSize">300</attribute> <attribute name="ClientMaxPoolSize">300</attribute> <attribute name="SocketTimeout">60000</attribute> <attribute name="ServerBindAddress">${jboss.bind.address}</attribute> <attribute name="ServerBindPort">4445</attribute> <attribute name="ClientConnectAddress">${jboss.bind.address}</attribute> <attribute name="ClientConnectPort">0</attribute> <attribute name="ClientRetryCount">1</attribute> <attribute name="EnableTcpNoDelay">false</attribute> <!-- Customized socket factory attributes <attribute name="ClientSocketFactoryName">custom.client.factory</attribute> <attribute name="ServerSocketFactoryName">custom.server.factory</attribute> <attribute name="SslDomain">java:/jaas/pooledInvoker</attribute> --> <depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager</depends> </mbean> <!-- ==================================================================== --> <!-- Remoting services --> <!-- ==================================================================== --> <!-- For detailed description of all these configuration attributes, please see the --> <!-- JBoss Remoting User's Guide or wiki (http://labs.jboss.com/portal/jbossremoting/docs/guide/index.html) --> <!-- The NetworkRegistry contains all the local and remote --> <!-- servers that it recognizes. The remote ones registered --> <!-- are dependant on the detectors running and which domains --> <!-- they are configured to identify. --> <mbean code="org.jboss.remoting.network.NetworkRegistry" name="jboss.remoting:service=NetworkRegistry"/> <!-- The Connector is the core component of the remoting server service. --> <!-- It binds the remoting invoker (transport protocol, callback configuration, --> <!-- data marshalling, etc.) with the invocation handlers. --> <mbean code="org.jboss.remoting.transport.Connector" name="jboss.remoting:service=Connector,transport=socket" display-name="Socket transport Connector"> <!-- Can either just specify the InvokerLocator attribute and not the invoker element in the --> <!-- Configuration attribute, or do the full invoker configuration in the in invoker element --> <!-- of the Configuration attribute. --> <!-- Remember that if you do use more than one param on the uri, will have to include as a CDATA, --> <!-- otherwise, parser will complain. --> <!-- <attribute name="InvokerLocator"><![CDATA[socket://${jboss.bind.address}:4446/?datatype=invocation]]></attribute> --> <attribute name="Configuration"> <!-- Using the following <invoker> element instead of the InvokerLocator above because specific attributes needed. --> <!-- If wanted to use any of the parameters below, can just add them as parameters to the url above if wanted use the InvokerLocator attribute. --> <config> <!-- Other than transport type and handler, none of these configurations are required (will just use defaults). --> <invoker transport="socket"> <attribute name="dataType" isParam="true">invocation</attribute> <attribute name="marshaller" isParam="true">org.jboss.invocation.unified.marshall.InvocationMarshaller</attribute> <attribute name="unmarshaller" isParam="true">org.jboss.invocation.unified.marshall.InvocationUnMarshaller</attribute> <!-- This will be port on which the marshall loader port runs on. --> <!-- <attribute name="loaderport" isParam="true">4447</attribute> --> <!-- The following are specific to socket invoker --> <!-- <attribute name="numAcceptThreads">1</attribute>--> <!-- <attribute name="maxPoolSize">303</attribute>--> <!-- <attribute name="clientMaxPoolSize" isParam="true">304</attribute>--> <attribute name="socketTimeout" isParam="true">600000</attribute> <attribute name="serverBindAddress">${jboss.bind.address}</attribute> <attribute name="serverBindPort">4446</attribute> <!-- <attribute name="clientConnectAddress">216.23.33.2</attribute> --> <!-- <attribute name="clientConnectPort">7777</attribute> --> <attribute name="enableTcpNoDelay" isParam="true">true</attribute> <!-- <attribute name="backlog">200</attribute>--> <!-- The following is for callback configuration and is independant of invoker type --> <!-- <attribute name="callbackMemCeiling">30</attribute>--> <!-- indicates callback store by fully qualified class name --> <!-- <attribute name="callbackStore">org.jboss.remoting.CallbackStore</attribute>--> <!-- indicates callback store by object name --> <!-- <attribute name="callbackStore">jboss.remoting:service=CallbackStore,type=Serializable</attribute> --> <!-- config params for callback store. if were declaring callback store via object name, --> <!-- could have specified these config params there. --> <!-- StoreFilePath indicates to which directory to write the callback objects. --> <!-- The default value is the property value of 'jboss.server.data.dir' and if this is not set, --> <!-- then will be 'data'. Will then append 'remoting' and the callback client's session id. --> <!-- An example would be 'data\remoting\5c4o05l-9jijyx-e5b6xyph-1-e5b6xyph-2'. --> <!-- <attribute name="StoreFilePath">callback</attribute>--> <!-- StoreFileSuffix indicates the file suffix to use for the callback objects written to disk. --> <!-- The default value for file suffix is 'ser'. --> <!-- <attribute name="StoreFileSuffix">cst</attribute>--> </invoker> <!-- At least one handler is required by the connector. If have more than one, must decalre --> <!-- different subsystem values. Otherwise, all invocations will be routed to the only one --> <!-- that is declared. --> <handlers> <!-- can also specify handler by fully qualified classname --> <handler subsystem="invoker">jboss:service=invoker,type=unified</handler> </handlers> </config> </attribute> <depends>jboss.remoting:service=NetworkRegistry</depends> </mbean> <!-- <mbean code="org.jboss.remoting.detection.jndi.JNDIDetector"--> <!-- name="jboss.remoting:service=Detector,transport=jndi">--> <!-- host to which the detector will connect to for the JNDI server. --> <!-- <attribute name="Host">localhost</attribute>--> <!-- port to which detector will connect to for the JNDI server. --> <!-- <attribute name="Port">5555</attribute>--> <!-- context factory string used when connecting to the JNDI server. --> <!-- The default is org.jnp.interfaces.NamingContextFactory. --> <!-- <attribute name="ContextFactory">org.acme.NamingContextFactory</attribute> --> <!-- url package string to use when connecting to the JNDI server. --> <!-- The default is org.jboss.naming:org.jnp.interfaces. --> <!-- <attribute name="URLPackage">org.acme.naming</attribute> --> <!-- Sets the number of detection iterations before manually pinging --> <!-- remote server to make sure still alive. This is needed since remote server --> <!-- could crash and yet still have an entry in the JNDI server, --> <!-- thus making it appear that it is still there. The default value is 5. --> <!-- <attribute name="CleanDetectionNumber">20</attribute>--> <!-- Specifies the domains in which the detector will recognize --> <!-- detections. If servers are not configured to be in these --> <!-- domains, they will not be added to NetworkRegistry. --> <!-- <attribute name="Configuration">--> <!-- <domains>--> <!-- <domain>roxanne</domain>--> <!-- <domain>sparky</domain>--> <!-- </domains>--> <!-- </attribute>--> <!-- </mbean>--> <!-- ==================================================================== --> <!-- Monitoring and Management --> <!-- ==================================================================== --> <!-- Uncomment to enable JMX monitoring of the bean cache <mbean code="org.jboss.monitor.BeanCacheMonitor" name="jboss.monitor:name=BeanCacheMonitor"/> --> <!-- Uncomment to enable JMX monitoring of the entity bean locking <mbean code="org.jboss.monitor.EntityLockMonitor" name="jboss.monitor:name=EntityLockMonitor"/> --> <!-- ==================================================================== --> <!-- An MBean that is a registry for JDBC type-mapping metadata --> <!-- ==================================================================== --> <mbean code="org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary" name="jboss.jdbc:service=metadata"/> <!-- ==================================================================== --> <!-- Deployment Scanning --> <!-- ==================================================================== --> <!-- An mbean for hot deployment/undeployment of archives. --> <mbean code="org.jboss.deployment.scanner.URLDeploymentScanner" name="jboss.deployment:type=DeploymentScanner,flavor=URL"> <!-- Uncomment (and comment/remove version below) to enable usage of the DeploymentCache <depends optional-attribute-name="Deployer">jboss.deployment:type=DeploymentCache</depends> --> <depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depends> <!-- The URLComparator can be used to specify a deployment ordering for deployments found in a scanned directory. The class specified must be an implementation of java.util.Comparator, it must be able to compare two URL objects, and it must have a no-arg constructor. Two deployment comparators are shipped with JBoss: - org.jboss.deployment.DeploymentSorter Sorts by file extension, as follows: "sar", "service.xml", "rar", "jar", "war", "wsr", "ear", "zip", "*" - org.jboss.deployment.scanner.PrefixDeploymentSorter If the name portion of the url begins with 1 or more digits, those digits are converted to an int (ignoring leading zeroes), and files are deployed in that order. Files that do not start with any digits will be deployed first, and they will be sorted by extension as above with DeploymentSorter. --> <attribute name="URLComparator">org.jboss.deployment.DeploymentSorter</attribute> <!-- <attribute name="URLComparator">org.jboss.deployment.scanner.PrefixDeploymentSorter</attribute> --> <!-- The FilterInstance specifies a URLLister.URLFilter for scanned directories. This DeploymentFilter is initialized with the given prefixes, suffixes and matches that define which URLs should be ignored. --> <attribute name="FilterInstance" attributeClass="org.jboss.deployment.scanner.DeploymentFilter" serialDataType="javaBean"> <!-- Files starting with theses strings are ignored --> <property name="prefixes">#,%,\,,.,_$</property> <!-- Files ending with theses strings are ignored --> <property name="suffixes">#,$,%,~,\,v,.BAK,.bak,.old,.orig,.tmp,.rej,.sh</property> <!-- Files matching with theses strings are ignored --> <property name="matches">.make.state,.nse_depinfo,CVS,CVS.admin,RCS,RCSLOG,SCCS,TAGS,core,tags</property> </attribute> <!-- Frequency in milliseconds to rescan the URLs for changes --> <attribute name="ScanPeriod">5000</attribute> <!-- A flag to disable the scans --> <attribute name="ScanEnabled">true</attribute> <!-- URLs are comma separated and resolve relative to the server home URL unless the given path is absolute. If the URL ends in "/" it is considered a collection and scanned, otherwise it is simply deployed; this follows RFC2518 convention and allows discrimination between collections and directories that are simply unpacked archives. URLs may be local (file:) or remote (http:). Scanning is supported for remote URLs but unpacked deployment units are not. Example URLs: deploy/ scans ${jboss.server.url}/deploy/, which is local or remote depending on the URL used to boot the server ${jboss.server.home}/deploy/ scans ${jboss.server.home)/deploy, which is always local file:/var/opt/myapp.ear deploy myapp.ear from a local location file:/var/opt/apps/ scans the specified directory http://www.test.com/netboot/myapp.ear deploys myapp.ear from a remote location http://www.test.com/netboot/apps/ scans the specified WebDAV location --> <attribute name="URLs"> deploy/ </attribute> <!-- Indicates if the scanner should recursively scan directories that contain no "." in their names. This can be used to group applications and services that must be deployed and that have the same logical function in the same directory i.e. deploy/JMX/ deploy/JMS/ ... --> <attribute name="RecursiveSearch">True</attribute> </mbean> </server>

I am getting the same exception, even though I have followed your suggestion of adding the recoverymanager in jboss-4.2.2.GA\server\default\conf\jbossjta-properties.xml

<properties depends="arjuna,txoj,jta" name="recoverymanager"> <property name="com.arjuna.ats.arjuna.recovery.recoveryPort" value="3800"/> </properties>

svchost.exe:420 TCP 0.0.0.0:135 0.0.0.0:0 LISTENING System:8 TCP 0.0.0.0:445 0.0.0.0:0 LISTENING System:8 UDP 0.0.0.0:445 *:* lsass.exe:232 UDP 0.0.0.0:1028 *:* mstask.exe:780 TCP 0.0.0.0:1039 0.0.0.0:0 LISTENING winlogon.exe:192 UDP 0.0.0.0:1045 *:* OUTLOOK.EXE:1316 UDP 0.0.0.0:1156 *:* soeagent.exe:1172 TCP 0.0.0.0:2021 0.0.0.0:0 LISTENING SndServ.exe:824 TCP 0.0.0.0:5001 0.0.0.0:0 LISTENING winvnc.exe:920 TCP 0.0.0.0:5900 0.0.0.0:0 LISTENING FrameworkServic:560 TCP 0.0.0.0:18081 0.0.0.0:0 LISTENING FrameworkServic:560 UDP 0.0.0.0:18081 *:* FrameworkServic:560 UDP 0.0.0.0:18082 *:* IEXPLORE.EXE:1936 UDP 127.0.0.1:1247 *:* IEXPLORE.EXE:2352 UDP 127.0.0.1:3178 *:* IEXPLORE.EXE:832 UDP 127.0.0.1:4012 *:* System:8 UDP 127.0.0.1:137 *:* System:8 UDP 127.0.0.1:138 *:* System:8 TCP 127.0.0.1:139 0.0.0.0:0 LISTENING lsass.exe:232 UDP 127.0.0.1:500 *:* System:8 TCP 127.0.0.1:1108 127.0.0.1:445 ESTABLISHED System:8 TCP 127.0.0.1:1114 127.0.0.1:445 ESTABLISHED OUTLOOK.EXE:1316 TCP 127.0.0.1:1158 127.0.0.1:1384 ESTABLISHED winscp413.exe:2088 TCP 127.0.0.1:1239 127.0.0.1:22 ESTABLISHED winscp413.exe:1488 TCP 127.0.0.1:1245 127.0.0.1:22 ESTABLISHED winscp413.exe:2088 TCP 127.0.0.1:1327 127.0.0.1:22 ESTABLISHED <non-existent>:308 TCP 127.0.0.1:1336 127.0.0.1:22 CLOSE_WAIT putty.exe:2276 TCP 127.0.0.1:1357 127.0.0.1:22 ESTABLISHED OUTLOOK.EXE:1316 TCP 127.0.0.1:1362 127.0.0.1:1314 ESTABLISHED winscp413.exe:1488 TCP 127.0.0.1:1467 127.0.0.1:22 ESTABLISHED winscp413.exe:1488 TCP 127.0.0.1:1535 127.0.0.1:22 ESTABLISHED putty.exe:2308 TCP 127.0.0.1:1553 127.0.0.1:22 ESTABLISHED OUTLOOK.EXE:1316 TCP 127.0.0.1:2674 127.0.0.1:1025 ESTABLISHED winscp413.exe:2088 TCP 127.0.0.1:2783 127.0.0.1:22 ESTABLISHED putty.exe:2952 TCP 127.0.0.1:4069 127.0.0.1:22 ESTABLISHED putty.exe:2964 TCP 127.0.0.1:4248 127.0.0.1:22 ESTABLISHED [System Process]:0 TCP 127.0.0.1:4306 127.0.0.1:135 TIME_WAIT [System Process]:0 TCP 127.0.0.1:4307 127.0.0.1:1025 TIME_WAIT [System Process]:0 TCP 127.0.0.1:4310 127.0.0.1:4308 TIME_WAIT IEXPLORE.EXE:1936 TCP 127.0.0.1:4319 127.0.0.1:443 CLOSE_WAIT OUTLOOK.EXE:1316 TCP 127.0.0.1:4320 127.0.0.1:1384 ESTABLISHED lsass.exe:232 UDP 127.0.0.1:4500 *:*

Hi Jaikiran,

Thanks for your reply. I have followed the below steps and try to run the server in port 01, but unfortunately I am getting the same error.

http://blog.techstacks.com/2009/01/changing-default-port-numbers-in-jboss.html
Changing Default Port Numbers in JBoss AS 4.x Port number assignments in JBoss application server 4.0 can be managed through the use of the Bindings Manager. The JBoss Bindings Manager can be loaded as part of jboss-service.xml for your server instance. For the example in this article, I will use the jboss-service.xml from the "default" server instance. Remove the comments surrounding the Binding Manager configuration from your server's jboss-service.xml so that the following is displayed: <mbean code="org.jboss.services.binding.ServiceBindingManager" name="jboss.system:service=ServiceBindingManager"> <attribute name="ServerName">ports-01</attribute> <attribute name="StoreURL">${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml</attribute> <attribute name="StoreFactoryClassName"> org.jboss.services.binding.XMLServicesStoreFactory </attribute> </mbean> Note that the ServerName parameter is utilizing ports-01. Note also that the StoreURL parameter is presently pointing to a sample configuration file. Open that file up in your editor now. This file contains four port configuration sections. Each port is incremented by 100 from the previous set of ports. For example, the default ajp port is 8009. The port number assigned to this set in the ports-01 configuration is 8109, the number assigned in the ports-02 configuration is 8209, etc. The default http port is 8080. This is set to 8180 in the ports-01 configuration, 8280 in the ports-02 configuration—you get the idea. Save this file to your server's conf directory as binding-manager.xml(same location as jboss-service.xml). You do not need to make any changes to this file for this example. Modify your server instance's jboss-service.xml file and change the StoreURL configuration in the binding manager section from: ${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xmlto: ${jboss.server.base.dir}/${jboss.server.name}/conf/binding-manager.xml Start up your server and it is now listening on the set of ports from the ports-01 section of the binding-manager.xml file. If you are running JBoss on Windows, depending upon the service wrapper you are using, you might have to delete the service and re-create it. I've seen some service wrappers (like the one that ships with some versions of Covalent Enterprise Ready Server for tomcat) that does not re-read configuration updates unless the service is removed and re-installed.

20:32:59,536 INFO [Server] Starting JBoss (MX MicroKernel)... 20:32:59,536 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139) 20:32:59,536 INFO [Server] Home Dir: C:\java\common\bin\jboss-4.2.2.GA 20:32:59,582 INFO [Server] Home URL: file:/C:/java/common/bin/jboss-4.2.2.GA/ 20:32:59,582 INFO [Server] Patch URL: null 20:32:59,582 INFO [Server] Server Name: default 20:32:59,582 INFO [Server] Server Home Dir: C:\java\common\bin\jboss-4.2.2.GA\server\default 20:32:59,582 INFO [Server] Server Home URL: file:/C:/java/common/bin/jboss-4.2.2.GA/server/default/ 20:32:59,582 INFO [Server] Server Log Dir: C:\java\common\bin\jboss-4.2.2.GA\server\default\log 20:32:59,582 INFO [Server] Server Temp Dir: C:\java\common\bin\jboss-4.2.2.GA\server\default\tmp 20:32:59,582 INFO [Server] Root Deployment Filename: jboss-service.xml 20:33:00,614 INFO [ServerInfo] Java version: 1.5.0_04,Sun Microsystems Inc. 20:33:00,614 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_04-b05,Sun Microsystems Inc. 20:33:00,614 INFO [ServerInfo] OS-System: Windows 2000 5.0,x86 20:33:01,880 INFO [Server] Core system initialized[b] 20:33:05,645 INFO [ServiceBindingManager] Initializing store 20:33:05,645 INFO [ServiceBindingManager] Using StoreURL: file:/C:/java/common/bin/jboss-4.2.2.GA/server/default/conf/binding-manager.xml 20:33:10,583 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8183/[/b] 20:33:10,614 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml 20:33:15,240 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. 20:33:15,240 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 20:33:16,177 INFO [TransactionManagerService] Starting recovery manager 20:33:16,771 INFO [TransactionManagerService] Recovery manager started 20:33:16,771 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference 20:33:18,677 ERROR [STDERR] Jan 5, 2009 8:33:18 PM com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init> WARNING: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: localhost; port: 3700" org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2257) at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2278) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:208) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:221) at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:104) at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:152) at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:146) at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:286) at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112) at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69) at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:89) at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:128) at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:380) at javax.naming.InitialContext.rebind(InitialContext.java:367) at com.arjuna.ats.jta.utils.JNDIManager.bindJTATransactionSynchronizationRegistryImplementation(JNDIManager.java:157) at com.arjuna.ats.jta.utils.JNDIManager.bindJTATransactionSynchronizationRegistryImplementation(JNDIManager.java:141) at com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService(TransactionManagerService.java:206) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor5.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.GeneratedMethodAccessor10.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:508) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused: connect at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:336) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:191) ... 61 more Caused by: java.net.ConnectException: Connection refused: connect at sun.nio.ch.Net.connect(Native Method) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:464) at java.nio.channels.SocketChannel.open(SocketChannel.java:146) at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:320) ... 62 more

Hi all,

I have a general query. I just want to know if i am having an application which is using EJB2.1 and want it to change it to EJB 3.0, how much impact will be in terms of code change and other factors?

I am facing the problem while statring the JBoss server 4.2.2.GA in Windows 2000. The problem is, in the port number 1099, some other application is running, which I am suspecting the JBoss is also using for JNDI. So I am getting the following error: I couldn't stop the application that is already running in the port number 1099.
14:29:33,159 INFO [Server] Starting JBoss (MX MicroKernel)... 14:29:33,206 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139) 14:29:33,237 INFO [Server] Home Dir: C:\java\common\bin\jboss-4.2.2.GA 14:29:33,237 INFO [Server] Home URL: file:/C:/java/common/bin/jboss-4.2.2.GA/ 14:29:33,237 INFO [Server] Patch URL: null 14:29:33,237 INFO [Server] Server Name: default 14:29:33,237 INFO [Server] Server Home Dir: C:\java\common\bin\jboss-4.2.2.GA\server\default 14:29:33,237 INFO [Server] Server Home URL: file:/C:/java/common/bin/jboss-4.2.2.GA/server/default/ 14:29:33,237 INFO [Server] Server Log Dir: C:\java\common\bin\jboss-4.2.2.GA\server\default\log 14:29:33,237 INFO [Server] Server Temp Dir: C:\java\common\bin\jboss-4.2.2.GA\server\default\tmp 14:29:33,253 INFO [Server] Root Deployment Filename: jboss-service.xml 14:29:34,315 INFO [ServerInfo] Java version: 1.5.0_04,Sun Microsystems Inc. 14:29:34,315 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_04-b05,Sun Microsystems Inc. 14:29:34,315 INFO [ServerInfo] OS-System: Windows 2000 5.0,x86 14:29:35,581 INFO [Server] Core system initialized 14:29:42,504 INFO [WebService] Using RMI server codebase: <a href="http://127.0.0.1:8083/" target="_blank" rel="nofollow">http://127.0.0.1:8083/</a> 14:29:42,535 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml 14:29:46,676 ERROR [Naming] Could not start on port 1099 java.net.BindException: Address already in use: JVM_Bind at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) at java.net.ServerSocket.bind(ServerSocket.java:319) at java.net.ServerSocket.<init>(ServerSocket.java:185) at javax.net.DefaultServerSocketFactory.createServerSocket(ServerSocketFactory.java:169) at org.jnp.server.Main.initBootstrapListener(Main.java:371) at org.jnp.server.Main.start(Main.java:321) at org.jboss.naming.NamingService.startService(NamingService.java:284) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) 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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at org.jboss.system.ServiceController.start(ServiceController.java:435) 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.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:508) at java.lang.Thread.run(Thread.java:595) 14:29:47,223 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. 14:29:47,223 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 14:29:48,176 INFO [TransactionManagerService] Starting recovery manager

So I have edited the jboss-service.xml file in the following location:
C:\java\common\bin\jboss-4.2.2.GA\server\default\conf\jboss-service.xml

I have changed the JNDI port number from 1099 to 11099 as follows:
<mbean code="org.jboss.naming.NamingService" name="jboss:service=Naming" xmbean-dd="resource:xmdesc/NamingService-xmbean.xml"> <!-- The call by value mode. true if all lookups are unmarshalled using the caller's TCL, false if in VM lookups return the value by reference. --> <attribute name="CallByValue">false</attribute> <!-- The listening port for the bootstrap JNP service. Set this to -1 to run the NamingService without the JNP invoker listening port. --> [B] <attribute name="Port">11099</attribute>[/B] <!-- The bootstrap JNP server bind address. This also sets the default RMI service bind address. Empty == all addresses --> <attribute name="BindAddress">${jboss.bind.address}</attribute> <!-- The port of the RMI naming service, 0 == anonymous --> <attribute name="RmiPort">1098</attribute> <!-- The RMI service bind address. Empty == all addresses --> <attribute name="RmiBindAddress">${jboss.bind.address}</attribute> <!-- The thread pool service used to control the bootstrap lookups --> <depends optional-attribute-name="LookupPool" proxy-type="attribute">jboss.system:service=ThreadPool</depends> <!-- An example of using the unifed invoker as the transport. <depends optional-attribute-name="InvokerProxyFactory" proxy-type="attribute">jboss:service=proxyFactory,type=unified,target=Naming</depends> --> <depends optional-attribute-name="Naming" proxy-type="attribute">jboss:service=NamingBeanImpl</depends> </mbean>

But I am getting some other error:
14:32:21,790 INFO [Server] Starting JBoss (MX MicroKernel)... 14:32:21,852 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139) 14:32:21,852 INFO [Server] Home Dir: C:\java\common\bin\jboss-4.2.2.GA 14:32:21,884 INFO [Server] Home URL: file:/C:/java/common/bin/jboss-4.2.2.GA/ 14:32:21,884 INFO [Server] Patch URL: null 14:32:21,884 INFO [Server] Server Name: default 14:32:21,884 INFO [Server] Server Home Dir: C:\java\common\bin\jboss-4.2.2.GA\server\default 14:32:21,884 INFO [Server] Server Home URL: file:/C:/java/common/bin/jboss-4.2.2.GA/server/default/ 14:32:21,884 INFO [Server] Server Log Dir: C:\java\common\bin\jboss-4.2.2.GA\server\default\log 14:32:21,884 INFO [Server] Server Temp Dir: C:\java\common\bin\jboss-4.2.2.GA\server\default\tmp 14:32:21,884 INFO [Server] Root Deployment Filename: jboss-service.xml 14:32:22,899 INFO [ServerInfo] Java version: 1.5.0_04,Sun Microsystems Inc. 14:32:22,899 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_04-b05,Sun Microsystems Inc. 14:32:22,899 INFO [ServerInfo] OS-System: Windows 2000 5.0,x86 14:32:24,103 INFO [Server] Core system initialized 14:32:31,057 INFO [WebService] Using RMI server codebase: <a href="http://127.0.0.1:8083/" target="_blank" rel="nofollow">http://127.0.0.1:8083/</a> 14:32:31,088 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml 14:32:35,964 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. 14:32:35,964 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 14:32:36,917 INFO [TransactionManagerService] Starting recovery manager 14:32:37,464 INFO [TransactionManagerService] Recovery manager started 14:32:37,464 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference 14:32:39,198 ERROR [STDERR] Jan 2, 2009 2:32:39 PM com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init> WARNING: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: localhost; port: 3700" org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2257) at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2278) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:208) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:221) at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:104) at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:152) at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:146) at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:286) at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112) at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69) at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:89) at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:128) at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:380) at javax.naming.InitialContext.rebind(InitialContext.java:367) at com.arjuna.ats.jta.utils.JNDIManager.bindJTATransactionSynchronizationRegistryImplementation(JNDIManager.java:157) at com.arjuna.ats.jta.utils.JNDIManager.bindJTATransactionSynchronizationRegistryImplementation(JNDIManager.java:141) at com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService(TransactionManagerService.java:206) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor4.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:508) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused: connect at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:336) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:191) ... 61 more Caused by: java.net.ConnectException: Connection refused: connect at sun.nio.ch.Net.connect(Native Method) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:464) at java.nio.channels.SocketChannel.open(SocketChannel.java:146) at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:320) ... 62 more 14:32:40,355 ERROR [STDERR] Jan 2, 2009 2:32:40 PM com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init> WARNING: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: localhost; port: 3700" org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2257) at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2278) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:208) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:221) at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:104) at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:152) at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:146) at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:286) at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112) at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69) at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:89) at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:128) at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:380) at javax.naming.InitialContext.rebind(InitialContext.java:367) at com.arjuna.ats.jta.utils.JNDIManager.bindJTATransactionSynchronizationRegistryImplementation(JNDIManager.java:157) at com.arjuna.ats.jta.utils.JNDIManager.bindJTATransactionSynchronizationRegistryImplementation(JNDIManager.java:141) at com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService(TransactionManagerService.java:206) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor4.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:508) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused: connect at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:336) at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:191) ... 61 more Caused by: java.net.ConnectException: Connection refused: connect at sun.nio.ch.Net.connect(Native Method) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:464) at java.nio.channels.SocketChannel.open(SocketChannel.java:146) at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:320) ... 62 more

Please help on this. My JDK is at:C:\java\common\bin\jdk1.5

C:\Documents and Settings\john01>netstat -na Active Connections Proto Local Address TCP 0.0.0.0:135 TCP 0.0.0.0:445 TCP 0.0.0.0:1039 TCP 0.0.0.0:2021 TCP 0.0.0.0:5001 TCP 0.0.0.0:5900 TCP 0.0.0.0:18081 TCP 127.0.0.1:139 [B]TCP 127.0.0.1:1099[/B] TCP 127.0.0.1:1105 TCP 127.0.0.1:1203 TCP 127.0.0.1:1308 TCP 127.0.0.1:1372 TCP 127.0.0.1:1373 TCP 127.0.0.1:1380 TCP 127.0.0.1:1387 TCP 127.0.0.1:1388 TCP 127.0.0.1:1389 TCP 127.0.0.1:1397 TCP 127.0.0.1:1591 TCP 127.0.0.1:1593 TCP 127.0.0.1:1607 TCP 127.0.0.1:1610 TCP 127.0.0.1:1630 TCP 127.0.0.1:1677 TCP 127.0.0.1:1680 TCP 127.0.0.1:1708 TCP 127.0.0.1:1753 TCP 127.0.0.1:2280 TCP 127.0.0.1:3973 UDP 0.0.0.0:445 UDP 0.0.0.0:1028 UDP 0.0.0.0:1044 UDP 0.0.0.0:1219 UDP 0.0.0.0:1395 UDP 0.0.0.0:3705 UDP 0.0.0.0:3729 UDP 0.0.0.0:18081 UDP 0.0.0.0:18082 UDP 127.0.0.1:1095 UDP 127.0.0.1:1204 UDP 127.0.0.1:1246 UDP 127.0.0.1:1439 UDP 127.0.0.1:3689 UDP 127.0.0.1:3721 UDP 127.0.0.1:3959 UDP 127.0.0.1:4644 UDP 127.0.0.1:4686 UDP 127.0.0.1:4996 UDP 127.0.0.1:137 UDP 127.0.0.1:138 UDP 127.0.0.1:500 UDP 127.0.0.1:4500
[ January 02, 2009: Message edited by: Micheal John ]

Thanks Bear Bibeault & Henry Wong. This is the thing/answer I have looked for. I think I have posted the question like difference between app & web server. Thanks for interperting properly.

I have missed the term "Dual Level" setup..

Hi seetharaman,

webserver=you can deploy jsp/servlet project //you can not deploy ejb related project[example:Apache]

ApplicationServer=webserver=you can deploy jsp/servlet+ejb project[example:jboss]

I know this. I think you are not getting my question.

I am having a general doubt. Generally what is the necsessity of using both web server and app server?.
for example:
Browser --> Web Server --> Application Server --> DB

As far as my knowledge, we can use web server for generating a dynami pages and application server for exposing the business logic.
(Just for differentiating both, though app server has providing more features).

Since app server is subset of web server and whatever we can do it in web server, can be done at app server. Then in which scenario/situation we have to use both web server and app server.?

I am facing a problem with double byte values (Kanji, Kana Characters - Japenese). I have an application which fetches the double byte values from db and displaying it in jsp page. While dislpaying in the jsp, all the kana and kanji are displaying properly. I need to download the csv(excel) of whatever we displaying in the jsp. While opening the csv, I am getting the question marks(?) in the place of kana and kanji characters. I have tried with setting the content type to UTF-8.

response.setContentType("text/html;UTF-8");
response.setCharacterEncoding("SJIS");

But nothing is working. I am wondering how it's being displaying properly in the JSP page with only setting the content type as UTF-8 charset, but not in the excel. Whether I am missing anything? Please help to throw some light on it.

response.setContentType("text/html;"); response.setCharacterEncoding("SJIS"); response.setHeader("Content-Disposition","attachment; filename=StReport.xls"); PrintWriter pw= response.getWriter(); pw.print("\t" + getValueFromDB()); // getValueFromDB() returns kanji/kana characters pw.close();
[ July 29, 2008: Message edited by: Micheal John ]

Congrats!!

I am planning to write web service exam and started reading monson haefel web service book and reached upto JAX-RPC chapter. Before proceeding further, i need to know whether my understanding is right?

Please correct me if something/my understanding is wrong? My aim is not only to clear the exam, but need to understand concept well. I need to lay a good foundation.

As a web service provider: (for example: service for adding two numbers) 1. Write an interface. 2. Write an implementation for that interface. 3. Using some tools/GUI (JAX-RPC compiler) generate the WSDL from the implementation 4. Post the WSDL in public place like UDDI registry for client access.

As a client: 1. Get the required WSDL from the UDDI registry. 2. Using some tools/GUI(JAX-RPC compiler) generate the endpoint interface, stub (which will implement the endpoint interface) and service from the WSDL 3. Write a client to access the web service. 4. A call to the stub will initiate a SOAP request to the endpoint interface and the endpoint interface will send back the SOAP reposne to the client.