Trying to create a JMS Client in LifeCycle Module. Sun Appserver 8

I have created a Lifecycle module which initializes a set of JMX Beans. One of them is a JMX Client.
I have created a JMS Queue Connection factory according to the guidelines and associated a JNDI name jms/TrQueueConnectionFactory.
I have created a destination of type Queue with JNDI name jms/catalogQueue.
When the code is trying to make get the reference to the queue connection factory, I encounter the following exception
NamingException
javax.naming.CommunicationException: serial context communication ex [Root exception is com.sun.enterprise.resource.PoolingException]
     at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:328)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.i2.catalog.services.request.BRR.startJmsConnection(BRR.java:662)
     at com.i2.catalog.services.request.BRR.startService(BRR.java:514)
     at com.i2.catalog.base.ServiceMBeanSupport.start(ServiceMBeanSupport.java:387)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
     at com.i2.catalog.base.ServiceManager.start(ServiceManager.java:347)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
     at com.i2.catalog.boot.CatalogController.start(CatalogController.java:401)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
     at com.i2.catalog.boot.Bootstrap.start(Bootstrap.java:188)
     at com.transora.im.startup.SunAppServerStartup.initialize(SunAppServerStartup.java:164)
     at com.transora.im.startup.SunAppServerStartup.handleEvent(SunAppServerStartup.java:98)
     at com.sun.appserv.server.ServerLifecycleModule.postEvent(ServerLifecycleModule.java:192)
     at com.sun.appserv.server.ServerLifecycleModule.onStartup(ServerLifecycleModule.java:234)
     at com.sun.appserv.server.LifecycleModuleService.onStartup(LifecycleModuleService.java:194)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:300)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:294)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.enterprise.resource.PoolingException
     at com.sun.enterprise.connectors.AdministeredObjectResource.createAdministeredObject(AdministeredObjectResource.java:143)
     at com.sun.enterprise.naming.factory.AdministeredObjectFactory.getObjectInstance(AdministeredObjectFactory.java:67)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301)
     at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:304)
     ... 39 more
Caused by: java.security.PrivilegedActionException: com.sun.enterprise.connectors.ConnectorRuntimeException
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.enterprise.connectors.AdministeredObjectResource.createAdministeredObject(AdministeredObjectResource.java:139)
     ... 42 more
Caused by: com.sun.enterprise.connectors.ConnectorRuntimeException
     at com.sun.enterprise.connectors.util.SetMethodAction.handleException(SetMethodAction.java:110)
     at com.sun.enterprise.connectors.util.SetMethodAction.run(SetMethodAction.java:96)
     ... 44 more
Caused by: java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.connectors.util.SetMethodAction.run(SetMethodAction.java:69)
     ... 44 more
Caused by: java.lang.IllegalArgumentException: MQ:Queue:Invalid Queue Name -
     at com.sun.messaging.Queue.setName(Queue.java:64)
     ... 49 more
It seems that there is a security issue. Is there any entry I need to have in the sever.policy to make it happen.
Note: I have defined jdbc datasource for oracle and the jmx services are able to access the datasource via JNDI lookup
Your help and direction is deeply appreciated.
Thanks in advance,
Chiths

As I know, the lifecycle module is just an external RMI client that has your lifecycle controled by container.
Please, correct me if I am wrong, but there is no way to access JMS or Datasource via external RMI clients.

Similar Messages

How to create a WEB client in EJB module in NB 4.1 ?

hi
I am using SUN AS and NB 4.1
I want to invoke a WS from an EJB. For some reason NB 4.1 doesn't allow me to create a WS client. Why ?

netbeans forum may prove to be more useful because
this seems to be a netbeans specific problem; an EJB
can be a WS client and this works as is evident with
the Adventure Builder sample app from blueprintsI generated WS stub manually without NB 4.1.

Exception trying to Create a Thick Client Application

JRCViewReport.java throws exception running as Java Application:
Crystal Reports-Berichtsviewer 11.8.0.671
java.vendor = Sun Microsystems Inc.
java.version = 1.5.0_09
os.name = Windows 2000
os.version = 5.0
os.arch = x86
Exception in thread "Command" java.lang.NoSuchMethodError: com.businessobjects.crystalreports.viewer.applet.ViewerUI.clearMessage()V
at com.businessobjects.crystalreports.viewer.applet.h.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
What is missing?

Hopefully the following kbase article will solve your issue:
http://technicalsupport.businessobjects.com/KanisaSupportSite/search.do?cmd=displayKC&docType=kc&externalId=c2018313&sliceId=&dialogID=7454883&stateId=1 0 7456062
-MJ

Stub j2ee.jar to jms-client.jar?

I'd like to be able to run a JMS client w/ only those j2ee.jar classes relevant to a JMS client. The j2ee.jar file is about 8 MB and contains everything under the sun. It would be nice to have a JMS client jar file under 500 KB that contains only those classes relevant to a JMS client.
Has anyone tried to create a jms-client.jar from the j2ee.jar that contains only the necessary classes to run a JMS client?
thanks

I was able to create a 1.1 MB jar file that can run my JMS client.
First I ran my JMSClient with the -verbose:gc option against the j2ee.jar. With a simple java app I parsed the loaded classes list, copied all these classes to a temp dir and then created the jar file.

Create a JMS reference to a IBM MQ Resource Adapter

