Netweaver 7.3 interoperate with Websphere MQ Error
Hi,
I was having problem to make my MDB (MessageDrivenBean) to listen to Websphere Queue. I have created all jms resources accordingly, but still encountered exception : javax.jms.InvalidDestinationException: queue:///CRRS.BROKER.REQ.UPD.03.
#2.0 #2019 10 06 18:52:20:914#+0800#Warning#com.sap.jms.resourceadapter.RaActivation#
#BC-JAS-JMS#jms#C0007F00000101E2000000CA0000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##
Attempt to activate endpoint has failed. Attempt number 0#
#2.0 #2019 10 06 18:52:20:914#+0800#Error#com.sap.jms.resourceadapter.ResourceAdapterImpl#
com.sap.ASJ.jms.000002#BC-JAS-JMS#jms#C0007F00000101E2000000CC0000161C#22411250000000044##com.sap.jms.resourceadapter.ResourceAdapterImpl#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##
There were problems initializing a Message-Driven Bean (MDB) of application sap.com/CRRSRatingEAR. No messages will be delivered to it. For more details, refer to the trace file.#
#2.0 #2019 10 06 18:52:20:915#+0800#Error#com.sap.jms.resourceadapter.ResourceAdapterImpl#
#BC-JAS-JMS#jms#C0007F00000101E2000000CD0000161C#22411250000000044##com.sap.jms.resourceadapter.ResourceAdapterImpl#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##
ActivationSpec could not be deployed/started due to internal problem, clean up will be performed, the activation spec was applicationName=sap.com/CRRSRatingEAR,connectionFactoryName : QCF_1,mAcknowledgeMode : null,maxPoolSize : 50,mClientId : null,mDestinationName : CRRS.BROKER.REQ.UPD.03,mDestinationType : javax.jms.Queue,minPoolSize : 0,mMessageSelector : null,mSubscriptionDurability : null,mSubscriptionName : null,mSAPMDBFailoverActivation : FALSE,mReconnectAttempts : 30,mSleepBetweenAttempts : 5000,mParallelConsumers : 1
[EXCEPTION]
javax.resource.spi.UnavailableException: Could not activate endpoint for the configured number of attempts
at com.sap.jms.resourceadapter.RaActivation.activate(RaActivation.java:193)
at com.sap.jms.resourceadapter.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:130)
at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:608)
at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findResourceAdapterByName(EndpointActivationImpl.java:156)
at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findAdapter(EndpointActivationImpl.java:95)
at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:68)
at com.sap.engine.services.ejb3.facades.internal.impl.server.MessagingFacadeImpl.activateEndpoint(MessagingFacadeImpl.java:43)
at com.sap.engine.services.ejb3.runtime.impl.Actions_MDBEndpointActivation.perform(Actions_MDBEndpointActivation.java:75)
at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:84)
at com.sap.engine.services.ejb3.container.ApplicationStarter.perform(ApplicationStarter.java:206)
at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:912)
at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.prepareStart(ContainerInterfaceImpl.java:438)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:508)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:279)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:242)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:435)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:478)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesSequentially(ParallelAdapter.java:315)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhases(StartTransaction.java:669)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2814)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationOnInstanceWait(DeployServiceImpl.java:3191)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationOnInstanceAndWaitAuth(DeployServiceImpl.java:3353)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2726)
at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:109)
at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:80)
at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:48)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:108)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:72)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:1138)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:1027)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:815)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deployInternal(DeployerImpl.java:450)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:224)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:904)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:459)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:983)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: javax.jms.InvalidDestinationException: queue:///CRRS.BROKER.REQ.UPD.03
at com.sap.jms.client.session.JMSSession.createConsumer(JMSSession.java:381)
at com.sap.jms.client.connection.JMSConnectionConsumer.<init>(JMSConnectionConsumer.java:37)
at com.sap.jms.client.connection.Connection.createConnectionConsumer(Connection.java:170)
at com.sap.jms.resourceadapter.RaActivation.setUpConnectionConsumer(RaActivation.java:221)
at com.sap.jms.resourceadapter.RaActivation.activate(RaActivation.java:162)
... 44 more
After I increased the log level, I noticed there was failure in jndi lookup for the queue and connection factory. I check the jndi lookup from NWA, it is available (eg. jms_vendor_queues_local/sap.com/CRRSRatingEAR/CRRS.BROKER.REQ.UPD.02)
#2.0 #2019 10 06 18:52:20:595#+0800#Info#com.sap.jms.resourceadapter.ResourceAdapterImpl#
#BC-JAS-JMS#jms#C0007F00000101E2000000AE0000161C#22411250000000044##com.sap.jms.resourceadapter.ResourceAdapterImpl#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##
Starting activation of JMS resource adapter endpoint factory. ActivationSpec is : applicationName=sap.com/CRRSRatingEAR,connectionFactoryName : QCF_1,mAcknowledgeMode : null,maxPoolSize : 50,mClientId : null,mDestinationName : CRRS.BROKER.REQ.UPD.02,mDestinationType : javax.jms.Queue,minPoolSize : 0,mMessageSelector : null,mSubscriptionDurability : null,mSubscriptionName : null,mSAPMDBFailoverActivation : FALSE,mReconnectAttempts : 30,mSleepBetweenAttempts : 5000,mParallelConsumers : 1#
#2.0 #2019 10 06 18:52:20:641#+0800#Info#com.sap.jms.resourceadapter.RaActivation#
#BC-JAS-JMS#jms#C0007F00000101E2000000AF0000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##
Attempt for lookup of destination failed. That could happen for 6.40 applications without application name.An attempt will be performed without the application name. The JNDI name is : jms_vendor_queues_local/sap.com/CRRSRatingEAR/CRRS.BROKER.REQ.UPD.02#
#2.0 #2019 10 06 18:52:20:646#+0800#Info#com.sap.jms.resourceadapter.RaActivation#
#BC-JAS-JMS#jms#C0007F00000101E2000000B00000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##
Performing JNDI lookup for obtaining connectionFactory : jms_vendor_factory_local/sap.com/CRRSRatingEAR/QCF_1#
#2.0 #2019 10 06 18:52:20:652#+0800#Info#com.sap.jms.resourceadapter.RaActivation#
#BC-JAS-JMS#jms#C0007F00000101E2000000B10000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##
First attempt for lookup failed. That could happen for 6.40 application without application name. We will continue with the fallback chain. The JNDI lookup is : jms_vendor_factory_local/sap.com/CRRSRatingEAR/QCF_1#
#2.0 #2019 10 06 18:52:20:652#+0800#Info#com.sap.jms.resourceadapter.RaActivation#
#BC-JAS-JMS#jms#C0007F00000101E2000000B20000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##
Performing JNDI lookup for obtaining connectionFactory : jms_vendor_factory_global/QCF_1#
#2.0 #2019 10 06 18:52:20:652#+0800#Warning#com.sap.jms.resourceadapter.RaActivation#
#BC-JAS-JMS#jms#C0007F00000101E2000000B30000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##
Attempt for lookup without application name failed. An attempt will be performed to use the default connectionFactory instead of the one supplied during deployment. The JNDI name is : jms_vendor_factory_global/QCF_1#
#2.0 #2019 10 06 18:52:20:652#+0800#Debug#com.sap.jms.resourceadapter.RaActivation#
#BC-JAS-JMS#jms#C0007F00000101E2000000B40000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##
Will try to lookup factory with lookupString jmsfactory/default/QueueConnectionFactory#
#2.0 #2019 10 06 18:52:20:653#+0800#Info#com.sap.jms.resourceadapter.RaActivation#
#BC-JAS-JMS#jms#C0007F00000101E2000000B50000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##
Performing JNDI lookup for obtaining connectionFactory : jmsfactory/default/QueueConnectionFactory#
#2.0 #2019 10 06 18:52:20:846#+0800#Debug#com.sap.jms.resourceadapter.RaActivation#
#BC-JAS-JMS#jms#C0007F00000101E2000000B60000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##
JMS version is 1.1#
#2.0 #2019 10 06 18:52:20:846#+0800#Debug#com.sap.jms.resourceadapter.RaActivation#
#BC-JAS-JMS#jms#C0007F00000101E2000000B70000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##
Exception listener was set#
I have run out of ideas on what is wrong. Please help.
Thanks.
Hi,
I have run diagnosis tool and from the output file, I notice the following error :
ResolverManager was not able to return an instance of object factory with name: com.ibm.mq.jms.MQQueueConnectionFactoryFactory
Caught java.lang.ClassNotFoundException: com.ibm.mq.jms.MQQueueConnectionFactoryFactory
Loader Info -
ClassLoader name: [service:jms_provider]
Loader hash code: 199d4a86
Living status: alive
Direct parent loaders:
[system:Frame]
[library:tcjemmodel~lib]
[service:naming]
[service:jmx]
[library:tcjej2eedescriptors~lib]
[library:jms]
[library:antlr]
[service:security]
[service:cross]
Resources:
D:\usr\sap\C12\J02\j2ee\cluster\bin\services\jms_provider\lib\private\sap.comtcjejms_providerimpl.jar
at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:278)
at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:247)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:367)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at com.sap.engine.system.naming.provider.ResolverManager.findObjectFactory(ResolverManager.java:376)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:66)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:33)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:228)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:283)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:559)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:619)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.sap.jms.resourceadapter.RaInitialContextDecorator.lookup(RaInitialContextDecorator.java:61)
at com.sap.jms.resourceadapter.RaActivation.lookupConnectionFactory(RaActivation.java:638)
at com.sap.jms.resourceadapter.RaActivation.setupConnectionFactory(RaActivation.java:569)
at com.sap.jms.resourceadapter.RaActivation.activate(RaActivation.java:152)
at com.sap.jms.resourceadapter.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:130)
at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:608)
at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findResourceAdapterByName(EndpointActivationImpl.java:156)
at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findAdapter(EndpointActivationImpl.java:95)
at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:68)
at com.sap.engine.services.ejb3.facades.internal.impl.server.MessagingFacadeImpl.activateEndpoint(MessagingFacadeImpl.java:43)
at com.sap.engine.services.ejb3.runtime.impl.Actions_MDBEndpointActivation.perform(Actions_MDBEndpointActivation.java:75)
at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:84)
at com.sap.engine.services.ejb3.container.ApplicationStarter.perform(ApplicationStarter.java:206)
at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:912)
at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.prepareStart(ContainerInterfaceImpl.java:438)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:508)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:279)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:242)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:435)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhases(ParallelAdapter.java:469)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhases(StartTransaction.java:677)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2814)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationOnInstanceWait(DeployServiceImpl.java:3191)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationOnInstanceAndWaitAuth(DeployServiceImpl.java:3353)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2726)
at com.sap.engine.services.deploy.logging.DSChangeLog.startApplicationAndWait(DSChangeLog.java:111)
at com.sap.engine.services.deploy.server.management.ApplicationInstanceDelegate$1.run(ApplicationInstanceDelegate.java:274)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)
Attempt for lookup without application name failed. An attempt will be performed to use the default connectionFactory instead of the one supplied during deployment. The JNDI name is : jms_vendor_factory_global/QCF_1
I have deploy the MQ library (using telnet command deploy_jms_library) and I can see the library loaded in NWA. Why is it not able to find the classes?
Please help.
Thanks.
Similar Messages
-
Error in JMS Adapter while communicating with WebSphere MQ 7.5
Guys,
I am trying to integrate JMS Adapter with WebSphere MQ.
JMS Adapter : 14.0.2.0
WebSphere MQ : 7.5
I am getting error like below. Please help me out. Thanks
17/04/14 16:25:49 java.lang.NoSuchMethodError: com.ibm.msg.client.jms.JmsSession.createQueue(Ljava/lang/String;)Ljavax/jms/Queue;
at com.ibm.mq.jms.MQSession.createQueue(MQSession.java:708)
at com.acta.adapter.jms.MQConfigHandler.getQueue(MQConfigHandler.java:74)
at com.acta.adapter.jms.JMSAdapter.getQueue(JMSAdapter.java:547)
at com.acta.adapter.jms.JMSGetOperation.start(JMSGetOperation.java:398)
at com.acta.adapter.sdk.OperationWrapper.runOperation(OperationWrapper.java:171)
at com.acta.adapter.sdk.OperationWrapper.run(OperationWrapper.java:94)
at java.lang.Thread.run(Thread.java:662)
I have added following jars in class path of the adapter.Problem solved after removing j2ee.jar file from classpath !
-
Error integrating OBIEE portlet with WebSphere Portal
Hi
I am trying to integrate OBIEE 10.1.3.4.1 with Websphere Portal.
I perform following steps :
1. Installed OBIEE and created a report at url "http://punitp63969d:9704/analytics/saw.dll?Dashboard"
2. Modified portlet.xml of sawjsr168portlets.war as follows
<preference>
<name>oracle.bi.presentation.sawserver.URL</name>
<value>http://punitp63969d:9704/analytics/saw.dll?Dashboard</value>
<read-only>false</read-only>
</preference>
<preference>
<name>oracle.bi.presentation.portlets.jsr168.reportui.AdminUserName</name>
<value>Administrator</value>
<read-only>false</read-only>
</preference>
<preference>
<name>oracle.bi.presentation.portlets.jsr168.reportui.AdminPwd</name>
<value>Administrator</value>
<read-only>false</read-only>
</preference>
<preference>
<name>oracle.bi.presentation.portlets.websphere.SuperuserSlotId</name>
<value>sawseveradmin</value>
<read-only>false</read-only>
</preference>
where Administrator/Administrator is user-id/password for OBIEE and
sawseveradmin is name of credential vault in WebSphere-Portal.
3. Deployed the war on WebSphere Portal and got portlet disable with following error in log :
WSVR0200I: Starting application: PA_SAWReport
9/4/09 18:42:52:067 IST 000001ff ApplicationMg A WSVR0204I: Application: PA_SAWReport Application build level: Unknown
9/4/09 18:42:52:708 IST 000001ff WebGroup A SRVE0169I: Loading Web Module: SAWReport.
9/4/09 18:42:52:973 IST 000001ff VirtualHost I SRVE0250I: Web Module SAWReport has been bound to default_host:10000,:80,:10002,:10015,:10016,:443,:10023,:10026,:10040,:10035.
9/4/09 18:42:53:130 IST 000001ff ApplicationMg A WSVR0221I: Application started: PA_SAWReport
9/4/09 18:42:59:692 IST 00000037 WebContainer E SRVE0255E: A WebGroup/Virtual Host to handle /searchfeed/myserver/scopes has not been defined.
9/4/09 18:43:26:458 IST 00000037 WebContainer E SRVE0255E: A WebGroup/Virtual Host to handle /searchfeed/myserver/scopes has not been defined.
9/4/09 18:43:50:318 IST 000000a5 ServletWrappe I SRVE0242I: PA_SAWReport [wps/PA_SAWReport] Oracle_Business_Intelligence_Report_View_Portlet: Initialization successful.
9/4/09 18:43:50:521 IST 000000a5 MimeResponseI E com.ibm.ws.portletcontainer.core.impl.MimeResponseImpl getWriter EJPPC0176W: Invalid content type
9/4/09 18:43:50:661 IST 000000a5 ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: Oracle_Business_Intelligence_Report_View_Portlet. Exception thrown : javax.servlet.ServletException: java.lang.IllegalStateException: No content type set.
at com.ibm.ws.portletcontainer.invoker.impl.PortletServlet.doDispatch(PortletServlet.java:369)
Caused by: java.lang.IllegalStateException: No content type set.
at com.ibm.ws.portletcontainer.core.impl.MimeResponseImpl.getWriter(MimeResponseImpl.java:114)
at com.siebel.analytics.web.portlets.jsr168.ReportUI.checkUser(ReportUI.java:852)
at com.siebel.analytics.web.portlets.jsr168.ReportUI.doView(ReportUI.java:167)
at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:328)
at com.siebel.analytics.web.portlets.jsr168.ReportUI.doDispatch(ReportUI.java:1058)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:233)
at com.ibm.ws.portletcontainer.invoker.impl.PortletFilterChainImpl.doFilter(PortletFilterChainImpl.java:128)
at com.ibm.wps.propertybroker.standard.filter.C2APortletFilter.doFilter(C2APortletFilter.java:185)
at com.ibm.ws.portletcontainer.invoker.impl.PortletFilterChainImpl.doFilter(PortletFilterChainImpl.java:120)
at com.ibm.ws.portletcontainer.invoker.impl.PortletServlet.doDispatch(PortletServlet.java:573)
at com.ibm.ws.portletcontainer.invoker.impl.PortletServletCollaboratorChainImpl.doCollaborator(PortletServletCollaboratorChainImpl.java:114)
at com.ibm.isclite.container.collaborator.PortletServletCollaborator.doRender(PortletServletCollaborator.java:68)
at com.ibm.ws.portletcontainer.invoker.impl.PortletServletCollaboratorChainImpl.doCollaborator(PortletServletCollaboratorChainImpl.java:105)
at com.ibm.ws.portletcontainer.rrd.RRDServerPortletServletCollaborator.doRender(RRDServerPortletServletCollaborator.java:123)
at com.ibm.ws.portletcontainer.invoker.impl.PortletServletCollaboratorChainImpl.doCollaborator(PortletServletCollaboratorChainImpl.java:105)
at com.ibm.ws.portletcontainer.cache.CacheCollaborator.doRender(CacheCollaborator.java:92)
at com.ibm.ws.portletcontainer.invoker.impl.PortletServletCollaboratorChainImpl.doCollaborator(PortletServletCollaboratorChainImpl.java:105)
at com.ibm.wps.pe.pc.waspc.core.impl.PortletServletCollaboratorImpl.doRender(PortletServletCollaboratorImpl.java:156)
at com.ibm.ws.portletcontainer.invoker.impl.PortletServletCollaboratorChainImpl.doCollaborator(PortletServletCollaboratorChainImpl.java:105)
at com.ibm.ws.portletcontainer.invoker.impl.PortletServlet.doDispatch(PortletServlet.java:273)
... 219 more
Please help me resolve this issue.Thanks in advance.I'm getting the same error on WebSphere 6.1.5. Is there any solution for this?
-
Problem in epm 11.1.1.3 configuration with websphere
hi there,
i am have installed epm 11.1.1.3 with websphere(ver 6.1) , but when i try to configure the workspace with websphere it asks me to give path for web server plug ins where mod_was_ap20_http.dll are installed .
i have also installed ibm http server(ver 6.0.1) but i am still not able to find that file .i chose the web server as ibm http server and apache but in both cases it is showing this problem.
thanks in advance.So are you seeing this error when accessing only HFM? Do you have planning or Reporting,does those work fine? Provide more details like what documents have you followed.If you disable SSL does it work?
Thanks
Vivek -
Integration with Websphere 5.0 (EJB 2.0) problems
Hello all,
Although a bit new to JDO, I have been trying to integrate Kodo 2.4 with
Websphere 5.0 (using EJB 2.0).
I have been basically binding a PersistenceManagerFactory into JNDI via
start-up servlet, however got the exception bellow when I tried to create
PersistenceManagerFactory (in setSessionContext of the EJB).
<i>JDOFatalInternalException: Could not perform automatic lookup of EJB
container's javax.transaction.TransactionManager implementation. Please ensure
that you are running the application from within an <b>EJB 1.1</b> compliant
EJB container, and then set the
com.solarmetric.kodo.ee.ManagedRuntimeProperties property to the appropriate
value to obtain the TransactionManager.</i>
The reference to EJB 1.1 actually scared me a bit. Does this imply that
Kodo (2.4) does not support J2EE 1.3?
Would you know how to set the
com.solarmetric.kodo.ee.ManagedRuntimeProperties to make it work with WSAD
5.0?
Thank you,
PetrPetr-
Is the integration with Websphere 5.0 application server officially
supported? Has anobody (that you know of) done it successfully yet?Yes, we do have reports of people using Kodo successfully from within
Websphere. However, it should be noted that it is not as rigorously
tested internally at SolarMetric as some other application servers (E.g.,
JBoss and WebLogic). In short, integration is known to work, but it
might be a little more rough around the edges than for other application
servers (as shown in our misspelling of Websphere's TransactionManager
implementation name).
How do I tell Kodo to use existing Datasource managed by app server?You can have Kodo use a named DataSource by specifying the
javax.jdo.option.ConnectionFactoryName property (see
http://www.solarmetric.com/docs/2.4.0/docs/manual.html#javax.jdo.option.ConnectionFactoryName).
This is often more appropriate for applications server usage, since it
allows you to configure pooling and other information from within the
application server's centralized configuration.
javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.app.DB2Driver
javax.jdo.option.ConnectionURL=jdbc:db2:snetWhat kind of driver is COM.ibm.db2.jdbc.app.DB2Driver? The DB2
configuration we use for testing with IBM's drivers is:
javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.net.DB2Driver
javax.jdo.option.ConnectionURL=jdbc:db2://SERVER_NAME/DATABASE_NAME
They shouldn't behave differently (I am guessing that the app driver is
a type 2 driver or something), but it might be worth a shot to try using
the net driver. If this fixes the problem, please let us know, because
it will indicate that Kodo has a deficiency with one of IBM's drivers
that we should look into resolving.
Since I have been trying to integrate with App server, this is the
initialization code that I use to bind PersistenceManagerFactory to JNDI.
You may find some funny stuff there.The binding code looks fine, and you are obviously able to retrive the
PM and start persistence operations. Note that you should also be able
to deploy Kodo as a Resource Adapter (which allows Kodo configuration
through the centralized Websphere configuration interface). However, I
doubt this is part of the issue.
So, in short, I recommend trying the following things:
1. Using the ConnectionFactoryName to use the DataSource defined for the
appserver, on the off chance this will fix it.
2. Using the net driver instead of the app driver.
3. Seeing if it will work with javax.jdo.option.Optimistic set to false
If none of these work, please let us know, and we will continue to
investigate other possible solutions.
In article <[email protected]>, Petr Bulanek wrote:
Hello Marc,
Very good guess. Pretty much the same code worked well without App server.
In that case, there obviously was no magic related to
TransactionManagerFactory initialization (see bellow).
Is the integration with Websphere 5.0 application server officially
supported? Has anobody (that you know of) done it successfully yet?
How do I tell Kodo to use existing Datasource managed by app server?
Here is the basic configuration (URL, class, etc):
javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory
javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.app.DB2Driver
javax.jdo.option.ConnectionURL=jdbc:db2:snet
javax.jdo.option.Optimistic=true
javax.jdo.option.RetainValues=true
javax.jdo.option.NontransactionalRead=true
We use DB2 Version 7.2/Version 7.1 FixPak 3 for Windows, in case it helps.
Since I have been trying to integrate with App server, this is the
initialization code that I use to bind PersistenceManagerFactory to JNDI.
You may find some funny stuff there.
The new EESimpleConfiguration(true) construct seems to (by default) read
the kodo.properties file that is part of the project.
EEConfiguration conf = new EESimpleConfiguration(true);
conf.setManagedRuntimeProperties(\"TransactionManagerMethod=com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager\");
conf.setManagedRuntimeClass(\"com.solarmetric.kodo.ee.InvocationManagedRuntime\");
EEPersistenceManagerFactory pmf =
new EEPersistenceManagerFactory(conf);
InitialContext ic = new InitialContext();
ic.rebind(\"KodoPMF\", pmf);
Thank you,
Petr
Marc Prud\'hommeaux wrote:
Petr-
It looks like DB2 doesn\'t like our attempt to close the connection
without a rollback or commit. This is odd, since we have never
seen this happen in our stand-alone DB2 tests. Can you let us know
the connection details (driver, connectionURL, etc)?
In the meantime, one possible workaround may be to turn off
optimistic transactions (since this will cause the PM to
only use a single Connection); can you try to specify:
javax.jdo.option.Optimistic=false
Also, have you tried to run this code in a non-managed environment
(e.g., outside the application server)? I would be interested
to know if it is related to running within an appserver.
In article <[email protected]>, Petr Bulanek wrote:
Hi Abe,
Thank you for a speedo reply. You guys really are on the ball!!!
As you suggested, the
\\\'com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager\\\'
did the job (for others, please note that the proper package name should
contain \\\'jts.jta\\\', not \\\'jts.jts\\\').
Unfortunately, I got another problem. When running a method containing
query (code bellow),
I get SQLException complaining about \\\'Invalid transaction state\\\'.
The method that executes the query is a stateless transactional Session
bean.
Thank you for your help,
Petr
--------------------------- DB2 - transaction state description
CLI0116E Invalid transaction state.
Explanation: There was a transaction in progress when SQLDisconnect was
called.
User Response: Call SQLTransact before calling SQLDisconnect.
--------------------------- Exception ------------------------------------
[2/01/03 16:34:19:050 EST] 563ddb8a SQL I
com.solarmetric.kodo.impl.jdbc.SQL [ C:336042896; T:1446894474;
D:118283149 ] preparing statement <369367952>: SELECT DISTINCT
PARENTX.JDOCLASSX FROM PARENTX
[2/01/03 16:34:19:050 EST] 563ddb8a SQL I
com.solarmetric.kodo.impl.jdbc.SQL [ C:336042896; T:1446894474;
D:118283149 ] executing statement <369367952>: [reused=1;params={}]
[2/01/03 16:34:19:061 EST] 563ddb8a JDBC I
com.solarmetric.kodo.impl.jdbc.JDBC [ C:336042896; T:1446894474;
D:118283149 ] close:
com.solarmetric.datasource.PoolConnection@14079b90[[requests=6;size=6;max=70;hits=0;created=6;redundant=0;overflow=0;new=6;leaked=0;unavailable=0]]
[2/01/03 16:34:19:061 EST] 563ddb8a JDBC I
com.solarmetric.kodo.impl.jdbc.JDBC [ C:336042896; T:1446894474;
D:118283149 ] close connection
[2/01/03 16:34:19:061 EST] 563ddb8a JDBC W
com.solarmetric.kodo.impl.jdbc.JDBC [ C:null; T:1446894474; D:118283149 ]
exception when closing connection
[2/01/03 16:34:19:541 EST] 563ddb8a JDBC W
com.solarmetric.kodo.impl.jdbc.JDBC TRAS0014I: The following exception
was logged COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0116E
Invalid transaction state. SQLSTATE=25000
atcom.solarmetric.datasource.ConnectionWrapper.close(ConnectionWrapper.java:243)
atcom.solarmetric.datasource.DataSourceImpl$AbstractPool.close(DataSourceImpl.java:690)
atcom.solarmetric.datasource.DataSourceImpl.close(DataSourceImpl.java:373)
atcom.solarmetric.datasource.DataSourceImpl.close(DataSourceImpl.java:347)
at com.solarmetric.datasource.PoolConnection.close(PoolConnection.java:70)
atcom.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.close(SQLExecutionManagerImpl.java:885)
atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.release(JDBCStoreManager.java:654)
atcom.solarmetric.kodo.impl.jdbc.ormapping.SubclassProviderImpl.getSubclasses(SubclassProviderImpl.java:274)
atcom.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.addSubclassConditions(ClassMapping.java:1239)
atcom.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.selectPrimaryMappings(ClassMapping.java:1218)
atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.executeQuery(JDBCStoreManager.java:717)
atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCQuery.executeQuery(JDBCQuery.java:92)
at com.solarmetric.kodo.query.QueryImpl.executeWithMap(QueryImpl.java:792)
atcom.solarmetric.kodo.query.QueryImpl.executeWithArray(QueryImpl.java:668)
at com.solarmetric.kodo.query.QueryImpl.execute(QueryImpl.java:609)
at com.testkodo.ejb.ControllerBean.observeHumans(ControllerBean.java:66)
--------------------------- Failing code sample
try {
PersistenceManager pm = factory.getPersistenceManager();
Extent ex = pm.getExtent(Parent.class, false);
Query q = pm.newQuery(ex, \\\"name==parName\\\");
q.declareParameters(\\\"String parName\\\");
Collection col = (Collection) q.execute(\\\"James\\\");
Iterator iter = col.iterator();
Parent pp;
Collection ch;
while (iter.hasNext()) {
pp = (Parent) iter.next();
System.out.println(pp);
ch = pp.getChildren();
Iterator it= ch.iterator();
while (it.hasNext()) {
System.out.println(it.next());
q.closeAll();
pm.close();
} catch (Exception e) {
System.out.println(e);
throw new EJBException(e);
Abe White wrote:
The reference to EJB 1.1 actually scared me a bit. Does this imply that
Kodo (2.4) does not support J2EE 1.3?
EJB 2.0 is also supported. Sorry for the confusing error message.
Would you know how to set the
com.solarmetric.kodo.ee.ManagedRuntimeProperties to make it work with
WSAD
5.0?
Try these settings:
com.solarmetric.kodo.ee.ManagedRuntimeClass=\\\\
com.solarmetric.kodo.ee.InvocationManagedRuntime
com.solarmetric.kodo.ee.ManagedRuntimeProperties=\\\\
TransactionManagerMethod=\\\\
com.ibm.ejs.jts.jts.TransactionManagerFactory.getTransactionManager
Marc Prud\'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com -
SAP Netweaver 04 SP16 deployed with Xalan 2.60 or Xalan 2.70
SAP Netweaver 04 SP16 deployed with Xalan 2.60 or Xalan 2.70
Have you tried to port and run (Sneak Preview) SAPNetWeaver java 04 SP16 or 04S SP7 with a later version on Xalan version 2.60 or Xalan version 2.70 along with jdk 1.4.2_(8 or greater)?
What specifically is failing? What patches or work around have you used to overcome compatibility issues with Xalan?
When we run Sneak Preview SAPNetWeaver java 04 SP16 SP7 with a version on Xalan version 2.60 or Xalan version 2.70 along with jdk 1.4.2_11, We get error 503 Service Unavailable, Application cannot be started
Details: com.sap.engine.services.deploy.container.ExceptionInfo: Error while parsing file data-source-aliases.xml.Hi
SAP does not allow usage of any other XML parsers with SAP web AS.
please have a look at this link
http://help.sap.com/saphelp_nw04/helpdata/en/36/ef353e39011a38e10000000a114084/frameset.htm
"Setting system properties in a system that supports more than one parser is prohibited".
The Error which you are getting is because one of the
java.system properties for parsing is
getting changed by xalan. These system properties are explictly set by the SAP XML implementation which it does not allow you to change.
Also can you please let me know where are you placing the xalan jar file ? is it deployed as a j2ee library or part of war ?
Hope this helps. please mark points for helpful answers
regards
rajesh kr -
J2ee agent 2.2 configuration problem with Websphere Portal 5.1
Hi,
I am trying to configure j2ee agent 2.2 with Websphere Portal server.
I have followed the document "Sun Java SystemAccess Manager
PolicyAgent 2.2 Guide for IBM WebSphere Portal Server 5.1.0.2"
Please see the thread "Problem with Sun's SSO system and Websphere Portal Server integration" for environment related information.
Also the security on app server has been enabled and is talking to LDAP.
My aim here is to enable application server (portal server) to autheticate requests.
I am getting following error when I log into the portal application.
07/03/2007 06:32:16:062 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
AmFilter: now processing: SSO Task Handler
07/03/2007 06:32:16:062 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
SSOTaskHandler: SSO Validation failed for null
07/03/2007 06:32:16:062 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
URLFailoverHelper: Checking if https://apollo.maxnewyorklife.com:443/amserver/UI/Login is available
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
WARNING: URLFailoverHelper: the url https://apollo.maxnewyorklife.com:443/amserver/UI/Login is not available
javax.net.ssl.SSLHandshakeException: unknown certificate
at com.ibm.jsse.bs.a(Unknown Source)
at com.ibm.jsse.bs.startHandshake(Unknown Source)
at com.ibm.net.ssl.www.protocol.https.b.o(Unknown Source)
at com.ibm.net.ssl.www.protocol.https.q.connect(Unknown Source)
at com.ibm.net.ssl.internal.www.protocol.https.HttpsURLConnection.connect(Unknown Source)
at com.sun.identity.agents.common.URLFailoverHelper.isAvailable(URLFailoverHelper.java:190)
at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:129)
at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
URLFailoverHelper: disconnected the connection for availability check
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
ERROR: URLFailoverHelper: No URL is available at this time
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
ERROR: AmFilter: Error while delegating to inbound handler: SSO Task Handler, access will be denied
[AgentException Stack]
com.sun.identity.agents.arch.AgentException: No URL is available at this time
at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:133)
at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
AmFilter: result =>
FilterResult:
Status : FORBIDDEN
RedirectURL : null
RequestHelper:
null
Data:
null
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
AmIdentityAsserter: result => TAIResult: status: 403, principal: null, subject: null
From whatever analysis I have done so far, I believe this issue is related to the personal certificate for sun one webserver (on which access manager & LDAP are installed) not registered with the application server (portal server).
I am not sure about the way I go by solving the issue.
Please can anybody help me out.
Thanks,
Yaseer
Message was edited by:
yazee
Message was edited by:
yazeeAnkush,
I am getting error as follows in the webserver error log:-
Error receiving request from 172.23.213.75 (SSL_ERROR_CERTIFICATE_UNKNOWN_ALERT: SSL peer had some unspecified issue with the certificate it received)
Although I can get into am console but with https://apollo.maxnewyorklife.com/amconsole
Tried the same thing, but couldnt resolve it. I will give it another go.
Generally I am getting same error again and again.
In my amWebsphere log file of j2ee agent (under root\am_wps_agent\agent_001\logs\debug) error I get.....
07/15/2007 04:19:11:656 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
AmFilter: now processing: SSO Task Handler
07/15/2007 04:19:11:766 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
SSOTokenValidator.validate(): Exception caught
com.iplanet.sso.SSOException: Invalid sessionid formatjava.lang.IllegalArgumentException: Invalid server id in session id com.iplanet.services.naming.ServerEntryNotFoundException: Naming Service is not available.
at com.iplanet.sso.providers.dpro.SSOProviderImpl.createSSOToken(SSOProviderImpl.java:205)
at com.iplanet.sso.SSOTokenManager.createSSOToken(SSOTokenManager.java:325)
at com.sun.identity.agents.common.SSOTokenValidator.validateInternal(SSOTokenValidator.java:252)
at com.sun.identity.agents.common.SSOTokenValidator.validate(SSOTokenValidator.java:157)
at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:88)
at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
07/15/2007 04:19:11:766 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
SSOTaskHandler: SSO Validation failed for AQIC5wM2LY4SfcwoaNKFd01DvjYeNPbR3wXaa9sMVjcKtwo=@AAJTSQACMDE=#
07/15/2007 04:19:11:766 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
URLFailoverHelper: Checking if https://apollo.maxnewyorklife.com:443/amserver/UI/Login is available
07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
WARNING: URLFailoverHelper: the url https://apollo.maxnewyorklife.com:443/amserver/UI/Login is not available
javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: No trusted certificate found
at com.ibm.jsse2.bw.a(Unknown Source)
at com.ibm.jsse2.bx.a(Unknown Source)
at com.ibm.jsse2.bx.a(Unknown Source)
at com.ibm.jsse2.v.a(Unknown Source)
at com.ibm.jsse2.v.a(Unknown Source)
at com.ibm.jsse2.u.a(Unknown Source)
at com.ibm.jsse2.bx.a(Unknown Source)
at com.ibm.jsse2.bx.l(Unknown Source)
at com.ibm.jsse2.bx.startHandshake(Unknown Source)
at com.ibm.net.ssl.www.protocol.https.b.o(Unknown Source)
at com.ibm.net.ssl.www.protocol.https.q.connect(Unknown Source)
at com.ibm.net.ssl.internal.www.protocol.https.HttpsURLConnection.connect(Unknown Source)
at com.sun.identity.agents.common.URLFailoverHelper.isAvailable(URLFailoverHelper.java:190)
at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:129)
at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
Caused by: com.ibm.jsse2.util.g: No trusted certificate found
at com.ibm.jsse2.util.f.b(Unknown Source)
at com.ibm.jsse2.util.f.b(Unknown Source)
at com.ibm.jsse2.util.d.a(Unknown Source)
at com.ibm.jsse2.bn.checkServerTrusted(Unknown Source)
at com.ibm.jsse2.z.checkServerTrusted(Unknown Source)
... 39 more
07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
URLFailoverHelper: disconnected the connection for availability check
07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
ERROR: URLFailoverHelper: No URL is available at this time
07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
ERROR: AmFilter: Error while delegating to inbound handler: SSO Task Handler, access will be denied
[AgentException Stack]
com.sun.identity.agents.arch.AgentException: No URL is available at this time
at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:133)
at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
Thanks,
Yaseer -
Urgent Requirement : Java Web Developer with Websphere Portal : CA
The Strategic Technologies Software Engineer - Advanced
Job Title Software Engineer - Advanced
Location : CA
Description:
This Advanced Web Developer position will be a development team that is enhancing the feature set on the corporate intranet, IBM portal based system.
Responsible for designing, developing and unit test components in a highly iterative and agile manner.
Responsible for Design and Development of JSR168 portlets, servlets, JSPs and deploying the same to IBM WebSphere Environment. Ability to understand Themes, Personalization, SSO and integrate portlets.
Responsible for writing Data access components using plain Java/JDBC and as well as using technologies like Spring and Hibernate
Ability to quickly learn and come up to speed in a new environment and follow standards.
Aside from solid web development skills, the candidate filling this position must have experience with test driven develop (TDD) techniques and have the demeanor and communication skills required for pair programming.
Responsible for coordinating with team members to achieve desired results and possible mentoring of Junior programmers whenever there is a need.
Proactively identifying issues in the development and bring up the same to the attention of tech lead or management attention at the very early stages. Ability to learn from team mates and solving issues quickly with the help of more knowledgeable team mates in that technology
Strong experience in JSR 168 compliant, portlet design and development, preferably in a IBM portal environment 2 to 4 years
Strong experience with Java, J2EE web application design, development of servlets, jsps, JSTL and good understanding of MVC framework minimum 4 years
Strong experience in coding unit tests with JUNIT
Experience with Javascript , html, XML and CSS in support of web application development
Experience with design and development of data access component in Java with SQL knowledge
Experience using IDEs like Eclipse , RAD and application servers like IBM Websphere Application Server
Must have good communication skills both verbally and in written form and the ability to work independently with minimal guidance and as a member of a team. Education: A computer science college degree or equivalent experience.
Must have:
8 years Java web development skills and excellent understanding of object-oriented analysis / design / programming.
5 years:
Deep understanding of web application design / web security
Good understanding of Model-View controller distributed architectures.
Experience with Websphere Studio Application Developer (Eclipse)
Experience with Service Oriented Architecture (SOA)
OO Analysis and Design experience.
Experience with the scrum agile development methodology, including TDD and JUNIT.
Hands-on experience with IBM's Websphere Portal is required.
If it interest you, please send your updated resume with your contact details ASAP at [email protected].
Regards,
Ejaz
Symphony Enterprises LLC
412-250-7227 (Tel) | 412-774-9230 (Fax)
IT Staffing | Training |
VERTICALS | Banking, Finance, Insurance | Healthcare | Manufacturing | Retail & Distribution
[email protected] | www.symphonyenterprises.com
WMBE & NWBE Certified Company
A Member of Women's Business Enterprise National Council (WBENC)
and National Association of Women Business Owners (NAWBO)I'm getting the same error on WebSphere 6.1.5. Is there any solution for this?
-
Weblogic app server wsdl web service call with SSL Validation error = 16
Weblogic app server wsdl web service call with SSL Validation error = 16
I need to make wsdl web service call in my weblogic app server. The web service is provided by a 3rd party vendor. I keep getting error
Cannot complete the certificate chain: No trusted cert found
Certificate chain received from ws-eq.demo.xxx.com - xx.xxx.xxx.156 was not trusted causing SSL handshake failure
Validation error = 16
From the SSL debug log, I can see 3 verisign hierarchy certs are correctly loaded (see 3 lines in the log message starting with “adding as trusted cert”). But somehow after first handshake, I got error “Cannot complete the certificate chain: No trusted cert found”.
Here is how I load trustStore and keyStore in my java program:
System.setProperty("javax.net.ssl.trustStore",”cacerts”);
System.setProperty("javax.net.ssl.trustStorePassword", trustKeyPasswd);
System.setProperty("javax.net.ssl.trustStoreType","JKS");
System.setProperty("javax.net.ssl.keyStoreType","JKS");
System.setProperty("javax.net.ssl.keyStore", keyStoreName);
System.setProperty("javax.net.ssl.keyStorePassword",clientCertPwd); System.setProperty("com.sun.xml.ws.transport.http.client.HttpTransportPipe.dump","true");
Here is how I create cacerts using verisign hierarchy certs (in this order)
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignClass3G5PCA3Root.txt -alias "Verisign Class3 G5P CA3 Root"
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignC3G5IntermediatePrimary.txt -alias "Verisign C3 G5 Intermediate Primary"
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignC3G5IntermediateSecondary.txt -alias "Verisign C3 G5 Intermediate Secondary"
Because my program is a weblogic app server, when I start the program, I have java command line options set as:
-Dweblogic.security.SSL.trustedCAKeyStore=SSLTrust.jks
-Dweblogic.security.SSL.ignoreHostnameVerification=true
-Dweblogic.security.SSL.enforceConstraints=strong
That SSLTrust.jks is the trust certificate from our web server which sits on a different box. In our config.xml file, we also refer to the SSLTrust.jks file when we bring up the weblogic app server.
In addition, we have working logic to use some other wsdl web services from the same vendor on the same SOAP server. In the working web service call flows, we use clientgen to create client stub, and use SSLContext and WLSSLAdapter to load trustStore and keyStore, and then bind the SSLContext and WLSSLAdapter objects to the webSerive client object and make the webservie call. For the new wsdl file, I am told to use wsimport to create client stub. In the client code created, I don’t see any way that I can bind SSLContext and WLSSLAdapter objects to the client object, so I have to load certs by settting system pramaters. Here I attached the the wsdl file.
I have read many articles. It seems as long as I can install the verisign certs correctly to web logic server, I should have fixed the problem. Now the questions are:
1. Do I create “cacerts” the correct order with right keeltool options?
2. Since command line option “-Dweblogic.security.SSL.trustedCAKeyStore” is used for web server jks certificate, will that cause any problem for me?
3. Is it possible to use wsimport to generate client stub that I can bind SSLContext and WLSSLAdapter objects to it?
4. Do I need to put the “cacerts” to some specific weblogic directory?
---------------------------------wsdl file
<wsdl:definitions name="TokenServices" targetNamespace="http://tempuri.org/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata">
<wsp:Policy wsu:Id="TokenServices_policy">
<wsp:ExactlyOne>
<wsp:All>
<sp:TransportBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<wsp:Policy>
<sp:TransportToken>
<wsp:Policy>
<sp:HttpsToken RequireClientCertificate="true"/>
</wsp:Policy>
</sp:TransportToken>
<sp:AlgorithmSuite>
<wsp:Policy>
<sp:Basic256/>
</wsp:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp:Policy>
<sp:Strict/>
</wsp:Policy>
</sp:Layout>
</wsp:Policy>
</sp:TransportBinding>
<wsaw:UsingAddressing/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
<wsdl:types>
<xsd:schema targetNamespace="http://tempuri.org/Imports">
<xsd:import schemaLocation="xsd0.xsd" namespace="http://tempuri.org/"/>
<xsd:import schemaLocation="xsd1.xsd" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="ITokenServices_GetUserToken_InputMessage">
<wsdl:part name="parameters" element="tns:GetUserToken"/>
</wsdl:message>
<wsdl:message name="ITokenServices_GetUserToken_OutputMessage">
<wsdl:part name="parameters" element="tns:GetUserTokenResponse"/>
</wsdl:message>
<wsdl:message name="ITokenServices_GetSSOUserToken_InputMessage">
<wsdl:part name="parameters" element="tns:GetSSOUserToken"/>
</wsdl:message>
<wsdl:message name="ITokenServices_GetSSOUserToken_OutputMessage">
<wsdl:part name="parameters" element="tns:GetSSOUserTokenResponse"/>
</wsdl:message>
<wsdl:portType name="ITokenServices">
<wsdl:operation name="GetUserToken">
<wsdl:input wsaw:Action="http://tempuri.org/ITokenServices/GetUserToken" message="tns:ITokenServices_GetUserToken_InputMessage"/>
<wsdl:output wsaw:Action="http://tempuri.org/ITokenServices/GetUserTokenResponse" message="tns:ITokenServices_GetUserToken_OutputMessage"/>
</wsdl:operation>
<wsdl:operation name="GetSSOUserToken">
<wsdl:input wsaw:Action="http://tempuri.org/ITokenServices/GetSSOUserToken" message="tns:ITokenServices_GetSSOUserToken_InputMessage"/>
<wsdl:output wsaw:Action="http://tempuri.org/ITokenServices/GetSSOUserTokenResponse" message="tns:ITokenServices_GetSSOUserToken_OutputMessage"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="TokenServices" type="tns:ITokenServices">
<wsp:PolicyReference URI="#TokenServices_policy"/>
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="GetUserToken">
<soap12:operation soapAction="http://tempuri.org/ITokenServices/GetUserToken" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="GetSSOUserToken">
<soap12:operation soapAction="http://tempuri.org/ITokenServices/GetSSOUserToken" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="TokenServices">
<wsdl:port name="TokenServices" binding="tns:TokenServices">
<soap12:address location="https://ws-eq.demo.i-deal.com/PhxEquity/TokenServices.svc"/>
<wsa10:EndpointReference>
<wsa10:Address>https://ws-eq.demo.xxx.com/PhxEquity/TokenServices.svc</wsa10:Address>
</wsa10:EndpointReference>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
----------------------------------application log
adding as trusted cert:
Subject: CN=VeriSign Class 3 International Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Issuer: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x641be820ce020813f32d4d2d95d67e67
Valid from Sun Feb 07 19:00:00 EST 2010 until Fri Feb 07 18:59:59 EST 2020
adding as trusted cert:
Subject: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x3c9131cb1ff6d01b0e9ab8d044bf12be
Valid from Sun Jan 28 19:00:00 EST 1996 until Wed Aug 02 19:59:59 EDT 2028
adding as trusted cert:
Subject: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x250ce8e030612e9f2b89f7054d7cf8fd
Valid from Tue Nov 07 19:00:00 EST 2006 until Sun Nov 07 18:59:59 EST 2021
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Cipher: SunPKCS11-Solaris version 1.6 for algorithm DESede/CBC/NoPadding>
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Cipher for algorithm DESede>
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.6 for algorithm RSA/ECB/NoPadding>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSetup: loading trusted CA certificates>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 28395435>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 115>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <25779276 SSL3/TLS MAC>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <25779276 received HANDSHAKE>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 16>
<Mar 7, 2013 6:59:22 PM EST> <Warning> <Security> <BEA-090477> <Certificate chain received from ws-eq.demo.xxx.com - xx.xxx.xxx.156 was not trusted causing SSL handshake failure.>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is untrusted>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (16): CERT_CHAIN_UNTRUSTED>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
java.lang.Exception: New alert stack
at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)
at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:296)
at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
at javax.xml.ws.Service.<init>(Service.java:56)
at ideal.ws2j.eqtoken.TokenServices.<init>(TokenServices.java:64)
at com.citi.ilrouter.util.IpreoEQSSOClient.invokeRpcPortalToken(IpreoEQSSOClient.java:165)
at com.citi.ilrouter.servlets.T3LinkServlet.doPost(T3LinkServlet.java:168)
at com.citi.ilrouter.servlets.T3LinkServlet.doGet(T3LinkServlet.java:206)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 6457753>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 6457753>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.removeContext(ctx): 22803607>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 14640403>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 115>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <23376797 SSL3/TLS MAC>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <23376797 received HANDSHAKE>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 16>
<Mar 7, 2013 6:59:22 PM EST> <Warning> <Security> <BEA-090477> <Certificate chain received from ws-eq.demo.xxx.com - 12.29.210.156 was not trusted causing SSL handshake failure.>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is untrusted>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (16): CERT_CHAIN_UNTRUSTED>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
java.lang.Exception: New alert stack
at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)
at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:296)
at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
at javax.xml.ws.Service.<init>(Service.java:56)
at ideal.ws2j.eqtoken.TokenServices.<init>(TokenServices.java:64)
at com.citi.ilrouter.util.IpreoEQSSOClient.invokeRpcPortalToken(IpreoEQSSOClient.java:165)
at com.citi.ilrouter.servlets.T3LinkServlet.doPost(T3LinkServlet.java:168)
at com.citi.ilrouter.servlets.T3LinkServlet.doGet(T3LinkServlet.java:206)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 16189141>I received a workaround by an internal message.
The how to guide is :
-Download the wsdl file (with bindings, not the one from ESR)
-Correct it in order that the schema corresponds to the answer (remove minOccurs or other things like this)
-Deploy the wsdl file on you a server (java web project for exemple). you can deploy on your local
-Create a new logicial destination that point to the wsdl file modified
-Change the metadata destination in your web dynpro project for the corresponding model and keep the execution desitnation as before.
Then the received data is check by the metadata logical destination but the data is retrieved from the correct server. -
Issue with OWA (404 error)
From the server itself i can use IPv6 https://[fe80::feef:ff56:c498:1f0]/owa - this opens the mailbox.
https://127.0.0.1/owa - this opens the mailbox
https://localhost/owa - this results in 404 - File or directory not found
using https://servername/owa - this results in 404 - file or directory not found
using https://192.168.10.10 - this results in 404 - file or directory not found
is this an issue with IIS bindings?
thanks in advanceHi,
I think you can check the authentication settings in IIS for exchange virtual directories.
Thanks,
James -
Problem with DMGs and error: "No Mountable File Systems"
Problem with DMGs and error: "No Mountable File Systems"
The files are not corrupt. The problem is occurring with all DMGs that are apparently formatted in MS-DOS FAT16. No the file will not mount with Disk utility or any other disk mounter programs I have found.
This is now the second time this occurred and now effects my MBP and my iMac. First time i spent days with Apple support and the only solution was ultimately back up the data, reformat the HD, start over from scratch and reload everything. That lasted about a month before the problem resurfaced and is now an issue on both iMac and MBP.
I tried to identify all the programs I installed immediately before the error, as I am convinced it is the result of a software conflict.
Recent programs includes:
1) upgrading from Parallels 5.5 to 6.0 on both machines.
2) using an HP secure II usb drive and setting up a secure disk.
3) installing new itunes 10
4) new update to Flip For Mac.
The files affected are downloaded dmgs, including personal brain and google earth, both which are formatted in FAT16.
Any help or thoughts? Apple has now spent hours trying and they say i now have to reformat and wipe and start over. That is unacceptable and based on pasted experience the problem is likely to repeat itself. having to wipe and rebuild a HD ever month is not an solution. i need to fid the root problem.
In the meantime, anyone got a real solution on how to extract the data for a DMG using a different method?
Message was edited by: remaiaWhere you able to find the solution, i am having the same problem, all was fine till i install some programs only same one i saw did we both did was flip4mac i uninstalled it but the problem is still there, i also restored and erased the hardrive but im not up to doing that all over again. If you found anything out let me know i would greatly appreciate it
-
My Premiere Pro won't open and keeps coming up with a 0xc000007b error message!! I have uninstalled
My Premiere Pro won't open and keeps coming up with a 0xc000007b error message!! I have uninstalled and reinstalled it but it will still not open.
It worked for me, any way we have to do following things now, I have seen this happens becasue of the corrupt dll for Visual C++ packages. if the following thing will not work, I am affraid we have to reinstall the windows 7
Good Luck
Try to remove all the Visual C++ 2010 Redistributable and Visual C++ 2008 Redistributable Packages (both x86 and x64) from the Control Panel
Download and install following Visual C++ Redistributable Packages
Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)
Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)
Microsoft Visual C++ 2010 SP1 Redistributable Package (x86)
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) -
Why does my itunes crash after start up with an "APPCRASH" error every time i open it?! I have been trying to fix this for weeks but all i can do it re-install it every other day which does nothing! I am desperate to get access to my itunes to get music on my phone and all of this just makes me want me to sell my iphone since there is no other way to add music to my phone. If things go get sorted soon you can say goodbye to my support.
For general advice see Troubleshooting issues with iTunes for Windows updates.
The steps in the second box are a guide to removing everything related to iTunes and then rebuilding it which is often a good starting point unless the symptoms indicate a more specific approach. Review the other boxes and the list of support documents further down the page in case one of them applies.
The further information area has direct links to the current and recent builds in case you have problems downloading, need to revert to an older version or want to try the iTunes for Windows (64-bit - for older video cards) release as a workaround for installation or performance issues, or compatibility with QuickTime or third party software.
Your library should be unaffected by these steps but there are also links to backup and recovery advice should it be needed.
tt2 -
Cannot load individual websites; Googling is fine, but URL comes up with a 404 error.
Since I updated Firefox, it seems my internet connectivity in that browser has dropped. I can Google things (not in the URL box, but in the Google box) perfectly, with the exception that sometimes the link clicked from Google doesn't load. However, I cannot actually visit an individual site by entering the URL. If I directly enter the URL, it comes up with a 404 error, site not found. If I try to navigate to some pages from a Google, it comes up with a connectivity problem page. I would really like to be able to use my Firefox again. In the meantime, I'll have to use Google Chrome.
Try clearing Firefox's cookies and cache
Do these steps and then reload the website you're having trouble with.
* Click the menu button [[Image:New Fx Menu]] , choose History and select Clear Recent History....
* In the Time Range to clear: drop-down, select Everything.
* Click the arrow next to Details to display the list of items that can be cleared.
* Select both Cookies and Cache.
* Click Clear Now.
Moreover, normally such issues are caused by a firewall/security software which doesn't recognize & therefore blocks new firefox versions:[[Fix problems connecting to websites after updating Firefox]]
Also see:
[[Firefox can't load websites but other browsers can]]
[[Websites don't load - troubleshoot and fix error messages]] -
We installed a new Server 2008 R2 server this spring. It is configured as a Terminal Server with 16 Wyse t10 thin clients connecting with RDP. We are a small resort so we run Springer Miller Host and SpaSoft. Ever since moving from PCs to the thin clients
and TS we have been seeing SpaSoft randomly crash with KERNELBASE.dll errors and also a lot of c0000005 and c0000006 errors. Springer Miller support says its a Microsoft Networking issue so no help there. The company we worked with to install this has no clue
so I hope to reach out to this community to solve this. I can also open support case with Microsoft Support but I am not sure if they will be of any help. Here are some examples of the errors:
"Event 1000
Faulting application name: SpaWin.exe, version: 3.4.0.0, time stamp: 0x2a425e19
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86
Exception code: 0x0eedfade
Fault offset: 0x0000c42d
Faulting process id: 0x3718
Faulting application start time: 0x01cf9ac7922487e9
Faulting application path: \\spasoft\spaapps\TermServ\SpaWin.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: cfdcf9a9-06ba-11e4-a5af-000c298d9aa5"
Also:
"Faulting application name: VH.EXE, version: 18.80.430.0, time stamp: 0x3f73b447
Faulting module name: VFP8R.DLL, version: 8.0.0.3117, time stamp: 0x3f73c232
Exception code: 0xc0000006
Fault offset: 0x0001d598
Faulting process id: 0x2bc8
Faulting application start time: 0x01cf99297ee1742f
Faulting application path: J:\HOSTPLUS\fxp32\VH.EXE
Faulting module path: J:\HOSTPLUS\fxp32\VFP8R.DLL
Report Id: 5fbc65c4-055c-11e4-a5af-000c298d9aa5"
And:
"Faulting application name: SpaWin.exe, version: 3.4.0.0, time stamp: 0x2a425e19
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x2aa0
Faulting application start time: 0x01cf988e6770e619
Faulting application path: \\spasoft\spaapps\TermServ\SpaWin.exe
Faulting module path: unknown
Report Id: 01029179-04b9-11e4-a5af-000c298d9aa5"
There are no network specific errors in any of the logs. I am thinking that SpaSoft needs to be run as an administrator but I am not sure how to do that in this environment. We have disabled DEP for all but essential Windows processes. All of the firewall
and AV has been completely disabled, and still getting these errors. Is there a way to run these applications as admin without the user actually being an admin? Should I go ahead and open a Microsoft support case? ThanksHi,
Thank you for posting in Windows Server Forum.
Explanation
The indicated program stopped unexpectedly. The message contains details on which program and module stopped. A matching event with Event ID 1001 might also appear in the event log. This matching event displays information about the specific error that occurred.
User Action
If an error report was generated for this error, you might be able to obtain more information about the error by sending the report to Microsoft for analysis.
Yeah, you can open a support case with Microsoft as they will help and guide you for proper solution. You can go through
this source article.
Hope it helps!
Thanks.
Dharmesh Solanki
Maybe you are looking for
-
How do I add a mailbox on my 4S?
The manual clearly says to add a mailbox "Go the the mailboxes list, tap Edit, then tap New Mailbox". There is no "Edit" option on my mailboxes screen
-
How can I transfer photos in pdf files to the photo gallery on my Android phone?
-
Cannot interactively use VNC when started from a signed jar
I wrote a Java wrapper class to run a shell command to start a VNC client. Then signed it and started it using web start. In the jnlp file, I granted all permission. I could start the vnc viewer successfully but the issue is that the mouse and keyboa
-
Ipad wont reboot & my sleep or lock button doesn't work??
I updated ios 7 on my ipad just yesterday. After a while I used it, then my ipad kept popping out shut down mode, and lock the screen randomly. I tried to reboot it, my screen kept locking randomly. I tried to reboot it for three times, and for the t
-
What is difference between desktop and workstation?
Can somebody explain the difference.