Global query block is causing a DNS server to fail a query with error code Name Error exists in the DNS database for WPAD
Global query block is causing a DNS server to fail a query with error code Name Error exists in the DNS database for WPAD on a Windows 2008 server.
The global query block list is a feature that prevents attacks on your network by blocking DNS queries for specific host names. This feature has caused the DNS server to fail a query with error code NAME ERROR for wpad.contoso.com. even though data
for this DNS name exisits in the DNS database. Other queries in all locally authoritative zones for other names that begin with labels in the block list will also fail, but no event will be logged when further queries are blocked until the DNS server
service on this computer is restarted.
Similar Messages
-
SQL query works in SSIS, SSMS/SQL server but fails in deployment?
The SQL query in my execute sql task is correct. It works in SSIS and SSMS also. But, it fails when I deploy my package. The error -
Code: 0xC002F210
Source: MySQLTask Execute SQL Task Description: Executing the query
"UPDATE [MyTable] SET MyCol..."
failed with the following error: "Invalid object name 'MyTable'.".
Possible failure reasons: Problems with the query "ResultSet" property
not set correctly parameters not set correctly or connection not established
correctly.
What could be the reason for this error and how do I fix it ?
Thanks.Does the database have the object [MyTable]? What is the default schema for the user? Is the table (assuming it exists) in the default schema for the user?
Russel Loski, MCT, MCSE Data Platform/Business Intelligence. Twitter: @sqlmovers; blog: www.sqlmovers.com
Yes, the DB has the object [MyTable]. The default schema is dbo, as given by SELECT SCHEMA_NAME()
The table is in the default schema for the user as per -
SELECT *
FROM INFORMATION_SCHEMA.TABLES
WHERE TABLE_SCHEMA = SCHEMA_NAME()
AND TABLE_NAME = 'MyTable' -
Hi Experts,
In our application we are trying to connect to the RAS server for the ad hoc reporting capabilities that allow users to modify reports over the Web.
In order to do this what are servers need to run on the server side( I am looking for settings on server side like, what are the servers and services to be run on).
When we try to open the document we are getting the error. The code and error msg are as follows.
private void GetReportClientDocument()
try {
sessionManager = CrystalEnterprise.getSessionMgr();
enterpriseSession = sessionManager.logon(username,password, servername, "SecEnterprise");
iStore = (IInfoStore) enterpriseSession.getService("InfoStore");
String sampleReportName = "Test_Open";
IInfoObjects infolist = iStore.query("Select SI_CUID From CI_INFOOBJECTS Where SI_NAME='" + sampleReportName + "' and SI_INSTANCE=0");
int lookUpId = 0;
for (int i = 0; i < infolist.size(); i++) {
IInfoObject siId = (IInfoObject) infolist.get(i);
lookUpId = siId.getID();
System.out.println("The CUID is: "+lookUpId);
IInfoObjects list = iStore.query("select * From CI_INFOOBJECTS Where SI_ID="+lookUpId);
IInfoObject report = (IInfoObject) list.get(0);
ReportClientDocument rcd = new ReportClientDocument();
IReportAppFactory appFactory = (IReportAppFactory) enterpriseSession.getService("RASReportFactory");
try {
System.out.println("Name of Document: "+rcd.getReportDocument().getName());
rcd = appFactory.openDocument(report, OpenReportOptions._openAsReadOnly,null);
} catch (ReportSDKException e) {
e.printStackTrace();
} catch (SDKException e) {
e.printStackTrace();
Error:
com.crystaldecisions.sdk.occa.report.lib.ReportSDKClientDocException: The document has not been opened.---- Error code:-2147215349 Error code name:docNotReady
at com.crystaldecisions.sdk.occa.report.lib.ReportSDKClientDocException.throwReportSDKClientDocException(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.getDatabaseController(Unknown Source)
at Viewer.GetReportClientDocument(Viewer.java:98)
at Viewer.main(Viewer.java:27)
Thanks in advance for your help.Hi Qiang,
Please check http://metalink.oracle.com/metalink/plsql/ml2_documents.showFrameDocument?p_database_id=NOT&p_id=1047650.6 for possible solutions for this error.
Thanks,
Erik -
Hi,
Developed Proxy <-->PI<-->JDBC SELECT scenario and getting the following error.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while sending by HTTP (error code: 500, error text: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
When I cross checked the JDBC Receiver communication channel in Runtime Work Bench
request and response were successfull. RWB shows the following message.
2009-06-12 09:34:50 Information The message was successfully received by the messaging system.
2009-06-12 09:34:50 Information Message successfully put into the queue.
2009-06-12 09:34:50 Information The message was successfully retrieved from the request queue.
2009-06-12 09:34:50 Information The message status was set to DLNG.
2009-06-12 09:34:50 Information Delivering to channel: DB2ReceiverTableSPT
2009-06-12 09:34:50 Information JDBC Adapter Receiver processing started, required QoS BestEffort
2009-06-12 09:34:50 Information JDBC Adapter Receiver Channel DB2ReceiverTableSPT:
2009-06-12 09:36:35 Information Database request processed successfully.
2009-06-12 09:36:35 Information The message was successfully delivered to the application using connection JDBC_http://sap.com/xi/XI/System.
2009-06-12 09:36:35 Information The message status was set to DLVD.
I had gone thru all the previous threads related to 'CLIENT_SEND_FAILED' but
those did not solve my problem.
Can some one help me to solve this issue.
Thanks,
Vijay.I made necessary changes as per the blog. Appended '_response' for JDBC response structure.
Still I am facing same problem.
Strange....delibarately gave the link so that you can cross-check the JDBC config on receiver side...I assume that the proxy is configured properly with the Sync communication....also mapping is done accordingly...
Regards,
Abhishek. -
Can I connect a PS3 wirelessly via the built-in AirPort card using internet sharing from my ethernet-wired iMac? It works for my Nook e-reader, but the PS3 give a DNS error code 8070102, I've tried alternate DNS settings, but no luck.
Can I connect a PS3 wirelessly via the built-in AirPort card using internet sharing from my ethernet-wired iMac? It works for my Nook e-reader, but the PS3 give a DNS error code 8070102, I've tried alternate DNS settings, but no luck.
-
DNS debug logging to determine if 2008R2 DNS server is still being queried?
We are removing multiple DNS servers. We have removed those servers from DNS reference from all dhcp scopes, and ran script across all windows servers to make sure they are not being used. There still might be Linux/telecom/workstations manually
set that we do not know about, so I was going to use debug logging just to look for queries that are coming and to try and determine where they came from. I have debug logging set to log packets for Incoming, UDP, Queries/Transfers, and Request, but having
trouble figuring out this log. Here is an example of what I am seeing. Does anyone have a reference for this? I am having trouble finding one.
Is this saying that a computernamed POS188 made a query for a host(A) record? or is it saying that a query came in from 128.1.60.221 for a host(A) record named POS188? Just looking for reference to help explain this. The good news is the only
IP address that shows(128.1.60.221) is the IP of the DNS server, but the only thing I could find for reference was this -
http://technet.microsoft.com/en-us/library/cc776361(WS.10).aspx
9/16/2014 12:05:23 AM 1144 PACKET 000000000624CBD0 UDP Rcv 128.1.60.221 8952 Q [0001 D NOERROR] A
(8)POS188(11)contoso(3)com(0)
Thanks,
Dan HeimHi Dan,
The example you provide means that the DNS server receive a packet sent by 128.1.60.221,and the packet is used to query a host(A) record named POS188.contoso.com.
And the detail information about each field of the message is shows below. It is also showed in the dns.log.
Message logging key (for packets - other items use a subset of these fields):
Field # Information Values
1 Date
2 Time
3 Thread ID
4 Context
5 Internal packet identifier
6 UDP/TCP indicator
7 Send/Receive indicator
8 Remote IP
9 Xid (hex)
10 Query/Response R = Response
blank = Query
11 Opcode
Q = Standard Query
N = Notify
U = Update
? = Unknown
12 [ Flags (hex)
13 Flags (char codes) A = Authoritative Answer
T = Truncated Response
D = Recursion Desired
R = Recursion Available
14 ResponseCode ]
15 Question Type
16 Question Name
The corresponding example:
9/16/2014 12:05:23 AM 1144 PACKET 000000000624CBD0 UDP
Rcv 128.1.60.221 8952 Q [0001
D NOERROR] A
(8)POS188(11)contoso(3)com(0)
Best Regards,
Tina -
When trying to create or update Azure RemoteApp collections that use a template image for some non-EN-US locales, it might fail with error "DNS server could not be reached". You might also see error code "DnsNotReachable".
Cause: There was a issue in Azure in which decimal punctuation was not treated properly if the locale of the template image used a comma (,) instead of a period (.).
Workaround: Before a fix was applied, the workaround was to use template images based on a locale that uses a period to delimit decimals, such as EN-US.
Resolution: As of March 19, 2015, a fix for this issue has been applied to Azure. You should once again be able to create collections from template images that use non-EN-US locales. If you continue to have this problem, please
try the workaround. If that works and the only difference in the template images is the locale, please email remoteappforum (at Microsoft). If the workaround does not work, the issue is likely caused by a DNS configuration issue such as:
No valid forwarders to public DNS servers configured on your internal DNS server(s).
A valid internal DNS server is not specified on your Azure RemoteApp VNet.
A VNet or internal network configuration issue is preventing the internal DNS servers from be reached by the VMs in the RemoteApp collection. -
Sql statement causes my JRun server to fail.
I'm beginning JSP and can't go through this recurrent error: the first request to the JSP page containing sql statement works well, in the second, an error occurs and finally, the third forces my Jrun server to fail with a stack error...
<CODE>
<%-- page global declaratiosn --%>
<%@ page import="java.sql.*,javax.sql.*,allaire.taglib.*" %>
<%
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver") ;
String url = "jdbc:odbc:ademeregion" ;
Connection con = DriverManager.getConnection( url , "" , "" ) ;
Statement stmt = con.createStatement();
ResultSet itom = stmt.executeQuery( "SELECT * FROM ITOM" ) ;
ResultSetMetaData itomMetaData = itom.getMetaData( ) ;
out.print( getServletContext().getInitParameter( "test" ) + "<br>" ) ;
%>
<table border=1 cellspadding=0 cellspacing=0>
<%
while( itom.next() ){%>
<tr>
<%
for (int i = 1 ; i <= itomMetaData.getColumnCount() ; i++ ){
out.print( "<td><font face=Verdana color=#EEEEEE size=1>" + itom.getString( i ) + "</font></td>") ;
%>
</tr><%
%>
</CODE>
I assume it could be a typical jdbc problem that beginners encounter...
Help required...
Thanks a lot...
SylvainThnks but it's allready done:
I had the following code allready:
<%
itom = null ;
itomMetaData = null ;
stmt.close( ) ;
con.close( ) ;
%>
But thanks anyway... -
J2ee server has suddenly stopped running with exit code -11113
Hi,
Have installed WAS 6.40 portal and TREX on same machine.
j2ee server has suddenly stopped with exit code -1331.sdm and dispatcher are working fine.
Please help..!
here is the default trace file
#1.5#000C29352CBB001400000149000008C400042E8904DE861B#1177065933781#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#sap.com/irj#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#Guest#192####59a32750edc011dbbdea000c29352cbb#Thread[ThreadPool.Worker7,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Pull packages failed - java.io.IOException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri: Connection refused: connect
at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:194)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
at java.lang.Thread.run(Thread.java:534)
#1.5#000C29352CBB00E600000000000008C400042E89108312C3#1177066129093#com.tssap.dtr.server.deltav.nameres.impl.SecureStoreNameServerConfig#sap.com/tcdtrenterpriseapp#com.tssap.dtr.server.deltav.nameres.impl.SecureStoreNameServerConfig#Guest#192####b885af50ef2c11dbcb71000c29352cbb#Thread[Scheduler_com.tssap.dtr.server.deltav.nameres.ProcessNameReservationsTask\#176_workerThread\#0,1,Scheduler_com.tssap.dtr.server.deltav.nameres.ProcessNameReservationsTask\#176]##0#0#Warning#1#/dtr/nameres#Java###error while retrieving data from secure-store
[EXCEPTION]
#1#com.sap.security.core.server.securestorage.exception.ObjectRetrievalException: Could not find clientID sapcomtcdtrenterpriseapp
at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.getClientsStorageLocation(RemoteSecureStorageClientContextImpl.java:231)
at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.retrieveObject(RemoteSecureStorageClientContextImpl.java:724)
at com.tssap.dtr.server.deltav.nameres.impl.SecureStoreNameServerConfig.loadConfiguration(SecureStoreNameServerConfig.java:54)
at com.tssap.dtr.server.deltav.nameres.impl.NameReservationManager.loadNameServerConfiguration(NameReservationManager.java:162)
at com.tssap.dtr.server.deltav.nameres.impl.NameReservationManager.processQueue(NameReservationManager.java:231)
at com.tssap.dtr.server.deltav.nameres.ProcessNameReservationsTask._run(ProcessNameReservationsTask.java:35)
at com.tssap.dtr.pvc.basics.transaction.AbstractSessionBoundTask.run(AbstractSessionBoundTask.java:37)
at com.tssap.dtr.pvc.util.scheduler.Invocation$Worker.run(Invocation.java:130)
at java.lang.Thread.run(Thread.java:534)
#1.5#000C29352CBB00140000014A000008C400042E8916B567FD#1177066233031#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#sap.com/irj#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#Guest#192####59a32750edc011dbbdea000c29352cbb#Thread[ThreadPool.Worker7,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Cannot contact ICE server - com.sapportals.wcm.WcmException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri: Connection refused: connect
at com.sapportals.wcm.util.http.slim.SlimRequester.doPerform(SlimRequester.java:608)
at com.sapportals.wcm.util.http.slim.SlimRequester.perform(SlimRequester.java:257)
at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:164)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
at java.lang.Thread.run(Thread.java:534)
#1.5#000C29352CBB00140000014B000008C400042E8916B570EB#1177066233031#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#sap.com/irj#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#Guest#192####59a32750edc011dbbdea000c29352cbb#Thread[ThreadPool.Worker7,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Pull packages failed - java.io.IOException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri: Connection refused: connect
at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:194)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
at java.lang.Thread.run(Thread.java:534)
#1.5#000C29352CBB000D0000001F000008C400042E8919E67A90#1177066286578#com.sap.portal.jsp#sap.com/irj#com.sap.portal.jsp#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_38##0#0#Warning#1#/System/Server#Java###null
[EXCEPTION]
#1#java.lang.NullPointerException
at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#000C29352CBB000D00000020000008C400042E8919E696EC#1177066286578#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_38##0#0#Error#1#/System/Server#Java###Exception ID:06:51_20/04/07_0132_8358550
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
Component : UserManagement.UserManagementMain
Component class : com.xyz.usermanagement.core.UserManagementMain
User : ncarste
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Original exception:
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:51)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
... 36 more
Caused by: java.lang.NullPointerException
at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
... 41 more
#1.5#000C29352CBB00180000000F000008C400042E891F950BA4#1177066381890#com.sap.portal.jsp#sap.com/irj#com.sap.portal.jsp#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_34##0#0#Warning#1#/System/Server#Java###null
[EXCEPTION]
#1#java.lang.NullPointerException
at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#000C29352CBB001800000010000008C400042E891F951BEF#1177066381890#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/Server#Java###Exception ID:06:53_20/04/07_0133_8358550
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
Component : UserManagement.UserManagementMain
Component class : com.xyz.usermanagement.core.UserManagementMain
User : ncarste
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Original exception:
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:51)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
... 36 more
Caused by: java.lang.NullPointerException
at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
... 41 more
#1.5#000C29352CBB001100000198000008C400042E892504640C#1177066473062#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#sap.com/irj#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#Guest#192####a71f1491edbf11dba7d1000c29352cbb#Thread[ThreadPool.Worker8,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Cannot contact ICE server - com.sapportals.wcm.WcmException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri: Connection refused: connect
at com.sapportals.wcm.util.http.slim.SlimRequester.doPerform(SlimRequester.java:608)
at com.sapportals.wcm.util.http.slim.SlimRequester.perform(SlimRequester.java:257)
at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:164)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
at java.lang.Thread.run(Thread.java:534)
#1.5#000C29352CBB001100000199000008C400042E892504642F#1177066473062#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#sap.com/irj#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#Guest#192####a71f1491edbf11dba7d1000c29352cbb#Thread[ThreadPool.Worker8,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Pull packages failed - java.io.IOException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri: Connection refused: connect
at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:194)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
at java.lang.Thread.run(Thread.java:534)
#1.5#000C29352CBB00110000019A000008C400042E89289DD7BB#1177066533437#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#sap.com/irj#com.sapportals.wcm.service.ice.wcm.ICEHttpConnection#Guest#192####a71f1491edbf11dba7d1000c29352cbb#Thread[ThreadPool.Worker8,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Cannot contact ICE server - com.sapportals.wcm.WcmException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri: Connection refused: connect
at com.sapportals.wcm.util.http.slim.SlimRequester.doPerform(SlimRequester.java:608)
at com.sapportals.wcm.util.http.slim.SlimRequester.perform(SlimRequester.java:257)
at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:164)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
at java.lang.Thread.run(Thread.java:534)
#1.5#000C29352CBB00110000019B000008C400042E89289DDB04#1177066533437#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#sap.com/irj#com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber#Guest#192####a71f1491edbf11dba7d1000c29352cbb#Thread[ThreadPool.Worker8,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Pull packages failed - java.io.IOException: sending request to: http://172.19.177.47:50001/irj/servlet/prt/portal/prtroot/com.sap.km.cm.ice request uri: Connection refused: connect
at com.sapportals.wcm.service.ice.wcm.ICEHttpConnection.getOutput(ICEHttpConnection.java:194)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.pullPackage(ICESubscriber.java:150)
at com.sapportals.wcm.service.ice.wcm.subscriber.ICESubscriber.run(ICESubscriber.java:101)
at com.sapportals.wcm.service.scheduler.SchedulerEntry.run(SchedulerEntry.java:171)
at com.sapportals.wcm.service.scheduler.crt.PoolWorker.run(PoolWorker.java:107)
at java.lang.Thread.run(Thread.java:534)
#1.5#000C29352CBB003000000028000008C400042E892CEAA96A#1177066605437#com.sap.portal.jsp#sap.com/irj#com.sap.portal.jsp#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_6##0#0#Warning#1#/System/Server#Java###null
[EXCEPTION]
#1#java.lang.NullPointerException
at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#000C29352CBB003000000029000008C400042E892CEAC648#1177066605562#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_6##0#0#Error#1#/System/Server#Java###Exception ID:06:56_20/04/07_0134_8358550
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
Component : UserManagement.UserManagementMain
Component class : com.xyz.usermanagement.core.UserManagementMain
User : ncarste
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Original exception:
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:51)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
... 36 more
Caused by: java.lang.NullPointerException
at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:270)
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
... 41 more
#1.5#000C29352CBB001A00000028000008C400042E8934452A55#1177066728921#com.sap.portal.jsp#sap.com/irj#com.sap.portal.jsp#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_1##0#0#Warning#1#/System/Server#Java###null
[EXCEPTION]
#1#java.lang.NullPointerException
at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:119)
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#000C29352CBB001A00000029000008C400042E8934453D75#1177066728921#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#ncarste#16318##EP6SR1.holnam.com_DV1_8358550#ncarste#4be48ab0ef2c11db836b000c29352cbb#SAPEngine_Application_Thread[impl:3]_1##0#0#Error#1#/System/Server#Java###Exception ID:06:58_20/04/07_0135_8358550
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
Component : UserManagement.UserManagementMain
Component class : com.xyz.usermanagement.core.UserManagementMain
User : ncarste
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.xyz.usermanagement.core.UserManagementMain.doContent(UserManagementMain.java:118)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Original exception:
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:51)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
... 36 more
Caused by: java.lang.NullPointerException
at jsp._sapportalsjsp_AccountAdminView.subDoContent(_sapportalsjsp_AccountAdminView.java:119)
at jsp._sapportalsjsp_AccountAdminView.doContent(_sapportalsjsp_AccountAdminView.java:45)
... 41 more
Thanks
RockyHi Rocky,
1)Goto configtool directory and run confgitool.sh
<drive:\>\usr\sap\sid\JC<InstanceNumber>\J2EE\configtool\configtool.sh
2)Under Clustre Data -> Global Server Configuration -> Services -> com.sap.security.cor.ume.services
3)Now find the parameter - ume.persistence.data_source_configuration
And change to default value (The default - dataSourceConfiguration_database_only.xml)
4)Click on set and then apply the setting. Then restart the server.
Hope it will be helpful.
Thanks & regards
Arun Singh -
Server silently fails on messages with a huge To: header; any ideas?
Our incoming relay (sendmail) occasionally receives messages which were sent to many recipients
(sometimes it's spam, sometimes valid maillists to which our users have subscribed). The messages
in question have a To: header which is typically over 6kb in size and over 80 lines long (and since
several recipients with short names/addresses may be grouped on one line, there's about a hundred
recipients listed).
It fails trying to relay these messages to our backend Sun Messaging Server (6.3-6.0.3 x64), and it
fails silently. I am not definitely sure that this is SMS's flaw and not Sendmails; but perhaps someone
can shed light on the matter? :)
SMS's mail.log_current receives such entries (here xxx.xxx.xxx.100 is the relay, xxx.xxx.xxx.73
is the backend server):
04-Dec-2008 16:54:44.62 tcp_local + O TCP|xxx.xxx.xxx.73|25|xxx.xxx.xxx.100|33728 SMTP
04-Dec-2008 16:59:44.62 tcp_intranet ims-ms VE 0 [email protected] rfc822;[email protected] ouruser@ims-ms-daemon relay.domain.ru ([xxx.xxx.xxx.100]) '' Timeout after 5 minutes trying to read SMTP packet
04-Dec-2008 16:59:44.62 tcp_local + C TCP|xxx.xxx.xxx.73|25|xxx.xxx.xxx.100|33728 SMTP Timeout
after 5 minutes trying to read SMTP packetSendmail logs a broken connection:
Dec 4 17:01:27 relay sendmail[14689]: [ID 801593 mail.crit] mB47gCN4014672: SYSERR(root): timeout writing message to sunmail.domain.ru.: Broken pipe
Dec 4 17:01:27 relay sendmail[14689]: [ID 801593 mail.info] mB47gCN4014672: to=<[email protected]>, delay=00:07:01, xdelay=00:06:58, mailer=esmtp, pri=329059, relay=sunmail.domain.ru. [xxx.xxx.xxx.73], dsn=4.0.0, stat=DeferredSniffing the wire gives strange results: The SMTP dialog part seems okay, the message is submitted
(relayed) only for our local user's address. But the message is not transferred until sendmail dies.
When the sendmail process dies (due to timeout or by a manual kill), about 3 packets appear in the
sniffer's output, starting with the usual "Received: from" lines and other header parts. The last packet
has text from the middle of the To: header, often breaking mid-word. Perhaps it's some buffering error
in either the sending Sendmail or the receiving Sunmail, or some server TCP-networking/sniffer glitch.
If I manually edit the queue file (/var/spool/mqueue/qfmB47gCN4014672 for the sample above) and delete
most of the To: header's lines, the message goes through okay.
This just does not seem logical - the message header text seems to be compliant (that is, each single
line is short, although all sub-lines of To: concatenate to a rather large text; but not that extremely large).
Neither sendmail nor sun mail report any error except networking socket failure.
MTUs are the same on both servers (1500), and any other large message (i.e. with attachments),
relays okay.
Are there any known issues on Sun Messaging Server (or Sendmail for that matter) which look like
this and ring a bell to a casual reader? :) Perhaps Sieve filters, etc.?
Since sendmail does successfully receive this message from the internet, and none of our several
incoming milters break along the way, I don't think it should have a huge problem forwarding it to
another server (I'll try experimenting though). This is why I think it's possible that Sun mail may be
at fault.
# imsimta version
Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 64bit)
libimta.so 6.3-6.03 (built 17:15:08, Mar 14 2008; 64bit)
SunOS sunmail 5.10 Generic_127112-07 i86pc i386 i86pcHello all, thanks for your suggestions.
In short, I debugged with Shane's suggestions. Apparently, tcp_smtp_server didn't get
a byte for 5 minutes so the read() was locked. At least, there's no specific failing routine
in Sunmail, so I'm back to research about Sendmail and networking, buffering and so on.
As I mentioned, when relay's sendmail process is killed, the system spits out about 3
packets of header data to the network...
Details follow...
By "silently failing" i meant that no obvious SMTP error is issued. The connection hangs
until it's aborted and both servers only complain on that - a failed network connection.
The resulting problem is that the sendmail relay marks sunmail as "Deferring connections"
in its hoststatus table, and valid messages are not even attempted for submission. At the
moment we fixed that brutally but effectively - by removing the hoststatus file for our sunmail
via cron every minute.
Concerning Mark's post, these servers are in the same DMZ, on a Cisco 2960G switch
which caused no specific problems. I mentioned MTU's are the same and standard,
because a few weeks back we did have LDAP replication problems due to experiments
with Jumbo frames, but solved them internally (I posted on this in the DSEE forum, also
asking how to compare LDAPs: [http://forums.sun.com/thread.jspa?threadID=5349017]).
We use this tandem of relay-backend servers for half a year now (and before we deployed
Sun Messaging Server, this sendmail relayed mails to our old server for many years).
So far this (large To:) is the only type of messages I see that cause such behavior; for
any other large mails the size does not matter, or at least some rejection explanation
is generated by one of the SMTP engines.
Shane, thanks for your help over and over ;)
I tried enabling the options you mentioned, ran "imsimta cnbuild" and reloaded the services.
Then I fired up the sniffer on the relay server, "tail -f mail.log_current" on the sunmail, and
submitted a "bad message" from the Sendmail queue.
In the sniffer the SMTP dialog went ok until submission of message data, where it hung as
before:
# ngrep "" tcp port 25 and host sunmail
T xxx.xxx.xxx.73:25 -> xxx.xxx.xxx.100:53200 [AP]
220 sunmail.domain.ru -- Server ESMTP (Sun Java(tm) System Messaging Server 6.
3-6.03 (built Mar 14 2008; 64bit))..
T xxx.xxx.xxx.100:53200 -> xxx.xxx.xxx.73:25 [AP]
EHLO relay.domain.ru..
T xxx.xxx.xxx.73:25 -> xxx.xxx.xxx.100:53200 [AP]
250-sunmail.domain.ru..250-8BITMIME..250-PIPELINING..250-CHUNKING..250-DSN..25
0-ENHANCEDSTATUSCODES..250-EXPN..250-HELP..250-XADR..250-XSTA..250-XCIR..25
0-XGEN..250-XLOOP 4A70E733A15FFE33EF3564BD522B1348..250-STARTTLS..250-ETRN.
.250-NO-SOLICITING..250 SIZE 20992000..
T xxx.xxx.xxx.100:53200 -> xxx.xxx.xxx.73:25 [AP]
MAIL From:<[email protected]> SIZE=200312..
T xxx.xxx.xxx.73:25 -> xxx.xxx.xxx.100:53200 [AP]
250 2.5.0 Address and options OK...
T xxx.xxx.xxx.100:53200 -> xxx.xxx.xxx.73:25 [AP]
RCPT To:<[email protected]> NOTIFY=SUCCESS,FAILURE,DELAY..DATA..
T xxx.xxx.xxx.73:25 -> xxx.xxx.xxx.100:53200 [AP]
250 2.1.5 [email protected] and options OK...
T xxx.xxx.xxx.73:25 -> xxx.xxx.xxx.100:53200 [AP]
354 Enter mail, end with a single "."...
#In the mail.log_current just one line appeared:
05-Dec-2008 10:51:18.46 tcp_local + O TCP|xxx.xxx.xxx.73|25|xxx.xxx.xxx.100|53200 SMTPSince it also mentions tcp_local channel, I decided to enable slave_debug on that as well.
Rebuilt the configs, and ran msg-stop to see if the processes actually die. When I checked
the "netstat -an | grep -w 25" and "ps -ef" outputs, there was indeed a tcp_smtp_server
process running:
mailsrv 23594 656 0 10:50:08 ? 0:00 /opt/SUNWmsgsr/messaging64/lib/tcp_smtp_serverBoth the sunmail and sendmail relay kept the socket ESTABLISHED. I took a pstack
of the tcp_smtp_server (below) and killed it with SIGSEGV so I have a core dump if
needed. Then I started the services and submitted the message from the queue again.
The SMTP dialog log was actually from tcp_local, and it ended with the lines like these
(note that even in this detailed log it just died with "network read failed" after 5 minutes,
I inserted an empty line to make it more visible):
11:21:18.26: Good address count 1 defer count 0
11:21:18.26: Copy estimate after address addition is 2
11:21:18.26: mmc_rrply: Return detailed status information.
11:21:18.26: mmc_rrply: Returning
11:21:18.26: Sending : "250 2.1.5 [email protected] and options OK."
11:21:18.26: Received : "DATA"
11:21:18.26: mmc_waend(0x00749cc0) called.
11:21:18.26: Copy estimate is 2
11:21:18.26: Queue area size 35152252, temp area size 2785988
11:21:18.26: 8788063 blocks of effective free queue space available; setting disk limit accordingly.
11:21:18.26: 1392994 blocks of free temporary space available; setting disk limit accordingly.
11:21:18.26: Sending : "354 Enter mail, end with a single "."."
11:26:18.27: os_smtp_read: [9] network read failed with error 145
11:26:18.27: Error: Connection timed out
11:26:18.27: Generating V records for all addresses on channel ims-ms .
11:26:18.27: mmc_flatten_address: Flattening address tree into a list.
11:26:18.27: Tree prior to flattening:
11:26:18.27: Level/Node/Left/Right Address
11:26:18.27: 0/0x0072ea30/0x00000000/0x00866050
11:26:18.27: 1/0x00866050/0x00751ef8/0x00751ef8 ouruser@ims-ms-daemon
11:26:18.27: Zero address: 0x00751ef8
11:26:18.27: smtpc_enqueue returning a status of 137 (Timeout)
11:26:18.27: SMTP routine failure from SMTPC_ENQUEUE
11:26:18.27: pmt_close: [9] status 0Apparently, tcp_smtp_server didn't get a byte for 5 minutes so a read() call was locked
and perhaps this is what didn't allow stop-msg to kill this process...
At least, there's no specific failing routine in Sunmail, so I'm back to research about
Sendmail and networking, buffering and so on. As I mentioned, when relay's sendmail
process is killed, the system spits out about 3 packets of header data to the network...
The pstack output for a waiting tcp_smtp_server process follows, for completeness sake:
23594: /opt/SUNWmsgsr/messaging64/lib/tcp_smtp_server
----------------- lwp# 1 / thread# 1 --------------------
fffffd7ffd830007 lwp_park (0, 0, 0)
fffffd7ffd829c14 cond_wait_queue () + 44
fffffd7ffd82a1a9 _cond_wait () + 59
fffffd7ffd82a1d6 cond_wait () + 26
fffffd7ffd82a219 pthread_cond_wait () + 9
fffffd7ffededf3e dispatcher_initialize () + 66e
0000000000404078 main () + 768
00000000004036fc ???????? ()
----------------- lwp# 2 / thread# 2 --------------------
fffffd7ffd830007 lwp_park (0, fffffd7ffc5fdda0, 0)
fffffd7ffd829c14 cond_wait_queue () + 44
fffffd7ffd82a012 cond_wait_common () + 1c2
fffffd7ffd82a286 _cond_timedwait () + 56
fffffd7ffd82a310 cond_timedwait () + 30
fffffd7ffd82a359 pthread_cond_timedwait () + 9
fffffd7ffd520ff4 PR_WaitCondVar () + 264
fffffd7ffd529854 PR_Sleep () + 74
fffffd7ffd62d5d8 LockPoller () + 88
fffffd7ffd5289e7 _pt_root () + f7
fffffd7ffd82fd5b _thr_setup () + 5b
fffffd7ffd82ff90 _lwp_start ()
----------------- lwp# 3 / thread# 3 --------------------
fffffd7ffd830007 lwp_park (0, fffffd7ffc3fdda0, 0)
fffffd7ffd829c14 cond_wait_queue () + 44
fffffd7ffd82a012 cond_wait_common () + 1c2
fffffd7ffd82a286 _cond_timedwait () + 56
fffffd7ffd82a310 cond_timedwait () + 30
fffffd7ffd82a359 pthread_cond_timedwait () + 9
fffffd7ffd520ff4 PR_WaitCondVar () + 264
fffffd7ffd529854 PR_Sleep () + 74
fffffd7ffd62d5d8 LockPoller () + 88
fffffd7ffd5289e7 _pt_root () + f7
fffffd7ffd82fd5b _thr_setup () + 5b
fffffd7ffd82ff90 _lwp_start ()
----------------- lwp# 4 / thread# 4 --------------------
fffffd7ffd830007 lwp_park (0, 0, 0)
fffffd7ffd829c14 cond_wait_queue () + 44
fffffd7ffd82a1a9 _cond_wait () + 59
fffffd7ffd82a1d6 cond_wait () + 26
fffffd7ffd82a219 pthread_cond_wait () + 9
fffffd7ffedf5fe8 pmt_refresh_stats () + d8
fffffd7ffd82fd5b _thr_setup () + 5b
fffffd7ffd82ff90 _lwp_start ()
----------------- lwp# 5 / thread# 5 --------------------
fffffd7ffedecf10 dispatcher_read(), exit value = 0x0000000000000000
** zombie (exited, not detached, not yet joined) **
----------------- lwp# 6 / thread# 6 --------------------
fffffd7ffd830007 lwp_park (0, fffffd7ffc1fded0, 0)
fffffd7ffd829c14 cond_wait_queue () + 44
fffffd7ffd82a012 cond_wait_common () + 1c2
fffffd7ffd82a286 _cond_timedwait () + 56
fffffd7ffd82a310 cond_timedwait () + 30
fffffd7ffd82a359 pthread_cond_timedwait () + 9
fffffd7ffeded829 dispatcher_housekeeping () + 1e9
fffffd7ffd82fd5b _thr_setup () + 5b
fffffd7ffd82ff90 _lwp_start ()
----------------- lwp# 14 / thread# 14 --------------------
fffffd7ffd83319a lwp_wait (d, fffffd7ffbdfdf24)
fffffd7ffd82c9de _thrp_join () + 3e
fffffd7ffd82cbbc pthread_join () + 1c
fffffd7ffedece66 dispatcher_joiner () + 36
fffffd7ffd82fd5b _thr_setup () + 5b
fffffd7ffd82ff90 _lwp_start ()
----------------- lwp# 13 / thread# 13 --------------------
fffffd7ffd832caa pollsys (fffffd7ffc1b9860, 1, fffffd7ffc1b97a0, 0)
fffffd7ffd7d9dc2 poll () + 52
fffffd7ffee6d7e8 pmt_recvfrom () + 868
0000000000405a3f os_smtp_read () + 1ff
0000000000404e3d smtp_get () + 9d
fffffd7ffec0fda7 big_smtp_read () + 797
fffffd7ffec36798 data () + a28
fffffd7ffec460ad smtpc_enqueue () + f9d
0000000000405343 tcp_smtp_slave () + 223
00000000004038a4 tcp_smtp_slave_pre () + 54
fffffd7ffedeccbc dispatcher_newtcp () + 46c
fffffd7ffd82fd5b _thr_setup () + 5b
fffffd7ffd82ff90 _lwp_start () -
Hi,
I have a windows 2008 R2 Enterprise servers with standalone MS-SQL 2008 R2 named instance. The server is having two networks, once production and the second for backup. The server FQDN is resolving to the production IP. The backup NIC
DNS dynamic update is disabled and an "A" record is registered with the dns. While trying to connect to the instance using the management studio:
Successfuly able to connect using the instance name, the production hostname, production IP and backup IP.
but while trying to connect to the insance using the backup hostname getting the below error:
"Login failed. The login is an untrusted domain and cannot be used with windows authentication. (Microsoft SQL server, Error: 18452) "
This is required for the backup tool to get connected using the backup FQDN of the server.
Should I need to create a host name alias, request you to kindly assist me with the best recommedation to fix this.
http://blogs.msdn.com/b/dbrowne/archive/2012/05/21/how-to-add-a-hostname-alias-for-a-sql-server-instance.aspxHi,
It might be a kerberos issue. Check that there are valid SPN's registered using the setspn utility - http://technet.microsoft.com/en-us/library/cc731241.aspx
Thanks, Andrew
My blog... -
If the Adobe Access Reference Implementation License Server throws a 300 error code, the most likely issue is that the evaluation of the Adobe Access DRM policy failed during license issuance, and that the license server refused to issue a license.
For example, if the policy specifies an end date that was in the past, the license server will see that the current time is beyond the validity date specified in the policy and reject the license request, recording an error code 300 in the Adobe Access license server's logfile.
cheers,
/Eric.I can't believe there is no answer to this question.
after all day researching I've given up google and went back to basics
OS X Server essentials book....
and I found it ...
So in Server.app left panel top... click on your server name and than Settings tab in the right one.
make sure that Enable Apple push notifications are ticked
Tha... tha... thats all folks -
Web server refuses connections - Service exited with abnormal code: 1
I have upgraded to yosemite 10.10.1, my web server refuses to allow connections and I get - Service exited with abnormal code: 1, in the log file. I have reloaded server software and I have rebooted and power restarted my Mac Mini many times
Fixed this stupid iTunes issue with the following procedure. YMMV
- Open the Activity Monitor (LaunchPad, Other, Activity Monitor)
- Force Quit the iTunes Helper app (I had multiply ones running, so quit them all)
- Install the iTunes .pkg from the Apple website.
- Force Quit the iTunes Helper again after install
- Shut Down the MacBook
- Start again (watch for the progress bar, that’s the fix for permissions working)
- Start iTunes
You mileage may vary, but it worked for me. -
Migrate CA to Server with Different Name? What is the CA really for?
So I'm reading and following along in this article:
http://technet.microsoft.com/en-us/library/ee126170(WS.10).aspx
Though I should have read through the whole thing first. Yes I want to Migrate the CA from Server A to Server B, but I dont want to Change the name of Server B to Server A!
I want Server B to have its New Name, though the article above is for Migrating to a Server that will have the Same Name as the old server. )-:
I'm not really sure what the CA is for. Seems like we had one in Win2003, and then when that Server Died and we had no Backup I just installed a new CA on a 2008 R2 server. It only has like 20 Certs issues, most of which Expired and have IUSR for the
Common Name. I think I might of used it once for A Cert for Testing HTTPS on a Dev Server....
Thanks,
Scott<-Maybe I'm not clear.
My Original Plan was to Move a CA to a New Server with a New Name. I backed-up the Old CA. Uninstalled it. Read the Directions, and Duh, I cannot CHange its Name.
After Reinstalling the OLD CA and restoring the Backup, It was Fully Functional. The Old Certs were back. I installed a NEW CA server in Parallel with the OLD CA Server reinstall. Then Moments later EVERY connected PC on the Network seemed
to request a Certificate from the a CA Server, though most Requested it from the OLD CA.
None of these PCs had a Certificate from Either CA Prior to the reinstall oflthe OLD/install of the new.
I have removed the Cert Templates from the OLD CA.
The OLD CA had 40+ Clients with Certs Issued. Most are "Computer (Machine)" and some are "Domain Controller Authentication" and some are Directory Email Replication"
How do I tell (either via GPO or login script or?) these clients that they need to request another Cert from the new CA. The Certs that were Issued on the OLD CA were not manually Requested. The PCs themselves or AD initiated the request.
Thanks, -
I'll be in a forum on a website and be fine for like 2 minutes then it will boot me and give that error.
Did you check your security software (firewall)?
A possible cause is security software (firewall) that blocks or restricts Firefox or the plugin-container process without informing you, possibly after detecting changes (update) to the Firefox program.
Remove all rules for Firefox from the permissions list in the firewall and let your firewall ask again for permission to get full unrestricted access to internet for Firefox and the plugin-container process.
See:
* [[Server not found]]
* [[Firewalls]]
Maybe you are looking for
-
IDOC/BAPI for Production order creation from Legacy system
Hi all We are using an interface to create Production orders from legacy to SAP. Would you recommend an IDOC or a BAPI to create Production orders. If IDOC or BAPI then could you please mention which one? thanks a bunch
-
More than one account on same computer?
Can I have more than one account on the same computer? Each account would have its own iPod and library. Thanks, Kristy
-
How to install the Leander Script
I do not understand how to install the Leander Script that I received as a gfit with my purchase of Adobe. The instructors say navigate to the folder where the fonts are. Then it says to select the fonts. I do not see how to select the fonts, then
-
About inventory opening balance & closing balance
hi all, i want to opening balace and closing balance date wise in my query. how to do it? regards, chetan.
-
Calculation when viewing report
Hi, Basically, all I need to do is to run the following statement whenever I view the report which is based on the BAU_HEAD_COUNT table. I tried using a trigger but didn't work because the table is mutating. I'm wondering if I can use one of the proc