Hi There,
We have deployed the IBM MQ RA (version 7.0.0.0-k000-L080529) on our CE 7.1 SP 4 system. We are trying to create a JMS reference to utilise the RA to put a message on an IBM MQ Queue.
We are trying to get to the RA using the following code snippet but can not get the relevant JMS / JNDI references with the activation config created:
String lookupName = "java:QCF1"; //or something similair
ConnectionFactory cf = (ConnectionFactory) context.lookup(lookupName);
We have tried the XML below but the references it creates comes up in error status.
<?xml version="1.0" encoding="UTF-8"?>
<jms-resources xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="jms-resources.xsd">
 <connection-factory>
 <name>QCF1</name>
 <context-factory-type>
 <initial-context-properties>
 <initial-context-factory>com.sap.engine.services.jndi.InitialContextFactoryImpl
 
 </initial-context-factory>
 <provider-url>localhost</provider-url>
 <security-principal>user</security-principal>
 <security-credentials>password</security-credentials>
 </initial-context-properties>
 <link-factory-name>deployedAdapters/QueueConnectionFactory/nonGlobalTx/QueueConnectionFactory</link-factory-name>
 <user-name>jms-user-name</user-name>
 <password>jms-password</password>
 <library-name>IBMMQ</library-name>
 </context-factory-type>
 </connection-factory>
 <destination>
 <name>TargetQueue</name>
 <type>javax.jms.Queue</type>
 <external-destination-type>
 <link-connection-factory>QCF1
 
 </link-connection-factory>
 </external-destination-type>
 </destination>

Hi There,
We have deployed the IBM MQ RA (version 7.0.0.0-k000-L080529) on our CE 7.1 SP 4 system. We are trying to create a JMS reference to utilise the RA to put a message on an IBM MQ Queue.
We are trying to get to the RA using the following code snippet but can not get the relevant JMS / JNDI references with the activation config created:
String lookupName = "java:QCF1"; //or something similair
ConnectionFactory cf = (ConnectionFactory) context.lookup(lookupName);
We have tried the XML below but the references it creates comes up in error status.
<?xml version="1.0" encoding="UTF-8"?>
<jms-resources xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="jms-resources.xsd">
 <connection-factory>
 <name>QCF1</name>
 <context-factory-type>
 <initial-context-properties>
 <initial-context-factory>com.sap.engine.services.jndi.InitialContextFactoryImpl
 
 </initial-context-factory>
 <provider-url>localhost</provider-url>
 <security-principal>user</security-principal>
 <security-credentials>password</security-credentials>
 </initial-context-properties>
 <link-factory-name>deployedAdapters/QueueConnectionFactory/nonGlobalTx/QueueConnectionFactory</link-factory-name>
 <user-name>jms-user-name</user-name>
 <password>jms-password</password>
 <library-name>IBMMQ</library-name>
 </context-factory-type>
 </connection-factory>
 <destination>
 <name>TargetQueue</name>
 <type>javax.jms.Queue</type>
 <external-destination-type>
 <link-connection-factory>QCF1
 
 </link-connection-factory>
 </external-destination-type>
 </destination>

Unable to connect jms client to stcms in JCAPS62 using admin\adminadmin

I'm trying a simple java jms client to STCMS in jcaps62 but getting exception
javax.jms.JMSSecurityException: Access denied by server. Check userid and password.
at com.stc.jms.sockets.ProxyStcms.newSession(ProxyStcms.java:271)
The following is my code snippet:
Properties p = new Properties();
               p.put(InitialContext.INITIAL_CONTEXT_FACTORY,
                         "com.stc.jms.jndispi.InitialContextFactory");
               p.put(InitialContext.PROVIDER_URL, "stcms://localhost:18007");
               p.put(InitialContext.SECURITY_PRINCIPAL, "admin");
               p.put(InitialContext.SECURITY_CREDENTIALS, "adminadmin");
               p.put("com.stc.jms.jndispi.disconnected", "true");
               InitialContext ctx = new InitialContext(p);
               QueueConnectionFactory fact = (STCQueueConnectionFactory) ctx.lookup("connectionfactories/queueconnectionfactory");
               Connection conn = fact.createConnection();
               Session session = (Session) conn.createSession(false, Session.AUTO_ACKNOWLEDGE);
Could any one throw some light on this
Note: I have tried encrypting "adminadmin" and pass it, but no luck.

yes it is working with in collaboration etc., with in GF and working when removed security for stcms. But here is it, I could able to connect to it through JMSJCA rar.

JMS Client Program

Hi,
I'm trying to run my JMS Client program to post a message to XI JMS Queue.
But I'm getting the following exception... java.lang.ClassCastException
at QueueConnectionFactory.
Also tried to catch the name of the returned class name...
com.sap.engine.services.jndi.persistent.UnsatisfiedReferenceImpl
Can anyone has an idea what could be the possible solution?
Any help is highly appreciated.
Here are the details...
SAP_NAMING_PROVIDER_URL = localhost:50204 (50200 being J2EE port)
SAP_INITIAL_CONTEXT_FACTORY_IMPL = "com.sap.engine.services.jndi.InitialContextFactoryImpl"
QueueConnectionFactory queueConnectionFactory =(QueueConnectionFactory) jndiContext.lookup("jmsfactory/default/QueueConnectionFactory")
Queue queue = (Queue) jndiContext.lookup(
"jmsqueues/default/MyTestQueue")
Thanks and Regards,
Vijay

Hi Archana,
The link isn't working and giving a message as..."Error: Session expired!"
By the way my code is an extract of the one that is available at... <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/44/efec3341ad67d8e10000000a155369/frameset.htm">help.sap.com</a>
If you think this is different to the one that you intend to send, can you please send me the correct one?
Thanks and Regards,
Vijay Kalyan

