I have been trying to extract the data from DB and export the attachment through email.
But, I am getting the error below while trying:
[statistics] connecting to socket on port 3477
[statistics] connected
Exception in component tSendMail_1 (ABC)
javax.mail.AuthenticationFailedException: failed to connect
at javax.mail.Service.connect(Service.java:322)
at javax.mail.Service.connect(Service.java:172)
at javax.mail.Service.connect(Service.java:121)
at javax.mail.Transport.send0(Transport.java:190)
at javax.mail.Transport.send(Transport.java:120)
at local_project.ABC_2_0.ABC.tSendMail_1Process(ABC.java:1186)
at local_project.ABC_2_0.ABC.tDBInput_2Process(ABC.java:924)
at local_project.ABC_2_0.ABC.runJobInTOS(ABC.java:1467)
at local_project.ABC_2_0.ABC.main(ABC.java:1318)
[statistics] disconnected
Job ABC ended at 14:46 11/08/2018. [exit code=1]
Could someone help me here?
Please check whether the port no 3477 is open for sending mail.And try the same again
Can someone help me with this SailsJs error
Running "less:dev" (less) task
verbose: Lowering sails...
verbose: Sent kill signal to child process (26729)...
../staging.platform/node_modules/sails-disk/lib/adapter.js:80
grabConnection(conn).dropCollection(coll, relations, cb);
^
TypeError: Cannot read property 'dropCollection' of undefined
at Object.drop (../staging.platform/node_modules/sails-disk/lib/adapter.js:80:27)
at module.exports.drop (../staging.platform/node_modules/waterline/lib/waterline/adapter/ddl/index.js:110:13)
at afterAsyncEach (../staging.platform/node_modules/waterline/lib/waterline/adapter/sync/strategies/alter.js:190:14)
at ../staging.platform/node_modules/async/lib/async.js:52:16
at Object.async.forEachOf.async.eachOf (../staging.platform/node_modules/async/lib/async.js:236:30)
at Object.async.forEach.async.each (../staging.platform/node_modules/async/lib/async.js:209:22)
at ../staging.platform/node_modules/waterline/lib/waterline/adapter/sync/strategies/alter.js:134:13
at wrapper (../staging.platform/node_modules/waterline/node_modules/lodash/index.js:3592:19)
at applyInOriginalCtx (../staging.platform/node_modules/waterline/lib/waterline/utils/normalize.js:421:80)
at wrappedCallback (../staging.platform/node_modules/waterline/lib/waterline/utils/normalize.js:324:18)
at success (../staging.platform/node_modules/waterline/node_modules/switchback/lib/normalize.js:33:31)
at _switch (../staging.platform/node_modules/waterline/node_modules/switchback/lib/factory.js:58:28)
at ../staging.platform/node_modules/sails-disk/lib/adapter.js:88:19
at Timeout._onTimeout (../staging.platform/node_modules/sails-disk/lib/adapter.js:179:10)
at ontimeout (timers.js:365:14)
at tryOnTimeout (timers.js:237:5)
at Timer.listOnTimeout (timers.js:207:5)
The problem I am having is, this error popped up without real cause. On my local machine my Sails App works - however, on my sandbox remote server, I just started getting the error...
I am completely at a lost...
I have a server on which I have installed Jira application. Now we have changed the IP schema and since then I am not able to access Jira. In catalina.out log I have found below error
2016-04-18 13:12:55,958 localhost-startStop-1 ERROR [o.o.c.entity.jdbc.DatabaseUtil] Unable to establish a connection with the database... Error was:org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
2016-04-18 13:12:55,959 localhost-startStop-1 ERROR [o.o.c.entity.jdbc.DatabaseUtil] Could not get table name information from the database, aborting.
2016-04-18 13:12:55,982 localhost-startStop-1 ERROR [NoModule] Error getting datasource via DBCP: JdbcDatasourceInfo{uri='jdbc:postgresql://192.168.1.228:5432/jira', driverClassName='org.postgresql.Driver', username='super', password='********', isolationLevel='null', connectionProperties=null, connectionPoolInfo=ConnectionPoolInfo{maxSize=20, minSize=20, initialSize=null, maxIdle=20, maxWait=30000, sleepTime=300000, lifeTime=600000, deadLockMaxWait=600000, deadLockRetryWait=10000, validationQuery=null, minEvictableTimeMillis=null, timeBetweenEvictionRunsMillis=null, poolPreparedStatements=null, testOnBorrow=null, testOnReturn=null, testWhileIdle=null, maxOpenPreparedStatements=null, numTestsPerEvictionRun=null, removeAbandonedTimeout=300, validationQueryTimeout=null, defaultCatalog=null}}
java.lang.RuntimeException: javax.management.InstanceAlreadyExistsException: com.atlassian.jira:name=BasicDataSource
Any idea where and how to change that IP?
I go into /opt/atlassian/jira/bin folder and run ./config.sh
There I entered proper details and then save the config.
This time dbconfig.xml file generated in /var/atlassian/application-data/jira/ folder.
And my issue resolved.
I have a application which will receive files from FTP and uploaded in to Mainframe server.
I am getting a "Socket error 10053 software caused connection abort" when I assign
FTPTransfertype = ftASCII
If I change this to FtBinary I'm not getting this error but data not uploaded properly in this mode.
I am getting this error only in application server (Production server) not in the development server (here I faced this issue only once in the FTPTransfertype = ftASCII assignment)
I have changed the FTP connectivity mode to Passive but its not working..
Please help me on this.
I recomment to see Microsoft Windows Socket Errors page:
https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx
In your case:
Software caused connection abort. An established connection was
aborted by the software in your host computer, possibly due to a data
transmission time-out or protocol error.
After starting the run/debug configuration begins build and deploy application. All goes well. The only thing that provides continuously JBoss Log SocketException:
2012-07-16 12:43:30,424 DEBUG [org.jboss.naming.Naming] Error writing response to /127.0.0.1 java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1847) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1756) at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1257) at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1211) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1395) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1547) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:333) at org.jnp.server.Main$BootstrapRequestHandler.run(Main.java:516) at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:148) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756) at java.lang.Thread.run(Thread.java:662)
At issues.jboss.org/browse/JBAS-3417 offer a solution:
If you set server / etc / host with:
IP fqn name
where IP is in «Error writing response to / IP"
Ex:
... "Error writing response to / 10.1.0.1"
10.1.0.1 test.mydomain test
you resolve the problem
But I have something 127.0.0.1 localhost, it is already registered in the default c:\ Windows\system32\drivers\etc\hosts
In the Troubleshooting says:
You may notice something in the JBoss logs similar to the following:
2009-01-28 08:36:57,381 DEBUG
[org.jboss.naming.NamingService]
Error writing response to / 127.0.0.1 <[http://127.0.0.1]>
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0 (Native Method)
This is most likely an anomalous and benign «problem». That is, it should not affect the operation of any applications deployed to JBoss.
If this does not affect deployed application can be any way to hide it? And then the continuous output overshadows the other posts and eats memory.