If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Javae.net.BindException: Address in Use error

Started by sachin, 09 Jan 2006 12:49:52 PM

Previous topic - Next topic

sachin

In one of our scheduled report, this error caused the report to fail, any idea what happened to cause this error.

java.net.BindException: Address in use: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.Socket.<init>(Unknown Source) at java.net.Socket.<init>(Unknown Source) at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:129) at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:157) at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:114) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:180) at org.apache.axis.client.Call.invokeEngine(Call.java:2564) at org.apache.axis.client.Call.invoke(Call.java:2553) at org.apache.axis.client.Call.invoke(Call.java:2248) at org.apache.axis.client.Call.invoke(Call.java:2171) at org.apache.axis.client.Call.invoke(Call.java:1691) at com.cognos.developer.schemas.bibus._2.CognosReportNetBindingStub.wait(CognosReportNetBindingStub.java:6600) at noticecast.services.soap.sdk.SDKClientPort.wait(SDKClientPort.java:300) at noticecast.services.soap.sdk.AuthenticatingSDKClientPort.wait(AuthenticatingSDKClientPort.java:117) at com.cognos.sds.job.JobStepNode$1.run(JobStepNode.java:103) at java.lang.Thread.run(Unknown Source)


Thanks a lot
sachin

MrO

That's not a CRN error, but a webserver (prolly Tomcat) error. It means that 2 instances are trying to use the same port (eg. 80 or 8080). Most likley it's because one instance has shutdown improperly (without releasing the address), then a second one started but could not bind to this address. You should check your webserver logs to see what went wrong to prevent this form happening in the future.

Gz

sachin

MrO,

I checked my Tomcat Logs and I see an error which appaers everytime CRN server is re-started. It says -

Initializing Coyote HTTP/1.1 on port 9300: 11 Jan 2006 06:27:01,787
ERROR [main] org.apache.commons.digester.Digester - Parse Error at line 140 column 11: The content of element type "web-app" must match "(icon?,display-name?,description?,distributable?,context-param*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*)".: 11 Jan 2006 06:27:02,177
org.xml.sax.SAXParseException: The content of element type "web-app" must match "(icon?,display-name?,description?,distributable?,context-param*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*)".
   at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
-----

so I believe as you said the error is due to Tomcat. Well, when i searched the web i understood that the cognos Web.xml file in WEB-INF folder under Web-apps->p2pd is not being parsed by Digester (parsing tool) in tomcat. Didnt know exactly what to do to resolve this, any idea.

Thanks
Sachin