Cannot create more JMS connection

Hi,
I got the following error:
WARNING: RAR5117 : Failed to obtain/create connection from connection pool [ jms/batchExecutorMDBConnectionFactoryPool ]. Reason : com.sun.appserv.connectors.internal.api.PoolingException: In-use connections equal max-pool-size and expired max-wait-time. Cannot allocate more connections.I have cleared all messages in the queue, redeployed my application. But somehow the connections still existed in the connection pool and therefore i always see this error appearing whenever i re-launch my application.
I created JMS connection locally and close it immediately after sending message as suggested out there to avoid connection leaking.
Could you help me how to clear all connections in order to re-run my application. Then slowly i can find out where the connection leaking is?
I am using glassfish 3.1.2 with the setting 500 maximum connection in the jms connection factory
thanks,
-CM

CardM wrote:
Could you help me how to clear all connections in order to re-run my application. Then slowly i can find out where the connection leaking is?
I am using glassfish 3.1.2 with the setting 500 maximum connection in the jms connection factoryErrr, reboot the server?
Glassfish questions should go in the glassfish forum: http://www.java.net/forums/glassfish/glassfish

JMS Client hangs while trying to create a TopicSession

We have a thick client which connects to a WLS 8.1 Sp3 server. At client startup, it subscribes to a distributed topic. Today morning, we noticed that most of the clients started hanging at the point where they try to subcribe to the distributed topic. We had to restart the servers to resolve this issue. I've pasted a part of the thread dump at the end of this message, and would appreciate any feedback on this.
 
 This happened on our test servers which run in a cluster, and which have a limited scale license. 
 Here's the thread dump - 
 "AWT-EventQueue-1" prio=7 tid=0x009e85d0 nid=0x7f8 in Object.wait() [190ef000..190efd88] 
 at java.lang.Object.wait(Native Method) 
 - waiting on <0x20217400> (a weblogic.rjvm.ResponseImpl) 
 at weblogic.rjvm.ResponseImpl.waitForData(ResponseImpl.java:74) 
 - locked <0x20217400> (a weblogic.rjvm.ResponseImpl) 
 at weblogic.rjvm.ResponseImpl.getTxContext(ResponseImpl.java:99) 
 at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:104) 
 at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:137) 
 at weblogic.jms.dispatcher.DispatcherImpl_813_WLStub.dispatchSyncFuture(Unknown Source) 
 at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSync(DispatcherWrapperState.java:339) 
 at weblogic.jms.client.JMSConnection.createSessionInternal(JMSConnection.java:400) 
 at weblogic.jms.client.JMSConnection.createTopicSession(JMSConnection.java:359) 
 at com.wellmanage.trading.shared.util.PmwMessageService.subscribe(PmwMessageService.java:373) 
 at com.wellmanage.fipmt.client.notification.NotificationListener.subscribeToNotificationMessages(NotificationListener.java:173) 
 at com.wellmanage.fipmt.client.Main$11.run(Main.java:1174) 
 at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178) 
 at java.awt.EventQueue.dispatchEvent(EventQueue.java:454) 
 at com.wellmanage.common.pcsf.client.exception.ExceptionHandlerEventQueue.dispatchEvent(ExceptionHandlerEventQueue.java:26) 
 at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201) 
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151) 
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145) 
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137) 
 at java.awt.EventDispatchThread.run(EventDispatchThread.java:100) 

Hello,
 Were you able to resolve your problem? How did you resolve it? I am having the same problem.
 Any help will be greatly appreciated!
 Thanks,
 Mamta

Error when trying to create Calendar Client GPO

I am trying to create a GPO in a Windows 2003 domain to deploy Oracle Calendar Client 10.1.2. I run cal_win_1012.exe /a and it installs the app in the specified network location (\\Server\Share\OracleCalendar\program files\Oracle\Calendar) and the 'Oracle Calendar.msi' file in this location. When i attempt to create a GPO with this MSI file, it gives the following error:
Add operation failed. Unable to extract deployment information from the package. Run validation on the package to ensure that the package is correct.
I am able to browse to the MSI file from a PC and run the installer, and it installs, i just cannot create a GPO with the MSI file. Any help is appreciated.

Might be an idea to search support.microsoft.com for the errormessage (or Google). Seems that you are not alone. Could be a bug in Windows and not in the package.
I see things like this http://support.microsoft.com/kb/324886

Trying to make jms client inside web service

Hi i am trying to make a jms call inside a webservice
but whenever i try to execute the web service it gives error with following url
http://localhost:8280/axis/services/WSTune?method=setTune&r=TUNE
i have deploy this service on jboss and code is working properly in normal java application
and i have also placed the jar files inside axis/web-inf/lib folder
soapenv:Envelope>
−
 <soapenv:Body>
−
 <soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>java.lang.reflect.InvocationTargetException</faultstring>
−
 <detail>
<ns1:hostname>linux</ns1:hostname>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>my code is following
package services;
import java.util.Properties;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.jms.Queue;
import javax.jms.Session;
import javax.jms.MapMessage;
import javax.jms.TextMessage;
import javax.jms.QueueSession;
import javax.jms.QueueRequestor;
import javax.jms.QueueConnection;
import javax.jms.QueueConnectionFactory;
import com.chetu.MyStream;
public class WSTune
 InitialContext ctx;
 Queue queue;
 String tunedata;
 String queueName;
 QueueConnectionFactory connFactory;
 String rid; // Request id
 public String setTune(String r)throws Exception
 rid=r;
 MyStream m=new MyStream();
 m.setData(new byte[]{'a','b'});
 System.out.println("Started WSTune");
 queueName = "queue/mytQueue";
 try {
 System.out.println("==> 1");
 Properties props = new Properties();
 System.out.println("==> 2");
 props.setProperty("java.naming.factory.initial","org.jnp.interfaces.NamingContextFactory");
 System.out.println("==> 3");
 props.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming");
 System.out.println("==> 4");
 props.setProperty("java.naming.provider.url", "127.0.0.1:1099");
 System.out.println("==> 5");
 ctx = new InitialContext(props);
 System.out.println("==> 6");
 } catch (NamingException e) {
 System.out.println("Could not create JNDI API " +
 "context: " + e.toString());
 System.exit(1);
 try {
 System.out.println("==> 7");
 Object tmp = ctx.lookup("ConnectionFactory");
 System.out.println("==> 8");
 System.out.println("lookup completed");
 connFactory = (QueueConnectionFactory)tmp;
 System.out.println("==> 9");
 queue = (Queue) ctx.lookup(queueName);
 System.out.println("==> 10");
 } catch (Exception e) {
 System.out.println("JNDI API lookup failed: " +
 e.toString());
 e.printStackTrace();
 System.exit(1);
 System.out.println("==> 11");
 QueueConnection queueConn = connFactory.createQueueConnection();
 /* queueConn.start();
 QueueSession queueSession = queueConn.createQueueSession(false,Session.DUPS_OK_ACKNOWLEDGE);
 QueueRequestor requestor = new QueueRequestor(queueSession, queue);
 MapMessage message = queueSession.createMapMessage();
 message.setString("ID",rid);
 message.setString("COMMAND","TUNE");
 TextMessage result = (TextMessage) requestor.request(message);
 message.clearBody();
 tunedata=result.getText();
 queueConn.close();*/
 System.out.println("==> 12");
 // return tunedata;
 return rid+" from the WS";
}and in tomcat log it is printing up to 7 numbers.
Thanks in advance however its very urgent

Hi Simon,
 Other thing you can do is compare the HTTP requests (including header) from both Delphi and XMLSPY. I suspect if the SOAP message is same in both case the difference might be in the header. But one thing is certain, WAS can not respond differently for same request, don't you think so ?
Cheers,
Sanjeev

Weblogic JMS Client App fails creating queue connection

Using the example provided from installation: ...\bea\wlserver_10.0\samples\server\examples\src\examples\jms\queue\QueueBrowse.java
I can successfully connect and display the queue when this test app runs on the local Weblogic Server. When I run the test app on a remote server (not the Weblogic server), I get the following error:
Exception in thread "main" weblogic.jms.common.JMSException: [JMSClientExceptions:055053]Error creating connection to the server: java.rmi.MarshalException: failed to marshal connectionCreateRequest(Lweblogic.jms.frontend.FEConnectionCreateRequest;); nested exception is:
 java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is:
 java.lang.NullPointerException
 at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:258)
 at weblogic.jms.client.JMSConnectionFactory.createConnectionInternal(JMSConnectionFactory.java:285)
 at weblogic.jms.client.JMSConnectionFactory.createQueueConnection(JMSConnectionFactory.java:165)
 at com.lodestarcorp.custom.QueueBrowse.init(QueueBrowse.java:53)
 at com.lodestarcorp.custom.QueueBrowse.main(QueueBrowse.java:129)
Caused by: java.rmi.MarshalException: failed to marshal connectionCreateRequest(Lweblogic.jms.frontend.FEConnectionCreateRequest;); nested exception is:
 java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is:
 java.lang.NullPointerException
 at weblogic.rjvm.BasicOutboundRequest.marshalArgs(BasicOutboundRequest.java:91)
 at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:332)
 at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
 at weblogic.jms.frontend.FEConnectionFactoryImpl_1001_WLStub.connectionCreateRequest(Unknown Source)
 at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:224)
 ... 4 more
Caused by: java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is:
 java.lang.NullPointerException
 at weblogic.rmi.internal.DescriptorManager.createRuntimeDescriptor(DescriptorManager.java:118)
 at weblogic.rmi.internal.DescriptorManager.getBasicRuntimeDescriptor(DescriptorManager.java:89)
 at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java:55)
 at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java:41)
 at weblogic.rmi.internal.OIDManager.makeServerReference(OIDManager.java:194)
 at weblogic.rmi.internal.OIDManager.getReplacement(OIDManager.java:175)
 at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceSmartStubInfo(RemoteObjectReplacer.java:116)
 at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceObject(RemoteObjectReplacer.java:102)
 at weblogic.rmi.utils.io.InteropObjectReplacer.replaceObject(InteropObjectReplacer.java:62)
 at weblogic.utils.io.ChunkedObjectOutputStream.replaceObject(ChunkedObjectOutputStream.java:40)
 at weblogic.utils.io.ChunkedObjectOutputStream$NestedObjectOutputStream.replaceObject(ChunkedObjectOutputStream.java:141)
 at java.io.ObjectOutputStream.writeObject0(Unknown Source)
 at java.io.ObjectOutputStream.writeObject(Unknown Source)
 at weblogic.messaging.dispatcher.DispatcherWrapper.writeExternal(DispatcherWrapper.java:152)
 at weblogic.jms.frontend.FEConnectionCreateRequest.writeExternal(FEConnectionCreateRequest.java:98)
 at java.io.ObjectOutputStream.writeExternalData(Unknown Source)
 at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)
 at java.io.ObjectOutputStream.writeObject0(Unknown Source)
 at java.io.ObjectOutputStream.writeObject(Unknown Source)
 at weblogic.rjvm.MsgAbbrevOutputStream.writeObject(MsgAbbrevOutputStream.java:614)
 at weblogic.rjvm.MsgAbbrevOutputStream.writeObjectWL(MsgAbbrevOutputStream.java:605)
 at weblogic.rmi.internal.ObjectIO.writeObject(ObjectIO.java:38)
 at weblogic.rjvm.BasicOutboundRequest.marshalArgs(BasicOutboundRequest.java:87)
 ... 8 more
Caused by: java.lang.NullPointerException
 at weblogic.rmi.internal.BasicRuntimeDescriptor.createSkeletonClass(BasicRuntimeDescriptor.java:272)
 at weblogic.rmi.internal.BasicRuntimeDescriptor.<init>(BasicRuntimeDescriptor.java:158)
 at weblogic.rmi.internal.BasicRuntimeDescriptor.<init>(BasicRuntimeDescriptor.java:140)
 at weblogic.rmi.internal.DescriptorManager.createRuntimeDescriptor(DescriptorManager.java:110)
 ... 30 more
FYI: I did create the wlfullclient.jar from the installation.
Could the problem be related to a proxy issue? It's not a DNS problem (I've tested with the IP address).
Thanks,
Brian

I had this very same issue, in a project I was importing directly individual jars:
 <classpathentry kind="lib" path="lib/javax.jms_1.1.1.jar"/>
 <classpathentry kind="lib" path="lib/weblogic.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.weblogic.security.identity_1.1.2.1.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.weblogic.workmanager_1.9.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.weblogic.workmanager.ja_1.9.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.transaction_2.7.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.weblogic.rmi.client.ja_1.8.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.weblogic.rmi.client_1.8.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.weblogic.security.wls_1.0.0.0_6-1-0-0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.utils.full_1.9.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.weblogic.security_1.0.0.0_6-1-0-0.jar"/>
 <classpathentry kind="lib" path="lib/wlclient.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.utils.classloaders_1.8.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.management.core_2.8.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.descriptor_1.9.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.logging_1.8.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.timers_1.7.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.weblogic.socket.api_1.2.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.weblogic.security.digest_1.0.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.weblogic.lifecycle_1.4.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.store_1.7.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.common.security.api_1.0.0.0_6-1-0-0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.utils.wrapper_1.4.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.messaging.kernel_1.8.0.0.jar"/>
 <classpathentry kind="lib" path="lib/com.bea.core.utils.expressions_1.4.0.0.jar"/>
and everything was working;
in another project I was importing the "Weblogic System Libraries" libraries, and I was getting the NullPointerException...
I have the sensation that there is room for improvement in the way libraries are managed.

I am not able to create a JMS connection from a custom component in UCM

I am trying to create a custom component which makes a JMS connection and inserts messages in JMS Queue.
THe JMS server is hosted on Weblogic Application Server.
When the code runs I am getting the factory object and the queue object.
But when I try to get a connection it throws an error as pasted below.
WHen I googled the same error It has shown a simliar problem in TOmcat in sun thread
It said two jar files xerces.jar and xml-apis.jar are obsolete.
I replaced with the new version.
still the same problem occurred
Please help
Pasting the code and exception here
Code __________________________________________
import java.util.Date;
import java.util.Hashtable;
import javax.jms.*;
import javax.naming.*;
import weblogic.jms.client.WLConnectionImpl;
import weblogic.jms.extensions.*;
import javax.rmi.PortableRemoteObject;
public class SimpleProducer {
public static void drive() {
final int NUM_MSGS;
 NUM_MSGS = 93;
Context jndiContext = null;
Hashtable<String, String> ht;
 ht = new Hashtable<String, String>();
 ht.put(Context.INITIAL_CONTEXT_FACTORY,
 "weblogic.jndi.WLInitialContextFactory");
 ht.put(Context.PROVIDER_URL, "t3://punitp52975d:7001");
try {
 jndiContext = new InitialContext(ht);
} catch (NamingException e) {
System.out.println("Could not create JNDI API context: " +
e.toString());
System.exit(1);
ConnectionFactory connectionFactory = null;
Destination dest = null;
try {
 Object home = jndiContext.lookup("CNFT"); // where iiopTestDS is jndi name for my DataSource.
connectionFactory =(ConnectionFactory)PortableRemoteObject.narrow(home , ConnectionFactory.class);
 Object home1 = jndiContext.lookup("QUEUE2"); // where iiopTestDS is jndi name for my DataSource.
dest =(Destination)PortableRemoteObject.narrow(home1 , Destination.class);
 /*connectionFactory = (ConnectionFactory) jndiContext.lookup(
"CNFT");
dest = (Destination) jndiContext.lookup("QUEUE2");
System.out.println("connectionFactory,dest "+connectionFactory+dest);*/
} catch (Exception e) {
System.out.println("JNDI API lookup failed: " + e.toString());
e.printStackTrace();
System.exit(1);
//WLConnectionImpl connection = null;
WLConnection connection = null;
WLMessageProducer producer = null;
try {
 System.out.println("Getting Connection "+(WLConnection) connectionFactory.createConnection());
//connection = (WLConnection) connectionFactory.createConnection();
 System.out.println("Connection created");
WLSession session =
(WLSession) connection.createSession(false, Session.CLIENT_ACKNOWLEDGE);
producer = (WLMessageProducer) session.createProducer(dest);
WLMessage message = (WLMessage) session.createTextMessage();
//TextMessage message = session.createTextMessage();
for (int i = 91; i < NUM_MSGS; i++) {
((TextMessage) message).setText("This is message " + (i + 1));
Long l = new Date().getTime();
message.setLongProperty("ReleasedDate",l );
System.out.println("Sending message: " + ((TextMessage) message).getText());
producer.send(message);
producer.send(session.createMessage());
} catch (Exception e) {
System.out.println("Exception occurred: " + e.toString());
} catch (Throwable et) {
System.out.println("Exception occurred: " + et.toString());
et.printStackTrace();
finally {
if (connection != null) {
try {
connection.close();
} catch (Exception e) {
 System.out.println("*************Instantiating Producer***************");
Exception_________________________________________________________________
Exception occurred: java.lang.NoSuchMethodError: javax.xml.parsers.SAXParserFactory.getSchema()Ljavax/xml/validation/Schema;
java.lang.NoSuchMethodError: javax.xml.parsers.SAXParserFactory.getSchema()Ljavax/xml/validation/Schema;
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.<init>(SAXParserImpl.java:124)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl.newSAXParserImpl(SAXParserFactoryImpl.java:115)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:143)
at weblogic.xml.jaxp.WebLogicSAXParserFactory.<init>(WebLogicSAXParserFactory.java:62)
at weblogic.rmi.internal.wls.WLSRMIEnvironment.getSAXParser(WLSRMIEnvironment.java:136)
at weblogic.rmi.internal.DescriptorManager.getDescriptorAsMap(DescriptorManager.java:170)
at weblogic.rmi.internal.DescriptorManager.getDescriptorAsMap(DescriptorManager.java:159)
at weblogic.rmi.internal.DescriptorManager.createRuntimeDescriptor(DescriptorManager.java:104)
at weblogic.rmi.internal.DescriptorManager.getBasicRuntimeDescriptor(DescriptorManager.java:85)
at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java:51)
at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java:37)
at weblogic.rmi.internal.OIDManager.makeServerReference(OIDManager.java:194)
at weblogic.rmi.internal.OIDManager.getReplacement(OIDManager.java:175)
at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceRemote(RemoteObjectReplacer.java:120)
at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceObject(RemoteObjectReplacer.java:103)
at weblogic.rmi.extensions.server.ServerHelper.exportObject(ServerHelper.java:223)
at weblogic.rmi.internal.OIDManager.initializeDGCServer(OIDManager.java:231)
at weblogic.rmi.internal.OIDManager.getReplacement(OIDManager.java:144)
at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceRemote(RemoteObjectReplacer.java:120)
at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceObject(RemoteObjectReplacer.java:103)
at weblogic.rmi.extensions.server.ServerHelper.exportObject(ServerHelper.java:223)
at weblogic.corba.server.naming.ReferenceHelperImpl.exportObject(ReferenceHelperImpl.java:233)
at weblogic.rmi.extensions.PortableRemoteObject.exportObject(PortableRemoteObject.java:34)
at weblogic.messaging.dispatcher.DispatcherImpl.export(DispatcherImpl.java:85)

This is probably related to this other issue http://www.adobeforums.com/webx/.59b7fbab/0.
Jasmin

Create a Secure Client for a Secure Web Service- is failing

Hi,
This is actually with reference to the webservice tutorial.I am trying the example on Create a Secure Client for a Secure Web Service and have followed all the steps mentioned,however I am getting the following error:
D:\JDev11gTp\jdk\bin\javaw.exe -client -classpath D:\Jdev11gTpInstance\mywork\WebServiceApplications\.adf;D:\Jdev11gTpInstance\mywork\WebServiceApplications\WebServiceProjects\classes;D:\JDev11gTp\webservices\lib\jaxws-api.jar;D:\JDev11gTp\webservices\lib\jws-api.jar;D:\JDev11gTp\webservices\lib\orawsmetadata.jar;D:\JDev11gTp\webservices\lib\wsclient.jar;D:\JDev11gTp\j2ee\home\lib\activation.jar;D:\JDev11gTp\j2ee\home\lib\ejb.jar;D:\JDev11gTp\j2ee\home\lib\jms.jar;D:\JDev11gTp\j2ee\home\lib\jta.jar;D:\JDev11gTp\j2ee\home\lib\mail.jar;D:\JDev11gTp\j2ee\home\lib\servlet.jar;D:\JDev11gTp\webservices\lib\jaxrpc-api.jar;D:\JDev11gTp\webservices\lib\wsserver.jar;D:\JDev11gTp\webservices\lib\wssecurity.jar;D:\JDev11gTp\webservices\lib\wsdl.jar;D:\JDev11gTp\webservices\lib\orasaaj.jar;D:\JDev11gTp\webservices\lib\saaj-api.jar;D:\JDev11gTp\webservices\lib\orawsdl.jar;D:\JDev11gTp\webservices\lib\orawsrm.jar;D:\JDev11gTp\webservices\lib\orawsrel.jar;D:\JDev11gTp\webservices\lib\jaxr-api.jar;D:\JDev11gTp\webservices\lib\orajaxr.jar;D:\JDev11gTp\webservices\lib\relaxngDatatype.jar;D:\JDev11gTp\webservices\lib\xsdlib.jar;D:\JDev11gTp\webservices\lib\mdds.jar;D:\JDev11gTp\webservices\lib\wsif.jar;D:\JDev11gTp\webservices\lib\fabric-common.jar;D:\JDev11gTp\webservices\lib\fabric-interceptors.jar;D:\JDev11gTp\jlib\jaxen.jar;D:\JDev11gTp\jlib\oraclepki.jar;D:\JDev11gTp\jlib\ojpse.jar;D:\JDev11gTp\jlib\jsr106.jar;D:\JDev11gTp\jlib\jsr105.jar;D:\JDev11gTp\jlib\osdt_xmlsec_jce.jar;D:\JDev11gTp\jlib\osdt_wss_jce.jar;D:\JDev11gTp\jlib\osdt_saml_jce.jar;D:\JDev11gTp\jlib\osdt_saml2_jce.jar;D:\JDev11gTp\jlib\osdt_core.jar;D:\JDev11gTp\jlib\osdt_cert.jar;D:\JDev11gTp\jlib\osdt_xmlsec.jar;D:\JDev11gTp\jlib\osdt_wss.jar;D:\JDev11gTp\jlib\osdt_saml.jar;D:\JDev11gTp\jlib\osdt_saml2.jar;D:\JDev11gTp\jlib\ojmisc.jar;D:\JDev11gTp\j2ee\home\lib\http_client.jar;D:\JDev11gTp\j2ee\home\jazncore.jar;D:\JDev11gTp\j2ee\home\oc4jclient.jar;D:\JDev11gTp\rdbms\jlib\xdb.jar;D:\JDev11gTp\j2ee\home\lib\javax77.jar;D:\JDev11gTp\lib\java\api\jsr173_api.jar;D:\JDev11gTp\lib\java\shared\sun.jaxb\2.0\jaxb-impl.jar;D:\JDev11gTp\lib\java\shared\sun.jaxb\2.0\jaxb-xjc.jar;D:\JDev11gTp\lib\java\shared\sun.jaxb\2.0\jaxb1-impl.jar;D:\JDev11gTp\j2ee\home\lib\oc4j-schemas.jar;D:\JDev11gTp\jlib\ojdl.jar;D:\JDev11gTp\jlib\ojdl2.jar;D:\JDev11gTp\jlib\fmw_audit.jar;D:\JDev11gTp\j2ee\home\lib\jmxri.jar;D:\JDev11gTp\j2ee\home\lib\jmx_remote_api.jar;D:\JDev11gTp\j2ee\home\lib\adminclient.jar;D:\JDev11gTp\j2ee\home\lib\jmxframework.jar;D:\JDev11gTp\j2ee\home\lib\jmxspi.jar;D:\JDev11gTp\j2ee\home\lib\xmlcfg.jar;D:\JDev11gTp\jlib\dms.jar;D:\JDev11gTp\jlib\orai18n.jar;D:\JDev11gTp\j2ee\home\lib\commons-digester.jar;D:\JDev11gTp\j2ee\home\lib\spring.jar;D:\JDev11gTp\lib\java\shared\oracle.wsm\11.1.1.0\wsm-policy-core.jar;D:\JDev11gTp\lib\java\shared\oracle.wsm\11.1.1.0\wsm-pmclient.jar;D:\JDev11gTp\lib\java\shared\oracle.wsm\11.1.1.0\wsm-pap.jar;D:\JDev11gTp\lib\java\shared\oracle.wsm\11.1.1.0\wsm-agent.jar;D:\JDev11gTp\lib\java\shared\oracle.wsm\11.1.1.0\wsm-secpol.jar;D:\JDev11gTp\lib\java\shared\oracle.javatools\11.1.1.0.0\javamodel-rt.jar;D:\JDev11gTp\lib\java\shared\oracle.javatools\11.1.1.0.0\javatools-nodeps.jar;D:\JDev11gTp\lib\java\shared\oracle.toplink\11.1.1.0.0\toplink-sdo.jar;D:\JDev11gTp\lib\java\api\jaxb-api.jar;D:\JDev11gTp\lib\xmlparserv2.jar;D:\JDev11gTp\lib\xml.jar;D:\JDev11gTp\jakarta-taglibs\commons-logging-1.0.3\commons-logging.jar -Dhttp.proxyHost=localhost -Dhttp.proxyPort=8099 -Dhttp.nonProxyHosts= -Dhttps.proxyHost=localhost -Dhttps.proxyPort=8099 -Dhttps.nonProxyHosts= HelloPolicyPortClient
Feb 1, 2008 5:13:43 PM oracle.j2ee.ws.common.context.ContextInterceptor init
INFO: Context provider properties file not found
Feb 1, 2008 5:13:44 PM oracle.wsm.audit.Auditor <init>
INFO: Created J2SE auditor for componentType=OWSM-AGENT busstop=D:\oracle\product\10.2.0\client_1\auditlogs\OWSM-AGENT filter=false auditor=oracle.security.audit.Auditor@143a083
Feb 1, 2008 5:13:44 PM oracle.wsm.audit.Auditor <init>
INFO: Created J2SE auditor for componentType=OWSM-PM-LIB busstop=D:\oracle\product\10.2.0\client_1\auditlogs\OWSM-PM-LIB filter=false auditor=oracle.security.audit.Auditor@15af049
SEVERE: WSM-04514 An MDS error occurred.
SEVERE: WSM-09012 No key, WSM-06002, was found in the resource bundle oracle.wsm.resources.policyvalidation.PolicyValidationMessageBundle.
javax.xml.ws.WebServiceException: oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-06002 PolicyReference Invalid policy reference
at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:466)
at oracle.j2ee.ws.client.jaxws.WsClientProxyInvocationHandler.invoke(WsClientProxyInvocationHandler.java:204)
at $Proxy28.sayHello(Unknown Source)
at HelloPolicyPortClient.main(HelloPolicyPortClient.java:35)
Caused by: oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-06002 PolicyReference Invalid policy reference
at oracle.integration.platform.common.InterceptorChainImpl.createPolicyEnforcementException(InterceptorChainImpl.java:217)
at oracle.integration.platform.common.InterceptorChainImpl.processRequest(InterceptorChainImpl.java:104)
at oracle.j2ee.ws.client.mgmt.runtime.SuperClientInterceptorPipeline.handleRequest(SuperClientInterceptorPipeline.java:91)
at oracle.j2ee.ws.client.jaxws.DispatchImpl.handleRequest(DispatchImpl.java:309)
at oracle.j2ee.ws.client.jaxws.DispatchImpl.handleRequest(DispatchImpl.java:290)
at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:444)
... 3 more
Process exited with exit code 0.
Can anyone please give any clue as to why this error is coming?
Thanks.

Hi
Please refer to this thread
Re: Can I create a login/password protection in Muse for a HTML5 page or two?

Why would i get this error when trying to create a browser to a queue

Is there a way to find out what Jar file weblogic is trying to
 open....
 i have this occuring on weblogic 7 sp1 when i try to create a browser
 to a queue
 java.lang.ExceptionInInitializerError:
 java.lang.IllegalStateException: zip file closed
 at java.util.zip.ZipFile.ensureOpen(ZipFile.java:377)
 at java.util.zip.ZipFile.getEntry(ZipFile.java:138)
 at java.util.jar.JarFile.getEntry(JarFile.java:176)
 at sun.net.www.protocol.jar.URLJarFile.getEntry(URLJarFile.java:67)
 at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:91)
 at sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:103)
 at java.net.URL.openStream(URL.java:793)
 at weblogic.common.internal.VersionInfo.getLocalWLPackages(VersionInfo.java:176)
 at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:34)
 at weblogic.common.internal.PeerInfo.<init>(PeerInfo.java:58)
 at weblogic.common.internal.PeerInfo.<init>(PeerInfo.java:49)
 at weblogic.common.internal.PeerInfo.<init>(PeerInfo.java:43)
 at weblogic.jms.frontend.FEBrowserCreateRequest.<clinit>(FEBrowserCreateRequest.java:98)
 at weblogic.jms.client.JMSSession.createBackEndBrowser(JMSSession.java:1750)
 at weblogic.jms.client.JMSQueueBrowser.<init>(JMSQueueBrowser.java:46)
 at weblogic.jms.client.JMSSession.createBrowser(JMSSession.java:1344)
 at com.gallup.scheduler.services.MessageStatusHandler.checkAndEmailStatus(MessageStatusHandler.java:192)
 at com.gallup.scheduler.services.MessageStatusHandler.handleAlarm(MessageStatusHandler.java:80)
 at com.jalios.jdring.AlarmManager.notifyListeners(AlarmManager.java:357)
 at com.jalios.jdring.AlarmWaiter.run(AlarmWaiter.java:110)
 at java.lang.Thread.run(Thread.java:479)


First time I've seen this one.
 The core issue may be that WL can not find its jar's
 manifest file META-INF/MANIFEST.MF, or can find it
 but can't open it.
 Are you doing something unique?
 A bunch of random questions for you:
 Is the full weblogic.jar in your classpath?
 Is it corrupted somehow?
 Is this problem unique to 7.0sp1?
 Is this application running on the server? In an applet?
 Tom Barnes
 Vishal Santoshi wrote:
 > Is there a way to find out what Jar file weblogic is trying to
 > open....
 > i have this occuring on weblogic 7 sp1 when i try to create a browser
 > to a queue
 >
 >
 >
 > java.lang.ExceptionInInitializerError:
 > java.lang.IllegalStateException: zip file closed
 > at java.util.zip.ZipFile.ensureOpen(ZipFile.java:377)
 > at java.util.zip.ZipFile.getEntry(ZipFile.java:138)
 > at java.util.jar.JarFile.getEntry(JarFile.java:176)
 > at sun.net.www.protocol.jar.URLJarFile.getEntry(URLJarFile.java:67)
 > at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:91)
 > at sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:103)
 > at java.net.URL.openStream(URL.java:793)
 > at weblogic.common.internal.VersionInfo.getLocalWLPackages(VersionInfo.java:176)
 > at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:34)
 > at weblogic.common.internal.PeerInfo.<init>(PeerInfo.java:58)
 > at weblogic.common.internal.PeerInfo.<init>(PeerInfo.java:49)
 > at weblogic.common.internal.PeerInfo.<init>(PeerInfo.java:43)
 > at weblogic.jms.frontend.FEBrowserCreateRequest.<clinit>(FEBrowserCreateRequest.java:98)
 > at weblogic.jms.client.JMSSession.createBackEndBrowser(JMSSession.java:1750)
 > at weblogic.jms.client.JMSQueueBrowser.<init>(JMSQueueBrowser.java:46)
 > at weblogic.jms.client.JMSSession.createBrowser(JMSSession.java:1344)
 > at com.gallup.scheduler.services.MessageStatusHandler.checkAndEmailStatus(MessageStatusHandler.java:192)
 > at com.gallup.scheduler.services.MessageStatusHandler.handleAlarm(MessageStatusHandler.java:80)
 > at com.jalios.jdring.AlarmManager.notifyListeners(AlarmManager.java:357)
 > at com.jalios.jdring.AlarmWaiter.run(AlarmWaiter.java:110)
 > at java.lang.Thread.run(Thread.java:479)

Trying to create a JMS Client in LifeCycle Module. Sun Appserver 8

Similar Messages

Maybe you are looking for